Hi kerryzhou,
Yes, can't read/write/erase with MCU Boot Utility. Still don't work today, same error.
Can debug with CMSIS-DAP, but "Mass erase" or "Erase by sector" from GUI Flash Tool doesn't work. I don't know how to to erase without this tool.
I joined the flexspi_QSPI_flash.h/.c & .cfx files from the Flash driver, where I did changes.
Basically I replaced the existing LUT with the LUT from the polling example, and there are differences on the NOR_CMD_LUT_SEQ_IDX_xx between the 2.
Thank you,
Benjamin
Hi kerryzhou
I erased the whole flash from RAM sector by sector with the polling code, and tested again at 80MHz and I get the same error.
Also tested at 100, 50 and 30MHz, with and without the "Enable second pinmux", but nothing better.
Hi kerryzhou
That setting don't change anything. When it was working, it was not enabled but it worked anyway.
I tried anyway, same deal (error 20106).
Hi Benjamin,
Thanks a lot for your effort, with MCUBootUtility, please try this configuration:
Just enable the QE bit again.
In factory, the BOOT_CFG in default use the external GPIO pin, you don't need to modify the fuse bit,
The related pins are:
If you want to boot from fuse, you need to burn the fuse BT_FUSE_SEL = 1, but I am not recommend to modify the fuse in the experimental phase.
Wish it helps you!
Have a great day,
Kerry
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
---------------------------------------------------------------------------
Hi kerryzhou
I had the error 20106 even if I erased first.
I posted a message below, that is not yet released from moderation, where I said that I got MCU Boot Utility to work finally without error (could read & write, was working great every time), but today, it don't want to! For whatever reason. Hardware didn't changed, but now it can't properly read the flash parameters (block size & others), I get garbage when reading, and writing returns and error code 20106.
And after trying several times, now it can't even detect the flash... :smileyangry:
But I can still upload with my CMSIS-DAP (I fixed the flash block config issue I had, modifying the flexspi_nor_config.c file). However, if I try to do a mass erase with the Flash GUI, I get an error:
Opening flash driver workspace/iMXRT1020_QSPI/iMXRT1020_QSPI/builds/MIMXRT1020-IS25LP128-FLEXSPI2.cfx
Sending VECTRESET to run flash driver
Flash device supported (16MB = 4096*4K at 0x60000000)
Mass Erase flash at 0x60000000
EraseChip (0x0, 0x0, 0x0) status 0x1 - driver reported driver error - EXTSPI driver rc 7002 (0x1B5A)
Closing flash driver iMXRT1020_QSPI/iMXRT1020_QSPI/builds/MIMXRT1020-IS25LP128-FLEXSPI2.cfx
Failed to erase flash: Ef(49): Flash driver operation gave error.
(100) Target Connection Failed
Unable to perform operation!
Command failed with exit code 1
Here is a screen capture of the issues I had this morning with MCU Boot Utility:
At first the memory sizes were wrong (3GB, should be 256B, 4k and 256KB I think) and reading returns error -4:
Then, after a flash memory erase, no more details but I can read garbage, but erase and write doesn't work (error 20106):
And now the flash isn't detected at all. Debugging via CMSIS-DAP works though.
I'm getting really tired of things suddenly working, then not, then a bit... I'll see tomorrow I suppose
At least I can debug code on the flash now, at last I'm able to work.
Hi Benjamin Balga,
If you want to debug the code in XIP, please check the hardware:
BOOT_CFG[10:8]=111
BOOT_MODE = 10; Internal boot.
The const struct flexspi_nor_config_s flash_config need to use your QSPI configuration.
You can refer to :
RT1050 - Debugging with QSPI flash on secondary pinmux
correct answer.
In your project, please check the memory detail:
Do you modify the .cfx driver as your secondary pinmux?
Wish it helps you!
Have a great day,
Kerry
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
---------------------------------------------------------------------------
Hi Benjamin Balga,
If it is your first time use the RT chip, why you don't connect the qspi flash to FlexSPI1? They will be more easy to get start, in factor the secondary pinmux just used as the backup memory.
If you use the lexspi_nor_polling_transfert run in RAM also can't make your external QSPI works, I think the hardware or your modified code still has problems.
From the RT102X RAM, your connected pins is correct.
So, now, can you test the FlexSPI1 secondary bus,whether there has the related QSPI wave or not?
Any updated information, please kindly let me know.
Have a great day,
Kerry
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
---------------------------------------------------------------------------
