Google
  Web www.gpspassion.com


GpsPasSion LIVE!
www.flickr.com
This is a Flickr badge showing public photos from GpsPasSion Live !. Make your own badge here.

www.NaviBlog.com



Versions

Links/Liens




Portal/Portail
Rechercher

- -

Polls/Sondages
Sondage
Pour vous guider sur la Route :
GPS Mobile (SEM)
GPS Intégré
Smartphone
Autre
Voter  -  Résultat des votes
Votes : 2402




Club GpsPasSion
Soutenez le site!

USA: (US$)
EUROPE: (€)
Guide Paypal


GpsPasSion Forums
Home | Profile | Register/Enregist. | Active Topics | Search/Recherche | FAQ
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 Advanced Topics
 General Technical Discussions
 Firmware versions of SiRF based receivers

Note: You must be registered in order to post a reply.
To register, click here. Registration is FREE!

Screensize:
UserName:
Password:
Format Mode:
Format: BoldItalicizedUnderlineStrikethrough Align LeftCenteredAlign Right Horizontal Rule Insert HyperlinkInsert EmailInsert Image Insert CodeInsert QuoteInsert List
   
Message:

* HTML is OFF
* Forum Code is ON
Smilies
Smile [:)] Big Smile [:D] Cool [8D] Blush [:I]
Tongue [:P] Evil [):] Wink [;)] Clown [:o)]
Black Eye [B)] Eight Ball [8] Frown [:(] Shy [8)]
Shocked [:0] Angry [:(!] Dead [xx(] Sleepy [|)]
Kisses [:X] Approve [^] Disapprove [V] Question [?]

  Check here to include your profile signature.
Check here to subscribe to this topic.
    

T O P I C    R E V I E W
Leif 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


Upgrade process
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:

2.3.2-GSW2-2.05.024-C1PROD1.0_6A
2.4.12.07-XMitac2.0-C1BETA1.1 0000003729
2.4.12.09-XMitac-C4PROD2.0 0000003729
2.4.13.03-XTrac2.0.2-C3PROD1.0


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."

150   L A T E S T    R E P L I E S    (Newest First)
IIB Posted - 22 oct. 2014 : 23:37:48
ANYONE,

I have a Holux GPSlim 236 with 3.1.1 firmware and would like to update it to 3.2.4 (or better still 3.2.5) if anyone can point me at a source for either of these firmware files (preferably from a GPSlim 236) it would be greatly appreciated.

Thanks

ps I've downloaded 3.1.1 from my GPSlim 236 if anyone needs that firmware.
IIB Posted - 21 oct. 2014 : 05:11:54
quote:
Originally posted by tsp

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 :)





Hi tsp,

I have a 236 with 3.1.1 firmware I'd like to update it to 3.2.4 but the file you posted on rapid share is no longer available. Is there some way I could get it from you?

Thanks
IIB Posted - 21 oct. 2014 : 01:50:34
quote:
Originally posted by Antineutrino

Hi cyberas...
Thanks for replying me!
The dump process is relatively simple.

HOW TO DUMP A SIRF GPS
Be sure you donwnloaded the latest versions of SIRFDemo and SIRFFlash.
You can grab the here:
http://www.falcom.de/support/software-tools/sirf/
It's important that you use SIRFFlash 3.2 because it has the option to flash in 'external boot mode'. This is the only way I managed to flash my device. Ok.. Now let's talk about the process.
Start SirfDemo and connect your GPS. In the menu select Action / Transmit Serial Message. Enter the string 'PSRF100,0,38400,8,1,0' without quotes , select NMEA mode and SEND it. This is the NMEA sentence to enable SiRF mode. After that send '94' (without quotes) using 'SiRF binary'. OK, now your GPS appears to be frozen. That's fine. Disconnect SIRF Demo and leave the GPS on. Now start SIRFFlash.
Select 'Read flash', the correct COM Port and 38400 Baud. Check 'Full duplex'. After that choose 'External' in 'Target boot mode state setting'. Chip select is 'CSN0' and Chip offset is '0'. The addresses are '0x0' for start and '0x79999' for the end. Now browse for an output file ( E.g.: c:\dump.bin) and click on 'Execute' and wait about 3 minutes.

That's all!

Cheers!



Hi Antineutrino,

I'm a little late in picking up on this thread but wanted to thank you for the instructions on use of SiRFflash (which I just used to download the firmware from my GPSlim 236 ("GSW3.1.1_3.1.00.07-C23B1.00"). In doing so I downloaded from 0X0 to 0X79999 and from 0X0 to 0X7FFFF.

Inspecting the 2 downloads with a hex editor I found the "0X79999" download ended 10 non null bytes into a 16 byte row (not surprisingly) while the "0X7FFFF" download ended with 6 rows of "FF FF ..." and a normal end of file designation of "A5 5A A5 5A".

From this I surmise the correct (full) download and any subsequent flashing of new code should use "0X7FFFF" as the end of file address.

Anyone using the 0X79999 address can expect strange results (if any) for a flash and an incomplete firmware file if downloading.

Anyone interested in obtaining the "0X7FFFF" download from me, just respond and we'll figure out a way.
tobbbie 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?
tobbbie 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 :-)
nmitra Posted - 19 avr. 2011 : 07:38:20
Its actually 1024kb.

Just sent to the email mentioned.
tobbbie 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 myspamdummy@trash-mail.com 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.

Thanks :-)
nmitra 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.
tobbbie 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).
nmitra 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.
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.
nmitra Posted - 18 avr. 2011 : 07:44:20
Thanks Tobbbie.

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?
tobbbie 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.
nmitra 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?
SandyLake 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.

thank you.
gpspassion 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?
SandyLake Posted - 13 févr. 2011 : 01:40:20
are there any firmware updates for sirf star iv chips?
Prompel Posted - 28 janv. 2011 : 18:12:51
quote:
Originally posted by Archie2008

Dump of my BU-353 bought on eBay recently, version GSW3.5.0_3.5.00.00-SDK-3EP2.01.

Brilliant!

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.

Thanks!
tobbbie Posted - 27 déc. 2010 : 23:30:47
Great you included the 7ffff sized version as well. My speculation on the dead device after uploading the 79999 sized firmware was that remaining incompatible configuration data may have killed the device. If all data are overwritten with a clean (FF) or consistent (full dump) data then this problem should not exist. The ROM space is 7ffff anyway - so why not fill it? I had noticed with different dumps after the device was used that data are changing in that area.
Still need to dare an upload as I have only one BT338 left (hardly ever use it any more) - maybe some time...
Archie2008 Posted - 26 déc. 2010 : 19:53:22
Dump of my BU-353 bought on eBay recently, version GSW3.5.0_3.5.00.00-SDK-3EP2.01. I have added screenshots for SirfDemo, SirfFlash, checksums in readme, 5% recovery record for archive. Do not know if this version any better of proven 3.2.x.

After reading the forum, TWO dumps are included - 0x0-0x79999 and 0x0-0x7ffff. There were different sizes observed before from different manufacturers, BTW real data in attached dumps is 0x0-0x79433, the rest is filled with FF-bytes.
http://rapidshare.com/files/439415611/BU-353_GSW3.5.0_3.5.00.00-SDK-3EP2.01.rar
morphis Posted - 03 déc. 2010 : 15:50:14
quote:
Originally posted by Prompel

