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.

TMDXICE3359 unable to boot Linux

Hi

I have a working Beaglebone and have compiled/booted my own MLO and uImages on the bone without any problems.

I'm using "TMDXICE3359 rev 1.0A"  but I'm struggling to get it to boot MLO/u-boot, any help would be much appreciated!

From "am335x-evm-sdk-bin-05.04.01.00"  I have the following binaries:

-rwxr-xr-x. 1  120 nfsnobody     37403 Apr 11 14:09 MLO-am335x-evm
-rwxr-xr-x. 1  120 nfsnobody    231388 Apr 11 14:09 u-boot-am335x-evm.img
-rw-r--r--. 1  120 nfsnobody   3061672 Apr 11 14:09 uImage-am335x-evm.bin
[root@core am335x-evm-sdk-bin]#

I copied these files to the vfat partition on the sdcard as follows:

-rw-r--r--. 1 bruce bruce   37403 Jun 22 12:06 MLO
-rw-r--r--. 1 bruce bruce   37403 Jun 22 12:07 MLO-am335x-evm
-rw-r--r--. 1 bruce bruce  231388 Jun 22 12:07 u-boot-am335x-evm.img
-rw-r--r--. 1 bruce bruce  231388 Jun 22 12:07 u-boot.img
-rw-r--r--. 1 bruce bruce 3061672 Jun 22 12:07 uImage-am335x-evm.bin
-rw-r--r--. 1 bruce bruce 3061672 Jun 22 12:07 uImage.bin

When I boot I see the following in minicom:

*** StarterWare AM335x Boot Loader. Build - 1.0.0 ***
Copying application image from MMCSD to RAM
 Unable to open application file from MMCSD
Copying application image from SPI to RAM
 Image Copy Successful, Executing Application..

So this is probably because I didn't copy MLO as "app"....  so I tried and got something different:

The sdcard now has MLO as "app" and "app.bin" (just in case):

-rw-r--r--. 1 bruce bruce   37403 Jun 22 12:19 app
-rw-r--r--. 1 bruce bruce   37403 Jun 22 12:20 app.bin
-rw-r--r--. 1 bruce bruce   37403 Jun 22 12:06 MLO
-rw-r--r--. 1 bruce bruce   37403 Jun 22 12:07 MLO-am335x-evm
-rw-r--r--. 1 bruce bruce  231388 Jun 22 12:07 u-boot-am335x-evm.img
-rw-r--r--. 1 bruce bruce  231388 Jun 22 12:07 u-boot.img
-rw-r--r--. 1 bruce bruce 3061672 Jun 22 12:07 uImage-am335x-evm.bin
-rw-r--r--. 1 bruce bruce 3061672 Jun 22 12:07 uImage.bin
[root@core am335x-evm-sdk-bin]# 

And when I power on and press the rest button I get:

*** StarterWare AM335x Boot Loader. Build - 1.0.0 ***                          
Copying application image from MMCSD to RAM                                     

Copying to RAM completed successfully
 Image Copy Successful, Executing Application..

So I thought perhaps the "app" or "app.bin" needs to be "u-boot" and not "MLO" ... so I tried that, sdcard now looks like:

-rw-r--r--. 1 bruce bruce  231388 Jun 22 12:23 app
-rw-r--r--. 1 bruce bruce  231388 Jun 22 12:23 app.bin
-rw-r--r--. 1 bruce bruce  231388 Jun 22 12:07 u-boot-am335x-evm.img
-rw-r--r--. 1 bruce bruce  231388 Jun 22 12:07 u-boot.img
-rw-r--r--. 1 bruce bruce 3061672 Jun 22 12:07 uImage-am335x-evm.bin
-rw-r--r--. 1 bruce bruce 3061672 Jun 22 12:07 uImage.bin
[root@core boot]# 

and when I power on and press the reset button minicom now shows:

*** StarterWare AM335x Boot Loader. Build - 1.0.0 ***
Copying application image from MMCSD to RAM

Copying to RAM completed successfully
 Image Copy Successful, Executing Application..

I'm not sure what application it's executing successfully? ...as I sure can't see any MLO or u-boot...  :))

So I then tried to compile my own images. I used "ti-sdk-am335x-evm-05.04.01.00" ...which compiled everything perfectly but again I got the exact same behavior as above.

My Fedora system sees the board when I connect:


Jun 22 12:32:07 core kernel: [60235.270134] usb 1-5.4: USB disconnect, device number 14
Jun 22 12:32:07 core kernel: [60235.270344] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
Jun 22 12:32:07 core kernel: [60235.270357] ftdi_sio 1-5.4:1.1: device disconnected
Jun 22 12:32:09 core kernel: [60237.890719] usb 1-5.4: new high-speed USB device number 15 using ehci_hcd
Jun 22 12:32:09 core kernel: [60237.977794] usb 1-5.4: New USB device found, idVendor=0403, idProduct=a6d0
Jun 22 12:32:09 core kernel: [60237.977798] usb 1-5.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jun 22 12:32:09 core kernel: [60237.977801] usb 1-5.4: Product: ICE
Jun 22 12:32:09 core kernel: [60237.977803] usb 1-5.4: Manufacturer: FTDI
Jun 22 12:32:09 core kernel: [60237.978866] usb 1-5.4: Ignoring serial port reserved for JTAG
Jun 22 12:32:09 core kernel: [60237.979606] ftdi_sio 1-5.4:1.1: FTDI USB Serial Device converter detected
Jun 22 12:32:09 core kernel: [60237.979643] usb 1-5.4: Detected FT2232H
Jun 22 12:32:09 core kernel: [60237.979646] usb 1-5.4: Number of endpoints 2
Jun 22 12:32:09 core kernel: [60237.979648] usb 1-5.4: Endpoint 1 MaxPacketSize 512
Jun 22 12:32:09 core kernel: [60237.979650] usb 1-5.4: Endpoint 2 MaxPacketSize 512
Jun 22 12:32:09 core kernel: [60237.979652] usb 1-5.4: Setting MaxPacketSize 512
Jun 22 12:32:09 core kernel: [60237.979984] usb 1-5.4: FTDI USB Serial Device converter now attached to ttyUSB0
Jun 22 12:32:09 core mtp-probe: checking bus 1, device 15: "/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.4"
Jun 22 12:32:09 core mtp-probe: bus: 1, device: 15 was not an MTP device
[root@core ti-sdk-am335x-evm-05.04.01.00]# 

So.....how do I get away from this embedded "app" story and move to embedded linux (MLO, u-boot and uImage) ..... any help would be greatly appreciated!

Cheers

Bruce