When I flash a custom Apalis T30 LDXE image I built using Yocto to my Apalis T30 (using Apalis Evaluation board) I get the following output:
U-Boot SPL 2016.11-2.8.6+g83a53c1 (May 15 2019 - 04:13:28)
Trying to boot from RAM
U-Boot 2016.11-2.8.6+g83a53c1 (May 15 2019 - 04:13:28 +0000)
SoC: tegra30
Reset cause: POR
DRAM: 2 GiB
MMC: Tegra SD/MMC: 0, Tegra SD/MMC: 1, Tegra SD/MMC: 2
In: serial
Out: vidconsole
Err: vidconsole
Warning: Please change 'lcd' to 'vidconsole' in stdout/stderr environment vars
Model: Toradex Apalis T30 2GB V1.1B, Serial# 02927622
Net: No ethernet found.
Hit any key to stop autoboot: 0
Booting from internal eMMC chip...
reading tegra30-apalis-eval.dtb
** Unable to read file tegra30-apalis-eval.dtb **
reading uImage
** Unable to read file uImage **
emmcboot failed
Booting from SD card in 8bit slot...
MMC: no card present
** Bad device mmc 1 **
MMC: no card present
** Bad device mmc 1 **
sdboot failed
Booting from USB stick...
starting USB...
USB0: USB EHCI 1.00
USB1: USB EHCI 1.00
USB2: USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... 2 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
** Bad device usb 0 **
** Bad device usb 0 **
usbboot failed
Booting via DHCP/TFTP/NFS...
No ethernet found.
No ethernet found.
nfsboot failed
Apalis T30 #
The only configuration I’ve made from the default settings was uncommenting the variable:
MACHINE ?= "apalis-t30"
and commenting the default one out. My bitbake command had 0 errors and 7 warnings, 6 of them about licensing mismatch and one saying I have no recipes for chromium, chromium-wayland, and mesa. To my knowledge this shouldn’t cause a failure on boot. I also get a successful compressed image file:
Apalis-T30_LDXE-Image_2.8b6-20190515.tar.bz2
I’m making sure to unzip it using root permissions. When flashing I’m using the update command to set up an SD and then use the SD to flash the board.
If I reflash the same SD card using the same command (./update -o /media/…/sdcard) but using the image I get from the binary images page:
Apalis T30 (2.7 | 2018-01-04 | 115.04 MB) Easy Installer Image,
From:
The board boots fine.
Any idea on why my Yocto build isn’t running? I did notice my version is 2.8 rather than the 2.7 that works just fine, I’m using the uboot that came with the module, do I need to update uboot to run 2.8? I don’t seem to get any errors when running ‘run setupdate’ and ‘run update’, only when it tries to boot afterwards.
Thanks.