I have dumped my GlobalSat BU-353, SiRF Version: GSW3.1.1TO_3.1.00.07-C23P1.00.

It can be found here: http://www.mediafire.com/?xvyiinegzky

Now, if only somebody could dump and upload a BU-353 version 3.2.4 or newer ... sigh ...




I had not done much playing around with my BU-353 . But the I pop'd back here to check up after my post earlier in the year and what do I find your post :D.
So I threw caution out the window and risked my BU-353.......... Paydirt!!!! Its seaming to be working polling the SW version with SiRFDemo returns 'GSW3.1.1TO_3.1.00.07-C23P1.00' it was 'GSW3.0.2-GS_3.0.00.03-C5P1.02b'

Again thanks Prompel

We just have to find 3.2.x :p
I guess Ill try to nag GlobalSat again :#
I will also work up a guide for dumping and flashing the BU-353
matteovinci Posted - 22 juil. 2010 : 08:52:42
SiRFIII modules being used presently have the following software:

324.000.000-Ct00

i would assume the 324 refers to 3.2.4

seems there is now 3.2.5 available
http://www.falcom.de/uploads/media/VDD_3_2_5.pdf
tobbbie Posted - 20 juil. 2010 : 13:43:51

1.) not sure if the mouse is in SIRF or NMEA Mode after flashing, can you try SIRF?
2.) switch off mouse, then on again and reconnect
3.) if this does not work - open the mouse (4 screws, T4 I think) and disconnect the battery (~hard-reset)

Latest 3.) should bring you back to NMEA.
Arton Posted - 20 juil. 2010 : 13:08:45
I updated my TomTom Mk II to firmware BT-368 3.1.1. I'm experiencing the same green-led phenomenon where the light only flashes once I have a fix. But besides, when I now try to read data from the receiver, I only get lines of different length with all Hex 80 characters at the rate I usually received NMEA data. SirfDemo doesn't retrieve any other data (obviously) and the device doesn't react to any sent command. Any clue how to fix this?
Prompel Posted - 18 avr. 2010 : 16:46:50
I have dumped my GlobalSat BU-353, SiRF Version: GSW3.1.1TO_3.1.00.07-C23P1.00.

It can be found here: http://www.mediafire.com/?xvyiinegzky

Now, if only somebody could dump and upload a BU-353 version 3.2.4 or newer ... sigh ...

tobbbie Posted - 04 mars 2010 : 13:08:17
my dumps (x0 to x7ffff) of all versions I have collected (3.0.2, 3.1.1, 3.2.2, 3.2.4, also 3.0.2 from TomTom Mk II) are at http://www.mediafire.com/?jamvzceutqi
I doubt that the BU353 is much different to the TomTom - so you may want to try a later one (3.1.1 is the optimum for my TomTom, possibly a different one for yours).
I also have a Jentro bt-gps-8 but not done a dump from it yet. This device seems very tricky accessing the SIRF mode (and especially getting back) from it, so I did not dare yet. It did not have a later firmware version though as the ones listed above so I have no motivation to change it.
morphis Posted - 04 mars 2010 : 12:53:22
I have a Globalsat BU-353 with GSW3.0.2-GS_3.0.00.03-C5P1.02b

I have dumped the current flash with SiRFflash and can make it avalible if any one wants it.

But Im realy looking for someone who has a newer unit hopefully with firmware version of 3.1 or newer.
tobbbie Posted - 21 oct. 2008 : 14:45:35
The defaults are hard coded - but the SW can be programmed (e.g. via SirfDemo) to use DGSP - the commands are there (Menu - Navigation - DGPS...) and they are acknowledged from the device as well. However I could not see the expected result (a D-GPS Fix) yet - even under optimum satellite reception.
saimhe Posted - 21 oct. 2008 : 14:32:16
There is no way. Defaults are hardcoded so only a different firmware version might change that.

If circumstances permit (it's a custom solution etc), I would add a larger backup battery. Results would be even more remarkable if a super-cap typical for these designs is replaced with a coin cell.
bogdan.dumitru Posted - 21 oct. 2008 : 10:47:33
does anybody know how to permanentely set waas enabled in a sirf star 3 based device? (in my case it's a WAAS NOT ENABLED BT 368)
tobbbie Posted - 10 oct. 2008 : 15:23:05
...well I do not notice any changed performance. Even the two BT338 that I have are different with identical firmware in how fast they get a fix and how many satelites are tracked under bad condition. The TomTom is less sensitive, but once it has a fix it operates well (with any firmware).
My only advantage was stepping with the TomTom to 3.1.1 where the Elipsoid correction for Altitude is built in - the rest (3.2.2 or 3.2.4) is only more flexible what trickle power is concerned. This however is not well usable under changing conditions and delivers a much worse accuracy (but extended battery time).
bogdan.dumitru Posted - 10 oct. 2008 : 15:07:07
my problem exactly. i thought it was just Romania with no EGNOS. Yesterday i saw the sat 120 (which is one of the EGNOS sats i believe) with full signal but i had no fix to it.

edit: for no reason at all, for the sake of commemoration maybe ;)) how do they compare now? -> TomTom MkII and Globalsat, both with 3.2.4 ?
tobbbie Posted - 09 oct. 2008 : 10:22:37
Bogdan's firmware dump of BT368 version 3.2.4 is running well in both TomTom MkII and BT338. They behave the same like 3.2.2 for BT338 what the green LED is concerned, i.e. off until a fix is found and in NMEA mode it blinks synced with the RMC message. In SIRF mode the LED will freeze (on or off) - despite the operation is ok.
As mentioned earlier I have yet to discover advantages of 3.2.2 or 3.2.4 over 3.1.1. I think some trickle power options are more flexible and the DGPS could work - but so far I could never get a DGPS fix.
Allycat Posted - 09 oct. 2008 : 00:23:45
The "baud" rate over a Bluetooth link is only a "notional" value and the (internal) communications between GPS and BT chips is typically fixed at 38400 baud. If you send a NMEA or SiRF command to the GPS chip to change the baud rate (some GPS firmware is rightly arranged to ignore such commands), you can kill the communications (until a "factory reset" by clearing the RAM).
tobbbie Posted - 08 oct. 2008 : 09:14:53
Any baudrate is supported for normal operation (SIRF and NMEA)- but accessing the flash (read or write) can only be done at 38400.
I compared the firmware with a Holux for Sirf of the same version - and it is quite different. I once had the Holux 3.2.4 on my BT338 and TomTom but despite it worked - the Green LED was off all time - leaving you "blind".
Possibly I'll give your dump another try to see what happens...
bogdan.dumitru Posted - 07 oct. 2008 : 11:23:56
I've found by mistake (and then investigating more) that the GlobalSat BT368 support any baud rate through bluetooth (tested 9600 -> 57600, both sirf and nmea). so you can safely use the "switch to sirf" option from sirfdemo. you must disconnect and reconnect though when you change the baud rate.
bogdan.dumitru Posted - 07 oct. 2008 : 09:17:41
I dumped it.

Firmware information:
name: globalsat BT 368
firmware: GSW3.2.4_3.1.00.12-SDK003P1.00a
dumped from 0x0 to 0x7ffff
Flash: SST39VF400A
Baseband: GSP3
RF: GRF3i
Baud: 38400 ONLY (bluetooth connection)
MD5 sum: 2e8cbdd1302d22a3c48a4918c71b01d9

