I've run into problems like that before. I recommend ensuring that the
bootloader performs a cleanup: return all peripherals to their
original state and turn off any interrupts it previously enabled.
Otherwise, very subtle and hard-to-find bugs can creep in.
Out of curiosity, is this a custom boot
Just a update here for people facing similar issue in the future.
Actually Jose discovered the issue was not on NuttX itself, but it was
an Interrupt enabled in the bootloader that was missing an entry IRQ
vector table.
Best Regards,
Alan
On 2/20/24, Ambrocio, Jose wrote:
> Hello Nuttx team,
>
Hello Nuttx team,
I'm currently working on an embedded project that uses a bootloader and an
application. The target is a STM32G0B1VCI6 chip. I'm using the initial address
(0x0800 ) for the bootloader with 40K of size. Application starts at 0x0800
A000 with 216K of size. Before jumping to th
