TDA4VH-Q1: tiboot3.bin can't read spi nor id

Hi Fang,

Is this a custom board if yes then which part is being used?
Have you ported the custom changes from SDK 8.5 yo 9.2?

- Keerthy

I change only DDR part ;

I burn the tiboot3.bin to spi nor flash ;

then power on ; boot from spi nor flash ;

tiboot3 read the spi nor id is 0xff 0xff ;

how to config the uboot ?how to modify the dts?

can you give me some advice?

Hello Fang,

Can you share the logs from 8.5 SDK?

Changing DDR should not impact reading from spi. Which OSPI part is being used,?

Did you have custom changes on 8.5 SDK to make this OSPI work? If yes have you ported them to latest SDK?

Regards, 

Keerthy 

8.5 SDK I have no change for OSPI work

8.5 and 9.2.0 have so much different ;

9.2.0  default is spi nand boot ,how can I make change for spi nor boot . 

when I use TF card boot ;

sf probe  is  spi nand,but there is SPI NOR flash on board

=> sf probe
spi_nand nand@0: unknown raw ID fde916f0
Failed to initialize SPI flash at 0:0 (error 0)

how can I change dts to boot spi nor flash

Hi Fang,

Thanks for the details. I understood the issue.

diff --git a/board/ti/j784s4/evm.c b/board/ti/j784s4/evm.c
index 7e7f4a55..3bb26db9 100644
--- a/board/ti/j784s4/evm.c
+++ b/board/ti/j784s4/evm.c
@@ -79,6 +79,8 @@ static void __maybe_unused detect_enable_spinand(void *blob)
 #if defined(CONFIG_SPL_BUILD)
 void spl_perform_fixups(struct spl_image_info *spl_image)
 {
+       return;
+
        detect_enable_spinand(spl_image->fdt_addr);
        if (IS_ENABLED(CONFIG_K3_INLINE_ECC))
                fixup_ddr_driver_for_ecc(spl_image);

Can you try the above change so that there is no call to detect_enable_spinand.

This will ensure that OSPI NOR is chosen.

Let me know.

Thanks,
Keerthy

whe boot from TF card;  I can read the spi nor falsh ID ,when  I use the patch you give me .

But I use the same tiboot3.bin with TF card. 

The spi NOR ID stuill is ff ff ff ff

The flash is GD25Q256DFJRR

=> sf probe
jedec_spi_nor flash@0: unrecognized JEDEC id bytes: c8, 40, 19
Failed to initialize SPI flash at 0:0 (error 0)

U-Boot SPL 2023.04 (May 31 2024 - 19:53:28 +0800)
EEPROM not available at 0x50, trying to read at 0x51
Reading on-board EEPROM at 0x51 failed -121
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
SPL initial stack usage: 13456 bytes
Trying to boot from SPI
jedec_spi_nor flash@0: unrecognized JEDEC id bytes: ff, ff, ff
SPI probe failed.
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

The spi nor flash'ID still can't be read when I use spi boot.

U-Boot SPL 2023.04 (May 31 2024 - 19:53:28 +0800)
EEPROM not available at 0x50, trying to read at 0x51
Reading on-board EEPROM at 0x51 failed -121
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
SPL initial stack usage: 13456 bytes
Trying to boot from SPI
jedec_spi_nor flash@0: unrecognized JEDEC id bytes: ff, ff, ff
SPI probe failed.
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

fang gaojun said:

whe boot from TF card;  I can read the spi nor falsh ID ,when  I use the patch you give me .

Can you please confirm that the change is not helping you Boot? The newer SDK has NAND boot support added.
My suspicion is that on your custom board the Nand is getting chosen and hence the above hack to remove that out
of the equation. 

- Keerthy

The change help my Boot, whe I boot from tf card, I can read the spi nor ID .

We use boot pin below.

I want boot from QSPI  nor flash ,how to config the boot pin ,can you give me some advice.

fang gaojun said:

whe I boot from tf card

I am not understanding what is TF card.

Pasting from TRM:

MCU4 pin is 1 and MCU3 pin is 0 for QSPI.

- Keerthy

TF card is the SD card.

According to the table below, our configuration is accurate.

Last time you suspected that we started from SPI NAND.

spi nand boot mode is "serial nand" .  is it right ? 

if our boot pin config is correct . why the spi nor ID can't be read.

our  board hw is right,because  we boot from SD card ,use "sf porbe" cmd,we can read the spi nor id.

Hi Fang,

fang gaojun said:

our  board hw is right,because  we boot from SD card ,use "sf porbe" cmd,we can read the spi nor id

So summarizing the observations.

1. With SD boot sf probe you are able to read the QSPI NOR ID?
2. Are you seeing the correct QSPI device?
3. Please share the command output when you are seeing that SPI nor ID is read.
4. Are you able to copy/flash boot loaders to QSPI NOR?

- Keerthy

1.With SD boot sf probe you are able to read the QSPI NOR ID?

yes

2.Are you seeing the correct QSPI device?

when boot from SD boot , and put sf probe in  uboot cmd .

=> sf probe
jedec_spi_nor flash@0: unrecognized JEDEC id bytes: c8, 40, 19
Failed to initialize SPI flash at 0:0 (error 0

3.Please share the command output when you are seeing that SPI nor ID is read.

 sf probe

4.Are you able to copy/flash boot loaders to QSPI NOR?

out system can run ,when we boot from SD card,so we use "dd if=./tiboor3.bin of=/dev/mtdblock0" cmd to wite tiboo3.bin to qspi flash .

then put the config pin to spi nor boot , tiboot3.bin can't load tispil.bin ,because ,it can't read the spi nor flash ID like below.

U-Boot SPL 2023.04 (May 31 2024 - 19:53:28 +0800)
EEPROM not available at 0x50, trying to read at 0x51
Reading on-board EEPROM at 0x51 failed -121
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
SPL initial stack usage: 13456 bytes
Trying to boot from SPI
jedec_spi_nor flash@0: unrecognized JEDEC id bytes: ff, ff, ff
SPI probe failed.
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

sorry ,My phenomenon has reappeared again.

I use the following command to burn those three files.

dd if=./tiboot3.bin of=/dev/mtdblock0

dd if=./tispl.bin of=/dev/mtdblock0 bs=1k seek=512

dd if=./u-boot.img of=/dev/mtdblock0 bs=1k seek=2560

U-Boot SPL 2023.04 (Jun 05 2024 - 21:57:59 +0800)
EEPROM not available at 0x50, trying to read at 0x51
Reading on-board EEPROM at 0x51 failed -121
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
Value of my_variable: 02147483648
ECC is enabled, priming DDR which will take several seconds.
ECC: priming DDR completed in 1114 msec
SPL initial stack usage: 13456 bytes
Trying to boot from SPI
jedec_spi_nor flash@0: unrecognized JEDEC id bytes: ff, ff, ff
SPI probe failed.
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

Sorry I fail to understand how it worked and what changed? 

 - Keerthy

I really haven't changed anything.
In principle, is the inability to obtain the spi nor ID related to tispl.bin and u-boot.img?

If so, it depends on which part of them？

I made modifications from the new SDK, only modifying the DDR section to make my board run. But still unable to obtain the spi nor ID
dd if=./tiboot3.bin of=/dev/mtdblock0
dd if=./tispl.bin of=/dev/mtdblock0 bs=1k seek=512
dd if=./u-boot.img of=/dev/mtdblock0 bs=1k seek=2560
Is this part of my command correct

What is the pin name corresponding to the toggle switch SW2.1?

I used a cable to pull WKUP_GPIO0_6  low, but the spi nor ID is still 0xff

Hi Fang,

Please double check:

• if you are in the QSPI settings.
• You have flashed all 3 binaries at right place.

Since this thread has history I request to continue here and close the other thread: e2e.ti.com/.../tda4vh-q1-tda4vh-q1-tiboot3-bin-can-t-read-spi-nor-id

- Keerthy