jasonbu commented on issue #14514:
URL: https://github.com/apache/nuttx/issues/14514#issuecomment-2454189780

   > the last working commit is 
[f221c9e](https://github.com/apache/nuttx/commit/f221c9ecb436a32ecd14f54053d241722a1816a9)
 (for H7 you have to remove `timer_status` logic from example, for NRF52 it's 
not required)
   
   I tried with stm32h7 and return directly in timer_status.
   looks like also a sig action happend in timer handler.
   
   dump_stack in up_schedule_sigaction can get backtrace of.
   
   ```bash
   up_schedule_sigaction arch/arm/src/armv7-m/arm_schedulesigaction.c:104 
(discriminator 1)
   nxsig_queue_action sched/signal/sig_dispatch.c:199
   nxsig_tcbdispatch sched/signal/sig_dispatch.c:540
   group_signal_handler sched/group/group_signal.c:155
   group_foreachchild sched/group/group_foreachchild.c:78
   group_signal sched/group/group_signal.c:228
   nxsig_dispatch sched/signal/sig_dispatch.c:735
   nxsig_notification sched/signal/sig_notification.c:147
   timer_notifier drivers/timers/timer.c:127
   stm32_timer_handler arch/arm/src/chip/stm32_tim_lowerhalf.c:272
   irq_dispatch sched/irq/irq_dispatch.c:148
   exception_direct arch/arm/src/armv7-m/arm_doirq.c:49
   ```
   
   if it's urgent requirement, you can do 
   ```C
   const void * const _vectors[] locate_data(".vectors")
                                 aligned_data(VECTAB_ALIGN) =
   {
     /* Initial stack */
   
     IDLE_STACK,
   
     /* Reset exception handler */
   
     start,
   
     /* Vectors 2 - n point directly at the generic handler */
   
   #if 0
     [2 ... NVIC_IRQ_PENDSV] = &exception_common,
     [(NVIC_IRQ_PENDSV + 1) ... (15 + ARMV7M_PERIPHERAL_INTERRUPTS)]
                             = &exception_direct
   #else
     [2 ... ARMV7M_PERIPHERAL_INTERRUPTS] = &exception_common,
   #endif
   };
   ```
   in arch/arm/src/armv7-m/arm_vectors.c
   
   and we shall talk about how to cover these kind of usage.
   
   CC @GUIDINGLI @xiaoxiang781216 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to