You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've got an "old" TomTom Go (4N00.004) which is still working but the maps start becoming outdated. Hence, I was gladly surprised when I found Navit and NavitTom! I know TomTom Go is not the same as TomTom Go V2 in which NavitTom apparently works.
I can build the whole NavitTom bundle and copy ttsystem and opentom_dist/ to a 256 MB SD card with a FAT32 type partition. It boots, displays the calibration screen, allows me to calibrate the screen and then gets stuck on VFAT something (very small characters) telling something about "8.3 filenames" and "long filenames". This is right after detecting and configuring Bluetooth!
I'm copying both ttsystem and opentom_dist/ (renaming it to opentom) to a newly formatted SD card. However, it is not the original TomTom SD card which is FAT16 and has an MBR (and probably a bootloader). The instructions on docs/README_ext2_and_swap_config.txt seem to be a little out of date and although they are meant to use a swap partition on devices with 32M of RAM they are not clear on many aspects (like partitioning, etc).
My question is: is NavitTom stalled or is someone still developing it? If so I can provide more details on the point of failure and try to sort out how to make NavitTom run on TomTom One!
The text was updated successfully, but these errors were encountered:
I've got an "old" TomTom Go (4N00.004) which is still working but the maps start becoming outdated. Hence, I was gladly surprised when I found Navit and NavitTom! I know TomTom Go is not the same as TomTom Go V2 in which NavitTom apparently works.
I can build the whole NavitTom bundle and copy ttsystem and opentom_dist/ to a 256 MB SD card with a FAT32 type partition. It boots, displays the calibration screen, allows me to calibrate the screen and then gets stuck on VFAT something (very small characters) telling something about "8.3 filenames" and "long filenames". This is right after detecting and configuring Bluetooth!
I'm copying both ttsystem and opentom_dist/ (renaming it to opentom) to a newly formatted SD card. However, it is not the original TomTom SD card which is FAT16 and has an MBR (and probably a bootloader). The instructions on docs/README_ext2_and_swap_config.txt seem to be a little out of date and although they are meant to use a swap partition on devices with 32M of RAM they are not clear on many aspects (like partitioning, etc).
My question is: is NavitTom stalled or is someone still developing it? If so I can provide more details on the point of failure and try to sort out how to make NavitTom run on TomTom One!
The text was updated successfully, but these errors were encountered: