cancel
Showing results for 
Search instead for 
Did you mean: 

QSPI - NOR1 in TSV not detecting in STMCube programmer Tool

Shashikanth
Associate II

I have two NOR flash in my hardware.

 

  1. On SoM (Boot meadia detecting as NOR1 in Uboot)
  2. On Carrier Card

 

Both are detecting in Uboot as Nor0 and Nor1 but in STMCube programmer i am not able to flash to Nor1.

 

Tool given NOR1 not found error. So not able to flash to NOR1 and Boot from QSPI.

 

If i put NOR0 in tsv file it is flashing to carrier card NOr flash. I wanted to flash to On SoM QSPI which is detecting as NOR1 which is not supported in TSV file.

 

To test , I have made the carrier card SPI4 disabled then On SoM QSPI is detecting as NOR0 and flashing and booting works.

 

[2023-05-25 19:25:57] uboot> mtd list

[2023-05-25 19:26:01] SF: Detected is25wp016 with page size 256 Bytes, erase size 64 KiB, total 2 MiB

[2023-05-25 19:26:01] SF: Detected n25q256ax1 with page size 256 Bytes, erase size 64 KiB, total 32 MiB

[2023-05-25 19:26:01] List of MTD devices:

[2023-05-25 19:26:01] * nor0

[2023-05-25 19:26:01]  - device: is25wp016@0

[2023-05-25 19:26:01]  - parent: spi@4c002000

[2023-05-25 19:26:01]  - driver: jedec_spi_nor

[2023-05-25 19:26:01]  - path: /soc/spi@4c002000/is25wp016@0

[2023-05-25 19:26:01]  - type: NOR flash

[2023-05-25 19:26:01]  - block size: 0x10000 bytes

[2023-05-25 19:26:01]  - min I/O: 0x1 bytes

[2023-05-25 19:26:01]  - 0x000000000000-0x000000200000 : "nor0"

[2023-05-25 19:26:01] * nor1

[2023-05-25 19:26:01]  - device: micron32mb@0

[2023-05-25 19:26:01]  - parent: spi@58003000

[2023-05-25 19:26:01]  - driver: jedec_spi_nor

[2023-05-25 19:26:01]  - path: /soc/spi@58003000/micron32mb@0

[2023-05-25 19:26:01]  - type: NOR flash

[2023-05-25 19:26:01]  - block size: 0x10000 bytes

[2023-05-25 19:26:01]  - min I/O: 0x1 bytes

[2023-05-25 19:26:01]  - 0x000000000000-0x000002000000 : "nor1"

 

 

Please let me know how to resolve this issue.

Attached the STMCube programmer error and TSV file as .txt

1 ACCEPTED SOLUTION

Accepted Solutions
Shashikanth
Associate II

The issue is resolved.

The STM32CubeProgrammer tool does not support flashing to NOR1.

The problem i had is while flashing to NOR0 The Flash connected to SPI4 was detecting to NOR0, And Flash connected to QSPI was detecting as NOR1. So the tool was programming to the SPI4 flash and while booting the board trying to boot from QSPI NOR.

So in stm32mp131.dtsi i changed the QSPI node order and put it on the top of all SPI nodes. Now the QSPI NOR flash is detecting as NOR0 and flashing and booting works without any issue.

Thank you

Shashi

View solution in original post

1 REPLY 1
Shashikanth
Associate II

The issue is resolved.

The STM32CubeProgrammer tool does not support flashing to NOR1.

The problem i had is while flashing to NOR0 The Flash connected to SPI4 was detecting to NOR0, And Flash connected to QSPI was detecting as NOR1. So the tool was programming to the SPI4 flash and while booting the board trying to boot from QSPI NOR.

So in stm32mp131.dtsi i changed the QSPI node order and put it on the top of all SPI nodes. Now the QSPI NOR flash is detecting as NOR0 and flashing and booting works without any issue.

Thank you

Shashi