I followed the docs and used yocto to build a system for a ConnectCore6 SBC.
Again, following the docs, I used tftp to update the u-boot. The update seems to have gone OK, but afterwards I get no response from the board.
Did I brick the board? Is there a way to get it back?
Here is the log of the update:
U-Boot dub-2015.04-r4.5+ga714275 (Aug 11 2016 - 18:07:04)
CPU: Freescale i.MX6DL rev1.3 at 792MHz
CPU: Industrial temperature grade (-40C to 105C) at 46C
Reset cause: WDOG
I2C: ready
DRAM: 512 MiB
MMC: FSL_SDHC: 0 (eMMC), FSL_SDHC: 1
In: serial
Out: serial
Err: serial
ConnectCore 6 SOM variant 0x13: Industrial DualLite-core 800MHz, 4GB eMMC, 512MB DDR3, -40/+85C, Wireless, Bluetooth
Board: ConnectCore 6 SBC, version 3
WARNING: Undefined board ID!
Boot device: MMC4
PMIC: DA9063, Device: 0x61, Variant: 0x50, Customer: 0x00, Config: 0x56
Net: FEC [PRIME]
Hit any key to stop autoboot: 0
=> setenv ipaddr 192.168.10.123
=> setenv serverip 192.168.10.10
=> update uboot tftp u-boot-ccimx6qsbc-2015.04-r0.imx
Do you really want to program the boot loader? y
Using FEC device
TFTP from server 192.168.10.10; our IP address is 192.168.10.123
Filename ‘u-boot-ccimx6qsbc-2015.04-r0.imx’.
Load address: 0x12000000
Loading: ###########################
1.9 MiB/s
done
Bytes transferred = 388096 (5ec00 hex)
switch to partitions #1, OK
mmc0(part 1) is current device
MMC write: dev # 0, block # 2, count 758 … 758 blocks written: OK
Reading back firmware…
MMC read: dev # 0, block # 2, count 758 … 758 blocks read: OK
Verifying firmware…
Total of 97024 word(s) were the same
Update was successful
switch to partitions #0, OK
mmc0(part 0) is current device
=>