To the function defined in the RAM, after the memory is defined, __RAMFUNC(SRAM_ITC) should work directly, but to flexspi operation run in RAM, normally, we put the whole project :
SDK_2_10_0_EVK-MIMXRT1060\boards\evkmimxrt1060\driver_examples\flexspi\hyper_flash\polling_transfer
link to RAM and run it.
In fact, to your situation, you totally can use the ROM API instead of copy the flexSPI driver to the RAM, in fact, the ota_bootloader also use the ROM API. If you use the ROM API, you totally can run it in the flash directly, the sample code you can refer to OTA_bootloader or ROM API project:
SDK_2_10_0_EVK-MIMXRT1060\boards\evkmimxrt1060\driver_examples\fsl_romapi
About the function copy to RAM, when I define the code, I even didn't modify the ld file, I just define it like this:
_RAMFUNC(RAM4) void SysTick_DelayTicks(uint32_t n)
{
g_systickCounter = n;
while (g_systickCounter != 0U)
{
}
}
Then the map file you can find the SysTick_DelayTicks in RAM4.
Your project is based on the flashloader or the ota_bootloader? If you are based on the ota_bootloader, you don't need to copy the flexspi driver to the RAM, just use the ROM API.
If your customer API want to copy to RAM, you can define a new ram range, then define your API to RAM with _RAMFUNC(NewRAM).
Best Regards,
Kerry
I have checked your project yesterday, if just define it to the ITCM, and the map still in the external memory.
Just confirm your function again, do you want to use the secondary bootloader which can operate the hyperflash when the bootloader code already running in the flash, right? If yes, as the RT1060 contains the ota_bootloader, that just meet your demand, but that project is using the QSPI, what you need to do is to modify option, then the ROM API will help you do it. do you mind to use this way instead of porting your project?
SDK_2_10_0_EVK-MIMXRT1060\boards\evkmimxrt1060\bootloader_examples\ota_bootloader
I think to try this method will save your time.
eg: bootloader_config.h
Modify from:
// The FLASH is a QSPI FLASH which supports JESD216 standard, working at 120MHz
#define BL_FLEXSPI_NOR_CFG_OPT0 (0xc0000006u)
#define BL_FLEXSPI_NOR_CFG_OPT1 (0x0u)
To hyperflash:
// The FLASH is a hyer 3V0, 100Mhz
#define BL_FLEXSPI_NOR_CFG_OPT0 (0xc0333006u)
#define BL_FLEXSPI_NOR_CFG_OPT1 (0x0u)
Then you can try to test it directly.
If you meet any issues, just kindly let me know.
To your linker issues, I think you need to make sure: 1. RAM is enough to use, 2. divide one RAM range mainly used for your own API function.
In your shared another link, seems your previous RT1064 ROM API method totally works, just the RT1060 can't work, right? If yes, please modify the option which I suggest you, just use the hyperflash option as I know, the RT1060 totally can support the get_config() function.
If you still have issues, just kindly let me know, when I have time, I will also try to modify the SDK rt1060 ota_bootloader to hyperflash.
If your RT1064 already works with the ROM API, just keep patient, your RT1060 will also can be successful.
Best Regards,
Kerry
