Hi Dialog
We are working in DSPS host and DSPS device projects, DSPS device tx data every 1 min and goes to ext sleep.
DSPS host once received data from device 1 , host disconnects device , so device enters into ext sleep. now Dsps host scans for next device , and if scan report is there for next device then make the connection with device and after receiving data disconnect likewise i can connect to 6 dsps device's.
Now my problem is after some time , DSPS Host receives scan report for device x and trying to make the connection with this device , but DSPS host couldn't make the connection , so DSPS host code stops somewhere(seems after user_on_connection())..how to resolve this issue ??
Device:
Hi prasanth,
Your description is very generic, that fact that at some point the host gets an advertising event and when he tries to connect the code stops, doesn't give me enough info to assume anything. You will have to know exactly where the device has stopped, where the code goes ? NMI_Handler, Hardfault_Handler in any ASSERTION by the program ? Was that device previously connected with that Host and after a while the device can't connect ?
Thanks MT_dialog
Hi Dialog
My code stops after EXECUTE_CALLBACK_PARAM1_PARAM2(app_on_connection, connection_idx, param); actually , after this call back DSPS host should enters into profile to receive data.
DSPS_HOST finds device 1 , trying to make the connection , after above mentioned callback code stops..what could be the issue??
Hi prasanth,
它可以是任意hing, so please check where exactly your code stalls (check without sleep in debug mode), where the code is located when that happens. I suppose that after that, the device is unresponsive (no scanning or anything), so you will have to check where the device exactly stops, perhaps it doensn't stop and keeps on running (if that is the case you should se the PC running normally through the main while loop), NMI_Handler (if you are using the watchdog your code remains in a specific code over a specified amount of time), Hardfault ( access to an unalligned address or a bus error), any ASSERTION (perhaps your trying to cancel an allready cancelled timer). The fact that the insident occurs after the connection and when the callback runs could be either the cancelation of the timer, or an error during the discovery.
Thanks MT_dialog