CC2652P: BLE connection error CC2652P

Hi Sebastian,

I recommend you work on the problem step by step, first confirming the device is able to receive and transmit data (you can do so using SmartRF Studio).

Once this is confirmed, you can consider going to the next step and executing a software example such as simple_peripheral.

I hope this will help,

Best regards,

Hello Clément,

Thanks for your response. We verified that tx and rx are working with SmartRF Studio as you said.

But it still stops advertising. We load the example code simple_peripheral and sometimes we have an icall abort and sometimes and Error_SPIN as follows:

We have seen this post and tried the same thing but it doesnt work for us: https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1191771/cc2652p7-cc2652p7/4498493?tisearch=e2e-sitesearch&keymatch=cc2652p7#4498493

Best regards,

Sebastian

Hi Clément,

Thanks for your response.

Actually we followed a texas instrument application note for the hardware design.

Everything is working well, timers, uart, drivers, sensor controller, etc... It is only the BLE task with the Icall which has the higher priority the problem. Even the example code of cc1352p7_4 without modifications advertise only one time and then we lose it..

I can send you a schematic picture, maybe you see something wrong?

Thank you,

Best regards,

Sebastian

Might sound like a broken record telling you “hardware” again, but I’ve experienced this and it was sometimes due to one pad of the crystal not being soldered down. It’s worth taking a loupe to all the pads.

Hi Matt, Clément, Thanks for your response.

I'm working with Sebastian on the CC2652P.

I have checked the soldering on both 32.768kHz quartz and 48MHz quartz, there are OK. I also checked with oscilloscope if they oscillate correctly, and all seem to be OK. So i'm not sure if we have an hardware issue...

I also investigate a bit more, with SmartRF Studio by connecting a CC2652R in Packet TX mode, and our custom board (with the CC2652P7_4) in Packet RX Mode.

All Packet are correctly received.

I do the same in Packet TX mode, and all is OK.

So i think it's a software issue, or maybe a configuration problem.

The device seem to be advertising correctly, i can see it on BLE Scanner app, but if i try to connect, i'm stuck in an ICALL loop.

I logged BLE Stack MSG in SysMin output:

APP : ---- init APP : icall_directAPI to BLE func=0x1d025, status=0
APP : icall_directAPI to BLE func=0x206e9, status=0
APP : icall_directAPI to BLE func=0x23595, status=0
APP : icall_directAPI to BLE func=0x21089, status=0
APP : icall_directAPI to BLE func=0x22aad, status=0
APP : icall_directAPI to BLE func=0x22aad, status=0
APP : icall_directAPI to BLE func=0x23769, status=0
APP : icall_directAPI to BLE func=0x10026cd9, status=0
APP : icall_directAPI to BLE func=0x10026d2d, status=0
APP : icall_directAPI to BLE func=0x1002520d, status=0
APP : icall_directAPI to BLE func=0x10017f39, status=0
APP : ---- call GAP_DeviceInit
APP : icall_directAPI to BLE func=0x11501, status=0
SimplePeri TASK INIT Done====================
APP : Stack msg status=14, event=0x91
APP : Stack msg status=0, event=0xd0
APP : ---- got GAP_DEVICE_INIT_DONE_EVENT
APP : ---- call GapAdv_create set=0,0
APP : icall_directAPI to BLE func=0x10010199, status=0
APP : icall_directAPI to BLE func=0x14a75, status=0
APP : icall_directAPI to BLE func=0x14a75, status=0
APP : icall_directAPI to BLE func=0x1001ef1d, status=0
APP : icall_directAPI to BLE func=0x100174ed, status=0
APP : ---- call GapAdv_create set=1,0
ID Addr: 0xB0D2786C849B
RP Addr: 0x4B9E22176E6F
APP : App msg status=0, event=APP_PERIODIC_EVT         
APP : App msg status=0, event=APP_PERIODIC_EVT         
APP : App msg status=0, event=APP_PERIODIC_EVT         
APP : App msg status=0, event=APP_PERIODIC_EVT         <--- I try to connect here, and then no advertising more, and stuck in While loop...

Thanks for your help,

Best regards,

Valentin B.

Sorry to hear. Sometimes I have found a capacitor dangling off a pad or simply the wrong antenna settings when a connection won't hold. I messaged you—maybe you want to share some code? I also have a vested interest in the failure modes of the CC2652P!