Incorrect FlexSPI NOR LUT entries generated for iMXRT1010

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Incorrect FlexSPI NOR LUT entries generated for iMXRT1010

1,204 Views
benedek_kupper
Contributor III

Tool version: MCUXpresso IDE v11.2.1 [Build 4149] [2020-10-07]

Target: iMXRT1010EVK

When I generate a FlexSPI peripheral configuration with NOR flash LUT, the opcode0 is incorrect for ERASESECTOR and WRITESTATUSREG. We found this out as these commands weren't working, but comparing with an imported example (flexspi_nor_polling_transfer) we have found the problem:

  1. ERASESECTOR opcode is generated to 0xD7, the correct value is 0x20
  2. WRITESTATUSREG opcode is generated to 0x01, the correct value is 0x31
0 Kudos
3 Replies

1,191 Views
jingpan
NXP TechSupport
NXP TechSupport

Hi benedek_kupper,

Please note there is a comment at the top of LUT table.

/* Example of custom LUT. This LUT is for ISSI IS25WP064AJBLE QSPI Flash. You can change the bites according to manual of flash vendor. */

RT1010EVK use an AT25SF128 NOR flash. User should modify this table by themslevs.

 

Regards,

Jing

0 Kudos

1,186 Views
benedek_kupper
Contributor III

The problem is more conceptual then: why have a configuration item that cannot be modified by the tool itself, when manually editing generated code is bad practice, and can cause serious maintenance issues down the line?

0 Kudos

1,177 Views
jingpan
NXP TechSupport
NXP TechSupport

Hi,

Yes, you are right. At least there should also be a notes in the tool telling user the default LUT is not fit for all NOR flash. I'll escalate this problem to software team.

 

Regards,

Jing

0 Kudos