Problem with application, after booting from mcuboot.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2022-05-10 12:17 AM
Hello All,
I'm trying to chain load the baremetal application from mcuboot with stm32f429. It's chainload the application and reaches the baremetal main function but even though there is some problem with clock configuration, the application went to unknown state after after clock configuration. What is the proper way the transfer control to application from bootloader.
Right now, before handovering the control to application, I properly de initialized the clock, hal and systick timer. Below is the code snippet
__disable_irq();
SysTick->CTRL =0;
SysTick->LOAD=0;
SysTick->VAL=0;
HAL_RCC_DeInit();
HAL_DeInit();
And what is the best way to debug the mcuboot and application together with gdb?
- Labels:
-
Bootloader
-
STM32F4 Series
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2022-05-10 12:56 AM
Does anyone of your code enable the interrupts again?
If you creates some contractual obligations between stages you don't need to teardown the clocks only to reinitialize them.
A debugger should be able to step through the transition, even if only at a disassembly level.
Up vote any posts that you find helpful, it shows what's working..
