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.

OMAP-L138 Serial Flash utility

Other Parts Discussed in Thread: AM1808, OMAP-L138, OMAPL138

Hi,

 There is a serial flash utility for the OMAP L138 on http://processors.wiki.ti.com/index.php/Serial_Boot_and_Flash_Loading_Utility_for_OMAP-L138 . The customer is interested in building and running this completely from Linux and has seen issues with MONO frameworks on new Linux versions and had to use older version like Ubuntu 6.10 to make it run. Is this version been used with newer Ubuntu versions like 9.10?

Thanks,

--Gunter

  • Has the customer tried out the serial flasher with his version of Ubuntu? We have not tested it with that distribution, but the newer versions of MONO should work without issue.

    Jeff

  • I ran the demo application on AM1808 logic eXperimenter board. After I  plugged the ethernet, the device freezed. After several reset, I realized that the device didn't boot Linux anymore. I presumed that the flash gets corrupted on the way, so that I tried to reflash it using the instruction for restoring it without success.

    Note that I used the binaries and software already available with the SDK.

    Is this problem related to the fact that I am using an AM1808 instead of OMAP-L138 ? Has someone succeed in reflashing an AM1808 SOC ?

  • Since you posted this under a serial flasher thread, I assume you are using the serial flasher to reflash the SPI flash? The SDK only comes with the CCS version of the flasher.

    Jeff

  •  

    I followed the instruction for Flashing images to SPI Flash. Since I don't have the full version of CCS, I used the Serial Flasher requiring the UART cable available from here as suggested. I compile the OMAPL138 AM1808 TI Flash and Boot Utilities and use the executable generated without any success :(. The command issued was

     

    sfh_OMAP-L138.exe -flash ubl_AM1808_SPI_MEM.bin u-boot.bin -targetType AM1808 -flashType SPI_MEM -p COM1 -baud 115200

    and the output of the program:

     

     

     

    -----------------------------------------------------

       TI Serial Flasher Host Program for OMAP-L138

       (C) 2010, Texas Instruments, Inc.

       Ver. 1.67

    -----------------------------------------------------

          [TYPE] UBL and application image

          [UBL] ubl_AM1808_SPI_MEM.bin

         [APP IMAGE] u-boot.bin

         [DEVICE] SPI_MEM

     

    Attempting to connect to device COM1...

    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 8684-Byte section to address 0x80000000.

    (AIS Parse): Processing command 1: 0x58535901.

    (AIS Parse): Performing Opcode Sync...

    (AIS Parse): Loading section...

    (AIS Parse): Loaded 644-Byte section to address 0x800021EC.

    (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...

     

    Aborting program...

     

     

    Interfacing to the OMAP-L138 via UART failed.

    Please reset or power-cycle the board and try again...

    Is it necessary to use the full CCS version to be able to reprogram a corrupted SPI flash ?

     

     

  • No the serial flasher should work stand-alone without CCS. Can you connect to CCS and see where the PC is after the "Waiting for SFT on the OMAP-L138" message?

    Also as a test, can you try using the ubl_OMAPL138_SPI_MEM.bin instead?

    Jeff

  • I try ubl_OMAPL138_SPI_MEM.bin with and without option "-targetType AM1808" with the same result:

    ./sfh_OMAP-L138.exe -flash ubl_OMAPL138_SPI_MEM.bin u-boot.bin -targetType AM1808 -flashType SPI_MEM -p COM1 -baud 115200

     

    -----------------------------------------------------

       TI Serial Flasher Host Program for OMAP-L138

       (C) 2010, Texas Instruments, Inc.

       Ver. 1.67

    -----------------------------------------------------

     

     

          [TYPE] UBL and application image

           [UBL] ubl_OMAPL138_SPI_MEM.bin

     [APP IMAGE] u-boot.bin

        [DEVICE] SPI_MEM

     

    Attempting to connect to device COM1...

    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 8720-Byte section to address 0x80000000.

    (AIS Parse): Processing command 1: 0x58535901.

    (AIS Parse): Performing Opcode Sync...

    (Serial Port): Read error! (The operation has timed out.)

    (AIS Parse): I/O Error in read!

     

    Aborting program...

    (Serial Port): Read error! (Thread was being aborted.)

     

     

    Interfacing to the OMAP-L138 via UART failed.

    Please reset or power-cycle the board and try again...

    As for using CCS to debug the PC I don't understand what you mean!? I could try using gdb to debug sfh_OMAP-L138.exe but I am not proficient enough to do it yet. Anyway, I use a serial sniffer and find out that the AM1808 stop responding to request.

  • I meant connect to the device with CCS and see what address the program counter (PC) is pointing to. Then we can determine if the code got loaded or not.

    Jeff

  • I was able to connect to the target by following the instruction of the Zoom AM1606 DevKit User Manual.

    But now it seems it won't work anymore ... When connecting to the target in CCS Debug Perspective, I systematically got

    Error connecting to the target:
    Error 0x80000244/-2131
    Fatal Error during: Register, Initialization, OCS,
    Cannot access register at 0x00000000

    Nothing changed since then, except for the fact that the bootloader in SPI Flash might well be corrupted. I don't have any spare AM1808 SOC so I can't test another module yet.

  • Make sure the boot mode is set to emulation mode before connecting.

    Jeff