• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 476 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

unable to boot from u-boot with 'new' version of OMAPL137

Gilad kirshenboim
Prodigy 35 points
Other Parts Discussed in Thread: OMAP-L137

Hello,

We are using several OMAPL137 for our development , and we realized that with one of them we are unable to boot properly from u-boot.

After boot  we get 'Warning - Bad CRC ...." , and when running "sf probe 0" we get "fail to initialize SPI flash" 

We found that the difference is in the assembled  SPI flash type (the working boards are using 25x32 , while the unworking has the 25q32 ) these flash are different in their  winbond ID (0x3016 for the 'good' board and  0x4016 for the 'bad' board).

We assume this is related to the u-boot code programed in the flash 

pls help us to resolve this issue ASAP / send us a proper u-boot code.

Tnx,

Gilad

  • 0
    Guru 26430 points

    The last I checked, TI makes only two u-boot binaries available. One at arago-project.org dated 2009.11. The other in PSP 3.20 which also based upon 2009.11 version of u-boot. Neither of which supports 25q32.

    Newer versions of the PSP 3.x line support your memory chip but sadly TI does not provide any pre-built images for the OMAP-L:137. You can use the PSP source to build the OMAP-L137 binary. It appears that OMAP-L137 binaries haven't been updated since 2009.11.

    The head release of u-boot at arago-project.org looks to support your chip. You will have to build it youself for the OMAP-L137. Support for the 25q32 is done by adding a couple lines to drivers/mt/spi/winbond.c. You could add those lines to your version of u-boot. Once again you will have rebuild it yourself.

  • 0 in reply to Norman Wong
    TI__Intellectual 2620 points

    There's an updated version of SPIwriter and u-boot (for the same release that comes with the EVM) for the new SPI flash. They are located at the SDI site for the OMAP-L137 EVM http://support.spectrumdigital.com/boards/evmomapl137/revg/ 

  • 0 in reply to Loc Truong
    Prodigy 35 points

    Hi,

    I followed the steps under http://processors.wiki.ti.com/index.php/Serial_Boot_and_Flash_Loading_Utility_for_OMAP-L137 

    obtained the images from dsp-spi-ais.bin and dsp-spi-ais.bin from REL_LSP_02_20_00_07/PSP_02_20_00_07/bin/ and the new u-boot from the proposed location http://support.spectrumdigital.com/boards/evmomapl137/revg/ 

    The programmed seems to run well (see below) , but after re-booting the board (with the updated boot-switch - OFF-ON-OFF-ON-OFF-OFF) the board couldnt re-boot - see nothing with terminal.

    I have other OMAP L137 EVB which works well .

    I think I need to re-call the specific board .... pls advice.

     

    C:\Users\Admin\Desktop\u-boot>sfh_OMAP-L137.exe -flash_dsp dsp-spi-ais.bin ubl-
    pi.bin u-boot.bin -p COM7
    -----------------------------------------------------
    TI Serial Flasher Host Program for OMAP-L137
    (C) 2012, Texas Instruments, Inc.
    Ver. 1.67
    -----------------------------------------------------


    [TYPE] DSP UBL, ARM UBL, and application image
    [DSP UBL] dsp-spi-ais.bin
    [ARM UBL] ubl-spi.bin
    [APP IMAGE] u-boot.bin
    [TARGET] OMAPL137_v2
    [DEVICE] SPI_MEM
    [SPI Block] 0


    Attempting to connect to device COM7...
    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 15072-Byte section to address 0x11800000.
    (AIS Parse): Processing command 1: 0x58535901.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Loading section...
    (AIS Parse): Loaded 792-Byte section to address 0x11803AE0.
    (AIS Parse): Processing command 2: 0x58535901.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Loading section...
    (AIS Parse): Loaded 32-Byte section to address 0x11803E18.
    (AIS Parse): Processing command 3: 0x58535901.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Loading section...
    (AIS Parse): Loaded 20-Byte section to address 0x11803E38.
    (AIS Parse): Processing command 4: 0x58535906.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Performing jump and close...
    (AIS Parse): AIS complete. Jump to address 0x11803560.
    (AIS Parse): Waiting for DONE...
    (AIS Parse): Boot completed successfully.

    Waiting for SFT on the OMAP-L137...

    Flashing DSPUBL dsp-spi-ais.bin (5460 bytes) at 0x00000000

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

    100% [ ████████████████████████████████████████████████████████████ ]
    DSP UBL programming complete


    Flashing ARM UBL ubl-spi.bin (16384 bytes) at 0x00002000

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

    100% [ ████████████████████████████████████████████████████████████ ]
    ARM UBL programming complete


    Flashing application u-boot.bin (151248 bytes) at 0x00008000

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

    100% [ ████████████████████████████████████████████████████████████ ]
    Application programming complete


    Operation completed successfully.