The TomTom One.
Have just got myself a TomTom one. Lovely bit of GPS / Linux integration and hacker friendly too…
At the moment I’m just seeing what it could be capable of and the first step towards that is seeing what dmesg dumps out..
I’ve already bust out the boot loader and startup scripts and have been annotating a dump of ttn navigation app to see what interesting stuff I can glean from that.
Next on the list is gaining a remote shell without writing my own custom firmware or boot loader.
Read on for the messages log…
Linux version 2.6.10-tt1006 (aya@achilles.intra.local) (gcc version 3.3.4) #1 Thu Sep 8 09:52:45 CEST 2005
CPU: ARM920Tid(wb) [41129200] revision 0 (ARMv4T)
CPU: D VIVT write-back cache
CPU: I cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
CPU: D cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
Machine: TomTom GO
Memory policy: ECC disabled, Data cache writeback
CPU S3C2440A (id 0×32440001)
S3C2440: core 376.800 MHz, memory 94.200 MHz, peripheral 47.100 MHz
S3C2410 Clock control, (c) 2004 Simtec Electronics
IO_Init: Starting detection
Detected type 57, name TomTom ONE
On node 0 totalpages: 8192
DMA zone: 8192 pages, LIFO batch:2
Normal zone: 0 pages, LIFO batch:1
HighMem zone: 0 pages, LIFO batch:1
Built 1 zonelists
Kernel command line: console=ttySAC0,115200
irq: clearing subpending status 00000402
irq: clearing subpending status 00000002
PID hash table entries: 256 (order: 8, 4096 bytes)
timer tcon=00000000, tcnt 9951, tcnt_mod 0000, tcfg 00000200,00000000, usec 0000209d
selected clock c0195e7c (pclk) quot 25, calc 113221
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 32MB = 32MB total
Memory: 23552KB available (1448K code, 159K data, 84K init)
Calibrating delay loop… 188.00 BogoMIPS (lpj=470016)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
unpacking initramfs… done
Freeing initrd memory: 7168K
NET: Registered protocol family 16
S3C2410 Power Management, (c) 2004 Simtec Electronics
S3C2440: Initialising architecture
Bluetooth: Core ver 2.7
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
S3C2410 DMA Driver, (c) 2003-2004 Simtec Electronics
DMA channel 0 at c2800000, irq 33
DMA channel 1 at c2800040, irq 34
DMA channel 2 at c2800080, irq 35
DMA channel 3 at c28000c0, irq 36
ngffs: init_ngffs_fs: NGFFS initializing
TomTom GO Framebuffer Driver, (C) 2005 TomTom BV
ttgfb: ttgfb_alloc: Copying bootloader LFB
S3C2410 RTC, (c) 2004 Simtec Electronics
s3c2410-rtc s3c2410-rtc: rtc disabled, re-enabling
S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics
TomTom GO Hardware Detection Driver, (C) 2004,2005 TomTom BV
TomTom GO GPIO Driver, (C) 2004,2005 TomTom BV
TomTom GO ADC Driver, (C) 2004,2005 TomTom BV
TomTom GO Accelerometer Driver, (C) 2004,2005 TomTom BV
TomTom GO Battery Driver, (C) 2004,2005 TomTom BV
TomTom GO GPS Driver, (C) 2004,2005 TomTom BV
TomTom GO PWM Driver, (C) 2004,2005 TomTom BV
TomTom GO Touchscreen Driver, (C) 2004,2005 TomTom BV
CoolSound engine, (C) 2004,2005 TomTom BV
dma2: IRQ with no loaded buffer?
CoolSound: sound_dma_init: Buffers allocated and associated.
iis: iis_init: Current clock rate: 47100000
TomTom GO Remote Driver, (C) 2004,2005 TomTom BV
tomtomgo-rc: probe of tomtomgo-rc failed with error -1
s3c2410_serial0 at MMIO 0×50000000 (irq = 70) is a S3C2440
s3c2410_serial1 at MMIO 0×50004000 (irq = 73) is a S3C2440
s3c2410_serial2 at MMIO 0×50008000 (irq = 76) is a S3C2440
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
elevator: using deadline as default io scheduler
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.
Bluetooth: HCI UART driver ver 2.1
Bluetooth: HCI H4 protocol initialized
Bluetooth: HCI BCSP protocol initialized
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind 4096)
NET: Registered protocol family 1
Bluetooth: L2CAP ver 2.6
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO (Voice Link) ver 0.3
Bluetooth: SCO socket layer initialized
Bluetooth: RFCOMM ver 1.3
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Freeing init memory: 84K
selected clock c0195e7c (pclk) quot 25, calc 113221
TomTom GO Storage Device Driver, (C) 2004,2005 TomTom BV
SDx: sd card of 246016 sectors (120 MiB)
SDx: sd card of 246016 sectors (120 MiB)
sdcard: sdcard1
selected clock c0195e7c (pclk) quot 306, calc 9588
selected clock c0195e7c (pclk) quot 2, calc 981250
selected clock c0195e7c (pclk) quot 2, calc 981250
selected clock c0195e7c (pclk) quot 2, calc 981250
selected clock c0195e7c (pclk) quot 25, calc 113221
selected clock c0195e7c (pclk) quot 2, calc 981250
selected clock c0195e7c (pclk) quot 2, calc 981250
bcsp_recv: Out-of-order packet arrived, got 1 expected 0
FAT: bogus number of reserved sectors
VFS: Can’t find a valid FAT filesystem on dev sdcard.
FAT: filesystem 16 bits