Replies: 2 comments 5 replies
-
|
Hi @fbeaulier! Take a look at the user script documentation. The second example script, I think, should be what you want. Though honestly, I haven't fully tested it since I don't have an i.MX RT board with a different external flash. Here's the example: # This example applies to the NXP i.MX RT10x0 devices.
def will_connect():
# Look up the external flash memory region.
extFlash = target.memory_map.get_first_matching_region(name="flexspi")
# Set the path to an .FLM flash algorithm.
extFlash.flm = "MIMXRT105x_QuadSPI_4KB_SEC.FLM"The path to the .FLM file is relative to the project directory, set with Of course, this assumes you have an .FLM type flash algorithm handy for your flash. If you need help with that, just ask. One more bit of info… you can turn on logging of info about the FLM when it is loaded by setting the |
Beta Was this translation helpful? Give feedback.
-
|
Hi @flit ! Thanks for your answer. Now if i try to flash with pyocd i get this: It seems that in will_connect() the get_first_matching_region(...) returns None. Any idea ? |
Beta Was this translation helpful? Give feedback.
-
|
Apologies, I didn't realize you were using the CMSIS-Pack based RT1061. The example script was written assuming the builtin RT1052 target. The RT series CMSIS-Packs have different names for the memory regions, and there isn't a region defined for FlexSPI, just an algorithm (there should be both Since there isn't a region defined for FlexSPI, the user script needs to add the region instead of looking up the current one: def will_connect():
# Add the external flash memory region.
target.memory_map.add_region(FlashRegion(
name="flexspi",
start=0x60000000,
length=0x800000,
blocksize=0x10000,
page_size=0x100,
is_boot_memory=True,
flm="MIMXRT105x_QuadSPI_4KB_SEC.FLM", # relative to pyocd project directory
))I successfully tested this technique with an RT1052 using the CMSIS-Pack target instead of builtin. In fact, you almost certainly can use the built-in NB: currently the easiest way to list the memory regions for a target is to connect with |
Beta Was this translation helpful? Give feedback.
-
|
Thanks a lot for your help, it works now ! |
Beta Was this translation helpful? Give feedback.
-
|
Great! Glad I could help. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @flit On my MIMXRT1061 board i have changed the external NOR Flash from ISSI IS25LP064A to Windbond W25Q128JV. François Here is the output when i try to flash: During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): The above exception was the direct cause of the following exception: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): |
Beta Was this translation helpful? Give feedback.
-
|
HI François, That's right, you'll need an .FLM flash algo for the W25Q128JV. Assuming there is not already one available from NXP or elsewhere, you'll have to write it yourself using the MCUXpresso driver (or some other driver). The RT1061 MCUX SDK has the The FlashAlgo project has a framework for building FLM-style flash algorithms, and a number of examples for other devices. The specification for FLM algorithms is in the CMSIS-Pack docs. Unfortunately, FlashAlgo doesn't have an i.MX RT flash algo to start from. But I suppose it's better than nothing. My recommendation is to create a test project, in addition to the algo project, that has a Sadly, NXP does not release the source code for its FLM flash algos. However, it's probably worth asking your FAE. And any questions about NXP drivers or the hardware are better asked of NXP, as I don't have any experience there. Of course, if you have further questions, I'll be happy to help as best I can! |
Beta Was this translation helpful? Give feedback.
-
Hello,
Would it be possible to have an example of how to define external Flash for iMXRT1060 ?
I've been messing around with scripts without success.
With the EVK board it works just fine as-is because everything is auto-detected but i don't know how !
Now with my own board even with the exact same memory chip i can't flash anymore.
Any help is more than welcome !
Francois
Beta Was this translation helpful? Give feedback.
All reactions