Are you using the SD card reader that was included in the kit? I wonder if it could be an incompatibility with virtualbox and the USB stick.

I have seen some USB card readers fail when used with virtual machines.

I just pulled in the VM that we published, and ran the script per the instructions and the log I received matches the log that's published.

logic@logic:~/Downloads$ ./create_sdcard.sh
Devices available:
sdb is 3.7GB - Card Reader
Enter device: sdb
[sudo] password for logic:
Unmounting /media/logic/rootfs
Unmounting /media/logic/boot
Setting up sdb

Do you wish to continue? (y/N) y
Partitioning sdb.
mke2fs 1.42.13 (17-May-2015)
Missing "/home/logic/Downloads/rootfs/boot/MLO"! Cannot continue.


You can try formatting the card manually and see if it it's any different. Basically for the RAM Disk, you just need a FAT formatted SD card. If you want to try formatting the card in Windows, we have a tool here: http://support.logicpd.co...talid=0&EntryId=2760

You'll need to be logged into the support site for the link to work.

Once it's formatted, the newly created MLO needs to be copied first because the internal bootloader looks in a specific location on the SD card.

Just an FYI we don't have all the instructions documented yet on enabling all the features like WiFi, Bluetooth, etc. I know that they work personally, because I spent a bunch of my spare time testing them, but I never got around to documenting it all yet. I know for sure that you'll need the NVS files from the stock BSP in order to be FCC / IC compliant.


adam

I am not using the card reader provided so that could certainly be the case.

For the RAM Disk, I have tried formatting it in Windows as well as Linux but neither do the trick. I am going to try rebuilding the BSP and using clean files.

Thanks for the extra information.

-Carter

The DM3730 firmware has a hard time with FAT partitions, which can prevent it from seeing the MLO file. I've always just worked around it by formatting the SD card without any partitions at all:

# "Erase" everything by creating a new disk label
sudo parted -s ${DRIVE} mklabel loop

# Turn the entire drive into a filesystem
sudo mkfs.vfat -I -F 32 -n "BOOT" ${DRIVE}

I've never had a problem since I've switched to this method.

Thanks, Stephen. That definitely helped but on boot I am getting this message. 

U-Boot SPL 2016.03 (May 11 2016 - 00:30:42)
Trying to boot from MMC
bad magic
bad magic
** Partition 1 not valid on device 0 **
spl_register_fat_device: fat register err - -1
** Partition 1 not valid on device 0 **
spl_register_fat_device: fat register err - -1
spl_load_image_fat: error reading image u-boot.img, err - -1
spl: no partition table found
spl: no partition table found
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

 

Resetting the board just brings up the same message.

I haven't tested the U-boot with the format instructions he gave, but it appears as if MLO cannot find u-boot.img

This newer u-boot uses .img instead of .bin 

 

The partition structure may also not be correct for this U-Boot

adam

Are you able to get to the u-boot command line? If so, try running the following:

mmc init
fatinfo mmc 0

The output that I get when I run those commands is:

OMAP Logic # mmc init
mmc1 is available
OMAP Logic # fatinfo mmc 0
Interface: MMC
Device 0: Vendor: Rev: Prod:
Type: Hard Disk
Capacity: 32.0 MB = 0.0 GB (65536 x 512)
Partition 1: Filesystem: FAT32 "BOOT "

I was able to get the EXT3 RootFS method to work after all that. Thanks for all your help guys.

That's fantastic.

It's still a work in progress, and it's basically straight out kernel.org.

If you need newer features like LCD and touch screens, etc. the 4.6.x kernel has some updates, but the 4.4.x is long term supported in the Linux community.

adam