This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM3358: Unable to boot from SD card

Part Number: AM3358

I have a Beaglebone Green that I have upgraded to the latest image from eLinux, I can load this onto an SD card and boot from it without issue.

However when I try to do the same with an SD card carrying the output of the create-sdcard.sh script (from the ti-processor-sdk-linux-am335x-evm-03.02.00.05), it does not boot - there is no serial output (over the FTDI connector).  The script output completes successfully:

################################################################################

This script will create a bootable SD card from custom or pre-built binaries.

The script must be run with root permissions and from the bin directory of
the SDK

Example:
 $ sudo ./create-sdcard.sh

Formatting can be skipped if the SD card is already formatted and
partitioned properly.

################################################################################


Available Drives to write images to: 

#  major   minor    size   name 
1: 179        0   15558144 mmcblk0
 
Enter Device Number or n to exit: 1
 
mmcblk0 was selected

/dev/mmcblk0 is an mmcblkx device
Unmounting the mmcblk0 drives
 unmounted /dev/mmcblk0p1
 unmounted /dev/mmcblk0p2
Current size of mmcblk0p1 2295 bytes
Current size of mmcblk0p2 15555339 bytes

################################################################################

	Select 2 partitions if only need boot and rootfs (most users).
	Select 3 partitions if need SDK & other content on SD card.  This is
        usually used by device manufacturers with access to partition tarballs.

	****WARNING**** continuing will erase all data on mmcblk0

################################################################################

Number of partitions needed [2/3] : 2

 
Now partitioning mmcblk0 with 2 partitions...
 

################################################################################

		Now making 2 partitions

################################################################################

1024+0 records in
1024+0 records out
1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.129762 s, 8.1 MB/s
DISK SIZE - 15931539456 bytes
Warning: The resulting partition is not properly aligned for best performance: 1s % 2048s != 0s
Warning: The resulting partition is not properly aligned for best performance: 4591s % 2048s != 0s

################################################################################

		Partitioning Boot

################################################################################
mkfs.fat 4.0 (2016-05-06)
mkfs.fat: warning - lowercase labels might not work properly with DOS or Windows
WARNING: Not enough clusters for a 32 bit FAT!

################################################################################

		Partitioning rootfs

################################################################################
mke2fs 1.43.3 (04-Sep-2016)
/dev/mmcblk0p2 contains a ext3 file system labelled 'rootfs'
	last mounted on /run/media/cmannett85/rootfs on Thu Jan 12 19:13:28 2017
Proceed anyway? (y,n) y
Discarding device blocks: done                            
Creating filesystem with 3888834 4k blocks and 972944 inodes
Filesystem UUID: 1ec8fd8c-2f11-40a4-a353-4b04b320209b
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done   



################################################################################

   Partitioning is now done
   Continue to install filesystem or select 'n' to safe exit

   **Warning** Continuing will erase files any files in the partitions

################################################################################


Would you like to continue? [y/n] : y

 
 
Mount the partitions 
 
Emptying partitions 
 

Syncing....

################################################################################

	Choose file path to install from

	1 ) Install pre-built images from SDK
	2 ) Enter in custom boot and rootfs file paths

################################################################################

Choose now [1/2] : 1

 
Will now install from SDK pre-built images
now installing:  ti-processor-sdk-linux-am335x-evm-03.02.00.05
################################################################################

	Copying files now... will take minutes

################################################################################

Copying boot partition

MLO copied


u-boot.img copied


Copying rootfs System partition
                                                                                                                          

Syncing...
 
Un-mount the partitions 
 
Remove created temp directories 
 
Operation Finished

The boot partition contains both an MLO and u-boot.img file.  Does anyone have any advice on how to further diagnose this issue?