Because of the Thanksgiving holiday in the U.S., TI E2E™ design support forum responses may be delayed from November 25 through December 2. Thank you for your patience.

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

LAUNCHXL-CC2640R2: Unable to connect the Simple_Peripheral Project via Smart_Phone

Part Number: LAUNCHXL-CC2640R2
Other Parts Discussed in Thread: TIDA-01624, UNIFLASH, TMP117

Hello Team,

I have flashed the Projects (Simple Peripheral) and (Project_Zero) for many times using the CCS 10.3.1 and sometimes using the CSS Cloud, and these Projects have worked without any Problems.

I have then flashed the Software TIDA-01624 on the LounchPad using the CSS8.2 which automatically used an older version of the firmaware of the XDS110 probe.

The flashing was successfully completed but the Software did not worked probably and sometimes it did not showed up in the BLE Scanner app on my smart phone.

Therefore i have reflashed the Simple-Peripheral Project using CCS 10.3 which automatically update  the firmaware of the XDS110 probe to the newest  version and the Project did showed up in the BLE Scanner but i was not able to connect it any more.

I have also reflashed the Project_Zero software but  the name of the Project which showed up in the BLE Scanner app is (Simple Peripheral) and not (Project_Zero) and i still not able to connect it via BLE scanner. (FOTO 2)

In (Foto1) you can see what is the Error which appears when i try to connenct the Project.

No matter which Project i flash from the ble-Example, i see only (Simple Peripheral) in the BLE Scanner App and i will not be able to connect it !

I have traid to falsh the Project  (poratble) from the Demo-Example and this Project worked fine.

So i think the Problem appears just when i flash a ble-Project !

Do you have any ideas to solve this Problem ?

Thanks in advance

Best regards

Tareq

 

  • Hi Tareq,

    I have assigned an expert to help with your query.

    Best Regards,

    Jan

  • Thank you Jan.

  • Hi Tareq,

    Thank you for posting on the E2E forums, I have a couple of questions that may help us get closer to debugging this problem. 

    1. What version of the SDK are you using?

    2. Does flashing the hardware with the simple_peripheral hex file located in the SDK using UniFlash or Flash Programmer work?

    3. Are you using custom hardware or a launchpad, and if you're using a launchpad, do you mind attaching a picture of it?

    I have also reflashed the Project_Zero software but  the name of the Project which showed up in the BLE Scanner app is (Simple Peripheral) and not (Project_Zero) and i still not able to connect it via BLE scanner.

    This sometimes happens because the way LightBlue caches the names of devices. One method is to rapidly refresh the scanning page. After a couple of refreshes the name should change. If the name never changes after multiple refreshes, then we can confirm that the hardware isn't being flashed correctly.

    A quick thing to try is switching the XDC debug probe in CCS 10.3 to the older version. This can be done by navigating to the project's properties. Once there, please refer to the attached photo.

    Best,

    Nima Behmanesh

  • Hello Nima,

    Thank you very much for replying my question.

    1.The SDK i am using is CC2640R2 SDK 5.10.0.02

    2.I did try to reflash the Hadrware with the hex file using UniFlash and that did not solve ther Problem.

    3. i am using the launchpad : LAUNCHXL -CC2640R2

    I have rapidly refreshed the scanning page the scanning Page but the name (Simple-Peripheral) did not change.

    on the other hand my PC was able to find the Project-Zero. Foto4

    The same is happening when i try to conntect to the Project from the Phone or from the PC, i will get this in the Putty Console : Foto7

    I also have traid to switch the XDC debug probe in CCS 10.3 to the older version. But unfortunately this also did not solve the Problem. Foto3.

  • Hi Tareq,

    Thank you for your reply. I have a couple more questions.

    1. Do you have access to another cc2640r2 launch pad? 

    If so, please flash the second launch pad with host_test and use BTool (Task 2 has instructions) and check if you can interact with the device.

    2. What model phone are you currently using, and do you have access to any other phones to test with?

    3. Do you mind attaching the console output from UniFlash after clearing the flash and re-flashing?

    Thank you,

    Nima Behmanesh

  • Hello Nima,

    Thank you very much for your answer.

    I was using an iphone ios 14.6  now i am using an andriod Phone and with the andriod Phone i was able to see the Project Zero and connected it successfully. so thank you very much for your advise !

    Maybe the problem was in my iphone therefor i will use the andriod Phone for the next test.

    The reasone why i am using the launch pad and the TMP117 sensor is becasue i want to test the Software TIDA-01624 on the launch pad and see if the software really work befor i make a PCB disgen for the TIDA-01624 and order the PCB.

    Do you think that the Software TIDA-01624 is 100% compatible with the launchpad "LAUNCHXL -CC2640R2" ?

    Or shell i just use the reference pcb-disgen from TIDA-01624 and make a protype from it and then test the software direktly on it ?

    Thank you again for your advice and solving the problem

    Best Regards,

    Tareq

  • Hi Tareq,

    No problem, I'm happy that my advice was helpful.

    Do you think that the Software TIDA-01624 is 100% compatible with the launchpad "LAUNCHXL -CC2640R2" ?

    Yes, the TIDA-01624 reference design was made and verified using the CC2640R2. As long as the reference design is followed, then the expected behavior should be seen.

    Best,

    Nima Behmanesh

  • Maybe the problem was in my iphone therefor i

    As Nima mentioned IOS Lightblue caches the name of the devices. Another you can do is turn off the IOS smartphone Bluetooth and then turn it on again.

    -kel