• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 100 subscribers
  • Views 239 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

AM6442: OSPI interface place QSPI flash, no SPI CLK out when uboot.

Taylor Lin
Prodigy 150 points
Part Number: AM6442

Hi Sir,

I used the MX25L6433FM2I-08G (SO8-QSPI) on the OSPI interface, the terminal didn't show anything, then checked that OSPI0_CLK was low, indicating that QSPI was not working.

Then I refer to https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1034403/am6442-how-to-boot-with-qspi-boot?tisearch=e2e-sitesearch&keymatch=QSPI%25252525252525252520Boot#, Bootmode is set to SPI, the terminal has information output, but it still cannot be turned on. The log information below shows that there is no device on the SPI interface.


U-Boot SPL 2021.01-g827cbd9e-dirty (Sep 02 2022 - 13:23:58 +0800)
SYSFW ABI: 3.1 (firmware rev 0x0016 '22.1.1--v2022.01 (Terrific Llam')
SPL initial stack usage: 13392 bytes
Trying to boot from SPI
jedec_spi_nor flash@0: unrecognized JEDEC id bytes: c2, 20, 17
SPI probe failed.
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

How to boot up from the OSPI interface with QSPI/SPI flash?

1. Boot Mode is set to QSPI, why that OSPI0_CLK didn't output?

2. Does it work when OSPI interface uses SPI flash?

3. If Q2 works, which option is Boot Mode set on, can you share the steps to build the Boot Image?

 

BR, Taylor

  • 0
    TI__Guru 65105 points

    Hello Taylor,

    Taylor Lin said:
    U-Boot SPL 2021.01-g827cbd9e-dirty (Sep 02 2022 - 13:23:58 +0800)
    SYSFW ABI: 3.1 (firmware rev 0x0016 '22.1.1--v2022.01 (Terrific Llam')
    SPL initial stack usage: 13392 bytes
    Trying to boot from SPI
    jedec_spi_nor flash@0: unrecognized JEDEC id bytes: c2, 20, 17
    SPI probe failed.

    From the log file, it looks to me the first stage BL--R5 SPL boots ok from QSPI. Then R5 SPL fails probing QSPI for loading the next stage A53 SPL from QSPI.
    I'm adding some checkpoints:

    - Check with the flash vendor on QSPI driver support in u-boot, for example, Is the flash ID in "/drivers/mtd/spi/spi-nor-ids.c"?
    - Check if QSPI DT node and Pinmux are configured correctly in R5/A53 SPL/u-boot DTS files?
    I'm using OSPI on AM64x EVM as an example, searching "*ospi0*" in the following DTS files for your reference.
    arch/arm/dts/k3-am642-evm-u-boot.dtsi
    arch/arm/dts/k3-am642-evm.dts
    arch/arm/dts/k3-am642-r5-evm.dts

    Best,
    -Hong

  • 0 in reply to Hong Guan64
    Prodigy 150 points

    Hi Hong,

    Thanks for your reply, the log file is that bootstrap set to SPI mode, if set to QSPI mode, there is no log.

    I will pass your suggestion to our software team to check if it works in SPI mode.

    BR, Taylor

  • 0 in reply to Taylor Lin
    Prodigy 150 points

    Hi Hong,

    Finally, we boot in SPI mode, AM64x cannot boot in QSPI mode.

    Maybe TI needs to update the AM64x datasheet because the SoC ROM code doesn't support QSPI mode boot, thanks.

    BR, Taylor