Getting u-boot prompt using UART port for AVNET OMAP-L138 EVM.

From RidgeRun Developer Connection

Revision as of 21:34, 31 January 2011 by Mgruner (Talk | contribs)
Jump to:navigation, search

the AVNET Board still don't have support to recover the SoMM

Contents

Recovering the board

Download the package from rr-recovery-tools-avnet.tar.gz (Only members are allowed to download)

Untar the file rr-recovery-tools-avnet.tar.gz

rr@rr-desktop:~$ tar -xvzf rr-recovery-tools-avnet.tar.gz 
RECOVERY-AVNET-TOOLS/
RECOVERY-AVNET-TOOLS/u-boot.bin
RECOVERY-AVNET-TOOLS/ubl_OMAPL138_SPI_MEM.bin
RECOVERY-AVNET-TOOLS/sfh_OMAP-L138.exe

Set the boot pins to UART2 boot mode

This is done by setting switch S7 on the OMAP-L138 EVM according to the following table:


Pin# 1 2 3 4 5 6 7 8
Position OFF OFF OFF OFF OFF OFF ON ON


Connect a serial cable from the host computer to the OMAP-L138 EVM
Open a command prompt on the host computer and change directory to where the flashing utility was saved

Run the flashing utility with this command

rr@rr-desktop:~$ mono./sfh_OMAP-L138.exe -erase -p <PORT>

Note:If the serial port is not on ttyS0, the correct port must be specified using the "-p" option. To determine which ttySX port to use, open minicom, connect to one of the ports, and make sure the word "BOOTME" appears when the EVM is reset.


 rr@rr-desktop:~$ mono ./sfh_OMAP-L138.exe -erase -p /dev/ttyS1


-----------------------------------------------------
   TI Serial Flasher Host Program for OMAP-L138
   (C) 2010, Texas Instruments, Inc.
   Ver. 1.67
-----------------------------------------------------


      [TYPE] Global erase
    [DEVICE] SPI_MEM

Attempting to connect to device /dev/ttyS1...
Press any key to end this program at any time.

(AIS Parse): Read magic word 0x41504954.
(AIS Parse): Waiting for BOOTME... (power on or reset target now)
(AIS Parse): BOOTME received!
(AIS Parse): Performing Start-Word Sync...
(AIS Parse): Performing Ping Opcode Sync...
(AIS Parse): Processing command 0: 0x58535901.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Loading section...
(AIS Parse): Loaded 9244-Byte section to address 0x80000000.
(AIS Parse): Processing command 1: 0x58535901.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Loading section...
(AIS Parse): Loaded 668-Byte section to address 0x8000241C.
(AIS Parse): Processing command 2: 0x58535906.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Performing jump and close...
(AIS Parse): AIS complete. Jump to address 0x80000000.
(AIS Parse): Waiting for DONE...
(AIS Parse): Boot completed successfully.

Waiting for SFT on the OMAP-L138...

Erasing flash
 100% [ ???????????????????????????????????????????????????????????? ]
                            Erase complete                 

Set the boot pins to SPI boot mode

After the UBL and u-boot files have been flashed, set the boot pins to SPI boot mode and reboot the board. This is done by setting switch S7 on the OMAP-L138 EVM according to the following table:

Pin# 1 2 3 4 5 6 7 8
Position OFF OFF OFF OFF OFF OFF OFF OFF

Run the flashing utility with this command

Once u-boot has been loaded, reboot the board and enjoy your recovered board


rr@rr-desktop:~$ mono ./sfh_OMAP-L138.exe -flash ubl.spibin u-boot.bin -p /dev/ttyS1


-----------------------------------------------------
   TI Serial Flasher Host Program for OMAP-L138
   (C) 2010, Texas Instruments, Inc.
   Ver. 1.67
-----------------------------------------------------


      [TYPE] UBL and application image
       [UBL] ubl.spibin
 [APP IMAGE] u-boot.bin
    [DEVICE] SPI_MEM

Attempting to connect to device /dev/ttyS1...
Press any key to end this program at any time.

(AIS Parse): Read magic word 0x41504954.
(AIS Parse): Waiting for BOOTME... (power on or reset target now)
(AIS Parse): BOOTME received!
(AIS Parse): Performing Start-Word Sync...
(AIS Parse): Performing Ping Opcode Sync...
(AIS Parse): Processing command 0: 0x58535901.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Loading section...
(AIS Parse): Loaded 9244-Byte section to address 0x80000000.
(AIS Parse): Processing command 1: 0x58535901.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Loading section...
(AIS Parse): Loaded 668-Byte section to address 0x8000241C.
(AIS Parse): Processing command 2: 0x58535906.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Performing jump and close...
(AIS Parse): AIS complete. Jump to address 0x80000000.
(AIS Parse): Waiting for DONE...
(AIS Parse): Boot completed successfully.

Waiting for SFT on the OMAP-L138...

Flashing UBL ubl.spibin (9340 bytes) at 0x00000000

 100% [ ???????????????????????????????????????????????????????????? ]
                  Image data transmitted over UART.                   

 100% [ ???????????????????????????????????????????????????????????? ]
                       UBL programming complete                       


Flashing application u-boot.bin (153444 bytes) at 0x00010000

 100% [ ???????????????????????????????????????????????????????????? ]
                  Image data transmitted over UART.                   

 100% [ ???????????????????????????????????????????????????????????? ]
                   Application programming complete                   


Operation completed successfully.

Before installing the sdk

Rebooting the board will show the configuration above:

UBL customized by RidgeRun
Booting TI User Boot Loader
        UBL Version: 1.65
        UBL Flashtype: SPI 
Starting SPI Memory Copy...
Valid magicnum, 0x55424CBB, found at offset 0x00010000.
   DONE
Jumping to entry point at 0xC1080000.


U-Boot customized by RidgeRun
U-Boot 2009.01 (Jul 20 2010 - 15:19:52)

DRAM:  64 MB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
ARM Clock : 300000000 Hz
DDR Clock : 300000000 Hz
Invalid MAC address read.
Hit any key to stop autoboot:  0 
AVNET # 

set the ethaddr on the u-boot environment

The MAC address is printed on your SoC, as a 6 pair of hexadecimal numbers separated by colons.

u-boot > setenv ethaddr <MAC-ADDRESS GIVEN WITH THE SoMM>
u-boot > saveenv

You're able and ready to install the sdk

Installing the SDK

Go to SDK dir

rr@rr-desktop:~$ cd $(DEVDIR)


Install kernel image on your board

Go to your DEVDIR and install your kernel's image.

rr@rr-desktop:~$ make installkernel

Install the SDK on your board

rr@rr-desktop:~$ make install
Navigation
Toolbox