HI I have uploaded debian images to Brendan's site, http://www.barwap.com/upload/ now I wonder does it even boot to your tomtom's :)
If it boots and prints something like debian login: you can try to scan bluetooth to see if there's a host called tomtom-0 If you see this, that's a good sign, you can login to it as root (no password) via bluetooth rfcomm channel 2 However, It may not work out of the box or it needs setup. My image expects bluetooth device to be at /dev/ttySAC1 I imagine various hardware may get it different setup is in /root/bin/bluetoothinit.sh and /etc/bluetooth/uart if you can login, congratulations, then you can setup on your computer a DUN server (dial up networking) and enter your computer's bluetooth MAC address to tomtom's rfcomm1 device, address is in /etc/bluetooth/rfcomm.conf Basically there's a bluetooth chip that might cause problems or be different on various hardware, And it needs some user space initialization program to be run before linux bluetooth daemons are started. Also It can crash kernel when initialized and restarted too much (in my case, more than once is too much :) If you have bluetooth keyboard and/or mouse you can pair them with the tomtom specifying their bluetooth MAC address with command hidd --connect 11:22:33:44:55:66 With keyboard and mouse working (and network via DUN of course) I recommend you to install framebuffer X.org X11 server, ion2 window manager and dillo2 web browser (official debian dosen't yet have dillo2 but there exist debian package for arm in some nslu2 project web site (can't remember exact url but you'll find it). It works well on tomtom If it works, we can call the debian for tomtom DebDeb Best regards, Davor On 1/8/09, davor emard <[email protected]> wrote: > HI > > I have uploaded debian images to Brendan's site, > http://www.barwap.com/upload/ > now I wonder does it even boot to your tomtom's :) > > If it boots and prints something like debian login: > you can try to scan bluetooth to see if > there's a host called tomtom-0 > If you see this, that's a good sign, you can login > to it as root (no password) via bluetooth rfcomm channel 2 > > However, It may not work out of the box or it needs > setup. My image expects bluetooth device to be at /dev/ttySAC1 > I imagine various hardware may get it different > setup is in /root/bin/bluetoothinit.sh and /etc/bluetooth/uart > > if you can login, congratulations, then you can setup on > your computer a DUN server (dial up networking) and > enter your computer's bluetooth MAC address to tomtom's > rfcomm1 device, address is in /etc/bluetooth/rfcomm.conf > > Basically there's a bluetooth chip that might cause problems > or be different on various hardware, And it needs some user > space initialization program to be run before linux bluetooth > daemons are started. Also It can crash kernel when initialized > and restarted too much (in my case, more than once is too much :) > > If you have bluetooth keyboard and/or mouse you can pair them > with the tomtom specifying their bluetooth MAC address with command > > hidd --connect 11:22:33:44:55:66 > > With keyboard and mouse working (and network via DUN of course) > I recommend you to install framebuffer X.org X11 server, ion2 > window manager and dillo2 web browser (official debian dosen't > yet have dillo2 but there exist debian package for arm in some nslu2 > project web site (can't remember exact url but you'll find it). It works > well on tomtom > > If it works, we can call the debian for tomtom DebDeb > > Best regards, > Davor >
