-
Book Overview & Buying
-
Table Of Contents
-
Feedback & Rating
Embedded Linux Projects Using Yocto Project Cookbook
By :
If you have problems booting your image, follow this recipe to troubleshoot.
lsusb utility on your Linux host to see whether the Wandboard appears as follows:Bus 002 Device 006: ID 15a2:0054 Freescale Semiconductor, Inc. i.MX6Q SystemOnChip in RecoveryMode
If you don't see this, try a different power supply. It should be 5V, 10W.
$ minicom -D /dev/ttyS0 -b 115200
You will need to add your user to the dialout group, or try to run the command as sudo. This should open a 115200 8N1 serial connection. The serial device may vary in your Linux host. For example, a USB-to-serial adapter may be detected as /dev/ttyUSB0. Also, make sure both hardware and software flow control are disabled.
Make sure you have a DHCP server running on the test network where the target is.
You can use a packet sniffer like Wireshark to capture a network trace on your Linux host and filter packages like the bootp protocol. At the least, you should see some broadcasts from your target, and if you use an Ethernet hub, you should also see the DHCP replies.
Optionally, you can log in to your DHCP server and check the logs to see if a new IP address has been assigned. If you see an IP address being assigned, you might want to consider adding an SSH server, like
Dropbear, to your core-image-minimal image so that you can establish a network connection with the target. You can do this by adding the following line to the conf/local.conf configuration file:
IMAGE_INSTALL_append = " dropbear"
Note the space after the initial quote.
After building and reprogramming, you can then start an SSH session to the Wandboard from your Linux host with:
$ ssh root@<ip_address>
The connection should automatically log in without a password prompt.
These steps will have your Wandboard start booting, and you should have some output in your serial connection.
If everything else fails, you can verify the position of the bootloader on your microSD card. You can dump the contents of the first blocks of your microSD card with:
$ sudo dd if=/dev/sdN of=/tmp/sdcard.img count=10
You should see a U-Boot header at offset 0x400. That's the offset where the i.MX6 boot ROM will be looking for the bootloader when bootstrapped to boot from the microSD interface. Use the following commands:
$ head /tmp/sdcard.img | hexdump 0000400 00d1 4020 0000 1780 0000 0000 f42c 177f
You can recognize the U-Boot header by dumping the U-Boot image from your build. Run the following commands:
$ head u-boot-wandboard-quad.imx | hexdump 0000000 00d1 4020 0000 1780 0000 0000 f42c 177f
Change the font size
Change margin width
Change background colour