ATTENTION:

The firmware is the heart of devices and it is a very sensible matter. It is NOT a matter of trial and error. If you do a mistake, it is very likely that the device is bricked FOREVER. Please do check that when you flash your device, the firmware file is in the right format, it is not corrupted (md5 sum) and IT IS compatible with your device.

the firmware bin file with the md5 sum file:

http://www.box.net/shared/2kc2pdtjj7
bogdan.dumitru Posted - 07 oct. 2008 : 08:28:31
as this one is in warranty, i can freely test things..

i will dump the firmware as soon as i get an windows machine on my hands.
tobbbie Posted - 04 oct. 2008 : 02:21:12
I noticed the BT338 has also much better reception than the TomTom - as well as faster fixes. I suspect that you can do anything you like - but should be careful with flashing to the device :-)
I'd bet the firmware is 3.2.2 and identical to the BT338 3.2.2 version.
You could dump it (please until 7ffff) and give us a chance to fry another device?
bogdan.dumitru Posted - 03 oct. 2008 : 17:23:05
I bought a GlobalSat BT 368. When i first saw it.. i began to sweat all over. it looked so puny and plasticy and .. fragile compared to my trusty old (now deceased) Tomtom Mk II. BUT.. TO MY EXTREME SURPRISE ... the signal both accuracy and sensibility it's incredible. the difference it's enormous between the two. (Why?? they both use the same chip SS3 don't they? )

Anyway, anybody got any ideea how can i _SAFELY_ play with his sirf mode settings?
bogdan.dumitru Posted - 03 oct. 2008 : 09:58:23
thank you tobbbie. it's too late. yesterday when i tried by trial and error to find the bootsel pad, i fried the sirf chip. it's all gone now.

i'm looking to buy another gps. any ideea? (as in the best bluetooth gps receiver in the world today) ?
tobbbie Posted - 02 oct. 2008 : 23:49:12
my dumps (x0 to x7ffff) of TomTom II (3.0.2), BT338 (3.0.2) and BT338 (3.1.1) are at the following link: -> deleted, no more available

Update 20090106: new ZIP with all versions I have collected (3.0.2, 3.1.1, 3.2.2, 3.2.4, also 3.0.2 from TomTom Mk II) at http://rapidshare.de/files/41287744/Firmware_Globalsat.zip.html
Update 20100304: same ZIP at http://www.mediafire.com/?jamvzceutqi
bogdan.dumitru Posted - 02 oct. 2008 : 13:52:16
as i stated earlier, i did opened the device. i don't really know what to look for.
tobbbie Posted - 02 oct. 2008 : 13:37:37
Hm - really sorry about the failure here. As I said the code is identical (I did a binary compare). So if you do not want to open the device (why??) try what I suggested above. I was lucky that everything worked for me and I do believe that the device can recover from invalid data.
Other speculations about the UART is only an idea - nothing I did myself.

Don't blame the forum - everyone here will try to help as much as he can (including me). If you feel to dump the device - do it and may it rest in peace. All work that you invest in time and effort there will not "pay" for the result. Counting your time and effort it is surely cheaper to just buy a new GPS. I did experiment only with these devices because I have 3 of them for various reasons.
bogdan.dumitru Posted - 02 oct. 2008 : 13:05:43
ok, i want to make it clear for everybody. my tomtom mkII is now dead because of this forum. i need this forum to help me with at least an ideea of getting it back.
bogdan.dumitru Posted - 02 oct. 2008 : 12:51:20
ok. i cracked it open.
disconnected battery, short circuit the pads that connects to the battery. after this, it behaves the same. DEAD.

i can see a lot of pads on the back of the pcb. any ideea on how can i force it to enter boot mode or whatever the name is to force flashing it again?
bogdan.dumitru Posted - 02 oct. 2008 : 12:07:29
i flashed it just as i flashed the 3.2.2 version. my bluetooth connection still goes online but the sirf really seems stone dead.

about the link... i always tripple check stuff, that's why i asked about it, i was absolutely sure that you actually have that file on your device, and that's why you give me the quote with confindence... that's why i asked for a dump from yours in the first place.

anyway.. i don't know how to recover it.. should i just throught it out the window? please detail about what should i try with sirfdemo. opening the case it is not an option for me at this moment.
tobbbie Posted - 02 oct. 2008 : 12:00:33
oops :-( Then the advise to dump only until 79999 is not a valid one - what did you do for the "erase before flash" part? Cyberas should remove that link then and I will upload my dumps to some place instead (any suggestions where?). I don't have it hand currently though.
To recover your device you will have some more options to play with the advanced options that sirfdemo offers regarding the UART settings. Strange enough is that the BT part should still give you a connection. I am SURE that the missing data after 79999 are not software parts. Several dumps of the same device deliver always different content there.
Hoping that the software (which IS complete on your device, suspected the flash worked OK) will recover from invalid data in this area after some time you should BT-link it to some PC and just keep it connected doing nothing (observe that BT stays connected).
Another option could possibly be to disconnect the battery for a long time and hope for some battery-backed data to disappear.
bogdan.dumitru Posted - 02 oct. 2008 : 11:49:28
does anybody know how to force put tomtom mk2 in boot mode?
bogdan.dumitru Posted - 02 oct. 2008 : 11:38:28
yep... it's dead now. thank you very much.
bogdan.dumitru Posted - 02 oct. 2008 : 11:19:10
ok tobbbie, that is clear enough. i will proceed to reflash with that dump. hope i will not end up in the same pit as the guy who fried it's gps with that particular file.
i will submit my result here.

thank you!
tobbbie Posted - 02 oct. 2008 : 11:16:51
quote:
Originally posted by cyberas

The dump has 498074 bytes, here you are:
http://www.cyberas.republika.pl/BT339/dumpBT339.zip


This link still works.

A few posts later I stated:

quote:
Originally posted by tobbbie
I compared the BT339 with my BT338 dump of 3.1.1 and it is binary identical (except I dumped from 0x0 to 0x7ffff). The data after 0x79999 seem to be dynamic tables anyway - so no reason to bother about this.


bogdan.dumitru Posted - 02 oct. 2008 : 11:16:48
quote:
Originally posted by bogdan.dumitru

tobbbie thanks.. i've been searching this forum back and forth, googled it, went out and screamed for it... the closest i've been was a ftp from xda-developers but nothing to be found there...
it really is damn frustrating, i've found a holux image of 3.1.1, and of course i know it won't work. i'm prepared to put online a ftp with organised directories and files with firmwares for gps devices if someone can direct me to some sources.

anyway, tobbbie, would you be so kind and upload your 3.1.1 fw that is working in your tomtom mk2 and link me to it?

thanks.. again. and sorry if i'm annoying


EDIT: is cyberas's dump 3.1.1 version? it is not clear... also i see that someone had problems flashing his dump. i beg for some clear black on white informations about this firmware. German style!

bogdan.dumitru Posted - 02 oct. 2008 : 10:54:49
tobbbie thanks.. i've been searching this forum back and forth, googled it, went out and screamed for it... the closest i've been was a ftp from xda-developers but nothing to be found there...
it really is damn frustrating, i've found a holux image of 3.1.1, and of course i know it won't work. i'm prepared to put online a ftp with organised directories and files with firmwares for gps devices if someone can direct me to some sources.

anyway, tobbbie, would you be so kind and upload your 3.1.1 fw that is working in your tomtom mk2 and link me to it?

thanks.. again. and sorry if i'm annoying
tobbbie Posted - 02 oct. 2008 : 10:30:03
Hi bogdan,

...well I have not seen an advantage of 3.2.2 over 3.1.1 as mentioned in my later posts. You can use the BT339 FW linked in the posts here as it is binary identical to the BT338 (V 3.1.1). Not sure if I stated it in this forum here. With this you have the original green LED behaviour.

bye
tobbbie
:-)
bogdan.dumitru Posted - 02 oct. 2008 : 08:59:44
ok tobbbie, sorry for not paying attention. i was mislead by your statement:
"My old TomTom MkII is now upgraded to the very same FW (also BT338 3.2.2 and works ok as well with that, including the behavior of the green LED."
but never read the P.S. in which you were saying the led is off till you get a fix.

so now a question: do you find 3.1.1 good enough? is 3.2.2 better in any way?
where can i get 3.1.1 (the one tested and working in your tomtom)
(yes, i am actually reading/posting from a nokia phone so.. yes, i tend to miss some posts, i am always on the move :( )

Thank you very much for your patience and help.
tobbbie Posted - 02 oct. 2008 : 00:25:17
look up my reports in this thread :-)
bogdan.dumitru Posted - 01 oct. 2008 : 18:56:17
thank you tobbbie.

i have managed to update my tomtom mkII gps to 3.2.2 but ... what a struggle it was.
first of all, i have no PCs. Only Macs. Today i borrowed my father's vista 64 ultimate laptop just for updating my tomtom.
It is because of vista.. or because of the microsoft stack, or because of the bluetooth hardware in my father's dell, i don't know, but when i tried dumping the firmware it always locked (RANDOMLY!!!!) somewhere in the middle of the process.

So... i gave up vista and moved on to my iBook G4. Installed Virtual PC, installed Windows XP on top of that... no success, even though i tripple checked my virtual serial connections, SIRFDemo just couldn't get through. ** SO TAKE NOTE: It seems that on PowerPC Macs you really can't update sirf devices.

I then jumped to my intel mac mini. Installed Parallels, installed windows xp, search through the whole net backwards and forwards till finally got the serial working with a 3rd party ultility for Parallels called Serial Client, which let me set baud rate and connect to both parallels and my bluetooth tomtom. Windows then quickly bragged about finding COM1 and installed it.

Did a test first just to be sure, and dumped the firmware from the tomtom twice then compared the files with hexeditor, just to see if there is any transmission corruption issues from this weird setup of mine.
Flashed with Antineutrino's bin file : http://rapidshare.com/files/140119231/Bt-338_3.2.2_.bin and ....

well.... it works ok i guess, but i do have a problem now.

the green led that used to continuously glow when it searched for satellites and then intermitentely flashed when got a fix, now just stays shut off, dark and sinister until it gets a fix, then starts flashing..
anybody has an ideea about how can i get my green led to the initial behaviour? now i can't really tell if it's off or on but with no satellites fixed. it's a bit frustrating when you power it on.

EDIT: Don't you find it weird that the setup Mac+Parallels+ some beta utility did the work but vista didn't? ... you have to wonder.
tobbbie Posted - 01 oct. 2008 : 15:34:07
Hi bogdan,

look at the previous page in the post of antineutrino you will find the BT338 3.2.2 this is the best available version. In case you need the older ones (3.1.1 of BT338), look further up there is a small post referring to the BT339 - also having a link. Try to read the own original FW first to see if all communication works properly.

Good luck,

bye
tobbbie
:-)

