LP-EM-CC2745R10-Q1: Error: 1 nodes not identified at all Error when we running BLE channel sounding Key Node and Car Node application examples

Hey Prasad,

It seems to be that the script is not able to detect your connected car_node

Have you modified the COM port in ble_device_car_node_with_distance.py?

Make sure that the car_node is connected to your computer. Modify the COM port in the script to match the UART/application COM port of the car_node device.

Regards,

Marvin

Hi Marvin,

We updated the correct COM port in the script before executing ble_device_car_node_with_distance.py. However, we still encountered the same error. We were using Python 3.13 to run the script. Do we need to use a lower version of Python, or should it work with Python 3.13?. 

Regards

Rajiv.K

Hi again, 

Please use python version 3.10.11, as mentioned in the README.md located here: SDK\tools\ble\ble_agent\

Make sure to follow the installing steps there.

Try to change XDS if you are continuing to see this issue.

Regards,

Marvin 

One thing I forgot to mention. You need to check if you have a valid HSM image on the device.

Regards,

Marvin

Hi Marvin, how to verify this HSM image on the device. 

Rajiv

Hi Marvin, I was able to run the Python script, and the car node device started scanning for devices. It could not recognize the Key node device, but it was able to find other BLE devices in the site. Could you please assist further to resolve this.

Regards

Rajiv.K

The key node is most likely not advertising, which is why it is not showing up.

Can you put the device in debug mode to see if the device is stuck in any exception handler?

Did you make sure that both devices had valid HSM FW?

This is how you do it:

- Open up Uniflash -> enter device name "CC2745R10" -> click start -> click Setting & Utilities -> Read HSM System Information -> wait for status

Regards,

Marvin

Hi Marvin,

We debugged the Key Node device and found that it is not advertising. We imported the Key Node project into CCS and ran it in debug mode, where execution got stuck in the assert handler.

We then flashed the HSM image on both devices and validated it. After restarting in debug mode, the execution is now stuck in the following function:

Hi Marvin,

We were able to debug and run the key node application. It has started advertising. The car node was able to scan the key node and establish a connection. Attached is the log for your reference. However, the distance value is not showing up.

Could you please clarify this issue?.

