LP-EM-CC2340R5: SUPERVISION_TIMEOUT_TERM trouble when I test LP-EM-CC2340R5 BOM rev:A

Hi YiKai,

I am not sure on your issue. Can you please guide me to the example you are working with ?  Is it our data_stream or basic_ble example. 

The simple peripheral example is not available for CC2340 and the described SDK.

Regards,

Alex

I use another CC2640R2 to run simple_peripheral.

Hi YiKai,

I cannot reproduce you issue here.

My setup:

Simple peripheral on CC2652RB  and

host_test with BTOOL on CC2340 is working.

Is your debugger active on the Simple peripheral device ?

What is the supervision timout you set?

Regards,

Alex

Simple peripheral on CC2652RB can connect to CC2340R5 host_test+Btool without issue. But if I run C:/ti/simplelink_cc2640r2_sdk_5_30_00_03/examples/rtos/CC2640R2_LAUNCHXL/blestack/hexfiles/cc2640r2lp_simple_peripheral.hex on my CC2640R2 LaunchPad, I will see SUPERVISION_TIMEOUT_TERM issue on my Btool. By the way, I don't do any Connection Settings after I establish connection between CC2340R5 host_test+Btool  and CC2640R2 Simple peripheral.

Hi YiKai,

Actually I cannot reproduce this issue here.

I am using:

LP-EM-CC2340R5 with host_test and Btool from 7.1.00.35 SDK.

and 

LAUNCHXL-CC2640 with the simple_peripheral.hex from 5.30.00.03 SDK

Below see my btool. Actually it seems like we used similar settings.

Can you ensure PG2 silicon is equipped on your Launchpad? 

Regards,

Alex

How can I check if it's PG2 silicon on my Launchpad?

Hi Yikai,

Just look at the Chip if there is written CC2340 on the chip it should be the production version.

Regards,

Alex

Please check my attached picture. I don't know if it's PG2 silicon

Hi YiKai,

this should be the latest silicon. Within TI we add a X or P in front of the Chip number to mark preproduction or early sample silicon.

I will try to do further investigations on your issue but I am not sure as I cannot replicate the issue right now.

Regards,

Alex

Hi YiKai,

To confirm, the supervision timeout only occurs when you have a CC2340R5 running host_test connected to a CC2640R2 running simple_peripheral? It does not occur when you have a CC2340R5 running host_test connected to the CC2652RB running simple_peripheral? Based on your previous replies, it seems you used the ble4 simple_peripheral, can you try using the ble5 simple_peripheral to see if we can replicate the behavior in ble5 as well?

Best Regards,

Jan

Hi Jan, I actually tested C:\ti\simplelink_cc2640r2_sdk_5_30_00_03\examples\rtos\CC2640R2_LAUNCHXL\ble5stack\hexfiles\cc2640r2lp_simple_peripheral.hex and see the same issue.

Hi YiKai,

Good catch! Yes, I believe the behavior you are observing is due to the all 0s bluetooth address. As a quick test, can you use uniflash to verify the contents at address 0x4E000058? Is it all 00s there as well? If it is, then there may be an issue with the IC itself, please let your TI representative know and we would be happy to replace your LaunchPad with a working replacement. I truly apologize for any inconvenience this may be causing.

In the meantime, do you have access to another CC2340R5 board? If so, then I would suggest to continue your evaluation and development on another board while we replace your faulty one. You may also be able to change the address mode of the faulty board to Randoms Static Address and this may prevent the supervision timeout behavior, so that is worth a test.

Best Regards,

Jan

Hi Jan,

The content in 0x4E000058 shows 0xffff.... Do you think it's abnormal?

I tried to use GAP_DeviceInit in btool to set addrMode to ADDRMODE_RANDOM to test again but I still see the same issue. Do I need to run other btool command after GAP_DeviceInit to make ADDRMODE_RANDOM  to take effect?

By the way, Uniflash shows the following CC2340 chip revision. Should this rev. A(1.0) SoC work without problem?

Hi YiKai,

For reference, this is how one of my working boards looks like at that address:

I believe seeing all FFs or all 00s at that address is unexpected. As a quick test, could you mass erase your device and check if the address is still all 00s or all FFs?

YiKai Chen said:

I tried to use GAP_DeviceInit in btool to set addrMode to ADDRMODE_RANDOM to test again but I still see the same issue. Do I need to run other btool command after GAP_DeviceInit to make ADDRMODE_RANDOM  to take effect?

Does running the command return success? 

Best Regards,

Jan

Hi Jan,

1.I try to do mass erase to my CC2340 but still get all zeros in address 0x4E000058

2.No, my GAP_DeviceInit  returns failure.

Do you have any further suggestion?

Hi Jan,

Do you know why there is CC2340R5 launchpad with all-zero values in address 0x4E000058? Is there any alternative to fix this issue if we see it again?

OK, I see and Thanks for your help!