bogdan.dumitru Posted - 01 oct. 2008 : 14:33:05
Hello everyone!
I have a bluetooth gps receiver TomTom MKII with an antique firmware version. From what i've gathered from this thread, this little baby has been upgraded to a more recent firmware. Here is a quote from tobbbie :
quote:
P.S.: My old TomTom MkII is now upgraded to the very same FW (also BT338 3.2.2 and works ok as well with that, including the behavior of the green LED. I was confident that it works, because the MAC address of the bluetooth part is from the GlobalSat range (see http://www.techzoom.net/lookup/check-mac.en)



The bottom line. I am skilled with firmware updating and digital electronics in general but i want to be sure of what i am doing.
So here is the question: What firmware do i want to flash to the TomTom MK II (from where? i'm unable to find file links on this forum on this matter).

thank you very much. very nice forum :)
stefrance_fr Posted - 10 sept. 2008 : 16:40:39
Hello,

Thank you but I tried everything. The only way is finding the pin on the PCB of the BT338 and to put it at High (3.3V)

When the firmware is broken, no other way.

Steph
tobbbie Posted - 08 sept. 2008 : 12:44:18
Yesterday I changed the firmware in my devices:
- TomTom MkII is on BT338-3.1.1
- BT338(1) is again on 3.1.1 as well
For both LEDs are working as expected and now I can enjoy the Elipsoid corrected height data for the TomTom (original 3.0.2) as well :-)
In the meantime I also had a test with the Holux 3.2.4 FW on my BT338, but with no additional gain observed over 3.2.2 or 3.1.1. Even more downsides with the 3.2.4 FW:
- Green "fix" LED is never working
- switch from NMEA to Sirf via SirfDemo puts the device (sometimes, e.g. after cold boot) in a hardly accessible state. BT connection stays, but SirfDemo cannot decode anything. Remove battery for several minutes puts it back to cold-boot, resulting in sending NMEA sentences then. Watching the data via a RS232 com port logger reveals only binary garbage received.
Could not get DGPS running as well - so no reason to stay with this version.
-> anyone with problems to access bootmode: check out what happens on the COM port after it is connected, possibly you can find a clue there?
You could also play with the UART settings of SirfDemo.

I still wonder that the advantage of BT338 3.2.2 over 3.1.1 shall be.

bye
tobbbie
:-)
stefrance_fr Posted - 01 sept. 2008 : 09:15:37
quote:
NO NEED TO QUOTE A MESSAGE DIRECTLY ABOVE YOURS, MAKES THE FORUMS EASIER TO READ, THANKS ;-) GPSPASSION TEAM
In case of broken firmware, no NMEA sentence can be sent to the device. We have to put it boot mode with internal procedure. To do that we have to put VCC on the Boot mode Pin of the sirf star ship.

The problem is we don't know the pin "Boot mode" on the PCB of the BT338. If I see a data sheet of a Sirf star III, this pin is sometimes 13 sometimes 20 sometimes 3 (!!!) ... depends of manufacturer. I've try the tree solutions, nothing happens.

An idea ?

