| Versions |
  |
|
| Author |
 Topic  |
|
Leif
Sweden
141 Posts |
 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."
|
Edited by - Leif on 03 mai 2005 22:14:17
|
|
|
Ads
|
|
|
gpspassion
93392 Posts |
|
|
Carl@SiRF
USA
158 Posts |
Posted - 11 mai 2005 : 23:32:24
|
Here's a little insight into SiRF version numbers:
2.3.2-GSW2-2.05.024-C1PROD1.0_6A -- the GSW2 means standard SiRFstarII software, and 2.3.2 is the release version number. The 2.05.024 or similar numbers are internal numbers into the engineering data base. C1 is the build variant, a number that varies with each software type, but can relate to flash builds vs. RAM (debug) builds, builds with or without SBAS support (WAAS), builds with one or two serial port support, NMEA or binary protocol default, etc. Prod means this is a released rather than a beta (test) version. 1.00 means the release is without any post-release bug fixes. If there is a letter or letters after the Prod1.00, like Prod1.02b, this would mean that some specific "patches" have been added to provide interim fixes for known bugs. After that, anything on the line is likely added by the manufacturer for internal version control.
A number like 2.4.12.07-XMitac2.0-C1BETA1.1 0000003729 with XMitac2.0 means this is XTrac 2.0 customized by SiRF for Mitac. In general, an X in the number will imply XTrac software, while GSW2 or GSW3 will indicate standard code for SiRFstarII or SiRFstarIII, respectively.
Carl - SiRF Customer Support |
 |
