You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ROM bootloader (in STM32L476VG, at least), will not necessarily alias buffer at memory address 0x0 to the correct bank flash (or the even the flash at all)
By default, the value in the register SCB->VTOR is zero, meaning you rely on the bootloader to correctly alias the flash bank for you, which may not happen. If you leave it at zero, you could end up with someone else's interrupt vector table.
Worse yet, because the two firmware images are essentially identical, you could end up with the other firmware's interrupt vector table and use it successfully without even knowing it. But when a real firmware upgrade comes, the interrupt tables will no longer match. Classic example of what worked in the lab, didn't work in the field
Thanks for sharing your insight about this!
I fixed it as you suggested, but do not currently have any way to test whether this even compiles (STM32CubeIDE refusing to import this project). Until I can confirm this works, I'll leave this issue open.
ROM bootloader (in STM32L476VG, at least), will not necessarily alias buffer at memory address 0x0 to the correct bank flash (or the even the flash at all)
By default, the value in the register SCB->VTOR is zero, meaning you rely on the bootloader to correctly alias the flash bank for you, which may not happen. If you leave it at zero, you could end up with someone else's interrupt vector table.
I suggest doing this:
SCB->VTOR = 0x08000000;
g4-dual-bank-example/Core/Src/main.c
Lines 142 to 144 in a4f098d
The text was updated successfully, but these errors were encountered: