The way LL_EXTI_Init is written in all of the cube APIs means if you do this: LL_EXTI_InitTypeDef exti_config = {
.Line_0_31 = foo,
.LineCommand = ENABLE,
.Mode = LL_EXTI_MODE_IT,
.Trigger = LL_EXTI_TRIGGER_NONE,
...
I'm using the tamper peripheral clocked from the LSE (32.768Khz crystal), triggered by a tamper event on PC13. The core is clocked from the HSI, using the PLL to run at 120MHz.The tamper peripheral seems to work fine under normal operation, but if an...
Thanks @waclawek.jan, I did notice that the flash read protection (RDP) talks about erasing the backup registers and SRAM2 in certain conditions. So I was wondering if the chip designers have piggy-backed off this mechanism for the tamper protection...
The LL examples are probably as close as you'll get https://github.com/STMicroelectronics/STM32CubeH7/blob/master/Projects/NUCLEO-H723ZG/Examples_LL/I2C/I2C_OneBoard_Communication_IT/Src/main.c#L268, Most of the LL functions are just a single line t...
I use the `__LL_I2C_CONVERT_TIMINGS` macro defined in the "*_ll_i2c.h" files which makes the value slightly easier to interpret, but I still use the CubeMX tool to generate the timings.0x10901031 would become __LL_I2C_CONVERT_TIMINGS(0x1, 0x9, 0x0, 0...
Oh, well this is starting to make a bit more sense, the reference manual doesn't seem to explicitly say this anywhere, but the SRAM2 sector gets erased to 0's when there's a tamper detection event.So no **** I get stack corruption when the stack is i...
Apologies the slow reply, this is a really weird issue, but I think I've kind of got to the bottom of it. So yes I mean on return of the breakpoint, and actually I realised, after the execution of the interrupt handler.When I get the hard fault these...