|
|
Server
5 Posts |
Posted - 27 mai 2005 : 23:31:06
|
Is it technically possible to flash firmware via bluetooth interface? Please, comment on this.
It will be very helpful for many users here. Could SiRF partners make more public policy in this therm? Please, help us.
Golbalsat BT-338 + Siemens SX1 |
|
|
|
zven
7 Posts |
Posted - 27 juin 2005 : 21:59:25
|
I remember that it was possible to upgrade my Fortuna Clip-On via Bluetooth.
So it's technically possible. Had Globalsat thought about it?
Fortuna Clip-On + Asus A620bt |
|
|
|
paulkbiba
USA
5064 Posts |
Posted - 27 juin 2005 : 22:08:19
|
It certainly is possible, but if you look at the forums you will see that a lot of people had trouble with doing it and a number of them destroyed their units. The Fortuna experience certainly shows that offering such an option can be a major technical support nightmare and may end up causing more ill will than customer satisfaction.
Moderator
Don't forget the GPSPassion Club! |
|
|
|
dreamie
Sweden
27 Posts |
Posted - 06 juil. 2005 : 14:49:30
|
| Does anyone know if it is possible to upgrade Globalsats BT-338 ? |
|
|
|
gpspassion
93392 Posts |
|
|
Ginosergio
6 Posts |
Posted - 27 juil. 2005 : 14:49:37
|
I have read on various places, that Holux 236 is flashable with new firmwares. Someone has info ? Someone bought it ?
Carl@Sirf, it's really an "end user" job ?? Where do we get new firmwares ? Are they the same for every brand... ? Eg: Sirf 3.1.1 for BT-338 is the same "file" as Sirf 3.1.1 for Holux 236 ???
Thanks ! |
|
|
|
Pedro-G
27 Posts |
Posted - 01 août 2005 : 14:45:32
|
| BuyGPSnow seem to be shipping their new Globalsat BT-338 units with the latest 3.1.1 firmware. |
|
|
|
duco67
Italy
6 Posts |
Posted - 04 août 2005 : 16:15:25
|
To Carl@SiRF (sorry for so many questions  ):
How is it possible to know the firmware version of the SiRFStar III chipset for the GlobalSat BT-338 (i.e.: how can I read the version having a Globalsat BT-338)?
Build with two serial port means you can connect on the same time via Bluetooth up to two device (e.g. PDA+cellular phone), or what else?
Is the SiRFStar III chipset DGPS ready? I mean not only using SBAS, but also a serial I/O for RTCM 2.x data (using the 2nd serial port)?
What about the possibility to update firmware versions via Bluetooth?
Thank You in advance.
duco67 |
|
|
|
gpspassion
93392 Posts |
|
|
Squaredancer
284 Posts |
Posted - 10 août 2005 : 03:15:01
|
Copied from the buygpsnow.com website about the list of changes going to V3.1.1, Paul said:
"> Corrects potential cold start visible list problem, which could affect performance if all satellites are below 32 db-Hz
> Limits the 50 BPS thresholds to 27 to avoid undetected parity errors, which can give position errors."
Does the 1st one mean that low signal performance is enhanced or degraded if all signals are below 32db??
No. 2, What are the talking about by reducing 50BPS thresholds to 27? |
|
|
|
gpspassion
93392 Posts |
Posted - 10 août 2005 : 03:25:15
|
Well 50bps could stand for 50 bits per second which is the normal speed of the navigation data (almanach, ephemeris) transmission from a GPS satellite, so I guess adjusting the rate on the receiver can influence the amount of data transferred over a given period of time, maybe Carl can pitch in but this is probably a bit over all of our heads ;-)
_________________________________________________________________________
Discounts and Assistance/Réductions et Assistance (Club GpsPasSion) / Où commencer? |
|
|
|
Squaredancer
284 Posts |
Posted - 10 août 2005 : 03:48:32
|
What about the first question:
"> Corrects potential cold start visible list problem, which could affect performance if all satellites are below 32 db-Hz"
Does it mean that low signal performance is enhanced or degraded if all signals are below 32db?? |
|
|
|
IIB
8 Posts |
Posted - 28 août 2005 : 03:56:44
|
quote:
Originally posted by Squaredancer
What about the first question:
"> Corrects potential cold start visible list problem, which could affect performance if all satellites are below 32 db-Hz"
Does it mean that low signal performance is enhanced or degraded if all signals are below 32db??
Yo all,
Here's the full quote from US Globalsat on SiRF 3.1.1:
Per US Globalsat, here are the list of improvements for version 3.1.1:
-> Allow the SiRF III chipset to be WAAS capable and activated via the “SiRF DEMO” utility software. *
-> Corrects potential message error in acquisition, which could result in no navigation data and also improves bit sync capability and recovery mode. (This error can cause fix problems from reacquisition after a blockage from receiving data also know as the ‘jet-lag” symptom).
-> Corrects cold start frequency search range problem, where frequency was not searched properly after 30 seconds.
-> Corrects potential cold start visible list problem, which could affect performance if all satellites are below 32 db-Hz
-> Corrects Message “41” datum field.
-> Corrects date stamp not updating.
-> Limits the 50 BPS thresholds to 27 to avoid undetected parity errors, which can give position errors.
In order to demodulate the 50 bps navigation message stream during satellite tracking, the receiver must have a pretty good phase lock on the carrier - the worse the phase tracking accuracy, the more data bit errors can be expected. At the normally received power levels of the C/A code into a 0 dBic antenna (no gain - or loss antenna) the phase lock/Costas tracking loop of the receiver loses phase lock at about 25 dB C/No. Adding 2 dB to this level gives about an order of magnitude (10 times) better bit error rate.
The 32 dB-Hz C/No is apparently the low limit for a high probability acquisition with large uncertainties (a "cold start"). To acquire a signal the receiver has to search for the signal in both frequency and time, at each point in the search it has to "dwell" at the frequency and time being searched to recover the signal (if the signal is at that frequency and time). For a weak signal (apparently below 32 dB-Hz) the reciver must dwell to long to meet the TTFF and or ther is a low probability of detecting the signal for the fixed dwell time.
Hope this helps,
IIB |
|
|
|
Topic |
|
|
|
| This page was generated in 2,12 seconds. |
 |
|
- 
- 
Firmware versions of SiRF based receivers
