• State
  • Locked Locked
  • Replies 9 replies
  • Subscribers 100 subscribers
  • Views 2047 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.

Where can I get the stock (factory) version of u-boot for OMAP-L138 LCDK?

Tankist
Expert 1690 points
Other Parts Discussed in Thread: OMAP-L138, OMAPL138

I need to repair u-boot in OMAP-L138 LCDK. I just found a .bin version in MCSDK, I made .ais file and flashed it into my board. But the messages which I get when the board is booting are differ to native messages which I see in the new borad. So I realize that versions of u-boot don't match each other. I need the exactly copy of the factory version. Where can I get it?

  • 0
    TI__Guru 65405 points
    Hi Tankist,

    You can download the last MCSDK release from the link:
    software-dl.ti.com/.../index_FDS.html
    but you probably done this yet.
    Could you attach booting log from the current software and if you kept same booting log from your previous software to determine the versions?

    BR
    Tsvetolin Shulev
  • 0
    TI__Mastermind 43955 points
    Hi Tankist,
    You can find the pre-built u-boot binary in the following location once you installed the latest MCSDK of OMAPL138.

    ~ti\mcsdk_1_01_00_02\images\u-boot-omapl138-lcdk.bin
  • 0 in reply to Shankari G
    Expert 1690 points

    Shankari G said:
    You can find the pre-built u-boot binary in the following location once you installed the latest MCSDK of OMAPL138.

    ~ti\mcsdk_1_01_00_02\images\u-boot-omapl138-lcdk.bin

    I said about it before - this version DOES NOT MATCH u-boot with factory software.

    These are sample of start log both versions:

    NAND:  512 MiB                                            NAND:  512 MiB                                    
    MMC:   davinci: 0                                       MMC:   davinci: 0                                 
    Bad block table found at page 262080, version 0x01      Bad block table found at page 262080, version 0x01
    Bad block table found at page 262016, version 0x01      Bad block table found at page 262016, version 0x01
    *** Warning - bad CRC, using default environment        *** Warning - bad CRC, using default environment  

    1. In:    serial                                                              In:    serial                                     
    2. Out:   serial                                                            Out:   serial                                     
    3. Err:   serial                                                            Err:   serial                                     
    4. ARM Clock : 456000000 Hz                                           
    5. DDR Clock : 150000000 Hz                               Net:   No ETH PHY detected!!!                                
    6. Net:   Error: Ethernet init failed!                           Error: Ethernet init failed!                      
    7. Board Net Initialization Failed                             Board Net Initialization Failed        
    8. DaVinci-EMAC                                                     DaVinci-EMAC                                      
    9. Hit any key to stop autoboot:  0                           Hit any key to stop autoboot:  0                  
    10. Card did not respond to voltage select!             Card did not respond to voltage select!           
    11. Unknown command 'sf' - try 'help'                        Unknown command 'sf' - try 'help'                 
    12. Unknown command 'sf' - try 'help'                        Unknown command 'sf' - try 'help'                 
    13. Wrong Image Format for bootm command        Wrong Image Format for bootm command              
    14. ERROR: can't get kernel image!                         ERROR: can't get kernel image!                    
    15. U-Boot >                                                                 U-Boot >                               

    The left column is the 'native' (factory) u-boot, the right one - \mcsdk_1_01_00_02\images\u-boot-omapl138-lcdk.bin

    You can see easily the differences in rows 4-6.

  • 0 in reply to Tankist
    TI__Guru** 116100 points
    This is the binary which is default u-boot binary.
    May I know what is the purpose of restoring the actual facotry u-boot ?
  • 0 in reply to Titusrathinaraj Stalin
    Expert 1690 points
    Because it has at least different PLL settings for DSP side, maybe something else. I developed my DSP application with that u-boot, but when I flashed it with Starterware bootloader I realized that something wrong with the frequency. When I restored u-boot from MCSDK the problem remained. So I need to analyse the problem.
    I don't understand what the problem is to share the binary file for me.
  • 0 in reply to Tankist
    TI__Mastermind 43955 points

    Hi Tankist,


    Because it has at least different PLL settings for DSP side, maybe something else. I developed my DSP application with that u-boot, but when I flashed it with Starterware bootloader I realized that something wrong with the frequency. When I restored u-boot from MCSDK the problem remained. So I need to analyse the problem.

    If you developed DSP application with u-boot, you can boot u-boot then run DSP application, why you are using the starterware bootloader ?

    Able to run your DSP application from u-boot ?
    Some reference link here.




    If no, then please work with starterware application & bootloader.

  • 0 in reply to Shankari G
    Expert 1690 points

    I use Starterware bootloader because I can't run my DSP application from u-boot.

    I still haven't got an answer for my question.

  • 0 in reply to Tankist
    TI__Mastermind 43955 points
    Hi Tankist,
    Did you refer the link which is from my last response ?
    support.criticallink.com/.../DSP_Quick_Start

    Can you patch and enable the "bootdsp" command in u-boot ?
  • 0 in reply to Shankari G
    Expert 1690 points

    It's very intresting, thank you.It might cause a problem because I did the similar thing for "bootelf" command when I tried to run ARM application from u-boot, but it was unsuccessful - application doesn't start.

    I will try it as soon as I recover my u-boot back.