Thank you
Stephane
tobbbie Posted - 31 août 2008 : 20:58:21
Hm...well if I remember right the device was in "System Reset" state and an immediate connection via SirfDemo delivered NMEA sentences - strange :-(
Did you leave out the battery for some extended time (e.g. overnight) to see if that improves getting through until the SIRF part?
Some Bluetooth programs on the PC drop the connection to the device if a program closes the COM port (when they have "autoconnected"). I did my upgrades successfully with either Blue Soleil stack or recently with the standard Microsoft stack.
paolino Posted - 31 août 2008 : 20:46:09
Yes for all. I took care also during the flash reading, which finished successfully.
tobbbie Posted - 31 août 2008 : 17:06:46
Did you take care to set the boot-mode to external when flashing?
Also mind that 38400 baud is the native speed of the interface, so this may help?
paolino Posted - 30 août 2008 : 23:22:10
dead firmware also for my bt-338, after upgrading to the newest version.
Only the blue led is blinking, but SirfDemo and Sirfflash cannot detect the device info, altough BT module is working right.
Any idea? I cannot find hardware pins for boot mode activation.
stefrance_fr Posted - 30 août 2008 : 13:13:31
quote:
Originally posted by Antineutrino

By the way I'll continue looking for a 'hardware way' to put my 'fried one' in boot mode so I can try to recover it with a new flash...
I read about the Holux GPSSlim 'boot mode' so I'm sure that a way IS there, even it is really hard to find without any scheme or datasheet....




Hello

I have the same problem (dead firmware). If someone find the two pins on a BT338 to set it in boot mode ...

Thank you
tobbbie Posted - 29 août 2008 : 23:29:49
I did the update of my old (original 3.0.2) BT338 to 3.2.2 - now the green LED is no more blinking in Sirf Mode (it freezes in the state when you switch to Sirf, either on or off) - but it does blink in NMEA (sync' with the RMC message) - very nice to detect you left the device in the wrong protocol!
This happened to me several times already and I was seeking very long for reasons why the applications could not communicate with the device.

Besides this nice feature, I wonder what actuall is the gain of 3.2.2 over 3.1.1, does anyone know?

bye
tobbbie
:-)

P.S.: My old TomTom MkII is now upgraded to the very same FW (also BT338 3.2.2 and works ok as well with that, including the behavior of the green LED. I was confident that it works, because the MAC address of the bluetooth part is from the GlobalSat range (see http://www.techzoom.net/lookup/check-mac.en)

P.P.S.: The green LED seems to be off also in NMEA until a SAT fix is found. It stays frozen in Sirf Mode though (on or off).
guiumb Posted - 29 août 2008 : 11:40:22
Dear all, many thanks for your help. Finally i was able to upgrade my holux GPSslim 236 (board Rev.B) with firmware 3.1.4 usign Bluetooth connection. It's work fine and upgrading also SirfTech PPC software on PDA with version 2.20 I can see the data about SBAS correction. NICE !!!
Many thanks again to all people that write on this forum !!! Thank again for your knowledge and experience that we had the chance to share.
Umberto
tobbbie Posted - 26 août 2008 : 10:37:32
Thanks a lot! I will have to load it from home this evening but it will still take until the weekend that I can test it.
Antineutrino Posted - 26 août 2008 : 02:07:54
Here is BT-338 3.2.2...

http://rapidshare.com/files/140119231/Bt-338_3.2.2_.bin

This night I couldn't compare the two PCBs so you have to wait a bit more...

tobbbie Posted - 25 août 2008 : 17:15:27
Good luck - if they use the same chipset (and after all it's Sirf anyway) - possibly the wiring is not so complicated and you just have to set the right chipset pin to ground only to achieve this. I doubt that there is SW logic attached to it. Did you ask the guy who has found the Holux HW-Bootmode for assistance?
Antineutrino Posted - 25 août 2008 : 16:58:54
By the way I'll continue looking for a 'hardware way' to put my 'fried one' in boot mode so I can try to recover it with a new flash...
I read about the Holux GPSSlim 'boot mode' so I'm sure that a way IS there, even it is really hard to find without any scheme or datasheet....
tobbbie Posted - 25 août 2008 : 14:31:52
I have two of them (old ones from ebay) - this would leave one intact at least :-)
Antineutrino Posted - 25 août 2008 : 14:29:36
quote:
Originally posted by tobbbie

Hi antineutrino,

...can't wait - will you check the interior (HW) board revision as well and compare the "old" BT338 against the new one?

thanks + let me know when you did,

bye
tobbbie
:-)



Ok I will double check this... So you won't fry your Bt-338 as I did with my previous one...
tobbbie Posted - 25 août 2008 : 13:59:58
Hi antineutrino,

...can't wait - will you check the interior (HW) board revision as well and compare the "old" BT338 against the new one?

thanks + let me know when you did,

bye
tobbbie
:-)
Antineutrino Posted - 25 août 2008 : 13:08:31
quote:
Originally posted by tobbbie

Hi Antineutrino,

..well I have the BT338 dumps of 3.0.2 and 3.1.1 FW - if you need them PM me. You mention a 3.2.2 for the BT338 - is that available somewhere?

bye
tobbbie
:-)



Hi tobbbie...
I just bought a new BT-338 with 3.2.2 firmware so I can dump it and send the firmware to you, if you need...

Cheers!
gunther12 Posted - 10 août 2008 : 11:06:42
saimhe, thanks for the link.
This sounds bad but - originally installed firmware 3.1.0? on my Digitus (=236B) didn't have this NMEA bug. Unfortunately I was not able to backup it due to unspecified errors. Is there any 236B-firmware around which reports lower speeds in RMC sentence? Could someone *** please *** provide a link? Geocaching is horror without directions shown .
Greetings, Gunther
tobbbie Posted - 10 août 2008 : 01:38:10
I compared the BT339 with my BT338 dump of 3.1.1 and it is binary identical (except I dumped from 0x0 to 0x7ffff). The data after 0x79999 seem to be dynamic tables anyway - so no reason to bother about this.

bye
tobbbie
:-)
saimhe Posted - 10 août 2008 : 01:21:50
This has been already reported and still no ideas whether a "truly fixed" firmware exists.
gunther12 Posted - 10 août 2008 : 00:43:41
Strange thing here with v3.2.2 (and also v3.1.1) on a Digitus-labeled 236B: In NMEA mode, Speed Over Ground (in RMC sentence) always reports "0" (and not 0.1 or 0.14 etc.) when the receiver is static. Also heading doesn't vary, but coordinates change minimally. In SiRF mode everything is ok. Any clues?
Gunther
tobbbie Posted - 08 août 2008 : 19:55:19
Hi Antineutrino,

..well I have the BT338 dumps of 3.0.2 and 3.1.1 FW - if you need them PM me. You mention a 3.2.2 for the BT338 - is that available somewhere?

bye
tobbbie
:-)
Antineutrino Posted - 04 août 2008 : 12:39:45
Hi cyberas!
Thank again for your help...
The flashing process went straight to the end so no problems here...
I've already found that link about Holux GPSlim, and set to pieces my Bt-338. Too Bad I didn' find any pad to set it in boot mode...
Well... Exactly... I found too many of them on the back side of the PCB without any label on them and it's bit difficult to access them while the Bt-338 is on. So I think only a professional technician could repair it...

cyberas Posted - 01 août 2008 : 16:35:52
I'm very sorry to hear that, Antineutrino. Did the process stop suddenly or what happened, finished and GPS doesn't work?
I don't know if it is possible, but look at this:
http://web.mac.com/tomtastic/site/log/Entries/2007/6/18_Holux_GPSlim236_boot_mode.html
"Whilst we can send message 148 (0x94) to it from SiRFdemo to enable this mode, it’s handy to know one can also short the highlighted pads above (two gold pads enclosed in the white square border just above the label ‘C48’) whilst turning the unit on to achieve the same thing."
There is alternative way to go to boot mode, maybe similar pads you can find in your device?
Antineutrino Posted - 01 août 2008 : 13:21:07
Thanks a lot cyberas....