adv local name: Key Node
Create a connection with [9, 129, 91, 85, 205, 120] as a central
00:00:00:00:00:00: scan disabled
Connection Data
----------------------------------------------------------------------
Status:                 0
Opcode:                 5
Address Type:           ADDRTYPE_PUBLIC_ID
Device Address:         78:CD:55:5B:81:09
Connection Handle:      0
Connection Role:        8
Connection Interval:    24
Connection Latency:     0
Connection Timeout:     2000
Clock Accuracy:         0
----------------------------------------------------------------------
Didn't get NWP_PAIRING_STATE_COMPLETE, wait for NWP_PAIRING_STATE_ENCRYPTED in case we already bonded
Pairing Complete
Connection Handle:     0
State:                 4
Status:                0
------------------------------------------------------
***** read local cap *****
***** read remote cap *****
Remote Capabilities
----------------------------------------------------------------------
_io: []
event: 64
conn_handle: 0
status: 0
num_config: 4
max_procedures: 0
num_antennas: 1
max_ant_path: 4
role: 3
optional_modes: 1
rtt_cap: 0
rtt_aa_only_n: 255
rtt_sounding_n: 0
rtt_random_payload_n: 255
nadm_sounding: 0
nadm_random_seq: 0
optional_cs_sync_phy: 6
no_fae: 1
ch_sel_3c: 0
cs_based_ranging: 0
t_ip1_cap: 120
t_ip2_cap: 120
t_fcs_cap: 448
t_pm_csap: 2
t_sw_cap: 1
snr_tx_cap: 0
----------------------------------------------------------------------
***** security enable *****
Security Enable
----------------------------------------------------------------------
_io: []
event: 67
conn_handle: 0
status: 0
----------------------------------------------------------------------
***** set default settings *****
***** create config *****
Create Config
----------------------------------------------------------------------
_io: []
event: 65
conn_handle: 0
status: 0
config_id: 0
state: 1
main_mode: 3
sub_mode: 255
main_mode_min_steps: 0
main_mode_max_steps: 0
main_mode_repetition: 0
mode_zero_steps: 3
role: 0
rtt_type: 0
cs_sync_phy: 1
channel_map: [252, 255, 127, 252, 255, 255, 255, 255, 255, 31]
ch_m_repetition: 1
ch_sel: 0
ch3c_shape: 0
ch3c_jump: 0
rfu0: 0
t_ip1: 3
t_ip2: 3
t_fcs: 6
t_pm: 1
rfu: 0
----------------------------------------------------------------------
***** procedure enable *****
Procedure Enable
----------------------------------------------------------------------
_io: []
event: 68
status: 0
conn_handle: 0
config_id: 0
enable: 1
aci: 0
pwr_delta: 128
sub_event_len: 28450
sub_events_per_event: 1
sub_event_interval: 0
event_interval: 3
procedure_interval: 0
procedure_count: 1
----------------------------------------------------------------------
Waiting for NWP_CS_APP_DISTANCE_RESULTS
***** procedure enable *****
Procedure Enable
----------------------------------------------------------------------
_io: []
event: 68
status: 0
conn_handle: 0
config_id: 0
enable: 1
aci: 0
pwr_delta: 128
sub_event_len: 28450
sub_events_per_event: 1
sub_event_interval: 0
event_interval: 3
procedure_interval: 0
procedure_count: 1
----------------------------------------------------------------------
Waiting for NWP_CS_APP_DISTANCE_RESULTS
***** procedure enable *****
Procedure Enable
----------------------------------------------------------------------
_io: []
event: 68
status: 0
conn_handle: 0
config_id: 0
enable: 1
aci: 0
pwr_delta: 128
sub_event_len: 28450
sub_events_per_event: 1
sub_event_interval: 0
event_interval: 3
procedure_interval: 0
procedure_count: 1
----------------------------------------------------------------------
Waiting for NWP_CS_APP_DISTANCE_RESULTS
***** procedure enable *****
Procedure Enable
----------------------------------------------------------------------

regards

Rajiv.K

Hey Rajiv,

Can you enable PA and LNA in sysconfig. It is located under "RCL". Do you have a way of reading these pin? Would like to see the TX and RX activity of both devices. 

Can you try to reset both devices and rerun the demo?

Have you made any changes to the configurations?

Regards,

Marvin 

Hi Marvin,

I was unable to locate the PA and LNA settings in SysConfig, and I haven’t made any changes to the current SysConfig settings.

We’ve tried resetting the devices multiple times, but the result remains the same — the distance value is not being displayed.

Could you please provide the exact .bin or .hex files for both the car and key node applications, along with the correct SysConfig setup? This would help me run the demo quickly and verify the functionality.

Regards

Rajiv.K

Hi Marvin,

I am seeing the below warning in the sysconfig, 

is it causing the issue?.

regards

Rajiv

Hi Marvin,

Attached sysconfig file of both Keynode and car node application for your reference. Please let us know any configuration to be modified. 

car__key_node_sysconfig.zip

Rajiv

Hi Marvin,

 Enabled PA and LNA under RCL. Below is the status of the TX and RX of both devices.

D0-Car node- PA

D1 - Car node - LNA

D3 - Key Node - PA

D4 - Car node - LNA

Before Pairing to Key node

After Pairing with key node

FYI

https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/538/car_5F00_node_5F00_LP_5F00_EM_5F00_CC2745R10_5F00_Q1_5F00_freertos_5F00_ticlang.outhttps://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/538/key_5F00_node_5F00_LP_5F00_EM_5F00_CC2745R10_5F00_Q1_5F00_freertos_5F00_ticlang.out

Hey Rajiv, 

I have added to binary files that I have tested and are working on my side. Please test this also on your side. 

The warning is just stating that the SW is not certified yet with the BLE 6.0 spec, so no problems there.

From the photos you shared it seems that there is no activity after the devices have paired, which is probably why you are not able to receive any distance results.

The .out files above are built straight out of the box. If you have a BLE sniffer, then that would be also great to use to see what is going on during the connection.

Regards,

Marvin