Difference between revisions of "Tomtom ONE IQ Routes"

From YobiWiki
Jump to navigation Jump to search
m (Reverted edits by Etegohy (Talk) to last revision by PhilippeTeuwen)
 
(31 intermediate revisions by the same user not shown)
Line 89: Line 89:
 
<br>After the Tomtom was plugged and software was installed, Windows wanted to reboot because of a new driver installed, typical...
  
<br>After the Tomtom was plugged and software was installed, Windows wanted to reboot because of a new driver installed, typical...
   
  +
==Software Upgrades==
−
==Misc==
  
−
===Software===
 +
===8.414===
  +
So I finally connected the device to a Windows box and let it upgrade whatever it wanted (you don't need to login to do that apparently).
  +
<br>The [http://www.tomtom.com/6141 changelog] didn't show yet what were the improvements
  +
<br>Now it shows (for what changed):
  +
<pre>
  +
App 8.414 (1239/090707) OS : 320300
  +
GPS v1.20, Boot 5.5130
  +
</pre>
  +
  +
===Latest Map Guarantee===
  +
I was a bit surprised that even after having linked my device with my account it proposed to buy map updates while I was supposed to get them for free the first time.
  +
<br>Then I discovered the menu option Tools -> Use Latest Map Guarantee -> Get it now
  +
<br>Note that you can only use it once and only in the first sth (3 months?) after having bought it.
  +
  +
See below for the failure I had after an update, it worked better when I removed first the old map (but beware it also removes your favorites etc so make a backup first!)
  +
  +
New map was 200Mb larger but it came with... 200Mb of cspeech_XXX.dat files which are probably the TTS data, useless for my model so I can probably remove them.
  +
  +
==Applications==
  +
===Links===
 
Beware it's maybe compatible only with previous Tomtom One versions!!
  
Beware it's maybe compatible only with previous Tomtom One versions!!
 
* http://home.comcast.net/~spheasant1/3rd_party.html
  
* http://home.comcast.net/~spheasant1/3rd_party.html
 
* http://www.tomtomax.fr/index.html
  
* http://www.tomtomax.fr/index.html
  +
* http://www.webazar.org/tomtom/plugins.php
  +
* http://gps.dg4sfw.de/
   
  +
===TTconsole===
  +
[http://www.opentom.org/TomTom_Console TTconsole], to get virtual keyboard, click on upper right corner (but extreme right was inactive on my setup, I've to click sth like 5mm away from the right border.
  +
<br>Keyboard is qwertz, argh. ( > is shift+<, / is shift+7, = is shift+0)
  +
  +
====uname -a====
  +
Linux (none) 2.6.13-tt320300 #1 Tue Jul 7 15:25:59 CEST 2009 armv5tejl unknown
  +
====/proc/cpuinfo====
  +
<pre>
  +
Processor : ARM926EJ-Sid(wb) rev 5 (v5l)
  +
BogoMIPS : 131.48
  +
Features : swp half thumb fastmult edsp java
  +
CPU implementer : 0x41
  +
CPU architecture: 5TEJ
  +
CPU variant : 0x0
  +
CPU part : 0x926
  +
CPU revision : 5
  +
Cache type : write-back
  +
Cache clean : cp15 c7 ops
  +
Cache lockdown : format C
  +
Cache format : Harvard
  +
I size : 8192
  +
I assoc : 4
  +
I line length : 32
  +
I sets : 64
  +
D size : 8192
  +
D assoc : 4
  +
D line length : 32
  +
D sets : 64
  +
  +
Hardware : TomTom GO
  +
Revision : 0011
  +
Serial : 0000000000000000
  +
</pre>
  +
====dmesg====
  +
<pre>
  +
04 Simtec Electronics
  +
Detected type 34, name TomTom ONE IQ Routes Edition
  +
On node 0 totalpages: 16384
  +
DMA zone: 16384 pages, LIFO batch:7
  +
Normal zone: 0 pages, LIFO batch:1
  +
HighMem zone: 0 pages, LIFO batch:1
  +
CPU0: D VIVT write-back cache
  +
CPU0: I cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
  +
CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
  +
Built 1 zonelists
  +
Kernel command line: console=/dev/null quiet
  +
irq: clearing subpending status 00000406
  +
irq: clearing subpending status 00000002
  +
PID hash table entries: 512 (order: 9, 8192 bytes)
  +
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
  +
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
  +
Memory: 64MB = 64MB total
  +
Memory: 54784KB available (2026K code, 415K data, 92K init)
  +
Calibrating delay loop... 131.48 BogoMIPS (lpj=328704)
  +
Mount-cache hash table entries: 512
  +
CPU: Testing write buffer coherency: ok
  +
unpacking initramfs... done
  +
Freeing initrd memory: 7168K
  +
NET: Registered protocol family 16
  +
S3C Power Management, (c) 2004 Simtec Electronics
  +
S3C2412: Initialising architecture
  +
S3C2412: IRQ Support
  +
S3C2412: Clock Support, UPLL 96.000 MHz
  +
S3C24xx CpuFrequency Scaling (DVS), (c) 2008 TomTom B.V.
  +
SCSI subsystem initialized
  +
usbcore: registered new driver usbfs
  +
usbcore: registered new driver hub
  +
Bluetooth: Core ver 2.7
  +
NET: Registered protocol family 31
  +
Bluetooth: HCI device and connection manager initialized
  +
Bluetooth: HCI socket layer initialized
  +
S3C DMA Driver, (c) 2003-2004 Simtec Electronics
  +
DMA channel 0 at c4800000, irq 33
  +
DMA channel 1 at c4800040, irq 34
  +
DMA channel 2 at c4800080, irq 35
  +
DMA channel 3 at c48000c0, irq 36
  +
ngffs: init_ngffs_fs: NGFFS initializing
  +
TomTom GO Backlight S3C, (C) 2007 TomTom BV
  +
Activate backlight_en
  +
TomTom GO Framebuffer Driver, (C) 2005 TomTom BV
  +
ttgfb: ttgfb_alloc: Using LFB from bootloader (reserved memory).
  +
S3C2410 RTC, (c) 2004 Simtec Electronics
  +
s3c2410-rtc s3c2410-rtc: rtc disabled, re-enabling
  +
S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics
  +
S3C2412 EVT3 Watchdog Workaround, (c) 2006 TomTom
  +
S3C24XX Internal Flash poweroff workaround, (c) 2008 TomTom
  +
TomTom GO Hardware Detection Driver, (C) 2004,2005 TomTom BV
  +
TomTom GO ADC Driver, (C) 2004-2007 TomTom BV
  +
TomTom GO S3C24XX Generic ADC Driver, (C) 2007 TomTom BV
  +
TomTom GO GPIO Driver, (C) 2004,2005 TomTom BV
  +
gpio_hw_init: UART 'ttySAC0' => 0
  +
TomTom GO Accelerometer Driver, (C) 2004,2005 TomTom BV
  +
TomTom GO Battery Driver, (C) 2004,2005,2006,2007 TomTom BV
  +
TomTom GO GPS Driver, (C) 2004,2005 TomTom BV
  +
TomTom GO Touchscreen Input Driver, (C) 2007 TomTom BV
  +
Done
  +
CoolSound engine, (C) 2004,2005 TomTom BV
  +
dma2: IRQ with no loaded buffer?
  +
CoolSound: sound_dma_init: Buffers allocated and associated.
  +
reallocating sound DMA buffer (previous:0 new:4096 allocating:65536)
  +
reallocating sound DMA buffer (previous:0 new:4096 allocating:65536)
  +
iis2410: iis_init: Current clock rate: 66000000
  +
TomTom GO Buzzer Driver, (C) 2006 TomTom BV
  +
TomTom GO Gyro Driver, (C) 2007 TomTom BV
  +
TomTom GO Legacy USB mode detect, (C) 2007 TomTom BV (usbmode:)
  +
usbmode: Probing
  +
usbmode: Initialized
  +
usbmode: register_usbmode_driver
  +
TomTom S3C24XX USB mode driver, (C) 2007 TomTom BV (s3c24xx_usbmode:)
  +
TomTom GO Buspower monitor, (C) 2007 TomTom BV (buspower:)
  +
buspower: buspower_probe
  +
Done
  +
Valencia/Murcia dock driver - v1.0
  +
Cagliari dock driver - v1.0
  +
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
  +
s3c2412-uart.0: s3c2410_serial0 at MMIO 0x50000000 (irq = 70) is a S3C2412
  +
s3c2412-uart.1: s3c2410_serial1 at MMIO 0x50004000 (irq = 73) is a S3C2412
  +
s3c2412-uart.2: s3c2410_serial2 at MMIO 0x50008000 (irq = 76) is a S3C2412
  +
io scheduler noop registered
  +
io scheduler deadline registered
  +
RAMDISK driver initialized: 16 RAM disks of 7168K size 1024 blocksize
  +
PPP generic driver version 2.4.2
  +
PPP Deflate Compression module registered
  +
PPP BSD Compression module registered
  +
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
  +
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
  +
TomTom GO IDE Driver, (C) 2004,2005 TomTom BV
  +
physmap flash device: 80000 at 0
  +
Found: EON EN29LV400BB
  +
number of JEDEC chips: 1
  +
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
  +
s3c2410-ohci s3c2410-ohci: S3C24XX OHCI
  +
s3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1
  +
s3c2410-ohci s3c2410-ohci: irq 42, io mem 0x49000000
  +
hub 1-0:1.0: USB hub found
  +
hub 1-0:1.0: 2 ports detected
  +
usbcore: registered new driver hiddev
  +
usbcore: registered new driver usbhid
  +
drivers/usb/input/hid-core.c: v2.01:USB HID core driver
  +
usbcore: registered new driver usbserial
  +
drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0
  +
drivers/usb/serial/usb-serial.c: USB Serial support registered for CP2101
  +
usbcore: registered new driver CP2101
  +
drivers/usb/serial/cp2101.c: Silicon Labs CP2101/CP2102 RS232 serial adaptor driver v0.04
  +
s3c2412-i2c s3c2412-i2c: slave address 0x08
  +
s3c2412-i2c s3c2412-i2c: bus frequency set to 375 KHz
  +
s3c2412-i2c s3c2412-i2c: i2c-0: S3C I2C adapter
  +
Bluetooth: HCI USB driver ver 2.8
  +
usbcore: registered new driver hci_usb
  +
Bluetooth: HCI UART driver ver 2.1
  +
Bluetooth: HCI H4 protocol initialized
  +
Bluetooth: HCI BCSP protocol initialized
  +
Trying to set irq type for IRQ-1
  +
s3c-sdi: probe: mapped sdi_base=f1200000 irq=83 irq_cd=4294967295 dma=0.
  +
s3c-sdi: initialization done.
  +
S3C2410 GPIO SPI Driver
  +
registering c02234dc: scp1000-baro
  +
TomTom GO SCP1000 Barometer Driver, (C) 2007 TomTom BV
  +
scp1000-baro: Missing platform data!
  +
registering c0223508: kxr94-gadc
  +
NET: Registered protocol family 2
  +
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
  +
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
  +
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
  +
TCP: Hash tables configured (established 4096 bind 4096)
  +
TCP reno registered
  +
TCP bic registered
  +
NET: Registered protocol family 1
  +
Bluetooth: L2CAP ver 2.7
  +
Bluetooth: L2CAP socket layer initialized
  +
Bluetooth: SCO (Voice Link) ver 0.4
  +
Bluetooth: SCO socket layer initialized
  +
Bluetooth: RFCOMM ver 1.5
  +
Bluetooth: RFCOMM socket layer initialized
  +
Bluetooth: RFCOMM TTY layer initialized
  +
Bluetooth: HIDP (Human Interface Emulation) ver 1.1
  +
usbmode: usbmode_late_init
  +
s3c24xx_usbmode: helper_disable_host_port
  +
s3c24xx_usbmode: s3c24xx_initial_to_idle
  +
s3c24xx_usbmode: idle_enter SUCCESS
  +
Freeing init memory: 92K
  +
Warning: unable to open /dev/console as initial console, res=-19.
  +
s3c24xx_usbmode: buspower_changed POWER EVENT
  +
usbmode: USB power off while in idle mode. (not expected)
  +
usbmode:[1,1] USB_STATE_IDLE==(USB_EVENT_POWER_OFF) NOP
  +
mmcblk0: mmc0:0001 AKG00M 2007040KiB
  +
mmcblk0: p1
  +
FAT: free clusters recounted: 94354
  +
FAT: filesystem 32 bits
  +
gps: gps_ioctl: WARNING: Ignoring IOW_GPS_OFF
  +
selected clock c022f084 (pclk) quot 428, calc 9600
  +
selected clock c022f084 (pclk) quot 34, calc 115183
  +
PORT_S3C2412 impossible RTS gpio mapping for port 1
  +
gps: gps_ioctl: WARNING: Ignoring IOW_GPS_ON
  +
selected clock c022f084 (pclk) quot 428, calc 9600
  +
selected clock c022f084 (pclk) quot 70, calc 57591
  +
selected clock c022f084 (pclk) quot 106, calc 38394
  +
selected clock c022f084 (pclk) quot 213, calc 19197
  +
selected clock c022f084 (pclk) quot 34, calc 115183
  +
selected clock c022f084 (pclk) quot 70, calc 57591
  +
selected clock c022f084 (pclk) quot 428, calc 9600
  +
selected clock c022f084 (pclk) quot 428, calc 9600
  +
selected clock c022f084 (pclk) quot 70, calc 57591
  +
selected clock c022f084 (pclk) quot 106, calc 38394
  +
selected clock c022f084 (pclk) quot 213, calc 19197
  +
selected clock c022f084 (pclk) quot 34, calc 115183
  +
selected clock c022f084 (pclk) quot 70, calc 57591
  +
selected clock c022f084 (pclk) quot 428, calc 9600
  +
</pre>
  +
====ps====
  +
<pre>
  +
PID Uid VmSize Stat Command
  +
1 root 652 S /bin/sh /init
  +
2 root SWN [ksoftirqd/0]
  +
3 root SW< [events/0]
  +
4 root SW< [khelper]
  +
5 root SW< [kthread]
  +
25 root SW< [kblockd/0]
  +
28 root SW< [khubd]
  +
82 root SW [pdflush]
  +
83 root SW [pdflush]
  +
85 root SW< [aio/0]
  +
84 root SW [kswapd0]
  +
154 root SW [mtdblockd]
  +
176 root SW< [kmmcd]
  +
182 root SW< [s3c24xx-spi-gpi]
  +
185 root SW< [krfcommd]
  +
192 root SW< [mmcqd]
  +
273 root 572 S syslogd -C -S
  +
280 root 404 S launchserver /var/run/launchsock
  +
375 root 1480 S /bin/glgps normal
  +
379 root 560 S /bin/ttpnpd
  +
382 root 652 S /bin/sh /init
  +
393 root 26648 R /bin/ttn
  +
396 root 26648 S /bin/ttn
  +
397 root 26648 S < /bin/ttn
  +
398 root 572 S /bin/sh /mnt/sdcard/TTconsole/TTconso
  +
399 root 540 S ./TTconsole/TTconsole
  +
400 root 708 S /bin/sh
  +
402 root 676 R ps ax
  +
</pre>
  +
====df====
  +
<pre>
  +
Filesystem 1k-blocks Used Available Use% Mounted on
  +
mtd0 256 4 252 2% /mnt/flash
  +
/dev/mmcblk0p1 2001868 1624408 377460 81% /mnt/sdcard
  +
</pre>
  +
====/mnt/flash====
  +
<pre>
  +
drwxr-xr-x 1 root root 0 Apr 9 2000 .
  +
drwxr-xr-x 5 root root 0 Jan 1 1970 ..
  +
drwx------ 1 root root 0 Aug 29 23:28 extra_settings
  +
-rw-r--r-- 1 root root 13 Apr 9 2000 restore1.dat
  +
-rw-r--r-- 1 root root 926 Jan 1 2000 settings.dat
  +
dr-xr-xr-x 1 root root 0 Jan 1 1970 sysfile
  +
-rw-r--r-- 1 root root 20 Jan 1 2000 testfile
  +
-rw-r--r-- 1 root root 4 Jan 1 2000 ttsys.dta
  +
</pre>
  +
  +
===[http://www.opentom.org/TTTracklog TTTracklog]===
  +
And the extension with stop button
  +
===[http://www.opentom.org/Height Height]===
  +
As I've a small screen I had to edit Height/height.cfg -> d7 & n7
  +
  +
==Misc==
 
===Reset===
  
===Reset===
 
* Be sure the battery is full, leave it charging for at least 2 hours with the loading green LED turned on.
  
* Be sure the battery is full, leave it charging for at least 2 hours with the loading green LED turned on.
Line 100: Line 386:
   
 
===Backup===
  
===Backup===
  +
====full backup, partition image====
 
It's very important to make a first backup of your Tomtom as soon as possible as I got my first problem very soon, see below.
  
It's very important to make a first backup of your Tomtom as soon as possible as I got my first problem very soon, see below.
 
<br>To make the backup under Linux, ideally do it as very first time even before turning it on so you'll have the very initial image (change /dev/sdb to your own device):
  
<br>To make the backup under Linux, ideally do it as very first time even before turning it on so you'll have the very initial image (change /dev/sdb to your own device):
Line 125: Line 412:
 
unlabeled,
 
unlabeled,
 
FAT (16 bit)
  
FAT (16 bit)
  +
====full backup, on file basis====
−  
−
I didn't do it like that, rather my device was automounted after I configured it so I copied the whole file structure manually to a ext3 partition. This was still ok to save my device when it crashed.
 +
Actually I didn't do it like that, rather my device was automounted after I configured it so I copied the whole file structure manually to a ext3 partition. This was still ok to save my device when it crashed.
 
<br>FYI a few files were already created/modified after the initial setup and usage:
  
<br>FYI a few files were already created/modified after the initial setup and usage:
   
Line 141: Line 428:
 
-rwxr-xr-x 1 phil phil 68 2009-08-29 18:19 UserPatch.dat
  
-rwxr-xr-x 1 phil phil 68 2009-08-29 18:19 UserPatch.dat
   
−
===Filesystem failure!!!===
 +
====inc backup====
  +
Sometimes you want to see exactly those files who changed since last time (e.g. you added voices, POI,...)
−
Well it didn't take long to have the first troubles:
  
  +
<br>You can copy the files from the Tomtom fs to have a first full backup (but not a partition image)
  +
<br>Then make from time to time other backups (without the big map files if you didn't change maps, to get quicker).
  +
<br>Then run dupemap from magicrescue to keep only the files which have changed since the initial backup:
  +
dupemap -d tomtom-fs.orig.map scan tomtom-fs.orig
  +
dupemap -d tomtom-fs.orig.map delete,report tomtom-fs.incremental
  +
Then prune empty directories:
  +
<br>Execute several times the following until you don't have error messages:
  +
find . -type d -empty -exec rm -r {} \;
  +
  +
===Files===
  +
* Favorites:
  +
** <map-subdir>/MapSettings.cfg
  +
* Map corrections by user:
  +
** <map-subdir>/MapUserPatch.dat
  +
* POI:
  +
** <map-subdir>/<POIname>.bmp
  +
** <map-subdir>/<POIname>.ov2
  +
** poi/<POIname>.tlv
  +
* Voices:
  +
** voices/data<NN>.bmp
  +
** voices/data<NN>.chk
  +
** voices/data<NN>.tlv
  +
** voices/data<NN>.vif
  +
  +
More info [http://www.ipmart-forum.com/showthread.php?t=252073 here]
  +
* for /text, [http://www.yournav.com/forum/index.php?s=42927de1fdab16a6b296735c51c87fda&showtopic=10413&st=0&p=88317&#entry88317 here]
  +
  +
[http://create.tomtom.com/manuals/create-your-own-content/ How to create your own content]: POI, voice, images, colour schemes, routes & map overlays
  +
  +
===QuickGPSfix===
  +
I was surprised my QuickGPSfix was not updated anymore at a point in time, I don't remember how it happened.
  +
<br>The solution I found was to restore the old QuickGPSfix file I had from Tomtom Home application (Add traffic, Voices etc -> More -> More -> More -> items on my computer -> QuickGPSfix Data) then trigger "Update my ONE"
  +
===Speed cameras===
  +
* http://radars.bnet.be ?
  +
* [http://forum.astel.be/showthread.php?t=47864 on Astel], integrated into [http://www.poiedit.com/downloads.htm POIedit]
  +
  +
==Failures!==
  +
  +
===Filesystem failure!===
  +
Well it didn't take long to have the first troubles, it happened before I did anything strange like adding applications or whatever:
 
<br>I accidentally hitted the radar report (three clicks as same place on screen on the quick menu is all you need :( ) and wanted to remove it manually before connecting my Tomtom online. So I mounted the device under linux again and started a big "diff -Naur".
  
<br>I accidentally hitted the radar report (three clicks as same place on screen on the quick menu is all you need :( ) and wanted to remove it manually before connecting my Tomtom online. So I mounted the device under linux again and started a big "diff -Naur".
 
<br>Then I discovered that there were strange new files in a subdirectory and when I started deleting those files I got a "read-only device" error.
  
<br>Then I discovered that there were strange new files in a subdirectory and when I started deleting those files I got a "read-only device" error.
Line 173: Line 500:
 
Disk label is apparently empty now.
  
Disk label is apparently empty now.
   
  +
===Infinite reboot after map update===
−
===Upgrade===
  
  +
After a "Latest Map Guarantee" update, the device never rebooted properly, sticking on Tomtom logo :(
−
So I finally connected the device to a Windows box and let it upgrade whatever it wanted (you don't need to login to do that apparently).
  
  +
<br>I tried to reset it, keeping power button pressed, and got green screen (like if you fire only the green sub-pixels).
−
<br>Then back on Linux I made another backup without the big map files to get quicker, then I ran dupemap from magicrescue to keep only the files which have changed since my initial backup:
  
  +
<br>Back on computer, connection with Tomtom HOME was fine.
−
dupemap -d tomtom-fs.almost.orig.map scan tomtom-fs.almost.orig
  
  +
<br>I noticed that size of the map in "items on device" was still the size of the previous smaller map.
−
dupemap -d tomtom-fs.almost.orig.map delete,report tomtom-fs.20090901
  
  +
<br>So I chose to delete the map from the device then tried again the map update and then it finally worked again.
  +
<br>Deletion of the "previous" map deleted also my map favorites.
  +
  +
When I tried to reinstall the backup of MapSettings.cfg it failed again so apparently that was the cause of the problem.
  +
<br>I reinstalled the "empty" MapSettings.cfg that came with the Latest Map Guarantee update and it worked fine again.
  +
  +
So now how to re-import my old favorites (& home address BTW)?
  +
  +
Googling...
  +
* [http://www.wolfkettler.co.uk/blog/tomtom-map-update-bug/ This blog] explains exactly the same issue, apparently an incompatibility between old mapsettings.cfg and new maps. <br>Her suggestion is to use POI to store favorites, mmm...
  +
* [http://www.tomtomforums.com/tomtom-go-630-720-720t-730-730t-740/16385-favorites-restore-question.html A solution] is proposed on this forum:
  +
** Copy again MapSettings.cfg to the device
  +
** Launch Tomtom HOME
  +
** Choose to operate your device remotely (this takes time to start)
  +
** Now on your remote Tomtom screen, add a favorite & delete it, this "fixes" the file
  +
** Now problem should be fixed, you're back with your favorites!
  +
  +
In the operation of deleting the old map and installing the new one, I lost also the speed cameras files & other POIs so I had to reinstall them from a previous backup
   
 
==TODO==
  
==TODO==
  +
* [http://www.webazar.org/tomtom/tripmaster.php?lang=uk Tripmaster]
−
* Try TTconsole & output same as [http://www.opentom.org/TomTom_XL_LIVE here], maybe dump /mnt/flash?
  

Latest revision as of 21:38, 24 November 2010

Description

Tomtom ONE IQ Routes - 2GB

On version page (in French here): 

 Appareil XXXXX XXXXX (sorry, confidential!)
 App 8.411 (1219/090319) OS : 301792
 64 Mo de RAM (disponible : 22.2 Mo)
 GPS v1.20, Boot 5.5128
 Carte:
 'Western_and_Central_Europe_2GB'
 v825.2157
 Langue: Français

On box, commercial ref.: 

4EK0.001.01

Probably very similar to this description

Working with Linux?

Status

Well it seems latest versions of Tomtom HOME don't work yet.
You can install it under wine but it doesn't recognize that the device is plugged in so it's pretty useless. 

aptitude install wine-unstable lib32nss-mdn cabextract
wget http://www.kegel.com/wine/winetricks
sh winetricks vcrun2005sp1
cd /media/INTERNAL
wine InstallTomTomHOME.exe

I also tried Maxibox:

Misc links

Beware some are probably referring to the older Tomtom One!

Mass storage

At least it appears just as a mass storage under Linux so you can backup, copy files etc.

  • Connect Tomtom to PC.
  • Turn Tomtom on
  • Choose to connect to PC.
kernel: usb 6-2: new full speed USB device using uhci_hcd and address 16
kernel: usb 6-2: New USB device found, idVendor=1390, idProduct=0001
kernel: usb 6-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
kernel: usb 6-2: Product: ONE IQ Routes
kernel: usb 6-2: Manufacturer: TomTom
kernel: usb 6-2: SerialNumber: PSnnnnCnnnnn
kernel: usb 6-2: configuration #1 chosen from 1 choice
kernel: Initializing USB Mass Storage driver...
kernel: scsi6 : SCSI emulation for USB Mass Storage devices
kernel: usbcore: registered new interface driver usb-storage
kernel: USB Mass Storage support registered.
kernel: usb-storage: device found at 16
kernel: usb-storage: waiting for device to settle before scanning
kernel: usb-storage: device scan complete
kernel: scsi 6:0:0:0: Direct-Access     TomTom   ONE IQ Routes    6209 PQ: 0 ANSI: 2
kernel: sd 6:0:0:0: Attached scsi generic sg2 type 0
kernel: sd 6:0:0:0: [sdb] 4014080 512-byte hardware sectors: (2.05 GB/1.91 GiB)
kernel: sd 6:0:0:0: [sdb] Write Protect is off
kernel: sd 6:0:0:0: [sdb] Mode Sense: 03 00 00 00
kernel: sd 6:0:0:0: [sdb] Assuming drive cache: write through
kernel: sd 6:0:0:0: [sdb] Assuming drive cache: write through
kernel:  sdb: sdb1
kernel: sd 6:0:0:0: [sdb] Attached SCSI removable disk

Output of fdisk print: 

Disk /dev/sdb: 2055 MB, 2055208960 bytes
64 heads, 63 sectors/track, 995 cylinders
Units = cylinders of 4032 * 512 = 2064384 bytes
Disk identifier: 0x00000000
   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1         995     2005797+   6  FAT16

Disk label is apparently "INTERNAL"

Working with Windows

As we don't have choice...
If you're behind a proxy you'll experience this:
Tomtom plugged in -> Start Installer -> connection error
Download and execute manually http://download.tomtom.com/sweet/application/home2latest/TomTomHOME2winlatest.zip
It'll install and then give again an error -> ok -> Tools -> Connection -> Proxy
After the Tomtom was plugged and software was installed, Windows wanted to reboot because of a new driver installed, typical...

Software Upgrades

8.414

So I finally connected the device to a Windows box and let it upgrade whatever it wanted (you don't need to login to do that apparently).
The changelog didn't show yet what were the improvements
Now it shows (for what changed): 

 App 8.414 (1239/090707) OS : 320300
 GPS v1.20, Boot 5.5130

Latest Map Guarantee

I was a bit surprised that even after having linked my device with my account it proposed to buy map updates while I was supposed to get them for free the first time.
Then I discovered the menu option Tools -> Use Latest Map Guarantee -> Get it now
Note that you can only use it once and only in the first sth (3 months?) after having bought it.

See below for the failure I had after an update, it worked better when I removed first the old map (but beware it also removes your favorites etc so make a backup first!)

New map was 200Mb larger but it came with... 200Mb of cspeech_XXX.dat files which are probably the TTS data, useless for my model so I can probably remove them.

Applications

Links

Beware it's maybe compatible only with previous Tomtom One versions!!

TTconsole

TTconsole, to get virtual keyboard, click on upper right corner (but extreme right was inactive on my setup, I've to click sth like 5mm away from the right border.
Keyboard is qwertz, argh. ( > is shift+<, / is shift+7, = is shift+0)

uname -a

Linux (none) 2.6.13-tt320300 #1 Tue Jul 7 15:25:59 CEST 2009 armv5tejl unknown

/proc/cpuinfo

Processor	: ARM926EJ-Sid(wb) rev 5 (v5l)
BogoMIPS	: 131.48
Features	: swp half thumb fastmult edsp java 
CPU implementer	: 0x41
CPU architecture: 5TEJ
CPU variant	: 0x0
CPU part	: 0x926
CPU revision	: 5
Cache type	: write-back
Cache clean	: cp15 c7 ops
Cache lockdown	: format C
Cache format	: Harvard
I size		: 8192
I assoc		: 4
I line length	: 32
I sets		: 64
D size		: 8192
D assoc		: 4
D line length	: 32
D sets		: 64

Hardware	: TomTom GO
Revision	: 0011
Serial		: 0000000000000000

dmesg

04 Simtec Electronics
Detected type 34, name TomTom ONE IQ Routes Edition
On node 0 totalpages: 16384
  DMA zone: 16384 pages, LIFO batch:7
  Normal zone: 0 pages, LIFO batch:1
  HighMem zone: 0 pages, LIFO batch:1
CPU0: D VIVT write-back cache
CPU0: I cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
Built 1 zonelists
Kernel command line: console=/dev/null quiet
irq: clearing subpending status 00000406
irq: clearing subpending status 00000002
PID hash table entries: 512 (order: 9, 8192 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 64MB = 64MB total
Memory: 54784KB available (2026K code, 415K data, 92K init)
Calibrating delay loop... 131.48 BogoMIPS (lpj=328704)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
unpacking initramfs... done
Freeing initrd memory: 7168K
NET: Registered protocol family 16
S3C Power Management, (c) 2004 Simtec Electronics
S3C2412: Initialising architecture
S3C2412: IRQ Support
S3C2412: Clock Support, UPLL 96.000 MHz
S3C24xx CpuFrequency Scaling (DVS), (c) 2008 TomTom B.V.
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
Bluetooth: Core ver 2.7
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
S3C DMA Driver, (c) 2003-2004 Simtec Electronics
DMA channel 0 at c4800000, irq 33
DMA channel 1 at c4800040, irq 34
DMA channel 2 at c4800080, irq 35
DMA channel 3 at c48000c0, irq 36
ngffs: init_ngffs_fs: NGFFS initializing
TomTom GO Backlight S3C, (C) 2007 TomTom BV
Activate backlight_en
TomTom GO Framebuffer Driver, (C) 2005 TomTom BV
ttgfb: ttgfb_alloc: Using LFB from bootloader (reserved memory).
S3C2410 RTC, (c) 2004 Simtec Electronics
s3c2410-rtc s3c2410-rtc: rtc disabled, re-enabling
S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics
S3C2412 EVT3 Watchdog Workaround, (c) 2006 TomTom
S3C24XX Internal Flash poweroff workaround, (c) 2008 TomTom
TomTom GO Hardware Detection Driver, (C) 2004,2005 TomTom BV
TomTom GO ADC Driver, (C) 2004-2007 TomTom BV
TomTom GO S3C24XX Generic ADC Driver, (C) 2007 TomTom BV
TomTom GO GPIO Driver, (C) 2004,2005 TomTom BV
gpio_hw_init: UART 'ttySAC0' => 0
TomTom GO Accelerometer Driver, (C) 2004,2005 TomTom BV
TomTom GO Battery Driver, (C) 2004,2005,2006,2007 TomTom BV
TomTom GO GPS Driver, (C) 2004,2005 TomTom BV
TomTom GO Touchscreen Input Driver, (C) 2007 TomTom BV
Done
CoolSound engine, (C) 2004,2005 TomTom BV
dma2: IRQ with no loaded buffer?
CoolSound: sound_dma_init: Buffers allocated and associated.
reallocating sound DMA buffer (previous:0 new:4096 allocating:65536)
reallocating sound DMA buffer (previous:0 new:4096 allocating:65536)
iis2410: iis_init: Current clock rate: 66000000
TomTom GO Buzzer Driver, (C) 2006 TomTom BV
TomTom GO Gyro Driver, (C) 2007 TomTom BV
TomTom GO Legacy USB mode detect, (C) 2007 TomTom BV (usbmode:)
usbmode: Probing
usbmode: Initialized
usbmode: register_usbmode_driver
TomTom S3C24XX USB mode driver, (C) 2007 TomTom BV (s3c24xx_usbmode:)
TomTom GO Buspower monitor, (C) 2007 TomTom BV (buspower:)
buspower: buspower_probe
Done
Valencia/Murcia dock driver - v1.0
Cagliari dock driver - v1.0
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
s3c2412-uart.0: s3c2410_serial0 at MMIO 0x50000000 (irq = 70) is a S3C2412
s3c2412-uart.1: s3c2410_serial1 at MMIO 0x50004000 (irq = 73) is a S3C2412
s3c2412-uart.2: s3c2410_serial2 at MMIO 0x50008000 (irq = 76) is a S3C2412
io scheduler noop registered
io scheduler deadline registered
RAMDISK driver initialized: 16 RAM disks of 7168K size 1024 blocksize
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
TomTom GO IDE Driver, (C) 2004,2005 TomTom BV
physmap flash device: 80000 at 0
Found: EON EN29LV400BB
number of JEDEC chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
s3c2410-ohci s3c2410-ohci: S3C24XX OHCI
s3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1
s3c2410-ohci s3c2410-ohci: irq 42, io mem 0x49000000
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.01:USB HID core driver
usbcore: registered new driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0
drivers/usb/serial/usb-serial.c: USB Serial support registered for CP2101
usbcore: registered new driver CP2101
drivers/usb/serial/cp2101.c: Silicon Labs CP2101/CP2102 RS232 serial adaptor driver v0.04
s3c2412-i2c s3c2412-i2c: slave address 0x08
s3c2412-i2c s3c2412-i2c: bus frequency set to 375 KHz
s3c2412-i2c s3c2412-i2c: i2c-0: S3C I2C adapter
Bluetooth: HCI USB driver ver 2.8
usbcore: registered new driver hci_usb
Bluetooth: HCI UART driver ver 2.1
Bluetooth: HCI H4 protocol initialized
Bluetooth: HCI BCSP protocol initialized
Trying to set irq type for IRQ-1
s3c-sdi: probe: mapped sdi_base=f1200000 irq=83 irq_cd=4294967295 dma=0.
s3c-sdi: initialization done.
S3C2410 GPIO SPI Driver
registering c02234dc: scp1000-baro
TomTom GO SCP1000 Barometer Driver, (C) 2007 TomTom BV
scp1000-baro: Missing platform data!
registering c0223508: kxr94-gadc
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
Bluetooth: L2CAP ver 2.7
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO (Voice Link) ver 0.4
Bluetooth: SCO socket layer initialized
Bluetooth: RFCOMM ver 1.5
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: HIDP (Human Interface Emulation) ver 1.1
usbmode: usbmode_late_init
s3c24xx_usbmode: helper_disable_host_port 
s3c24xx_usbmode: s3c24xx_initial_to_idle  
s3c24xx_usbmode: idle_enter SUCCESS
Freeing init memory: 92K
Warning: unable to open /dev/console as initial console, res=-19.
s3c24xx_usbmode: buspower_changed POWER EVENT 
usbmode: USB power off while in idle mode. (not expected)
usbmode:[1,1] USB_STATE_IDLE==(USB_EVENT_POWER_OFF) NOP
mmcblk0: mmc0:0001 AKG00M 2007040KiB 
 mmcblk0: p1
FAT: free clusters recounted: 94354
FAT: filesystem 32 bits
gps: gps_ioctl: WARNING: Ignoring IOW_GPS_OFF
selected clock c022f084 (pclk) quot 428, calc 9600
selected clock c022f084 (pclk) quot 34, calc 115183
PORT_S3C2412 impossible RTS gpio mapping for port 1
gps: gps_ioctl: WARNING: Ignoring IOW_GPS_ON
selected clock c022f084 (pclk) quot 428, calc 9600
selected clock c022f084 (pclk) quot 70, calc 57591
selected clock c022f084 (pclk) quot 106, calc 38394
selected clock c022f084 (pclk) quot 213, calc 19197
selected clock c022f084 (pclk) quot 34, calc 115183
selected clock c022f084 (pclk) quot 70, calc 57591
selected clock c022f084 (pclk) quot 428, calc 9600
selected clock c022f084 (pclk) quot 428, calc 9600
selected clock c022f084 (pclk) quot 70, calc 57591
selected clock c022f084 (pclk) quot 106, calc 38394
selected clock c022f084 (pclk) quot 213, calc 19197
selected clock c022f084 (pclk) quot 34, calc 115183
selected clock c022f084 (pclk) quot 70, calc 57591
selected clock c022f084 (pclk) quot 428, calc 9600

ps

  PID  Uid     VmSize Stat Command
    1 root        652 S   /bin/sh /init 
    2 root            SWN [ksoftirqd/0]
    3 root            SW< [events/0]
    4 root            SW< [khelper]
    5 root            SW< [kthread]
   25 root            SW< [kblockd/0]
   28 root            SW< [khubd]
   82 root            SW  [pdflush]
   83 root            SW  [pdflush]
   85 root            SW< [aio/0]
   84 root            SW  [kswapd0]
  154 root            SW  [mtdblockd]
  176 root            SW< [kmmcd]
  182 root            SW< [s3c24xx-spi-gpi]
  185 root            SW< [krfcommd]
  192 root            SW< [mmcqd]
  273 root        572 S   syslogd -C -S 
  280 root        404 S   launchserver /var/run/launchsock 
  375 root       1480 S   /bin/glgps normal 
  379 root        560 S   /bin/ttpnpd 
  382 root        652 S   /bin/sh /init 
  393 root      26648 R   /bin/ttn 
  396 root      26648 S   /bin/ttn 
  397 root      26648 S < /bin/ttn 
  398 root        572 S   /bin/sh /mnt/sdcard/TTconsole/TTconso
  399 root        540 S   ./TTconsole/TTconsole 
  400 root        708 S   /bin/sh 
  402 root        676 R   ps ax

df

Filesystem           1k-blocks      Used Available Use% Mounted on
mtd0                       256         4       252   2% /mnt/flash
/dev/mmcblk0p1         2001868   1624408    377460  81% /mnt/sdcard

/mnt/flash

drwxr-xr-x    1 root     root            0 Apr  9  2000 .
drwxr-xr-x    5 root     root            0 Jan  1  1970 ..
drwx------    1 root     root            0 Aug 29 23:28 extra_settings
-rw-r--r--    1 root     root           13 Apr  9  2000 restore1.dat
-rw-r--r--    1 root     root          926 Jan  1  2000 settings.dat
dr-xr-xr-x    1 root     root            0 Jan  1  1970 sysfile
-rw-r--r--    1 root     root           20 Jan  1  2000 testfile
-rw-r--r--    1 root     root            4 Jan  1  2000 ttsys.dta

TTTracklog

And the extension with stop button

Height

As I've a small screen I had to edit Height/height.cfg -> d7 & n7

Misc

Reset

  • Be sure the battery is full, leave it charging for at least 2 hours with the loading green LED turned on.
  • Push on on/off button for more than 15 secs till it starts

Backup

full backup, partition image

It's very important to make a first backup of your Tomtom as soon as possible as I got my first problem very soon, see below.
To make the backup under Linux, ideally do it as very first time even before turning it on so you'll have the very initial image (change /dev/sdb to your own device):

For the mbr: (in principle the first 512 bytes are enough, the rest is filled with zeroes) 

$ dd if=/dev/sdb of=tomtom-mbr.bin bs=512 count=245

For the filesystem:
Make sure your device is connected but not mounted!!! 

$ dd if=/dev/sdb of=tomtom-sdb1.bin
4011595+0 records in
4011595+0 records out
2053936640 bytes (2.1 GB) copied, 3604.15 s, 570 kB/s

$ file sdb1 
sdb1: x86 boot sector, 
      code offset 0x0, OEM-ID "        ", 
      sectors/cluster 64, 
      root entries 512, 
      Media descriptor 0xf8, 
      sectors/FAT 245, 
      heads 64, 
      hidden sectors 245, 
      sectors 4011595 (volumes > 32 MB) , 
      serial number 0x6f0ecbbd, 
      unlabeled, 
      FAT (16 bit)

full backup, on file basis

Actually I didn't do it like that, rather my device was automounted after I configured it so I copied the whole file structure manually to a ext3 partition. This was still ok to save my device when it crashed.
FYI a few files were already created/modified after the initial setup and usage:

Some files modified before the clock was set: 

-rwxr-xr-x 1 phil phil    48 2000-04-09 14:02 CurrentMap.dat
-rwxr-xr-x 1 phil phil  1515 2000-04-09 14:18 ttgo.bif
-rwxr-xr-x 1 phil phil   632 2000-04-09 14:02 Western_and_Central_Europe_2GB/DeletedPoi.local
-rwxr-xr-x 1 phil phil    48 2000-04-09 14:02 Western_and_Central_Europe_2GB/MapUserPatch.dat

And after the clock was set (here we check for files modified the last 5 days): 

$ find . -type f -mtime -5 -exec ls -l {} \;
-rwxr-xr-x 1 phil phil     3 2009-08-29 19:21 itn/temporary.iti
-rwxr-xr-x 1 phil phil  2848 2009-08-29 18:19 Western_and_Central_Europe_2GB/MapSettings.cfg
-rwxr-xr-x 1 phil phil   844 2009-08-29 19:21 settings.dat
-rwxr-xr-x 1 phil phil    68 2009-08-29 18:19 UserPatch.dat

inc backup

Sometimes you want to see exactly those files who changed since last time (e.g. you added voices, POI,...)
You can copy the files from the Tomtom fs to have a first full backup (but not a partition image)
Then make from time to time other backups (without the big map files if you didn't change maps, to get quicker).
Then run dupemap from magicrescue to keep only the files which have changed since the initial backup: 

dupemap -d tomtom-fs.orig.map scan tomtom-fs.orig
dupemap -d tomtom-fs.orig.map delete,report tomtom-fs.incremental

Then prune empty directories:
Execute several times the following until you don't have error messages: 

find . -type d -empty -exec rm -r {} \;

Files

  • Favorites:
    • <map-subdir>/MapSettings.cfg
  • Map corrections by user:
    • <map-subdir>/MapUserPatch.dat
  • POI:
    • <map-subdir>/<POIname>.bmp
    • <map-subdir>/<POIname>.ov2
    • poi/<POIname>.tlv
  • Voices:
    • voices/data<NN>.bmp
    • voices/data<NN>.chk
    • voices/data<NN>.tlv
    • voices/data<NN>.vif

More info here

How to create your own content: POI, voice, images, colour schemes, routes & map overlays

QuickGPSfix

I was surprised my QuickGPSfix was not updated anymore at a point in time, I don't remember how it happened.
The solution I found was to restore the old QuickGPSfix file I had from Tomtom Home application (Add traffic, Voices etc -> More -> More -> More -> items on my computer -> QuickGPSfix Data) then trigger "Update my ONE"

Speed cameras

Failures!

Filesystem failure!

Well it didn't take long to have the first troubles, it happened before I did anything strange like adding applications or whatever:
I accidentally hitted the radar report (three clicks as same place on screen on the quick menu is all you need :( ) and wanted to remove it manually before connecting my Tomtom online. So I mounted the device under linux again and started a big "diff -Naur".
Then I discovered that there were strange new files in a subdirectory and when I started deleting those files I got a "read-only device" error.
After that, the Tomtom was rebooting in an endless loop :(
I solved the problem by doing the following:
I read that the device was sometimes slow and for sure the FAT16 didn't seem to be handled in a robust way so I preferred to prepare everything offline:

  • Create an empty 2Gb file
dd if=/dev/zero of=tomtom-fixed.bin bs=512 count=4011595
  • Format it (here I let the default FAT32, remember the original one was FAT16...
mkfs.vfat tomtom-fixed.bin
  • Mount it loopback
mkdir tomtom-fixed
mount -o loop tomtom-fixed.bin tomtom-fixed
  • Copy files from my backup to the loopback mounted filesystem
  • Make sure your device is connected but not mounted!!!
  • Copy the new filesystem to the device (check what's your device link)
dd if=tomtom-fixed.bin of=/dev/sdb1
  • Disconnect the device and let it reboot

Yes!!! it worked again, pfiuuuut!

Note that it's now FAT32 but I didn't change the partition table which still says FAT16: 

Disk /dev/sdb: 2055 MB, 2055208960 bytes
64 heads, 63 sectors/track, 995 cylinders
Units = cylinders of 4032 * 512 = 2064384 bytes
Disk identifier: 0x00000000
   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1         995     2005797+   6  FAT16

Disk label is apparently empty now.

Infinite reboot after map update

After a "Latest Map Guarantee" update, the device never rebooted properly, sticking on Tomtom logo :(
I tried to reset it, keeping power button pressed, and got green screen (like if you fire only the green sub-pixels).
Back on computer, connection with Tomtom HOME was fine.
I noticed that size of the map in "items on device" was still the size of the previous smaller map.
So I chose to delete the map from the device then tried again the map update and then it finally worked again.
Deletion of the "previous" map deleted also my map favorites.

When I tried to reinstall the backup of MapSettings.cfg it failed again so apparently that was the cause of the problem.
I reinstalled the "empty" MapSettings.cfg that came with the Latest Map Guarantee update and it worked fine again.

So now how to re-import my old favorites (& home address BTW)?

Googling...

  • This blog explains exactly the same issue, apparently an incompatibility between old mapsettings.cfg and new maps.
    Her suggestion is to use POI to store favorites, mmm...
  • A solution is proposed on this forum:
    • Copy again MapSettings.cfg to the device
    • Launch Tomtom HOME
    • Choose to operate your device remotely (this takes time to start)
    • Now on your remote Tomtom screen, add a favorite & delete it, this "fixes" the file
    • Now problem should be fixed, you're back with your favorites!

In the operation of deleting the old map and installing the new one, I lost also the speed cameras files & other POIs so I had to reinstall them from a previous backup

TODO

Retrieved from "https://wiki.yobi.be/index.php?title=Tomtom_ONE_IQ_Routes&oldid=6907"