when you try to ssh, it could most probably be because one of your other network interfaces (wired/wireless) is being assigned an IP address of the form 192.168.0.* ,because of which the routing table contains a default gateway entry that is confusing poor new usb0 interface.

The easiest way to work around this is to specify a tighter netmask for usb0 like:

I encountered the same problem, but I still had a gcc3 installed (gcc-3.4.6-r1 in a seperate slot from the system default gcc4, to be exact. This means that if you're using gentoo, you will not need to downgrade your system gcc). I simply added --cc=gcc-3.4.6 to ./configure's switches and make finished without major problems. --LordHelmchen 20:12, 11 April 2007 (CEST)

If you still encounter this problem with gcc3, make sure you don't have -march set anywhere like in CFLAGS (I had -march=athlon-xp). unsetting CFLAGS before re-running the configure script solved the problem for me. --Vegar 22:10, 24 April 2007 (CEST)

If nothing else works, you should try to use gcc-3.3.* (tested using the x86-chroot as building environment) --Mathias

looks like I'm somehow getting a variable confused... when I try to run flash.sh with no arguments, I get a bunch of errors from sleep telling me that items such as `nand' for instance is an invalid time. I've encountered this problem both from the makefile and from a manual download. From what I can deduce, $2 should contain the number of (micro?)seconds for sleep to wait, but it looks like there's a target list, or some series of commands that are getting crosswired in.

I had the same output, and in my case the problem was that my image hadn't
built. I guess the flash.sh script behaves this way if there is no image
(todo: it would be good to modify the script to first check for an image, and
if it is missing, report it as such and exit.).

by using the current makefile for 2007.2 on 64bit ubuntu I was not able to point to buttons on the qemu screen correctly due to a calibration issue.
it seems that i had to imagine the screen turned around by 90° clockwise and only by guessing where the buttons would be I was able to open up the console and did a ts_calibrate to re orientate the screen - now everything works as expected.

Same problem here with a ubuntu 32bit running 2007.2. How did you do the ts_calibrate? It's already difficult for getting in the terminal (on the phone), but then I couldn't find the onscreen keyboard. How do you activate it?
Dolfje 13:03, 21 August 2007 (CEST) - the mokomakefile runs qemu with your keyboard as an usb device so you can use it to type. JoSch 17:57, 25 August 2007 (CEST)

Again same problem :) Would really like to try this out, but it is hard without calibration. 14:29 (CEST) Saturday, August 25 2007

Run qemu with the -portrait option to make the calibration at least match qemu's input orientation (which should be enough to start a terminal and type ts_calibrate for further calibration). Adding "-usbdevice keyboard" enables the USB keyboard. --Danielmewes 19:39, 28 August 2007 (CEST)

revision is 4024.
What should I do?
--xnike 09:26, 7 February 2008 (CET)

I got the same problem. I fixed it by editing "flash.sh" file(You can find it in $MokoHome/openmoko/trunk/src/host/qemu-neo1973/openmoko)
solution 1:
--------------------------------------------------------
at line 91:
change
kill $timer
to:
if $timer > 0; then
kill $timer
fi
at line 96:
change
kill $timer
to:
if $timer > 0; then
kill $timer
fi
--------------------------------------------------------
It works to me, hope it can help you:)
===========================================
solution 2:
also, it might happend like that because the uboot waiting time is too short.
in "flash.sh" file, find out the following lines:
#####
uboot $uboot_image 300 "
...
uboot splash.gz 60 "
...
uboot $kernel_image 60 "
...
uboot $rootfs_image 120 "
#####
you can find at the end of each line there is a number. you should double size them(just change the 300 to 600), and save the file. redo the "openmoko/flash.sh" commond.
it's also works for me.

This problems seems not restricted to x64, I had it on Ubuntu 8.10: in my case the solution was simply to comment out the exit -1 after it complains. It then starts into the emulator.

Views

Personal tools

Broken Link

Error connecting

If you get an error like

ssh: connect to host 192.168.0.202 port 22: No route to host

when you try to ssh, it could most probably be because one of your other network interfaces (wired/wireless) is being assigned an IP address of the form 192.168.0.* ,because of which the routing table contains a default gateway entry that is confusing poor new usb0 interface.

The easiest way to work around this is to specify a tighter netmask for usb0 like:

