After following the instruction in Getting started with Yocto on Wandboard - Wandboard Wiki - the Wandboard is stuck in U-Boot. When building I did deviate from the instructions by using MACHINE=wandboard, but bitbake would not accept "wandboard-solo". I'm assuming the bootfile is not configured correctly. Unfortunately I am new to this system - where is the bootfile for the Wandboard located in the Yocto build system?
Has anyone else had this issue?
Thank you.
below is the console output with boot environmental variables:
U-Boot 2016.03+fslc+gfd6b196 (Mar 27 2016 - 00:23:57 -0700)
CPU: Freescale i.MX6SOLO rev1.1 at 792 MHz
Reset cause: POR
Board: Wandboard rev C1
I2C: ready
DRAM: 512 MiB
MMC: FSL_SDHC: 0, FSL_SDHC: 1
*** Warning - bad CRC, using default environment
auto-detected panel HDMI
Display: HDMI (1024x768)
In: serial
Out: serial
Err: serial
Net: FEC [PRIME]
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
MMC: no card present
starting USB...
USB0: Port not available.
USB1: USB EHCI 1.00
scanning bus 1 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
USB device 0: unknown device
FEC Waiting for PHY auto negotiation to complete......... TIMEOUT !
BOOTP broadcast 1
...
=> printenv
baudrate=115200
board_name=C1
board_rev=MX6DL
boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${pref}
boot_extlinux=sysboot ${devtype} ${devnum}:${distro_bootpart} any ${scriptaddr}f
boot_net_usb_start=usb start
boot_prefixes=/ /boot/
boot_script_dhcp=boot.scr.uimg
boot_scripts=boot.scr.uimg boot.scr
boot_targets=mmc0 mmc1 usb0 pxe dhcp
bootcmd=run findfdt; run distro_bootcmd
bootcmd_dhcp=run boot_net_usb_start; if dhcp ${scriptaddr} ${boot_script_dhcp};i
bootcmd_mmc0=setenv devnum 0; run mmc_boot
bootcmd_mmc1=setenv devnum 1; run mmc_boot
bootcmd_pxe=run boot_net_usb_start; dhcp; if pxe get; then pxe boot; fi
bootcmd_usb0=setenv devnum 0; run usb_boot
bootdelay=2
bootfstype=fat
console=ttymxc0,115200
devnum=0
devplist=1
devtype=mmc
distro_bootcmd=for target in ${boot_targets}; do run bootcmd_${target}; done
ethact=FEC
ethaddr=00:1f:7b:b0:0c:76
ethprime=FEC
fdt_addr=0x18000000
fdt_addr_r=0x18000000
fdt_high=0xffffffff
fdtfile=imx6dl-wandboard.dtb
findfdt=if test $board_rev = MX6Q ; then setenv fdtfile imx6q-wandboard.dtb; fi
initrd_high=0xffffffff
ip_dyn=yes
kernel_addr_r=0x12000000
loadaddr=0x12000000
mmc_boot=if mmc dev ${devnum}; then setenv devtype mmc; run scan_dev_for_boot_pi
mmcdev=0
pxefile_addr_r=0x12000000
ramdisk_addr_r=0x13000000
ramdiskaddr=0x13000000
scan_dev_for_boot=echo Scanning ${devtype} ${devnum}:${distro_bootpart}..
.; fore
scan_dev_for_boot_part=part list ${devtype} ${devnum} -bootable devplist; env ee
scan_dev_for_extlinux=if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefi
scan_dev_for_scripts=for script in ${boot_scripts}; do if test -e ${devtype} ${e
scriptaddr=0x12000000
splashpos=m,m
update_sd_firmware=if test ${ip_dyn} = yes; then setenv get_cmd dhcp; else setei
update_sd_firmware_filename=u-boot.imx
usb_boot=usb start; if usb dev ${devnum}; then setenv devtype usb; run scan_devi
videoargs=setenv nextcon 0; if hdmidet; then setenv bootargs ${bootargs} video=}
Environment size: 3559/8188 bytes
...
Hi Mark
seems uboot-2016 is not integrated yet for this board, as according to
below link latest stable release is uboot-2015.04
one can post on meta-fsl-arm mailing list, so that someone familiar with
that board could try to assist you
https://lists.yoctoproject.org/listinfo/meta-freescale
Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------