I flashed back my BT-338 with your dump, but something was wrong. So it killed my GPS. I'm not complaining anything at you... You were so kind to dump your BT-339, so I can Thank You anyway.
Now I can only be upset with myself and think how much am I silly...

Now if I switch-on my Bt-338 I can say that only the Bluetooth interface is working. If I try to connect with SiRFDemo it does, but it's not sending any NMEA or SiRF messages. I tried to put it again in boot mode, but SiRFFlash doesn't work. Is there any other way to try to recover it?


cyberas Posted - 30 juil. 2008 : 22:32:21
The dump has 498074 bytes, here you are:
http://www.cyberas.republika.pl/BT339/dumpBT339.zip
Antineutrino Posted - 28 juil. 2008 : 12:50:31
Hi cyberas...
Thanks for replying me!
The dump process is relatively simple.

HOW TO DUMP A SIRF GPS
Be sure you donwnloaded the latest versions of SIRFDemo and SIRFFlash.
You can grab the here:
http://www.falcom.de/support/software-tools/sirf/
It's important that you use SIRFFlash 3.2 because it has the option to flash in 'external boot mode'. This is the only way I managed to flash my device. Ok.. Now let's talk about the process.
Start SirfDemo and connect your GPS. In the menu select Action / Transmit Serial Message. Enter the string 'PSRF100,0,38400,8,1,0' without quotes , select NMEA mode and SEND it. This is the NMEA sentence to enable SiRF mode. After that send '94' (without quotes) using 'SiRF binary'. OK, now your GPS appears to be frozen. That's fine. Disconnect SIRF Demo and leave the GPS on. Now start SIRFFlash.
Select 'Read flash', the correct COM Port and 38400 Baud. Check 'Full duplex'. After that choose 'External' in 'Target boot mode state setting'. Chip select is 'CSN0' and Chip offset is '0'. The addresses are '0x0' for start and '0x79999' for the end. Now browse for an output file ( E.g.: c:\dump.bin) and click on 'Execute' and wait about 3 minutes.

That's all!

Cheers!
cyberas Posted - 25 juil. 2008 : 19:18:58
quote:
Originally posted by Antineutrino


[...]Please could someone dump the original Bt-338 3.1.1 or 3.2.2 ROM?[...]


Antineutrino, I have BT-339 (AFAIK it is the same). If you are interested in I can dump this device, but please send me short instruction how to do it (for instance start and finish address, etc.).
Antineutrino Posted - 25 juil. 2008 : 00:59:30
Hello....
I have a BT-338 and I flashed using 3.2.2 of Holux 236. After that My GPS is still working but the fixing led doesn't work correctly. So I'd like to flash back but I lost the backup I made. Please could someone dump the original Bt-338 3.1.1 or 3.2.2 ROM?

I used SirfDemo 3.87 and SirfFlash 3.2 that has the 'external boot mode' option that solves the problem that many have to flash their units (Target not responding or unable to put in boot mode).

You can find this tools here...

http://www.falcom.de/support/software-tools/sirf/


Cheers!
ppcjvc Posted - 12 févr. 2008 : 15:29:51
Hi Carl,
you seem to be the expert here, can you please see

http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=55463&whichpage=15

me and roher ( Loox Users with internal GPS) can't seem to find the solution for this. Can you give us any clues?
I have tried every trick from the forums, I think, but noting works.

Thanks in advance
ppcjvc

quote:
Originally posted by Carl@SiRF

An interesting point about static nav for those of you worried about it: when SBAS is active in a system, even if static nav is turned on it should not be processed! So if you find SBAS on and static nav on, assume static nav is off. This little feature is not explained in our standard documents, but is definitely in the code.

polevoym Posted - 03 janv. 2008 : 19:58:09
Hi

I was trying to upgrade my Holux gpsslim 236 to the 3.2.4 firmware
using siftdemo 3.83 and sirfflash version 2.15.
I'm using BT in order to connect to the GPS.
I was able to switch to sirf mode and send the 94 command to the GPS, while trying to flash the gps I'm getting the following error "unable to get target external bus width info".

I would like to add that,I was able to see on the BT software that the sirfflash was able to connect to the GPS.

Do someone has a clue how to solve the problem?

regards,
Michael

gpspassion Posted - 02 déc. 2007 : 20:24:40
V3.2.5 spotted on Garmin GPS systems, starting with the nüvi 200 here http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=101914

Also added SiRFstarIII-LT to the list on the first page, first appearance on the Eten X800 GPS PDAPhone.
gpspassion Posted - 25 oct. 2007 : 00:44:45
No, can't be done, you need a SIF enabled firmware, SiRF licence it separetely I believe, where can the .ee file be downloaded "freely" ?
seatone Posted - 22 oct. 2007 : 18:55:22
A beginners's question:
I've bought a P535 ppc with integrated GPS (GSW3.3.3_3.1.00.12-SDK003P1.01a), and I'm very disappointed due to the lack of its instant fix capability.
Is there any kind of method to load the ephemeris file manually (with sirfdemo, or whatever...)into the GPS, since the .ee file can be downloaded freely? Or any kid of firmware update...or something :)
I've have already tried the sirfdemo for ppc, but there is no option (at least in my device) to load ee file (only load map...).
Any idea would be kindly welcomed :)
Thanx
ablaz3r Posted - 14 sept. 2007 : 12:14:39
Thanks again Alan!
I short circuit is as shown here: http://web.mac.com/tomtastic/site/log/Entries/2007/6/18_Holux_GPSlim236_boot_mode.html#
and after that it worked just fine...

Previously I was using the outgoing BT Com port but there were no NMEA sentences in the SirfDemo window, so I guess it was a connection issue.

Anw, it worked and I successfully updated the firmware!

Thanks!
Allycat Posted - 13 sept. 2007 : 11:30:16
Hi Nick,

I can't think of anything obvious that we're overlooking. Just a few checks/things to try:

You are using an outgoing BT COM port and receiving NMEA sentences in the SirfDemo window? When you send the command, this just stops? What does Hyperterminal receive if you try to run that? Try sending the command FROM Hyperterminal (you must add the $ and *checksum, which seems to be 0C). See the posts from beechfarm on this page:

http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=25575&whichpage=21

If you have a Pocket PC with BT, SirfTech is more predictable than SirfDemo, although you can't actually re-program the Holux firmware with it, of course.

Cheers, Alan.
ablaz3r Posted - 13 sept. 2007 : 01:41:50
Thanks for your reply Alan!

