Dear Support Team,
Problem 1:
我试图建立一个简单的Bluetooth-serial demo, I dowloaded the DSPS and the SPS demo, built it, downloaded into the chip, seems to work cause I can see
the device in the DSPS android app, but when I have a breakpoint in the app_connection_func that is not hit.
If I connect with another bluetooth scanner app than the breakpoint is hit. Also when trying to send some data trough the DSPS consolo(Rx/tx) I can't see any toggling signal
on the uart rx/tx lines (P0_4/5).
Problem 2:
If I reset the chip(Debug/reset) and then run again I can see some signals on the rx/tx lines, I don't know why(some rom code running ?) Also when try to reset and start again I have the following error: ***JLink Error: Could not start CPU core. (ErrorCode: -1), I have to stop the debugging and start it again to be able to execute the code again, why?
One minor update, i disabled the sleep modes and disabled also the flow controls.
We are in the early phase of the product the first choice was the dialog chip however we need support, can you recommend a FAE contact since the support trough the forum is a bit slow.
Best regards,
Laszlo
Hi Laszlo,
In the dsps application on the top of the frame there is a small green indication that shows that there is connection, when you connect to the application is the indication enabled? if not then you dont have a connection with the application and that why your handler doesn't hit. Can you please try to reinstall the app to your phone or try another android device. Since you dont have a connection i suppose that there is not going to be any dataflow on the UART.
The signals in UART on reset, are the bootrom code running. About the reset in Keil the chip will reset and the bootrom code will run again, since the jtag is disabled by the bootrom at the beggining of the booting procedure the debugger will detach and thats why you see the error message. You have to stop and start debugging.
Thanks MT_dialog
Dear Staff,
The problem was with the DSPS application, it needs to be restarted every time after connection loss otherwise it will not try to reconnect but keep the green indicator on.
Now it works, can see the signals on the scope and also tested with a loopback, and can receive back what i sent over the console.
Thanks for the prompt feedback.
Best regards,
Laszlo