CC2340R5: Notify problem

Hi Galaxy,

Thank you for reaching out.

Could you please specify the SDK version being used here?

Also, could you please share more details on the way you run this test? Among others, it would be nice to share a code snippet showing how the notifications are sent. In addition, I would like to understand better how the notification are received, and how you assess if some are missing.

Last but not least, please make sure to specify the connection interval used.

Galaxy Yue said:

Is it because CC2340 cannot notify so frequently?

I don't think so - For audio related projects, we manage to send notifications every 20 ms. So it should not be an issue.

Best regards,

SDK Version: 7_10_00_35

Later, I found out that it seemed that the Timer went to Notify in less than 1ms. This may have caused the number of pens to be missed.

Afterwards, I made modifications and found that TimerCallback was not entered according to the time I set, so I wrote a test code, as follows:

But when I use the oscilloscope to view it, the timercallback is not entered.

I modified the Code again and added sleep(1) as follows:

Use an oscilloscope to check that he only enters the timercallback every 1 second and lets the GPIO do the toggle action. In other words, he must rely on while to call enableInterrupt before entering the timercallback.

So how to trigger the purpose of setting counterTarget like this? Otherwise, it feels like using sleep for timing.

Best Regards,

Galaxy

Hi Galaxy,

I would recommend using a clock rather than a timer in this case. See https://dev.ti.com/tirex/content/simplelink_academy_for_cc23xx_7_40_00_00/_build_simplelink_academy_for_cc23xx_7_40_00_00/source/cc2340rx_04_connections.html#task-3-create-a-oneshot-or-periodic-clock-using-clockp-module

Best regards,