Thread: TomTom News & Announcements

biggerdave thanks for info and it looks like I will have to bin my GO910 because I tried the navcore supplied and even with the patch system file it will not boot further then the splash screen

Try the format on another computer, or try it short after a reboot of your own computer
Forget Home, you don't need it realy, just handle your device like an extra HDD

From:
1) wrong navcore update through TTHome,
2) wrong format of my TT XXL IQ navi

now receiving a Flashing Red X .

I made:

1) format to FAT 32
2) install through TTHome the first map of the device 8.70 and all the other updates.

the problem remains.

After:
1)I deleted all the files

2) copy all the files i had from an old backup of map 9.90

3) Run fastactivate

the problem remains .Receiving always a Flashing Red X .

Can someone help me

Could it be that the new Navcore had a file with the name system ?
It's likely that your bootloader it not working properly
You need a specilal Navcore to restore the original bootloader
You've to start from bootlader 0.001 to which you like
Mind your mailbox, if it work here I'm not quite sure about that

I did everything you said and my xxl now works with navcore 9.51 as before.

When i began,after the procedure you showed me, to use F/A and update meta txt it appeared that tt go bif or tt go navigation is missing. Then I copied and pasted from my backup files an archive with the name ttgo.iso(bif) and now everything works fine.
Flashing Red X dissapeared.
Also I put the file with the voices and everything is ok.

For those who may also have to deal with this problem, here are the steps taken

Just use Fastactivate or mine A_F_Activate, both are using that tool.
Connect to your pc so you're able to see your device as an extra drive
Copy the Navcore to your device
Reboot the divice

I didn't test it, but already some other did succesfully
When your device will start
Copy than bootloader 0.0001to your device the name is system
Boot again
When it start copy the next bootloader 5.5128 to your system and boot your system again.
If all went into the right way you may install any other Navcore which you like

But mind you, check if the Navcore has a file in it with the name system, remove it at once
When the version of that system file is higher than 5.5128 it will be installed as an upgrade, do this only when you want it

To downgrade follow the same steps and start again with bootloader 0.0001 and so on

Originally Posted by biggerdave

See this:- [Only registered and activated users can see links. ] and in more general detail:-
What’s the Key Issue?
The Global Positioning System provides accurate timing information to many of our critical systems – power grid, communications, financial markets, emergency services, and industrial control to name a few. It also includes the ability to transmit the proper date and time to a receiver by supplying the receiver with the current week and the current number of seconds into the week. This allows the receiver to translate the date and time into a more typical format – day, month, year, and time of day.
However, the field that contains the week number is a 10-bit binary number. This limits the range of the week number to 0 – 1023, or 1024 total weeks.
GPS week zero started January 6, 1980. The 1024 weeks counter ran out and rolled over on August 21, 1999. The week counter then reset to zero, and it has been recounting ever since. The next time the counter will reach week 1023 and rollover to zero is on April 6, 2019.

Should I Be Concerned?
Because this it is the second time the GPS week rollover will occur, many receiver manufacturers have prepared for it, and newer receivers will continue to operate without issue.
You should be concerned, though, if either of the following applies:

Receiver has been fielded for more than 10-15 years without firmware updates
Receiver is a core component of a critical timing system – ask yourself – what is the impact to my system if the GPS receiver stopped operating or put out wrong GPS or UTC information

In these cases, we want to verify that an issue will not occur. At a minimum, we recommend consulting your receiver manufacturer to confirm that the issue has been fully tested and will not occur. Many manufacturers have already issued compliance statements, and we expect them to continue to do so over the next year, up until the event occurs. To be sure that your system will not experience any failures related to this issue

----------------------------------------------------------------------------------

Further details (credit Entwood from another forum), and I quote:-

Talking to someone who knows a lot more than me about GPS and this "possible" problem... and he tells me that what TT are saying is probably a load of rubbish !!

Apparently the end of the epoch Week Number Rollover is exactly what it says ... it is a WEEK NUMBER rollover ... so the only devices that are affected are those that use/calculate "weeks" and utilise the "week number" index !!

As most SatNavs don't even use date/day information but simply use "time" then they will NOT be affected !!

He sent me to this site to show me that he wasn't talking rubbish, and sure enough, down the bottom is this little crumb of information ..

[Only registered and activated users can see links. ]

"This situation won’t affect a receiver’s ability to navigate and/or calculate precise time, but it has the potential to create week, month and year timestamps that are wildly wrong. Applications which rely on GPS data at that level may be seriously affected."

So to summarise, maybe TT are just over-reacting? Time will tell of course!