You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The BSP provides three functions to allow for waiting on events:
chbsp_event_wait_setup()
chbsp_event_wait()
chbsp_event_notify()
During the initial programming int shasta_detect_and_program() they are used so that the application can wait on the sensor reset.
Before programming, chbsp_event_wait_setup() is called to clear any pending events and chdrv_int_interrupt_enable() to enable the interrupts.
After programming and reset, event_wait is called to wait for the interrupt.
The problem is now that the called function event_wait() again calls chbsp_event_wait_setup() and chdrv_int_interrupt_enable().
This clears any potentially arrived events.
The BSP provides three functions to allow for waiting on events:
During the initial programming int shasta_detect_and_program() they are used so that the application can wait on the sensor reset.
Before programming, chbsp_event_wait_setup() is called to clear any pending events and chdrv_int_interrupt_enable() to enable the interrupts.
After programming and reset, event_wait is called to wait for the interrupt.
The problem is now that the called function event_wait() again calls chbsp_event_wait_setup() and chdrv_int_interrupt_enable().
This clears any potentially arrived events.
ultrasonic.soniclib/invn/soniclib/ch_driver.c
Lines 659 to 671 in a6514c1
I would suggest to remove the calls to
within event_wait()
@tdk-invn-oss/ultrasonic-maintainers
The text was updated successfully, but these errors were encountered: