Hi
I am pleased to say that the loader concept is now available for the following boards (various flash driver and simple configuration means that adapting to custom boards is child's play):
MIMXRT1010-EVK with i.MX RT 1011 [https://www.utasker.com/iMX/RT1010.html]
MIMXRT1015-EVK with i.MX RT 1015 [https://www.utasker.com/iMX/RT1015.html]
MIMXRT1020-EVK with i.MX RT 1021 [https://www.utasker.com/iMX/RT1020.html]
MIMXRT1050-EVK with i.MX RT 1052 - HyperFlash or QSPI [https://www.utasker.com/iMX/RT1050.html]
Embedded Artists iMX RT1052 OEM with i.MX RT 1052 [https://www.utasker.com/iMX/iMX_RT1052_OEM.html]
MIMXRT1060-EVK with i.MX RT 1062 [https://www.utasker.com/iMX/RT1060.html]
Embedded Artists iMX RT1062 OEM with i.MX RT 1062 [https://www.utasker.com/iMX/iMX_RT1062_OEM.html]
Teensy 4.0 with i.MX RT 1062 [https://www.utasker.com/iMX/Teensy_4.html]
MIMXRT1064-EVK with i.MX RT 1064 [https://www.utasker.com/iMX/RT1064.html]
New features integrated are:
- OTA upload support built in to the loaders (allowing applications to receive new code and let the loader safely upgrade)
- XiP application support. New applications can be loaded to directly run from SPI flash. This even allows SDK projects to be loaded with a simple change to the linker script setup, or large applications that can't fit into instruction RAM.
This give a single project (MCUXpresso, IAR, GCC make file, VIsualStudio) that can build many combinations of loaders for these i.MX RT parts allowing complete loader concepts to be completed with ease and no unnecessary development time lost. All parts share a common concept and share the same code for simplest maintenance. Using Visual Studio all parts are simulated and the complete loader concept can be tested and analysed in its simulator for highly accurate code coverage and peer reviews.
Regards
Mark
[uTasker project developer for Kinetis and i.MX RT]