I encountered the same problem, but I still had a gcc3 installed (gcc-3.4.6-r1 in a seperate slot from the system default gcc4, to be exact. This means that if you're using gentoo, you will not need to downgrade your system gcc). I simply added --cc=gcc-3.4.6 to ./configure's switches and make finished without major problems. --LordHelmchen 20:12, 11 April 2007 (CEST)

If you still encounter this problem with gcc3, make sure you don't have -march set anywhere like in CFLAGS (I had -march=athlon-xp). unsetting CFLAGS before re-running the configure script solved the problem for me. --Vegar 22:10, 24 April 2007 (CEST)

If nothing else works, you should try to use gcc-3.3.* (tested using the x86-chroot as building environment) --Mathias

Basic question

I am using the emulator after compiling 'make qemu'.
The basic gui screen has been created and it asks the following:

'Touch the crosshairs to calibrate the screen'

Unfortunately I do not know how to continue from this stage on...
Any mouse click on the crosshairs, or a keyboard touch won't initiate a click...

Does any body know how can I click the emulator screen and continue from this stage? --nighthawk 01:12, 9 April 2007

flash.sh fails

Try installing lynx (sudo apt-get install lynx) and run the openmoko/download.sh again,
then it should work.

question/answers

looks like I'm somehow getting a variable confused... when I try to run flash.sh with no arguments, I get a bunch of errors from sleep telling me that items such as `nand' for instance is an invalid time. I've encountered this problem both from the makefile and from a manual download. From what I can deduce, $2 should contain the number of (micro?)seconds for sleep to wait, but it looks like there's a target list, or some series of commands that are getting crosswired in.

I had the same output, and in my case the problem was that my image hadn't
built. I guess the flash.sh script behaves this way if there is no image
(todo: it would be good to modify the script to first check for an image, and
if it is missing, report it as such and exit.).

calibration problem

by using the current makefile for 2007.2 on 64bit ubuntu I was not able to point to buttons on the qemu screen correctly due to a calibration issue.
it seems that i had to imagine the screen turned around by 90° clockwise and only by guessing where the buttons would be I was able to open up the console and did a ts_calibrate to re orientate the screen - now everything works as expected.

Same problem here with a ubuntu 32bit running 2007.2. How did you do the ts_calibrate? It's already difficult for getting in the terminal (on the phone), but then I couldn't find the onscreen keyboard. How do you activate it?
Dolfje 13:03, 21 August 2007 (CEST) - the mokomakefile runs qemu with your keyboard as an usb device so you can use it to type. JoSch 17:57, 25 August 2007 (CEST)

Again same problem :) Would really like to try this out, but it is hard without calibration. 14:29 (CEST) Saturday, August 25 2007

Run qemu with the -portrait option to make the calibration at least match qemu's input orientation (which should be enough to start a terminal and type ts_calibrate for further calibration). Adding "-usbdevice keyboard" enables the USB keyboard. --Danielmewes 19:39, 28 August 2007 (CEST)

Segfault when flash.sh runs / 'bad magic number' error from qemu

I had an issue where make qemu and make flash-qemu-official both had a segfault when running flash.sh then when running make run-qemu I got errors from the bootloader about a 'bad magic number'.

The quick fix (per Mek in #openmoko) is to comment out the line in flash.sh that reads 'nand createbbt' .

Hangs at setenv bootcmd

Both manually and with MokoMakefile, flash.sh hangs for me at "setenv bootcmd '" (up to and including the apostrophe prints initially, then it goes onto "openmoko/flash.sh" after 300 sec):

revision is 4024.
What should I do?
--xnike 09:26, 7 February 2008 (CET)

I got the same problem. I fixed it by editing "flash.sh" file(You can find it in $MokoHome/openmoko/trunk/src/host/qemu-neo1973/openmoko)
solution 1:
--------------------------------------------------------
at line 91:
change
kill $timer
to:
if $timer > 0; then
kill $timer
fi
at line 96:
change
kill $timer
to:
if $timer > 0; then
kill $timer
fi
--------------------------------------------------------
It works to me, hope it can help you:)
===========================================
solution 2:
also, it might happend like that because the uboot waiting time is too short.
in "flash.sh" file, find out the following lines:
#####
uboot $uboot_image 300 "
...
uboot splash.gz 60 "
...
uboot $kernel_image 60 "
...
uboot $rootfs_image 120 "
#####
you can find at the end of each line there is a number. you should double size them(just change the 300 to 600), and save the file. redo the "openmoko/flash.sh" commond.
it's also works for me.

This problems seems not restricted to x64, I had it on Ubuntu 8.10: in my case the solution was simply to comment out the exit -1 after it complains. It then starts into the emulator.

I have got the same problem under Debian x86_64 but even though i suddenly got through the flashing.. when i run: