Can you post the boot log? I know several of us have tested the RAM disk, and I expect it work properly.

Most of the unfinished features should be regarding the Wireless (Bluetooth and WiFi) features.

adam

I'm having a hard time pasting the output into this field, so here is a Google Drive Link to the output from my dev kit. Additionally, at the start of the text are the steps I used to make the SD card. The User Guide is a bit confusing as to what exactly I should do, so I'm wondering if that's my problem. 

Link: https://drive.google.com/file/d/0B5BNvNIeIKgMV1p6d3Q0aGY4bFpIcUNYNmN1WTE3X0pmY1BV/view?usp=sharing

Thank you,
Elisabeth

On the surface, it appears as if the device tree is missing. I see from the log tha you're using the zImage_dtb, but it's not clear to me how you generated it.

Section 2.6.1 covers this. Can you verify the sizes of your zImage and the zImage_dtb? (you can also verify them against the origin zImage located in output/build/linux-4.4.9/arch/arm/boot

If they are the same size, then I am willing to bet the device tree is missing.

The solution would be to

cat logicpd-torpedo-37xx-devkit.dtb >> zImage

This will append the device tree to the tail end of the zImage. You can then copy that zImage to the SD card. I would rename it to zImage_dtb.

If you've already done the 'cat' instrucition once, it may fail to boot if you do it a second time.

I would erase the zImage and zImage_dtb files in your output/images directory and copy fresh copies into there from output/build/linux-4.4.9/arch/arm/boot

Does that make sense?

adam

Yes, that makes sense. I verified that they are different sizes:

logic@logic:~/logic/buildroot-2016.02$ ll output/images/zImage*
-rw-r--r-- 1 logic logic 4822920 May 11  2016 output/images/zImage
-rwxrwxr-x 1 logic logic 3596340 Apr 16 14:32 output/images/zImage_dtb*

I went through the RAMdisk from NAND instructions again and was finally able to get it to boot from NAND successfully. Now I'm on to the ubifs part.

 

Adam,
I have finally (yahoo!) gotten ubifs to boot from NAND. I was copying both the zImage and the zImage_dtb over to my SD Card, that may have been the problem. But, I also think the User Guide may be missing some instructions. After I added the below two steps, the rest worked like a charm and the SOM boots very well.

Section 3.2.3
Load Linux from RAMDisk once to format and setup UBI partition in NAND
** NEW STEP** OMAP Logic # nand unlock
** NEW STEP** OMAP Logic # setenv loadzimage 'nand read $loadaddr kernel'
OMAP Logic # setenv ramdiskimage rootfs.cpio.uboot
OMAP Logic # setenv ramdisksize 100000
OMAP Logic # setenv mmcrambootz 'run ramargs; run common_bootargs; run
dump_bootargs; run loadzimage; run loadramdisk; bootz ${loadaddr}
${ramdiskaddr}'
OMAP Logic # run mmcrambootz

Thank you for the help, or at least for the listening/reading.
Elisabeth