I installed SirfDemo 3.83 and tried with two different bluetooth dongles but still the program freezes when I try to switch to SiRF mode ;(.

Nick
ablaz3r Posted - 13 sept. 2007 : 01:41:18
Thanks for your reply Alan!

I installed SirfDemo 3.83 and tried with two different bluetooth dongles but still the program freezes when I try to switch to SiRF mode ;(.

Nick
Allycat Posted - 12 sept. 2007 : 16:35:51
Hi,

It works alright for me (I pasted the string from your post directly into SirfDemo), but I'm using SirfDemo 3.83. Presumably you're using a USB Dongle on a PC/laptop? I'm using quite an old Belkin dongle, and had great problems connecting to the Holux until I updated the drivers (now using Widcomm 3.0.1.912).

A thing you could try is to click the "gearwheel" at top-left, re-select the baud rate, and re-connect (I seem to remember having to do this on occasions). However, for firmware upgrading, I've always used a (home made) serial cable connection to my Holux236.

Of course you could try the Action: "Switch to SiRF Protocol" option, but that's almost *guaranteed* to kill the GPS !

Cheers, Alan.
ablaz3r Posted - 12 sept. 2007 : 13:58:36
Hi all,

just a quick question... I'm trying to update the firmware of my Holux GPSlim 236 using bluetooth. I am doing the following:

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.

The problem is that when I try to switch to SiRF using the above command the SiRFDemo just freezes! Is there another way for switching to SiRF mode?

ps. I am using SiRFDemo 3.81...
Allycat Posted - 21 août 2007 : 00:44:56
quote:
Originally posted by aaronprez

if I were driving, and slammed on my breaks, it won't immediately drop down to zero MPH, there is a few second delay. .


Hi aaronprez,

IMHO, that is not a characteristic of Static Navigation. It sounds more like a filter in the system, although "track smoothing" doesn't seem to be enabled in the Holux 3.2.x firmware.

I suspect that in your "braking" example above, the gps fix became lost or degraded at the same time. In this case the gps assumes that the current speed and direction are maintained, at least for a few seconds (Garmin handhelds are notorious for doing this for up to 30 seconds). I believe this may be a characteristic/feature of the Kalman filter used in the SiRF firmware. See Carl's second post in this thread:

http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=26282

The simplest way to check if SN is enabled is to monitor the position when the GPS is stationary (sometimes even indoors). If SN is NOT enabled then the position continuously wanders by a few metres, but with SN enabled the reported Position probably won't change at all (once the gps has a reasonably good fix).

Personally, I prefer to use SirfTech with my PPC and noticed in my tests that, using SiRF Protocol and SN enabled, the Lat, Long & Altitude remained static, the Speed at zero, but the "Course" (direction) still jumped about (indicating that the calculated position was actually changing).

Perhaps I should clarify that, in my post just above, I was only qualifying Carl's comment that SBAS disables SN. As far as I can see, the SN control flag works correctly (at least using SirfTech and MM-SiRFSetup).

Cheers, Alan.
aaronprez Posted - 20 août 2007 : 16:42:08
What makes even less sense to me is why you can't just click disable static navigation in SirfDemo and have it disabled.
Allycat Posted - 20 août 2007 : 14:32:53
How do you define "active in a system"? As far as I can see, SN is ONLY disabled if the receiver is actually APPLYING differential corrections.

IMHO, it is completely stupid for Holux to have enabled both SN and SBAS in the 3.2.4 firmware of the GR236. Firstly, it is at least confusing to be relying on an undocumented "feature" of the SiRF firmware. And the result seems to be the "worst of all worlds":

For the walker/geocacher, SN will kick in at any time that there is not a good and continuous view of a SBAS satellite (and here in Europe we don't always seem to get differential mode even when an EGNOS signal IS visible).

For the car driver (who might actually WANT SN enabled), there is the risk that the receiver may see a SBAS bird for long enough to switch off SN, and the driver could find the car "swirling about" whilst waiting at road junctions, etc..

Cheers, Alan.
cyberas Posted - 16 août 2007 : 21:32:15
quote:
Originally posted by Carl@SiRF
[...]
So if you find SBAS on and static nav on, assume static nav is off. This little feature is not explained in our standard documents, but is definitely in the code.


Why? For what?
Are you sure?
How do you know?

Carl@SiRF Posted - 16 août 2007 : 20:59:03
An interesting point about static nav for those of you worried about it: when SBAS is active in a system, even if static nav is turned on it should not be processed! So if you find SBAS on and static nav on, assume static nav is off. This little feature is not explained in our standard documents, but is definitely in the code.
aaronprez 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.
Allycat 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.
Gix 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 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.
aaronprez 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.
DeDragonSlayer 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!!
Gix 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.
aaronprez 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?
tsp 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 :)

saimhe 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).
tsp 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?
Gix 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!
cyberas Posted - 03 août 2007 : 21:51:34
quote:
Originally posted by Allycat

Hi tsp,

Yes, you need to use SirfDemo and SirfFlash. See the link from ink's post here (and then the links from aaronprez):

http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=84148

also the start of this thread:

http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=25575

It's better to use a serial cable connection (which always works at 38400 baud, CMOS/TTL levels) if possible. With Bluetooth you need to be very careful that SirfDemo does NOT use 56 kbaud.

Cheers, Alan.


I hope, above and below links and these pictures help you extract the firmware:

http://cyberas.republika.pl/GPSlim236/setupSiRFFlash.exe


aaronprez 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.
saimhe 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.
Allycat Posted - 03 août 2007 : 11:45:06
Hi tsp,

Yes, you need to use SirfDemo and SirfFlash. See the link from ink's post here (and then the links from aaronprez):

http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=84148

also the start of this thread:

http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=25575

It's better to use a serial cable connection (which always works at 38400 baud, CMOS/TTL levels) if possible. With Bluetooth you need to be very careful that SirfDemo does NOT use 56 kbaud.

Cheers, Alan.
saimhe Posted - 03 août 2007 : 09:57:06
Usually the firmware is given among with SiRFFlash utility, which can also dump the existing data.
tsp Posted - 02 août 2007 : 23:26:06
I could make it available If someone tells me how to dump it
cyberas Posted - 01 août 2007 : 23:40:03
[SNIP]
Very interesting.
Is somewhere V7 accessible? :)
tsp Posted - 01 août 2007 : 22:58:49
I just brought a hoolux 236. using sirftech to get the software version is show this string: GDSW3.2.4_3.1.00.12-SDK003P1.00a
does this mean I have firmware version 3.2.4 as the holux V6 firmware has the name GSW3.2.2_3.1.00.12-SDK003P1 ??
musky Posted - 29 juil. 2007 : 19:32:39
My experience is Sirf firmware version 3.1.1 doesn't have functional SBAS (WAAS/EGNOS) From your version string it appears you have 3.1 if I'm not mistaken. I think I know what you mean by "tangled", and the problem is, the resellers are told by Sirf that the unit is WAAS functional, and they just pass the information on, so it isn't totally their fault.

Correction (8/12/07) If your version string starts with GSW3.2.1, that indicates 3.2 firmware. Not sure why WAAS isn't working for you...
tureface Posted - 29 juil. 2007 : 12:32:36

SORRY I was wrong : I CAN'T turn on SBAS with gpsdemo


Hi . I bought rtb-2210/LP royalteK. With demogps i CAN'T turn on SBAS : with sirfdemo i saw that my receiver has GSW3.2.1PAT_3.1.00.12-SDK001p1.00c firmware . Is this the last for my 2210? I think no. Is for this reason that I CAN'T turn on SBAS ? In gpsdemo I only turn on "NMEA" but not SBAS : I read that to train NMEA I must train SBAS . Is it correct?
In auction of rtb-2210 was "rtb-2210 with chipset SiRF Star III GPS GSC3fLP " . Is this ? Have i been tangled ?
Help me, please : i can return the gps receiver ;-)
Very very thanks and scuse me for my english.
turefacer
cyberas Posted - 20 juin 2007 : 18:10:43
Thank you ink, I try to do it, but did you see the firmware 3.2.2 for BT-338 in the Internet?
I'm most interested in 3.2.2 for BT-338.

