| Versions |
  |
|
| Author |
 Topic  |
|
saimhe
Lithuania
123 Posts |
 Posted - 03 août 2007 : 15:59:42
|
| By the way, is the version string "GDSW3.2.4_3.1.00.12-SDK003P1.00a" the same both via binary and NMEA protocols? There have already been reports (e.g., in this thread) that one of versions provided by the chip is unrealistically high. |
 |
|
|
aaronprez
USA
21 Posts |
Posted - 03 août 2007 : 20:13:57
|
| tsp, if you could work on getting that 3.2.4 firmware out to us, that would be fantastic. Please keep us updated. If you can't figure out how to do it using Sirflash after going through the links let us know and maybe we could help. |
Edited by - aaronprez on 03 août 2007 20:14:59 |
|
|
|
cyberas
25 Posts |
|
|
Gix
3 Posts |
Posted - 04 août 2007 : 12:58:59
|
quote:
Originally posted by tsp
I could make it available If someone tells me how to dump it
Hi tsp, I may give some advices:
It is safe to use Bluetooth communication (assuming your Bluetooth PC interface is stable and working fine) with SiRFDemo or SiRFFlash but be careful to ALWAYS use 38400 baud. This means to NOT use in SiRFDemo the command form the menu "Switch to SiRF protocol" because this will drop your communication with the unit! To recover you'll have to discharge the backup battery by short-circuit or letting it without the main battery for several days...
The correct procedure using Bluetooth is:
- Pair the GPS with your PC, find the assigned COM port.
- Start SiRFDemo, choose the COM port and 38400 baud.
- click the green connect button and see if you have NMEA messages in the debug view.
- Switch to SiRF protocol by using Action/Transmit Serial message. Enter the message "PSRF100,0,38400,8,1,0" without quotes and choose NMEA.
- Now the unit will switch to SiRF and you'll see more messages in the windows.
- Now enter boot mode with your unit > Send again a serial message, this time choose SiRF and the message is "94"
- Now you can disconnect SiRFDemo and start SiRFFlash, configure it as shown above in the screen capture and read the flash in binary format.
- Close SiRFFlash, back to SiRFDemo, connect to the unit, then reset the unit by Action/Initialize Data Source/Factory Reset.
I hope everything will go fine! |
|
|
|
tsp
Denmark
4 Posts |
Posted - 04 août 2007 : 17:40:28
|
thanks all, will give it a try when I get back to my own computer with a bluetooth dongle(I don't have the data cable).
I'm allready aware of the danger of using SiRFDemo. I had to reset the device twice by discarging the backup battery before switching to sirfTech.
saimhe: The version string is gathered using the SiRF protocol. Do you know what NMEA command to send to get the firmware version?
Also I wonder if the version I have is the same as the Garmin update GSW3.2.4GARMIN_3.1.00.12-SDK001P1.01?
|
|
|
|
saimhe
Lithuania
123 Posts |
Posted - 05 août 2007 : 02:48:29
|
There is no such command. The version string is reported just after the receiver is powered up. For example (a different receiver):
$PSRFTXT,Version: 2.4.13.01-XTrac202-LD01*4D That means: assure that the receiver starts up in NMEA mode, and power it on while SiRFDemo or even a terminal emulator is running. That is the easiest way.
That bunch of PSRFTXT sentences should show up just after switching to NMEA, too -- if SiRFDemo immediately starts interpreting everything as NMEA (judging from a few recent logs, it sometimes fails and therefore at least one sentence is not displayed). |
Edited by - saimhe on 05 août 2007 21:55:11 |
|
|
|
tsp
Denmark
4 Posts |
Posted - 06 août 2007 : 18:52:45
|
saimhe: I can't get it to show the PSRFTXT sentence when switching back to NMEA using sirfdemo (and as I connect to it using bluetooth I can't see the startup message)
I extracted the firmware using the instruction by cyberas and gix. The file is available here: http://rapidshare.com/files/47341256/GDSW3.2.4_3.1.00.12-SDK003P1.zip.html
Remember it's extracted from a HOLUX GPSlim 236 REV:C 2006.03.16 (printed on the PCB). It will probably not work on a non holux gpslim 236 device
Use it at your own responsibility and don't blame me if your gps device explode :)
|
Edited by - tsp on 06 août 2007 18:53:59 |
|
|
|
aaronprez
USA
21 Posts |
Posted - 06 août 2007 : 19:12:01
|
| Thanks tsp, now the question begs, should this be attempted on revision B hardware? Anyone want to be a guinea pig? |
Edited by - aaronprez on 06 août 2007 19:27:48 |
|
|
|
Gix
3 Posts |
Posted - 06 août 2007 : 22:23:35
|
Well, I've done it. It's really fantastic... Thanks, tsp!
It seems SBAS and static navigation are enabled by default in this version (the correct string is GSW3.2.4_3.1.00.12-SDK003P1.00a). And the same FW version is also reported in NMEA mode. To see it just reset the unit and watch the debug view.
I don't have much time for testing but my impression is that SBAS is more stable.
I don't know the revision of my unit, but it is about one year old and initially was provided with 3.2.0 firmware.
|
Edited by - Gix on 06 août 2007 22:25:44 |
|
|
|
DeDragonSlayer
Poland
1 Posts |
Posted - 06 août 2007 : 22:29:56
|
Just uploaded it to a REV:B hardware, dated 2005.05.02 on the PCB. Original firmware was 3.1.1. At first glance version 3.2.4 seems to work just fine. So, I guess I'm the guinea pig now. :)
Big thanks to tsp for the new firmware!! |
Edited by - DeDragonSlayer on 06 août 2007 22:31:32 |
|
|
|
aaronprez
USA
21 Posts |
Posted - 06 août 2007 : 22:57:50
|
I did mine too, a revision B unit and now have 3.2.4 I don't notice anything really different, but like he said, static navigation was enabled by default. If anyone finds out if there is anything else different, please post. Doing some googling, I do notice comments about version 3.2.4 on various receivers using Sirfstar III chipsets:
"Simultaneously with the chip upgrade, the firmware of the iTrax300 receiver will be upgraded for several enhancements in navigation and robustness. With the new firmware version 3.2.4, navigation sensitivity will be improved to -158dBm and acquisition sensitivity to -143dBm."
"Latest update for SiRFstarIII based Garmin units: http://www.garmin.com/support/download_details.jsp?id=1629
contains: GSW3.2.4GARMIN_3.1.00.12-SDK001P1.01
dated: 11/03/2006
changelog:
Version 2.90:
1. Improved ephemeris collection under dynamics.
2. Additional SiRF maintenance improvements."
Actually I just noticed something. I put my hands over it to make it lose its fix on satellites, and even when it breaks its satellite fix in my software, the orange light keeps blinking rather than staying orange when it is trying to find a fix. |
Edited by - aaronprez on 06 août 2007 23:30:06 |
|
|
|
Allycat
United Kingdom
58 Posts |
Posted - 07 août 2007 : 21:56:43
|
Thanks all, and especially tsp,
I've also updated the firmware in my Rev:B, 2005/05/02 Holux 236 which I believe started with 3.1.0. Yes, it does seem to get good signals; I've already seen a differential fix (EGNOS PRN:120) and 11 active satellites from behind a south-facing window. The defaults do seem to be SN and EGNOS both ON, but this is a stupid combination and I'm not sure I trust SirfDemo.
However, I have had problems which have needed several battery-short-circuits to recover it from "never-never land". I've been using a serial cable, and this port now runs at 57600 baud, whereas previous versions have always worked ONLY at 38400 baud. But I have not yet managed to receive any recognisable data over the BlueTooth link at any baud rate (using SirfTech and GPSviewer,etc. on a PPC), although the device is definitely connecting and transmitting something. What baud rates are others finding and using?
In SirfFlash, I think I noticed the end address as 79999, but surely it should be 7FFFF? Finally, even with SN OFF, the NMEA sentences still don't report any non-zero speeds below about 3km/hr, as I've discussed here:
http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=82799
Cheers, Alan. |
|
|
|
Gix
3 Posts |
Posted - 08 août 2007 : 11:16:48
|
Hi Alan,
I'm using only Bluetooth and it is working at 38400 baud. What I have noticed (but not necesarily due to this new version) is that the PPC Bluetooth connection is not always reliable. It could help if you will not start GPS applications very soon one after another. I am used to watch the Bluetooth icon after I close a GPS application and see if the transfer is stopped and only after that I'm starting other application. And I'm not using the WM5 "shared" GPS feature because not all my programs are working with it.
Regarding the HEX addresses - they are automatically detected by the Flash program, so they should be correct :) |
|
|
|
Allycat
United Kingdom
58 Posts |
Posted - 08 août 2007 : 22:24:46
|
Thanks Gix. I've now discovered (part of) what's been happening:
Previous versions of the Holux firmware have operated the serial (cable) interface always at 38400 baud. However, v.3.2.4 seems to accept baud rate change commands, and the Sirfdemo "Action:Switch to Sirf Protocol" forces 57600 baud which "breaks" the Bluetooth communications. If I use "Action:Transmit serial message:NMEA:PSRF100,0,38400,8,1,0" then the BT works alright.
I'm not sure if it works at other rates than 38400 and 57600, but even this gives more ways to "kill" the communications. So, with this and the stupid enabling of SN, I may revert to the 3.2.2 firmware (or fit an externally accessible "factory reset" switch !)
The memory range is selected when the file is created, and it does seem to be the same size as previous versions (which we know do not fill the whole memory). But there is the risk that the firmware will get bigger, so it's worth watching the end address.
Today, I didn't see a differential fix, so EGNOS still seems to be very much in test mode.
Cheers, Alan. |
Edited by - Allycat on 08 août 2007 22:55:15 |
|
|
|
aaronprez
USA
21 Posts |
Posted - 09 août 2007 : 00:27:10
|
| I think there is an issue disabling static navigation with the 3.2.4 version. I disabled it using Sirfdemo, and it reports that it's disabled, but I can tell by its behavior that it's not disabled. Like if I were driving, and slammed on my breaks, it won't immediately drop down to zero MPH, there is a few second delay. I know it definitely behaves differently than with static navigation disabled on previous firmware. It might make me revert back to 3.2.2, because static navigation annoys me. |
Edited by - aaronprez on 09 août 2007 16:12:17 |
|
|
|
Topic |
|
|
|
| This page was generated in 0,69 seconds. |
 |
|
- 
del.icio.us
Firmware versions of SiRF based receivers
