Hi Stefano Voulaz,
Some test result on my side.
In the previous time, I use the __ramfunc at the BOARD_BootClockRUN, and the internal related API, it's not working.
Then, I modify the BOARD_BootClockRUN function, copy the whole and the internal related API to the flash address 0x60005000, in the IAR linker file, divide one flash section to put these API.
Use the following code to put in the specific flash area
#pragma default_function_attributes = @ ".xtal24mhz"
Related API
#pragma default_function_attributes =
Linker file related code:
define symbol m_text1_start = 0x60005000;
define symbol m_text1_end = 0x60FFFFFF;
place at address mem:m_text1_start { section .xtal24mhz };
In the MCUbootUtility OTFAD side, I just secure the no BOARD_BootClockRUN code.
Then modify the led_blinky code:
int main(void)
{
unsigned int i, j;
BOARD_InitPins();
Flash_bootclockrun();
// BOARD_BootClockRUN();
//BOARD_InitDebugConsole();
if (SysTick_Config(SystemCoreClock / 1000U))
{
while (1)
{
}
}
while (1)
{
/*
for(i=0;i<300;i++) for(j=0;j<65535;j++);
GPIO_PinWrite(EXAMPLE_LED_GPIO, EXAMPLE_LED_GPIO_PIN, 0U);
for(i=0;i<300;i++) for(j=0;j<65535;j++);
GPIO_PinWrite(EXAMPLE_LED_GPIO, EXAMPLE_LED_GPIO_PIN, 1U);
*/
SysTick_DelayTicks(1000U);
if (g_pinSet)
{
GPIO_PinWrite(EXAMPLE_LED_GPIO, EXAMPLE_LED_GPIO_PIN, 0U);
g_pinSet = false;
}
else
{
GPIO_PinWrite(EXAMPLE_LED_GPIO, EXAMPLE_LED_GPIO_PIN, 1U);
g_pinSet = true;
}
}
}
After the OTFAD secure, the led is blinking now.
I share you the related led_blinky.c and the linker file, you can test it on your SDK led_blinky code in the IAR version.
But, to be honest, I find it still has some issues, eg, if I add BOARD_InitDebugConsole(); then the OTFAD secure even failed, I am still trying to find the root issues.
Because our internal expert is really busy, then the talk and reply will have delay, anyway, I will do more testing on my own side.
This time, I think you can use my code and method to test it on your side, whether it also works for you or not?
Any updated information, please kindly let me know.
Thanks so much for your effort and patient.
Best Regards,
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 Stefano Voulaz,
Today, I do the test that comment the BOARD_BootClockRUN();
unsigned int i, j;
BOARD_InitPins();
//BOARD_BootClockRUN();
while (1)
{
for(i=0;i<300;i++) for(j=0;j<65535;j++);
GPIO_PinWrite(EXAMPLE_LED_GPIO, EXAMPLE_LED_GPIO_PIN, 0U);
for(i=0;i<300;i++) for(j=0;j<65535;j++);
GPIO_PinWrite(EXAMPLE_LED_GPIO, EXAMPLE_LED_GPIO_PIN, 1U);
} Just use the software delay to toggle the LED, and it is the XIP, the OTFAD is working.
I also find the AN 12670 have this note:
Don't encrypted a code section with frequency adjustment.
Then I checked with our internal department again with my test result, I get the information that, XTAL 24Mhz initialize code don't put in the OTFAD encrypted area.
So, I think we need to copy the BOARD_BootClockRUN() code to the no encrypted area, it should works OK.
You also can try it on your side, at least, without the frequency adjustment, the XIP code OTFAD can work.
Best Regards,
Kerry
Do you use the OTFAD Encrypted image boot?
Could you tell me how do you download the encrypted image to your chip?
Do you try to use the MCUBootUtility tool which already support the RT1011 OTFAD encrypted image boot:
Best Regards,
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 Stefano Voulaz,
I also meet some issues when I use the MCUBootUtility the OTFAD download, I didn't enable the HAB.
This is my fuse which is similiar to you, just I do not use the fuse boot.
but, after I download the code, I find the app still the plaintex.
Although the OTFAD DEK Keyblob is generated.
So, do you also check, when you download the code, the app is encrypted or the plaintext?
Tomorrow, I will also check my situation with the tool author.
This is my user key with 2 regions:
Any updated information, I will let you know.
Best Regards,
Kerry
