CC2340R5: Some question need to support

Hello,

Thanks for reaching out.

Please help me with the following questions to help you further:

1. Are you using an out of the box example from the SDK? Which one if yes?
2. What SDK version are you using?
3. What are you using as the central device? the Simplelink Connect mobile app for example?
4. How do you terminate the connection?

BR,

David.

Hi,

1. Use basic_ble and data_steam project on SDK

2. 7_20_01_10 version;

3. device: Android and Iphone; APP is Ti simplink connect;

4. use APP to terminate connection; use this button terminate connection;

SCH

CC2340R5.pdf

Hello,

Thanks for the info.

You mention this only happens when the TI_BASE_UUID_128() is modified, therefore this issue doesn't occur when it is using the default value?

Are you using the ticlang or iar compiler?

Have to done any modifications to those out of the box examples? Could you please elaborate on this modifications, if there are any.

You can take a look at the Debugging section of the User Guide for more information about exceptions.

If it is possible, I would suggest to try with the latest SDK version: simplelink_lowpower_f3_sdk_7_40_00_64

BR,

David.

Hi,

1. This problem occurs only when the UUID is changed to the UUID in the document. Using the default UUID does not have this problem.
2. Modified description: Only the UUID in the SDK is modified
3. Using SDK:7_40_00_64, the problem still exists, but the probability of occurrence is reduced. The faultISR error will still occur after you need to disconnect and reconnect multiple times.

Here are some questions: 1. Using the development board provided by TI, burning the sample project in the SDK, the equipment runs normally without exception.
2. Use the CC2340R5 chip purchased by our company and replace it on the development board provided by TI. Burning the sample project in the SDK does not work properly and generates ICall_anort(); Mistake.
3. The use of the board developed by our company is the same as the second point.

use TIclang

Hello,

Thanks for this additional details.

To make sure I understand correctly. When the TI EVM Launchpad is used with the cc2340R5 chip that comes with it, it works fine. But if this chip is desoldered and changed by a new one, the exceptions occur? I might be getting this wrong, is the development board the following: https://www.ti.com/tool/LP-EM-CC2340R5? Have you done any HW modifications to the board?

user5883945 said:

development board provided by TI

Also, when you change the UUID, it works correctly while you are working with the original TI Launchpad? I am trying to understand if is only the UUID modification or the hardware modification that might be generating this.

Could you please check the value of the faultISR inside xPSR -> EXCEPTION register.

BR,

David.

Hi,

There are two problems:
The first question is:
The SDK version is: 7_40 Using the data_steram project in the SDK If you change the UUID, a faultISR () error appears, this issue will not be discussed for the time being. The priority now is the second problem
The second question is described as follows:
The following occurs: The SDK version is 7_40_00, the sample code in the SDK is not modified, and TIClang is used.
1. Use the following: www.ti.com/.../LP-EM-CC2340R5 development board. Using the sample code from the SDK, download it to LP-EM-CC2340R5, the board works fine, and on the Simplink connect APP, Bluetooth can connect normally.
2. Use your own drawing board (you can look at the schematic to see if there is a problem, we have provided: CC2340R5.pdf), download the SDK sample code to the board, the board does not work properly, the board is in: Icall_abort () status. The following is a screenshot of the Debug that occurs icall_abort().
3. If the CC2340R5 chip purchased by the company is replaced on the LP-EM-CC2340R5 development board, the situation will be the same as the second point above.

Hi,

Due to holidays, there may be some delays in this thread. I truly apologize for any inconvenience this may cause. In the meantime, I have a few questions that will help us ensure we are understanding the behavior you are seeing in its entirety.

You have a LP-EM-CC2340R5 board and your own custom board. If you flash an unmodified 7.40 SDK BLE example to the LP-EM-CC2340R5, then it works fine. If you flash the same image on your custom board, then you program hangs. If you take one of your loose CC2340R5 ICs and place it the LP-EM-CC2340R5, then you see an icall_abort.

Is my understanding correct? Have you submitted your custom board design for a hardware design review?

Best Regards,

Jan

Hi

the current problem is what you understand. We have provided the PDF file of the schematic diagram.

SCH

7245.CC2340R5.pdf

Hi,

  The icall problem have been solved;

remain problem about change UUID go to fault ISR need to solve, thanks!

Hello,

Glad to hear that.

Could you please show me how you are modifying the UUID and what value are you using? Are you modifying the MACRO? TI_BASE_UUID_128()

BR,

David.

Hi David,

1. Customer used the syscfg tool and bcomdef.h file to change the UUID, as shown in the following picture;
2. In addition, after I changed the UUID, I used SimplelinkConnect-APP to disconnect the connection with LP-EM-CC2340R5, and found that the three tasks created in the Bluetooth protocol stack, among which the task with priority 5 would always be in runing state after disconnection. This situation doesn't feel normal.

Hello,

I have tried to reproduce the issue on my side unsuccessfully. I am able to modify the TI_BASE_UUID_128 using your values without issues. I also disconnected and connected several times (around 10). Some things I considered:

• I included the bcomdef.h file inside the project (found inside <SDK>\source\ti\ble5stack_flash\inc) and modified it as a copy before building.
• The UUID 0 in sysconfig is modified respecting the same format as the modification done in the bcomdef.h file.

BR,

David.