Basic Steps to Boot iMXRT1064

[Hat]

Hi All

I'm very new to NXP and ARM microcontrollers and I'm having a very hard time to figure what I need to do to get the iMXRT 1064 booting with barebones code.

I have bought the MIMXRT1064-EVK and have managed to run the example codes. But the codebase for this has so many components that I do not need.

I still can't find a guide document that lays out exactly what needs to be done to just get the iMXRT1064 booting (internal flash), without any of the EVK components.

I'm trying to make a new project using the SDK but set as "no board". I'm not sure what I need to change from the default project to get it running. The project is building but at runtime I get this error:

"Break at address "0x2020b4" with no debug information available, or outside of program code."

If anyone is aware of a guide to get with the steps to get the barebones MCU up and running, it would be much appreciated.

[gusarambula]

Hello Hat,

I would recommend using the New Project wizard but selecting the EVK board. This will include all necessary modules which are required, and to also add any additional drivers and elements that you may need for your application.

Regards,
Gustavo

[mjbcswitzerland]

Hi

In order to boot from the internal QSPI flash you need to ensure that you have a valid boot configuration at the start of its memory (0x70000000) followed by an image vector table (0x70001000) plus boot data (0x70001020) and optionally DCD data (0x70001030).
The image vector table is what points the processor to the final start up reset vector so that the code can begin its execution. From this point on standard general ARM details then apply.

See some introductory/concept videos at https://www.youtube.com/watch?v=GXztWg9m6_8&list=PLWKlVb_MqDQEOCnsNOJO8gd3jDCwiyKKe

https://www.utasker.com/iMX/RT1064.html

To understand the full details you will need to study the documents in some detail and reference working examples since there are a lot of configuration possibilities and not all information is obvious or simple to find. Errors will result in no operation (what you are seeing is such an error which causes the internal ROM loader to be taken and thus the address that you are seeing) and starting with a working reference and gradually making your own version will be possible, but using small steps so that the reason for failure can be identified at each step.

Once you start to grasp the general details you will need to ask specific question since a general answer is not easy in the case of the i.MX RT parts.

Regards

Mark
[uTasker project developer for Kinetis and i.MX RT]
Contact me by personal message or on the uTasker web site to discuss professional training, solutions to problems or product development requirements

[kellli01]

The QSPI is external to the IMXRT1064 I thought, not internal.

[mjbcswitzerland]

Hi

The i.MX RT 1064 has two FlexSPI interfaces and boots from its internal QSPI flash.

It can also use external ones but these are not needed if the internal 4MByte one is adequate.

Regards

Mark

[Luke1982]

How can I use the external ones to execute the code? Can I use one or both?

Thank You

[mjbcswitzerland]

Hi

You need to boot from the internal one but this code can configure the external one and jump to (additional) code there.

To load code to the external one you will either need to use a debugger script to configure it and load it via the debugger or install a boot loader in the internal one so that it can coordinate loading additional code and executing it accordingly.

Regards

Mark

[Luke1982]

Thank you for the answer!

what do you mean with "debugger script"? Usually I use Segger as debugger..

[mjbcswitzerland]

https://developer.arm.com/documentation/ka004582/latest/
https://developer.arm.com/documentation/101407/0542/Debugging/Debug-Scripting

For example.