Hi Marco,
I tested vector relocation on my side today. with my solution it also works. I was aware you already solved your problem with our expert LPCX support. So I am just for sharing my way. :-)
I currently don't have k64 bootloader. so I test your problem with KL25 bootloader I developed two years ago. I use this code for test because I am familiar with this bootloader code/
Kinetis Bootloader to Update Multiple Devices in a Network - for Cortex-M0+
then I use MCUXpresso to develop application code. here is my steps:
1. under MCUXpresso, create a new demo based on sdk sample, make sure you disable semihost and avoid any printf code in your app code.
2. relocate app code. for example in my demo I relocate it to 0x1000
3. make sure VTOR is well set
SCB->VTOR = 0x1000;
4. Make sure the relocated application code start address is well aligned to the relocation flash sector start address. For example, this is my case. I relocate app code start address from 0x1000.
after above change, the app code with vector relocation works perfect on my side.
I have verified it on my FRDM-KL25 board. But I think the method is the same for K64.
Have a great day,
Jennie Zhang
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Hello,
i have a problem to set the application using the bootloader.
I have change the memory allocation to copy the interrupt to the ram
add the line
// Insert call to copy vector table to RAM
data_init(0x0, 0x2000fc00, 0x400);
to ResetISR()
and re-set the handler
Install_RAM_Handler(UART4_RX_TX_IRQn, (uint32_t)UART4_RX_TX_IRQHandler);
Install_RAM_Handler(UART0_RX_TX_IRQn, (uint32_t)UART0_RX_TX_IRQHandler);
Install_RAM_Handler(PORTC_IRQn, (uint32_t)PORTC_IRQHandler);
Install_RAM_Handler(PORTD_IRQn, (uint32_t)PORTD_IRQHandler);
Install_RAM_Handler(LPTMR0_IRQn, (uint32_t)LPTMR0_IRQHandler);
Install_RAM_Handler(LLWU_IRQn, (uint32_t)LLWU_IRQHandler);
insted in the function
/*
* DC2
* 19/01/18
* Chiamata per riallocare gli interrupt in RAM
*/
void Install_RAM_Handler (IRQn_Type irq, uint32_t irqHandler) {
extern uint32_t __RAM_VECTOR[]; // taken from linker script
__disable_irq();
__RAM_VECTOR [irq+16] = irqHandler;
SCB->VTOR = (uint32_t)&__RAM_VECTOR;
__enable_irq();
}
i have a problem with the definition of __RAM_VECTOR[]. The compilare say undefined reference to `__RAM_VECTOR'.
Thanks
PS:
i have to change the setting
too?
Hello LPCX support and Jennie Zhang
I just found out what was causing the interrupt demo codes not to work with my bootloader. According to ARM Cortex M4 manual avialable at http://infocenter.arm.com/help/topic/com.arm.doc.dui0553a/DUI0553A_cortex_m4_dgug.pdf , SCB->VTOR is defined as the following:
So, in my code I loaded SCB->VTOR register with my application Flash start address shifted by 7 bits to the left, but that caused the MCU to reset and I didn't know why. So, after seeing the Jennie's message, I suspected that I should load that register with the value itself, and not shifted by 7 bits to the left. After doing that, everything is up and running!
But I'm still intrigued why MCUXpresso doesn't change SCB->VTOR register value automatically according to Program Flash address entered in Memory Configuration Editor. That sounds strange to me. In KDS demos, I didn't need to change SCB->VTOR register value in the code, what leads me to suspect, not to affirm because I haven't checked it yet, that Kinetis Design Studio already changes SCB->VTOR register according to linker file configuration in startup code and that is why we don't need to change SCB->VTOR value in code.
Your answer was decisive and enlightening, Jennie! Thank you very much!
I'd like to thank LPCX support for the first approach that copies the vector table to RAM. It is very interesting and could be useful in some cases.
Best regards!
Marco Coelho
DFAE - Siletec Eletronica
This is pretty straight forward to do - as follows ....
First of all use the memory configuration editor (detailed in the MCUXpresso IDE User Guide, chapter 12, "Memory Configuration and Linker Scripts") to split one of the RAM banks into two, one of which we will use to store the RAM copy of the vector table in. The start address of this RAM bank needs to be carefully aligned though, as the NVIC's VTOR register will need to be set to point to it (as described in ARM's documentation - for instance for Cortex-M4 at ARM Information Center ).
So in the case of my FRDM-K64 project, I take the standard memory configuration:
and split SRAM_UPPER to produce a second bank called RAM_VECTORS of the appropriate size, and moved this to the end of the list:
Note that the size of this bank is 0x400, and that is the maximum size possible for Cortex-M4 of the vector table (though generally not all 0x400 bytes are actually needed in most MCUs).
Now modify the startup file to add an extra call in ResetISR() to the data_init() function thus:
// Copy the data sections from flash to SRAM.
while (SectionTableAddr < &__data_section_table_end) {
LoadAddr = *SectionTableAddr++;
ExeAddr = *SectionTableAddr++;
SectionLen = *SectionTableAddr++;
data_init(LoadAddr, ExeAddr, SectionLen);
}
// At this point, SectionTableAddr = &__bss_section_table;
// Zero fill the bss segment
while (SectionTableAddr < &__bss_section_table_end) {
ExeAddr = *SectionTableAddr++;
SectionLen = *SectionTableAddr++;
bss_init(ExeAddr, SectionLen);
}
// Insert call to copy vector table to RAM
data_init(0x0, 0x2002fc00, 0x400);Now add a function to your code to modify one of the interrupt handlers in the RAM copy of the vector table, and update the VTOR register to point to the RAM block:
void Install_RAM_Handler (IRQn_Type irq, uint32_t irqHandler) {
extern uint32_t __base_RAM_VECTORS[]; // taken from linker script
__disable_irq();
__base_RAM_VECTORS [irq+16] = irqHandler;
SCB->VTOR = (uint32_t)&__base_RAM_VECTORS;
__enable_irq();
}And then add a call to your main code to install the required handler into the correct entry of the vector table
Install_RAM_Handler(I2C0_IRQn, (uint32_t)My_I2C0_IRQHandler);
More details of the vector table layout can be found in the ARM docs at - ARM Information Center
Regards,
MCUXpresso IDE Support
Hi Marco,
We can edit MCUXpresso project linker file with "Memory configuration editor".
The Memory Editor is accessed via the MCU settings dialog, which can be found at
Project Properties -> C/C++ Build -> MCU settings
the detailed information is already well described in document MCUXpresso_IDE_User_Guide.pdf, Chapter 12. we can customized our own linker file with it.
There is an option to disable "manage linker script", but it is not recommended.
Have a great day,
Jennie Zhang
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Hi Marco,
I tested vector relocation on my side today. with my solution it also works. I was aware you already solved your problem with our expert LPCX support. So I am just for sharing my way. :-)
I currently don't have k64 bootloader. so I test your problem with KL25 bootloader I developed two years ago. I use this code for test because I am familiar with this bootloader code/
Kinetis Bootloader to Update Multiple Devices in a Network - for Cortex-M0+
then I use MCUXpresso to develop application code. here is my steps:
1. under MCUXpresso, create a new demo based on sdk sample, make sure you disable semihost and avoid any printf code in your app code.
2. relocate app code. for example in my demo I relocate it to 0x1000
3. make sure VTOR is well set
SCB->VTOR = 0x1000;
4. Make sure the relocated application code start address is well aligned to the relocation flash sector start address. For example, this is my case. I relocate app code start address from 0x1000.
after above change, the app code with vector relocation works perfect on my side.
I have verified it on my FRDM-KL25 board. But I think the method is the same for K64.
Have a great day,
Jennie Zhang
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
