Tool version: MCUXpresso IDE v11.2.1 [Build 4149] [2020-10-07]
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:
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.
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?
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.