I'm trying out the new Yocto BSP 1.0.0 and so far it builds but I'm having some trouble getting mmc running in u-boot on our custom board. While troubleshooting this I ran into some trouble with GDB. If I build the full image (bitbake fsl-image-dfb) and dump that onto the SD card u-boot always comes up as follows
CPU: Freescale i.MX6Q rev1.2 at 792 MHz
CPU: Temperature 45 C, calibration data: 0x58d4f269
Reset cause: POR
DRAM: 1 GiB
MMC: FSL_SDHC: 0
MMC Device 1 not found
No MMC card found
Using default environment
However, when I use my BDI3000 and GDB to load the image ("u-boot-imx/2013.04-r0/git/u-boot") I can single-step through just fine, as soon as I "continue" it jumps into the weeds and nothing ever prints to the console. GDB u-boot debugging works fine on the old LTIB 4.1.0 BSP. I don't necessarily need gdb, but the problem is that the compile-test-repeat cycle is at a glacial pace when rebuilding the whole SD card image. Any ideas on what could be the culprit ?
I noticed there is a "u-boot-imx6qsabresd.imx" file in the images directory. What is this file used for ? I'm hoping that can be copied directly to an SD card somehow.