• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 99 subscribers
  • Views 425 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.

LINUXSDK-OMAPL138: SPI-boot

Risto Hedman
Expert 1770 points

Part Number: LINUXSDK-OMAPL138
Other Parts Discussed in Thread: OMAP-L138, OMAPL138

Hi,

We boot our custom board with SD and then from uBoot:

tftp 0xc0700000 u-boot.ais
sf probe 0
sf erase 0 0x100000
sf write 0xc0700000 0x0 0x100000

To verify 'TIPA'
sf read 0xc0701000 0x0 0x100000
md 0xc0701000 10

It seems to be ok.

SDK is 06_01_00_08 and in uBoot  .config all SPI- related things have been turned on and others, e.g. SD- boot related off. 

However, when I try SPI- boot, nothing happens.

So I would like to ask if there are any limitations with SPI1- boot in these 'new' SDK's. As I understand the u-boot.ais should be directly bootable from SPI as it is from SD (with slightly different  .config settings) is it so?

Regards,

ristoH

  • 0
    TI__Guru 50170 points

    Hi, Risto,

    Could you take a look at the video on "Restoring and Updating U-boot NAND on OMAP-L138 LCD" if you haven't seen it and see if it is what you want to do?

    https://www.youtube.com/watch?v=NKSdRAL7cLk

    Rex

  • 0 in reply to Rex Chang
    Expert 1770 points

    Hi Rex,

    Thank you but that video does not help me. What works with me:

    1. I can burn u-boot.ais into a SPI-FLASH into address I want to
    2. I can verify the content of newly burned content of the SPI-FLASH
    3. I've verified with scope that 138 is reading SPI-FLASH while booting if boot- switches command so

    However the board does not boot, either something is missing or is wrong in u-boot.ais OR the the address of the u-boot.ais in SPI-FLASH is wrong.

    Br, ristoH

  • 0 in reply to Risto Hedman
    TI__Guru 50170 points

    Hi, Risto,

    i just checked the U-boot User's Guide, SPI boot is not supported for OMAP-L138. In OMAP-L138 LCDK User's Guide, the NAND is on EMIF interface, and the dip switch SW1 to set boot mode has only UART2, NAND16, and MMC/SD0 modes supported. I am not sure how the SPI boot mode can be supported. Am I missing something?

    Rex

  • 0 in reply to Rex Chang
    Expert 1770 points

    Hi Rex,

    OMAPL138 definitely can boot from SPI, we've been using this property for a long time: uBoot.ais generated with AisGen  works fine. AisGen adds HW set up for RBL and that is it - when one loads this somehow to SPI-FLASH, it works.

    In

    ti-processor-sdk-linux-omapl138-lcdk-06.01.00.08/board-support/u-boot-2019.01+gitAUTOINC+029e4c009a-g029e4c009a/board/davinci/da8xxevm/README.da850

    there are instructions to do that - so far I've not managed to realize that because I stucked into SD- boot problem, which I have to solve first:

    U-Boot SPL 2019.01-g9b2e382ac5-dirty (Mar 18 2020 - 17:43:48 +0200)
    Trying to boot from MMC1
    spl: could not find mmc device 0. error: -19
    SPL: failed to boot from all boot devices
    ### ERROR ### Please RESET the board ###

    Best Regards,

    ristoH

  • 0 in reply to Risto Hedman
    Expert 1770 points

    Hi,

    I did some additional testing:

    1. Compiled uBoot with 'da850evm_defconfig' - only changing CONFIG_SPI_BOOT=y, CONFIG_SD_BOOT=n
    2. Booted uBoot with some old SD with operational eth0 and sf
    3. Flashed SPI- flash with instruction from /board/davinci/da8xxevm/README.da850 / 'Flashing the images to SPI' - OK

    And

    1. Compiled uBoot with 'da850evm_defconfig' - only changing CONFIG_SPI_BOOT=n, CONFIG_SD_BOOT=y
    2. Prepared SD with dd if=u-boot.ais of=/dev/sdb seek=117 bs=512 conv=fsync

    From boot console, changing boot switches:

    U-Boot SPL 2019.01-gaa412e8abe-dirty (Mar 19 2020 - 12:06:13 +0200)
    Trying to boot from SPI
    SPI probe failed.
    SPL: failed to boot from all boot devices
    ### ERROR ### Please RESET the board ###

    U-Boot SPL 2019.01-g9b2e382ac5-dirty (Mar 18 2020 - 17:43:48 +0200)
    Trying to boot from MMC1
    spl: could not find mmc device 0. error: -19
    SPL: failed to boot from all boot devices
    ### ERROR ### Please RESET the board ###

    Could someone please explane what happens here? Both devices obviously 'boot', meaning SPL starts but either finds u-boot which is in the very same 'file' SPL is booting from.

    Regards,

    ristoH