Hello,

I have the following issue:
my GPS has an internal flash to store the navcore & maps.

now this has "died" meaning sometimes it comes back alive and works for couple of monthes then dies again.
to resolve this i want to completely remove the "boot from internal flash" because when i start my GPS now.
it displays the boot image( tomtom ) then tries to start internal flash - fails , you see the loading screen of SD-card loading | also hangs on that some times because he wants to still start from internal flash.

so i want to remove the entry boot from flash , from the bootloader or boot.ini (if that exists)

or is there an easy fix to this ?

if there is a re-soldering fix to revive the flash forever. i'm also willing :)

please ask questions if something is unclear.

thanks in advance

Xtremegamer

Start by reading in our tutorial section and with a clean install of Navcore and map.
Instructions can be found in the corresponding threads.

xtremegamer wrote:to resolve this i want to completely remove the "boot from internal flash" because when i start my GPS now.
it displays the boot image( tomtom ) then tries to start internal flash - fails , you see the loading screen of SD-card loading | also hangs on that some times because he wants to still start from internal flash.
so i want to remove the entry boot from flash , from the bootloader or boot.ini (if that exists)

The bootloader is not your problem. It will not cause a device to sometimes boot & other times not boot.
You can not do what you are proposing. The bootloader is flashed into the 64 MB RAM memory, which you have no access to.
If this issue occurs with a complete setup (navcore & map) on the internal memory, as well as a complete setup (navcore & map) on a SD card, which becomes the default setup when inserted, then you have other issues.

Please run TomTom Current Configuration {13.11.2011}. Post the results here. Specify whether the results are from the internal or SD card.

Hello,
thanks for the fast reponse
i'll include the following :

I have a fully working setup on SD.

the internal memory is inaccessible via windows (shows drive but no disk (0Mb available)).

the unit seems to struggle with this because cold boot takes a long time to actually boot from SD.

ttgo.bif

Code: Select all

DeviceName=TomTom GO 720
DeviceVersionHW=GO 720
RamDiskVersion=20120927
BootLoaderVersion=10012
LinuxVersion=1000
ApplicationVersionVersionNumber=9465
ApplicationVersion=1074274.1


install.bif

Code: Select all

[TomTomGo]
RamDiskVersion=20120927
BootloaderTarget=s3c24xx
Bootloaderversion=5.5279
LinuxVersion=842337
ApplicationVersion=1074274


i understand your explanation of the bootloader as i suspected this is not modifyable directly.

i just want to know if there's way to either revive the internal memory or set SD-card as first boot device to put it in bios talk (i know its not the same ).
just want to know how this exactly determins where to start from.

please advice if this can be fixed , if not how i can put SD as first boot device.

Thanks in advance

xtremegamer wrote:i just want to know if there's way to either revive the internal memory or set SD-card as first boot device to put it in bios talk (i know its not the same ).
just want to know how this exactly determins where to start from.

please advice if this can be fixed , if not how i can put SD as first boot device.

This is addressed in line 3 of post 3.

tendriver wrote:This is addressed in line 3 of post 3.

Is there a way to know what slows down the process of switching to SD boot ?

Thanks in advance

xtremegamer wrote:the process of switching to SD boot?

I don't understand what you mean by "the process of switching to SD boot".

1 thing that I noticed is the ttgo.bif bootloader reads 1.0012 & the install.bif (whatever that is), reads 5.5279

We can either try to help - that means you follow the team instructions,
ot we can just play around and run in circles - thats what you do with your questions ;)