About GCalin

GCalin · 2024-09-05

Hello everyone, I am developing a simple bootloader application where I have the bootloader code located at 0x8000000 and the main firmware at 0x8008000.To jump from the bootloader to the firmware code I am using this code: typedef void (*pFunction)(...

GCalin · 2021-03-11

Hello everyone,I was wondering the proper way to use the STM32_CHACHA_20_Encrypt() and STM32_CHACHA_20_Decrypt() functions available on the ST CryptoLib. I run the standard demo code on a STM32F072C8 MCU and it apparently run correctly, returning PAS...

GCalin · 2024-09-05

Dumping the stack helped to pin point a initialization error in the firmware code, not related to the actual bootloader -> firmware jump. It was some work, but it was a nice opportunity to learn the ins and outs of the STM32.Thank you all for the inv...

GCalin · 2024-09-05

The fault is triggered at blx r3:...203 pFunction JumpToFirmware = (pFunction)(*(__IO uint32_t*)(0x8008000 + 4));08002d98: ldr r3, [pc, #72] @ (0x8002de4 <main+256>)08002d9a: ldr r3, [r3, #0]142 __ASM volatile ("cpsid i" : : : "memory");08002d9c: cps...

GCalin · 2024-09-05

No change.I even tried to blx 0x8008225 on the very first instruction of startup_stm32f091cbux.s, but it still causes the hard fault. Shouldn't it work? I could not find a detailed documentation that lists all possible hard fault on the Cortex M0 ass...

GCalin · 2024-09-05

That was exactly what I did. The bootloader and firmware are separated projects, fully functional. The bootloader just flashes the MCU from 0x8008000, replacing the firmware code when needed. Only jumping from the bootloader to the firmware are causi...

User statistics

User Activity

Hard fault on blx instruction - STM32F091CBU6

Using CHCHA20 crypto functions (STM32 CryptoLib 3.1.5)

Re: Hard fault on blx instruction - STM32F091CBU6

Re: Hard fault on blx instruction - STM32F091CBU6

Re: Hard fault on blx instruction - STM32F091CBU6

Re: Hard fault on blx instruction - STM32F091CBU6