Re: stm32f4 wakeup interrupt

2019-04-29 Thread Christian Mauderer
Am 29.04.19 um 03:36 schrieb Jython: > Thank you a lot ! maybe i was thinking make code more clear and then > forget the right No problem. Pointer bugs are most likely one of the most common ones for C programmers. You know the 4 most common bugs: - wrong parentheses - pointer bugs - off by one e

Re: stm32f4 wakeup interrupt

2019-04-28 Thread Jython
Thank you a lot ! maybe i was thinking make code more clear and then forget the right On Sun, Apr 28, 2019 at 3:27 PM Christian Mauderer wrote: > Am 27.04.19 um 16:40 schrieb Christian Mauderer: > > Am 24.04.19 um 10:00 schrieb Jython: > >> HI, ALL! > >> why the code stuck in wakeup handler whil

Re: stm32f4 wakeup interrupt

2019-04-28 Thread Christian Mauderer
Am 27.04.19 um 16:40 schrieb Christian Mauderer: > Am 24.04.19 um 10:00 schrieb Jython: >> HI, ALL! >> why the code stuck in wakeup handler while the RTC gets time work fine >> i have checked some days, but no register error found, i suspect that >> the handler function is the issue >> >> >> // cod

Re: stm32f4 wakeup interrupt

2019-04-27 Thread Christian Mauderer
Am 24.04.19 um 10:00 schrieb Jython: > HI, ALL! > why the code stuck in wakeup handler while the RTC gets time work fine > i have checked some days, but no register error found, i suspect that > the handler function is the issue > > > // code > rtems_isr rtc_wakeup_handler(rtems_vector_number vec

stm32f4 wakeup interrupt

2019-04-24 Thread Jython
HI, ALL! why the code stuck in wakeup handler while the RTC gets time work fine i have checked some days, but no register error found, i suspect that the handler function is the issue // code rtems_isr rtc_wakeup_handler(rtems_vector_number vector) { uint32_t STM32F4_RTC_ISR = (*(volatile ui