About MNeed.1

MNeed.1 · 2021-05-19

EXTI12 implies that the ARM external interrupt that is triggered is EXTI15_10_IRQn, when actually this pin triggers the EXTI2 interrupt. I think the issue is with the STM32Cube IDE code generator for this particular family of boards. (I tried to us...

MNeed.1 · 2021-01-27

I'm using the standard ANSI va_args approach here: int64_t arg64 = va_arg(args, int64_t);When stepping through the code the debugger clearly shows me a value like: 0xbeefbeef00000000

MNeed.1 · 2021-01-27

Oh I figured it out... This is a good one .... Turns out varargs with ARM32 and the GCC compiler (only?) requires the stack frame to be aligned at a 8 byte boundary. I was creating my own stack frames and everything else was working -- in fact for...

User statistics

User Activity

The STM32Cube IDE appears to generate misleading code (EXTI12) for what should be EXTI2 (pin is named PMOD-IRQ_EXTI2 according to the Users Manual) on the B-L4S5I-IOT01A board (probably a typo?)

Does the STM32 v1.5.1 GCC 7.3.1 toolchain have a limitation of 32-bit arguments for variable argument lists (stdarg.h) ? I am trying to pass 64-bit arguments via a variable argument list and I only see the upper 32-bits set (lower 32-bits are zero).

Re: Does the STM32 v1.5.1 GCC 7.3.1 toolchain have a limitation of 32-bit arguments for variable argument lists (stdarg.h) ? I am trying to pass 64-bit arguments via a variable argument list and I only see the upper 32-bits set (lower 32-bits are zero).