|T O P I C R E V I E W
||Posted - 03 mai 2005 : 22:11:13
Firmware versions of SiRF based receivers
Updated 20071202 by GpsPasSion
- Latest version observed:
- SiRFstar IIe/LP - GSW (ST) - FW2.32 - Haicom BT405
- SiRFstar IIe/LP - Xtrac v2 - v2.1 - Pharos iGPS 360 and Becker Traffic Assist
- SiRFstar IIxt - Xtracv2 - v2.2.0 - Globalsat BT-328
- SiRFstar III - GSW - FW 3.2.4 (Globalsat BT-338, BT-359, various AIOs), FW 3.2.5 - Garmin nüvi, SP550, 60C(s)x version 3.00 (GSW3.2.5GARMIN_3.3.01.06-SDK001P1.0)
- SiRFstar III - GSC (single chip) - FW3.1.1/Globalsat BT-359, FW3.2.0/Holux GPSlim 240, FW3.2.1/Royaltek RBT-2110
- SiRFstar III with SiRFInstantFix AGPS - ST - v3.2 - Eten G500, Mio A701, HTC P3300, Eten X500
- SiRFstar III LT with SiRFInstantFix AGPS - v3.0 - Eten X800 (GSWLT3.0.0HT_3.1.01.00-SDKLT001P1.OOb_ETEN-20070119-NMEA57600_S_EE-LX)
- Latest version announced
- SiRFstar IIe/LP - ST - v2.3.3
- SiRFstar IIe/LP - Xtrac v2 - same
- SiRFstar III - ST - v3.2 - see below
- SiRFstar III with SiRFInstantFix AGPS - ST - v3.2 - details here
Posted by Carl@SiRF in another thread: "SiRF provides the new versions to our direct customers, but it is up to them to determine if they want to provide an update mechanism to their customers. While the process is relatively simple, unless there is a hardware way to put the receiver into flash upgrade mode (internal boot mode is our term) there is a chance to get things stuck so you have to send it back to the manufacturer or a repair depot to recover. Further, you must be supplied with a flash programming utility to do the job since you cannot access the flash directly -- you have to go through the ARM processor on the SiRF chipset."
How does the various parts of the SiRF firmware version strings relate to features, customer versions etc?
What to look for first to know which version is oldest/newest?
For example these ones:
Posted by Carl@SiRF in another thread:
"SiRF provides the new versions to our direct customers, but it is up to them to determine if they want to provide an update mechanism to their customers. While the process is relatively simple, unless there is a hardware way to put the receiver into flash upgrade mode (internal boot mode is our term) there is a chance to get things stuck so you have to send it back to the manufacturer or a repair depot to recover. Further, you must be supplied with a flash programming utility to do the job since you cannot access the flash directly -- you have to go through the ARM processor on the SiRF chipset."
|15 L A T E S T R E P L I E S (Newest First)
||Posted - 19 avr. 2011 : 11:09:13
Thanks nmitra - I received the file. The second 512k are simply nulls.
Comparing this to the build 3.2.4 I have for the BT3_6_8 it is quite different - maybe I try it with my old BT338. Can you find out if that was really an original BT338 firmware on it or if it came from a different device?
||Posted - 19 avr. 2011 : 08:26:09
Did you send it with attachment? Just look at www.trash-mail.com. The email you sent does not carry an attachment.
Edit: I deleted the mail at trash-mail and sent you a mail to the address you had used for sending. Direct reply there :-)
||Posted - 19 avr. 2011 : 07:38:20
Its actually 1024kb.
Just sent to the email mentioned.
||Posted - 18 avr. 2011 : 20:14:07
It should be 512kB in binary format (x'7ffff= 512kB). Just Zip it, I will PM you my email address so you can send it.
Edit: There is no PM in the board here and the "email to..." function is blocked due to abuse. So upload it to any filehoster (I use mediafire which is free and has no restrictions like rapidshare has.) If that does not work either I have to get a one-time email to post it here in the board.
Edit again: just send it to firstname.lastname@example.org I will fetch it from there (anyone can basically). The email is alive for only 6 hours there (gets deleted automatically then or earlier if anyone does it manually). I should get notified from the GPSpassion forum if you just reply to the post here telling you sent the mail - so we can keep the transaction short.
||Posted - 18 avr. 2011 : 20:02:44
I do have the dump. Its 1024kb thru 7ffff. I dont know how to send it to you though. I dont have any webspace to host it.
||Posted - 18 avr. 2011 : 18:30:58
Do you have the dump of the one that was on it? If so, I would like to compare to that I have (which is from a BT368).
||Posted - 18 avr. 2011 : 17:52:50
So I have successfully downgraded to 3.1.1 and it has been running stable for the last 30 mins. Looks like I have made it.
Thanks a ton Tobbbie.
||Posted - 18 avr. 2011 : 08:25:26
I have looked around but could not find an instruction on the flashing either. If I remember right, the process is very close to the dump part - just not read but write in sirfflash. You have to search around the web I fear. At XDA developers we had a discussion on the same, there was a brief instruction from antineutrino: http://forum.xda-developers.com/showthread.php?t=354941
I have looked at the FW that I have on the PC with 3.2.4. It has the very same string inside as the one you reported, so probably it is the same (and thus not original).
If you upload the dump (length 7ffff please) somewhere I can compare it with the version I have stored.
||Posted - 18 avr. 2011 : 07:44:20
I am not sure if it was factory fitted because I got the unit from someone else who had not been using it for some time. So it might as well be an upgraded one.
I saw the intructions to download my dump but could not find instructions to flash it. Can you give me a link where I can read more?
||Posted - 15 avr. 2011 : 23:35:55
You should first dump your existing firmware and then downgrade to an older one. I would suggest the 3.11 which works very stable.
Are you sure the 3.2.4 is original? Have you bought the device new from an official source? So far the firmware from other Sirf III BT mice had the effect that the green-LED blinking while in NMEA mode was no longer working.
I have my BT338 only as backup (hardly ever use it), but I'd like to give the 3.2.4 a try if it is original.
||Posted - 15 avr. 2011 : 19:04:01
My BT 338 has factory shipped GSW3.2.4_3.1.00.12-SDK003P1.00a.
I am using it with iPhone 3G(S), IOS 4.2.1.
It connects fine, strong signals and great navigation for a couple of minutes and then goes into a hang. At times the green light is always on and no signals come thru, at times the green light is always off and no signlas come thru.
Have tried using it with my laptop with sirfdemo 3.87 with same results.
I read thru this forum and saw the "jet lag" issue with 3.0.2 with suggestions to flash to 3.1.1. I seem to already be on 3.2.4 so that does not work for me.
Any ideas what I can do?
||Posted - 27 févr. 2011 : 04:21:11
My mistake. I meant to inquire about the SIRFtitan firmware for the Ipaq 310.
Are you aware if there are any SIRFtitan firmware updates? The GPS chip may also be called Centrality Titan Atlas III, I'm not sure.
||Posted - 13 févr. 2011 : 03:32:24
Not that I've heard of, and at this point the only SiRFstarIV based consumer device is the Garmin Forerunner 110/210 as far as I know, with the TomTom/Nike watch announced for April. Globalsat did show some boards and trackers with SiRFstarIV at CES. Where you able to find another device with SiRFstarIV?
||Posted - 13 févr. 2011 : 01:40:20
are there any firmware updates for sirf star iv chips?
||Posted - 28 janv. 2011 : 18:12:51
Originally posted by Archie2008
Dump of my BU-353 bought on eBay recently, version GSW3.5.0_3.5.00.00-SDK-3EP2.01.
I downloaded the file, flashed the 0x7ffff dump and did a factory reset. Everything seems to be in order. My trusty BU-353 just got a new lease of life.