ink Posted - 20 juin 2007 : 15:06:51
If you want to upgrade your Holux GPSlim 236 to firmware 3.2.2, have a look here for some very useful information that will save you the price of the noddy Holux USB-Serial cable.

Drop me a comment on the site if you find it useful please :)

http://tinyurl.com/2hb2jn
gpspassion Posted - 24 mai 2007 : 15:22:03
Only GS can do that for you, not that you're likely to see any difference.
imreiki11 Posted - 23 mai 2007 : 19:33:32
My bt-359 is running the 3.1.1 fw. I was wondering if you guys could help me upgrade it to 3.2.2 or higher

Thank you
gpspassion Posted - 13 mars 2007 : 15:13:05
You'll find links for PC and PPC apps here http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=25575
steen Posted - 13 mars 2007 : 14:37:38
gspassion says "Just received the latest Royaltek RBT-2110 and it has v3.2.1".
Could someone tell me what to do in order to know the version? I just purchased a RoyalTek RBT 2110 but have no detailed documentation and no utility programs. I would really appreciate some help.
Thanks
Steen
gpspassion Posted - 28 janv. 2007 : 00:19:42
1. You can use a tool like APL SiRF, my test unit uses v3.1.1
2. No and firmware upgrades are very rarely offered.
dan_aka_jack Posted - 26 janv. 2007 : 20:56:20
Hi there!

I have a Mio P550. Please may I ask two quick questions:

1) How do I find out which Sirf firmware my PDA is using?

2) Can I update the Sirf firmware on my P550?

Many thanks,
Jack
gpspassion Posted - 17 janv. 2007 : 23:20:09
None, see previous discussions about that, most likely under an AGPS header of sorts.
maurizio Posted - 17 janv. 2007 : 18:55:35
For Carl@Sirf or anyone who may know:
Is it possible to tell us which are the FW versions of Sirf III modules (not bluetooth receivers) i.e. Leadtek or others and which available version support up/download ephemeris Sirf Commands to allow an AGPS application?.
Thanks
gpspassion Posted - 18 déc. 2006 : 03:06:19
Yes Garmin are getting the latest and greatest ! Just received a new BT-359 test unit with 3.2.2 and I'm seeing some improved accuracy multipath handling while driving, no change for pedestrian use though, the MTK 737 still seems better.
mag Posted - 03 déc. 2006 : 18:41:34
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.
cyberas Posted - 28 nov. 2006 : 12:24:00
quote:
Originally posted by BT338again

Hi, I've just received my 2nd BT338 receiver as a replacement for the 1st one that went faulty (wouldn't switch on). My replacement BT338 has got FW GSW3.1.1TO_3.1.00.07-C23P1.00 as reported by Sirfdemo Vers 3.81 The original BT338 had GSW3.1.1LowV 3.1.00.07-C23B1.00 .
Anybody know what the numbers & letters mean in the FW reported by Sirfdemo? and has the design changed much between the 2 Firmwares?

BT338again.



http://www.usglobalsat.com/faq_details/FAQ_BT338.htm#38Q
"38Q) What are the differences between the BT-338_GSW3V3.1.1LowV_F-GPS-03-0506222 vs. BT-338_GSW3.1.1TO_F-GPS-03-0510032?
38A) The difference is we add the RTC time to 1 day, compared with older version 2.5hrs. It will keep the data we stored within 1 day so that no need to do Cold start."
gpspassion Posted - 23 nov. 2006 : 02:51:10
I checked with GS a couple of weeks ago and they said all their GPS receivers shipped out with v3.2 now. No upgrade available.

Just received the latest Royaltek RBT-2110 and it has v3.2.1
cyberas Posted - 22 nov. 2006 : 22:06:13
What about Globalsat BT-338. Did somebody hear about v3.2 firmware for that device?
aaronprez Posted - 17 nov. 2006 : 20:58:51
It seems 3.2 is out there. Below is my email thread with Holux support:

http://www.boccebowl.com/holux.htm

I think I will be sending mine in to get 3.2. Not sure if it will help with WAAS issues, but I am willing to try.
gpspassion Posted - 12 juil. 2006 : 17:21:15
quote:
Originally posted by gpspassion

That's interesting, how did you figure that out ? Is there a way to read FW versions directly in the nüvi ? Wonder if that means that SIF is going to be made available on the nüvi as well, since 3.2 seems to be the FW version needed for that.


Someone kindly forwarded me a reply from Garmin saying that they had currently no plans to implement SIF on the nüvi.

_________________________________________________________________________
Discounts and Assistance/Réductions et Assistance (Club GpsPasSion) / Où commencer?
Oki Posted - 04 juil. 2006 : 12:39:00
The GetSWVer SiRF command does not return the right text string or it is not clear enough. It is definety a failure. The right identification of an item is critical. A FW revision is like model and serial number in a physical product, an error or a discrepancy in this information is considered a major non conformity from the quality point of view.

I work in the aerospace industry and if a quality assessment performed by the Agency finds this problem in an airworthy GPS, the product would be grounded and an investigation would be initiated. I have seen this procedure under similar circumstances when the identification of an item is not clear enough.

It is not critical in a PDA phone but it is still a fault. If an airworthy GPS is affected by this mistake then it can be a problem for the manufacturer and the clients. I am just trying to help.

Regards,
Oki

PD: I have removed bold fonts from names in my previous post. I am sorry about that, I didn't know bold font means call out I thought only uppercase meant that.
gpspassion Posted - 04 juil. 2006 : 12:19:15
hum, why would you call this a "failure", worst case it's just a typo, remember this is text chain, it performs as advertised that's the main thing, and please don't call out names in the forums especially in bold characters, people participate if they feel like it.

_________________________________________________________________________
Discounts and Assistance/Réductions et Assistance (Club GpsPasSion) / Où commencer?
Oki Posted - 04 juil. 2006 : 11:01:59
You are right, under SiRF protocol My Mitac Mio A701 reports FW version:
GSW3.3.0_3.1.00.12-C35ENG-11-02-2005

but under the EMEA protocol it reports FW version:
3.1.00.12.00-MitacGSW3EER00-GSW3.2.0-C35ENG

Which one is the right one?


Carl@SiRF,
Are SiRF going to address this failure or it is Mitac's fault?

Thanks,
Oki
gpspassion Posted - 03 juil. 2006 : 14:38:38
No, no a "typo" in the firmware line, not in your message ! Just a guess as the dates don't make much sense.

_________________________________________________________________________
Discounts and Assistance/Réductions et Assistance (Club GpsPasSion) / Où commencer?
Oki Posted - 03 juil. 2006 : 12:38:22
quote:
Originally posted by gpspassion

Well 3.3 is not bad since no one else has it, actually I wonder if it isn't a "typo" and shouldn't be 3.2.


It is not a typo error from my side (i did a copy-paste) and I hardly believe that the firmware ID had a typo error. You also told that it had the GSW3.3.0 in point 3 of your A701 review.

Maybe Carl@SiRF can clarify this since this revision 3.1.0.12 seems to be an old FW from Nov'05.

Regards,
Oki

GpsPasSion Forums © 2002-2015_GpsPasSion/Manzanite Go To Top Of Page
This page was generated in 1,23 seconds. Powered By: Snitz Forums 2000 Version 3.4.05