CC2564MODA: We are stuck at the HCI_Reset function (int BTPSAPI HCI_Reset(unsigned int BluetoothStackID, Byte_t *StatusResult)

Ofer Melman76748

Part Number: CC2564MODA

Hi ,

We have the CC2564MODA on our board and it started working (Logger file attached), We are working in UART cp3Wire mode, Currently we are stuck at the HCI_Reset function (int BTPSAPI HCI_Reset(unsigned int BluetoothStackID, Byte_t *StatusResult) file HCI.c, returning BTPS_ERROR_DEVICE_RESET_ERROR; we have started checking why we are getting the error and it looks as the flag HCI_CONTEXT_FLAGS_SYNCHRONOUS_HCI_FLAG is not set when we check it in the function HCISendPacket,

Any idea why this is happening maybe we are not setting/initialize some flags?

Please let me know if any other info. is needed,

Many Thanks

Loger Text

106   2   05/30/19 10:44:23.061   +0:00:00.000   BT Logger 1           uart_hci parameters: UartDIV=4, OS=17, SP=63, MoB=7
107   2   05/30/19 10:44:23.061   +0:00:00.000   BT Logger 1           temperature sensing: temp 26, read 0x20, vbe 0x2873319, slope 0x1f829
108   2   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           Temperature region = 6
109   3   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           In lc_rf_init_periodic_calibration
110   5   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           synch event REG received, module RF_CALIBRATION, msi 0
111   5   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           synch cmd start instance, module RF_CALIBRATION, msi: 0
112   5   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           synch cmd return event STARTED,module RF_CALIBRATION
113   2   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           ORCA Platform
114   2   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           Process type: Nominal
115   2   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           Chip revision: 6
116   2   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           Detected Clock = 38400000 Hz
117   2   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           Ref Clock = 38400000 Hz
118   2   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           XTAL wakeup mode is disabled
119   2   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           Ref Clock is valid for PLL
120   2   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           PLL Clock Output is OK
121   2   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           PLL Clock Out = 40000000 Hz
122   2   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           Clock Working mode: PLL Mode
123   2   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           ARM Clock = 40000000 Hz, Slow Clock: External
124   2   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           OCP Clock = 8000000 Hz
125   4   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           UART HCI baudrate = 116363
126   2   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           Gemini type Soft Gemini
127   3   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           lm_lc_get_local_features
128   3   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           lm_lc_set_brcst_retran
129   3   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           lm_lc_self_test_run_init_tests
130   2   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           Self Test passed
131   4   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           I2C doesn't exist !
132   3   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           lm_lc_get_local_bd_addr
133   3   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           Software version - 7.0.16
134   2   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           Deactivating timer: init
135   3   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           lm_lc_rf_periodic_calibration
136   2   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           Calibration started. Vector=0x1, 0x0
137   2   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           PHY FW Version 3.27
138   2   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           random 0x0 0x9a1f
139   2   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           random 0x2746 0x95b4
140   2   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           random 0x98f9 0xf55
141   2   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           random 0x7116 0x3be0
142   2   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           random 0xa7e5 0xae71
143   3   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           lm_lc_generate_rand
144   3   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           lm_lc_generate_rand
145   5   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           synch event FINISH received, module RF_CALIBRATION, msi 0
146   3   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           lm_lc_generate_rand
147   3   05/30/19 10:44:23.076   +0:00:00.015   BT Logger 1           lm_lc_generate_rand
148   4   05/30/19 10:44:25.931   +0:00:02.870   BT Logger 1           Transport detection: UART detected
149   3   05/30/19 10:44:25.931   +0:00:02.870   BT Logger 1           first byte recevied C0
150   3   05/30/19 10:44:25.931   +0:00:02.870   BT Logger 1           Disable FLIGHT MODE - Enable TX calibration
151   4   05/30/19 10:44:25.931   +0:00:02.870   BT Logger 1           Uart Active Protocol: H5 PROTOCOL
152   4   05/30/19 10:44:50.782   +0:00:27.721   BT Logger 1           H5 RX, Receive msg SYNC
153   4   05/30/19 10:44:50.782   +0:00:27.721   BT Logger 1           H5 TX, send msg SYNC_RESPONSE
154   4   05/30/19 10:44:50.782   +0:00:27.721   BT Logger 1           H5 TX, send msg SYNC
155   7   05/30/19 10:44:51.203   +0:00:28.142   BT Logger 1           *** WARNING *** H5 TX, retransmit lc_msg
156   4   05/30/19 10:44:51.203   +0:00:28.142   BT Logger 1           H5 TX, send msg SYNC
157   7   05/30/19 10:44:51.609   +0:00:28.548   BT Logger 1           *** WARNING *** H5 TX, retransmit lc_msg
158   4   05/30/19 10:44:51.609   +0:00:28.548   BT Logger 1           H5 TX, send msg SYNC

over 4 years ago

0 Vihang Parmar over 4 years ago

TI__Mastermind 29250 points

Ofer,

Traces 106 to 147 in the text above indicate that the CC256xB was powered up correctly. In other words, the power-up sequence explained in the datasheet was followed in enabling the controller.

Traces 148 and 150 indicate that the host is using the H5 protocol (3 wire UART transport from BT spec). Is this intentional? Generally, most systems would use H4 protocol for UART transport that uses hardware flow control.

Besides this, I do not see a HCI_Reset command being received on the controller from the host side. So it is likely that there is some problem in the HCI UART driver on the host side. Which host stack is being used in this system?

Best regards,

Vihang

0 Ofer Melman76748 over 4 years ago in reply to Vihang Parmar

TI__Intellectual 1580 points

Hi Vihang,

Thank you !

Yes we are using the H5 protocol (3 wire UART transport from BT spec),

What could be the issues in the HCI UART? any settings maby missing? can we get a correct logger to see what could the problem be?

I have attached the BTPSCFGI,h and BTPSCFG,h file is there something that we should change in the configuration settings?

The host stack is v4.1

Many Thanks

BTPSCFGI.h BTPSCFG.h

0 Ofer Melman76748 over 4 years ago in reply to Vihang Parmar

TI__Intellectual 1580 points

Hi Vihang,

Thank you !

Yes we are using the H5 protocol (3 wire UART transport from BT spec),

What could be the issues in the HCI UART? any settings maby missing? can we get a correct logger to see what could the problem be?

I have attached the BTPSCFGI,h and BTPSCFG,h file is there something that we should change in the configuration settings?

The host stack is v4.1

Many Thanks

BTPSCFGI.h 4442.BTPSCFG.h 0333.BTPSCFGI.h .h

0 Vihang Parmar over 4 years ago in reply to Ofer Melman76748

TI__Mastermind 29250 points

Ofer,

From the BTPSCFG.h file name, it appears that you are using the TI dual-mode BT stack or a version of it that is ported for a different host. If that is the case, I would recommend first checking if the H4 mode works correctly with one of the sample applications in the stack SDK. Once that is working, the only code change required to switch to H5 would be changing the HCI driver configuration in the main application initialization.

e.g. 

Replace 
   	/* Configure the UART Parameters.                                    */
	HCI_DRIVER_SET_COMM_INFORMATION(&HCI_DriverInformation, 1, VENDOR_BAUD_RATE, cpHCILL_RTS_CTS);
with
	/* Configure the UART Parameters.                                    */
	HCI_DRIVER_SET_COMM_INFORMATION(&HCI_DriverInformation, 1, VENDOR_BAUD_RATE, cp3Wire);

Ofer Melman76748 said:
What could be the issues in the HCI UART? any settings maby missing?

If this is a custom stack release or the standard release ported for some other MCU, the problem might actually be in the HAL and HCITRANS port itself.

Best regards,

Vihang

0 haim e2e over 4 years ago in reply to Vihang Parmar

Prodigy 10 points

Hello Vihang,

We have the UART starting working we had issues with the HCITR_COMProcess (Receiving) and HCITR_COMWrite (transmit) functions, in the logger we are getting an error - "Error RX, Got unexpected LC msg and ignore it, state=uninit, msg=CONFIG, slp_state=0" what does it mean? where can we find the uart message structure and messages type? do you have maybe a correct H% logger so we can compare,

logger05_s.txt

1	07/04/19 12:58:33.219   +0:00:00.000	uart_hci parameters: UartDIV=4, OS=17, SP=63, MoB=7	
2	07/04/19 12:58:33.219   +0:00:00.000	temperature sensing: temp 26, read 0x20, vbe 0x2873319, slope 0x1f829	
3	07/04/19 12:58:33.219   +0:00:00.000	Temperature region = 6	
4	07/04/19 12:58:33.219   +0:00:00.000	In lc_rf_init_periodic_calibration	
5	07/04/19 12:58:33.219   +0:00:00.000	synch event REG received, module RF_CALIBRATION, msi 0	
6	07/04/19 12:58:33.219   +0:00:00.000	synch cmd start instance, module RF_CALIBRATION, msi: 0	
7	07/04/19 12:58:33.219   +0:00:00.000	synch cmd return event STARTED,module RF_CALIBRATION	
8	07/04/19 12:58:33.219   +0:00:00.000	ORCA Platform	
9	07/04/19 12:58:33.219   +0:00:00.000	Process type: Nominal	
10	07/04/19 12:58:33.219   +0:00:00.000	Chip revision: 6	
11	07/04/19 12:58:33.219   +0:00:00.000	Detected Clock = 38400000 Hz	
12	07/04/19 12:58:33.219   +0:00:00.000	Ref Clock = 38400000 Hz	
13	07/04/19 12:58:33.219   +0:00:00.000	XTAL wakeup mode  is disabled	
14	07/04/19 12:58:33.219   +0:00:00.000	Ref Clock is valid for PLL	
15	07/04/19 12:58:33.219   +0:00:00.000	PLL Clock Output is OK	
16	07/04/19 12:58:33.219   +0:00:00.000	PLL Clock Out = 40000000 Hz	
17	07/04/19 12:58:33.219   +0:00:00.000	Clock Working mode: PLL Mode	
18	07/04/19 12:58:33.219   +0:00:00.000	ARM Clock = 40000000 Hz, Slow Clock: External	
19	07/04/19 12:58:33.219   +0:00:00.000	OCP Clock = 8000000 Hz	
20	07/04/19 12:58:33.219   +0:00:00.000	UART HCI baudrate = 116363	
21	07/04/19 12:58:33.219   +0:00:00.000	Gemini type Soft Gemini	
22	07/04/19 12:58:33.219   +0:00:00.000	lm_lc_get_local_features	
23	07/04/19 12:58:33.239   +0:00:00.020	lm_lc_set_brcst_retran	
24	07/04/19 12:58:33.239   +0:00:00.020	lm_lc_self_test_run_init_tests	
25	07/04/19 12:58:33.239   +0:00:00.020	Self Test passed	
26	07/04/19 12:58:33.239   +0:00:00.020	I2C doesn't exist !	
27	07/04/19 12:58:33.239   +0:00:00.020	lm_lc_get_local_bd_addr	
28	07/04/19 12:58:33.239   +0:00:00.020	Software version - 7.0.16	
29	07/04/19 12:58:33.239   +0:00:00.020	Deactivating timer: init	
30	07/04/19 12:58:33.239   +0:00:00.020	lm_lc_rf_periodic_calibration	
31	07/04/19 12:58:33.239   +0:00:00.020	Calibration started. Vector=0x1, 0x0	
32	07/04/19 12:58:33.239   +0:00:00.020	PHY FW Version 3.27	
33	07/04/19 12:58:33.239   +0:00:00.020	random 0x0 0x75ee	
34	07/04/19 12:58:33.239   +0:00:00.020	random 0xb6fd 0xa717	
35	07/04/19 12:58:33.239   +0:00:00.020	random 0x1bb4 0xb7c5	
36	07/04/19 12:58:33.239   +0:00:00.020	random 0xf8cc 0xadd6	
37	07/04/19 12:58:33.239   +0:00:00.020	random 0x8b9 0x696b	
38	07/04/19 12:58:33.239   +0:00:00.020	lm_lc_generate_rand	
39	07/04/19 12:58:33.239   +0:00:00.020	lm_lc_generate_rand	
40	07/04/19 12:58:33.239   +0:00:00.020	synch event FINISH received, module RF_CALIBRATION, msi 0	
41	07/04/19 12:58:33.239   +0:00:00.020	lm_lc_generate_rand	
42	07/04/19 12:58:33.239   +0:00:00.020	lm_lc_generate_rand	
43	07/04/19 12:58:33.379   +0:00:00.160	Transport detection: UART detected	
44	07/04/19 12:58:33.379   +0:00:00.160	first byte recevied C0	
45	07/04/19 12:58:33.379   +0:00:00.160	Disable FLIGHT MODE - Enable TX calibration	
46	07/04/19 12:58:33.379   +0:00:00.160	Uart Active Protocol: H5 PROTOCOL	
47	07/04/19 12:58:33.379   +0:00:00.160	H5 RX, Receive msg SYNC	
48	07/04/19 12:58:33.379   +0:00:00.160	H5 TX, send msg SYNC_RESPONSE	
49	07/04/19 12:58:33.379   +0:00:00.160	H5 TX, send msg SYNC	
50	07/04/19 12:58:33.379   +0:00:00.160	H5 RX, Receive msg SYNC	
51	07/04/19 12:58:33.379   +0:00:00.160	H5 TX, send msg SYNC_RESPONSE	
52	07/04/19 12:58:33.379   +0:00:00.160	H5 TX, send msg SYNC	
53	07/04/19 12:58:33.379   +0:00:00.160	H5 RX, Receive msg SYNC	
54	07/04/19 12:58:33.379   +0:00:00.160	H5 TX, send msg SYNC_RESPONSE	
55	07/04/19 12:58:33.379   +0:00:00.160	H5 TX, send msg SYNC	
56	07/04/19 12:58:33.379   +0:00:00.160	H5 RX, Receive msg CONFIG	
57	07/04/19 12:58:33.379   +0:00:00.160	H5 Error RX, Got unexpected LC msg and ignore it, state=uninit, msg=CONFIG, slp_state=0	
58	07/04/19 12:58:33.379   +0:00:00.160	H5 RX, Receive msg SYNC	
59	07/04/19 12:58:33.379   +0:00:00.160	H5 TX, send msg SYNC_RESPONSE	
60	07/04/19 12:58:33.379   +0:00:00.160	H5 TX, send msg SYNC	
61	07/04/19 12:58:33.379   +0:00:00.160	H5 RX, Receive msg SYNC_RESPONSE	
62	07/04/19 12:58:33.379   +0:00:00.160	H5 RX, Receive msg SYNC	
63	07/04/19 12:58:33.379   +0:00:00.160	H5 TX, send msg SYNC_RESPONSE	
64	07/04/19 12:58:33.379   +0:00:00.160	H5 RX, Receive msg [0x3e02]	
65	07/04/19 12:58:33.379   +0:00:00.160	H5 RX, Receive msg SYNC	
66	07/04/19 12:58:33.379   +0:00:00.160	H5 TX, send msg SYNC_RESPONSE	
67	07/04/19 12:58:33.379   +0:00:00.160	H5 RX, Receive msg SYNC_RESPONSE	
68	07/04/19 12:58:33.379   +0:00:00.160	H5 Error RX, Got unexpected LC msg and ignore it, state=init, msg=7d02, slp_state=0	
69	07/04/19 12:58:33.379   +0:00:00.160	H5 RX, Receive msg SYNC	
70	07/04/19 12:58:33.379   +0:00:00.160	H5 TX, send msg SYNC_RESPONSE	
71	07/04/19 12:58:33.379   +0:00:00.160	H5 RX, Receive msg SYNC_RESPONSE	
72	07/04/19 12:58:33.379   +0:00:00.160	H5 Error RX, Got unexpected LC msg and ignore it, state=init, msg=7d02, slp_state=0	
73	07/04/19 12:58:33.379   +0:00:00.160	H5 RX, Receive msg SYNC	
74	07/04/19 12:58:33.379   +0:00:00.160	H5 TX, send msg SYNC_RESPONSE	
75	07/04/19 12:58:33.379   +0:00:00.160	H5 RX, Receive msg SYNC_RESPONSE	
76	07/04/19 12:58:33.379   +0:00:00.160	H5 Error RX, Got unexpected LC msg and ignore it, state=init, msg=7d02, slp_state=0	
77	07/04/19 12:58:33.379   +0:00:00.160	H5 RX, Receive msg SYNC	
78	07/04/19 12:58:33.379   +0:00:00.160	H5 TX, send msg SYNC_RESPONSE	
79	07/04/19 12:58:33.379   +0:00:00.160	H5 RX, Receive msg [0x3e02]	
80	07/04/19 12:58:33.379   +0:00:00.160	H5 RX, Receive msg SYNC	
81	07/04/19 12:58:33.379   +0:00:00.160	H5 TX, send msg SYNC_RESPONSE	
82	07/04/19 12:58:33.379   +0:00:00.160	H5 RX, Receive msg SYNC_RESPONSE	
83	07/04/19 12:58:33.379   +0:00:00.160	H5 Error RX, Got unexpected LC msg and ignore it, state=init, msg=7d02, slp_state=0	
84	07/04/19 12:58:33.379   +0:00:00.160	H5 RX, Receive msg SYNC	
85	07/04/19 12:58:33.379   +0:00:00.160	H5 TX, send msg SYNC_RESPONSE	
86	07/04/19 12:58:33.379   +0:00:00.160	H5 RX, Receive msg SYNC_RESPONSE	
87	07/04/19 12:58:33.379   +0:00:00.160	H5 Error RX, Got unexpected LC msg and ignore it, state=init, msg=7d02, slp_state=0	
88	07/04/19 12:58:33.379   +0:00:00.160	H5 RX, Receive msg SYNC	
89	07/04/19 12:58:33.379   +0:00:00.160	H5 TX, send msg SYNC_RESPONSE	
90	07/04/19 12:58:33.379   +0:00:00.160	H5 RX, Receive msg SYNC_RESPONSE	
91	07/04/19 12:58:33.379   +0:00:00.160	H5 Error RX, Got unexpected LC msg and ignore it, state=init, msg=7d02, slp_state=0	
92	07/04/19 12:58:33.399   +0:00:00.180	H5 RX, Receive msg SYNC	
93	07/04/19 12:58:33.399   +0:00:00.180	H5 TX, send msg SYNC_RESPONSE	
94	07/04/19 12:58:33.559   +0:00:00.340	H5 RX, Receive msg [0x3e02]	
95	07/04/19 12:58:33.559   +0:00:00.340	H5 RX, Receive msg SYNC	
96	07/04/19 12:58:33.559   +0:00:00.340	H5 TX, send msg SYNC_RESPONSE	
97	07/04/19 12:58:33.559   +0:00:00.340	H5 RX, Receive msg SYNC_RESPONSE	
98	07/04/19 12:58:33.559   +0:00:00.340	H5 Error RX, Got unexpected LC msg and ignore it, state=init, msg=7d02, slp_state=0	
99	07/04/19 12:58:33.559   +0:00:00.340	H5 RX, Receive msg SYNC	
100	07/04/19 12:58:33.559   +0:00:00.340	H5 TX, send msg SYNC_RESPONSE	
101	07/04/19 12:58:33.559   +0:00:00.340	H5 RX, Receive msg SYNC_RESPONSE	
102	07/04/19 12:58:33.559   +0:00:00.340	H5 Error RX, Got unexpected LC msg and ignore it, state=init, msg=7d02, slp_state=0	
103	07/04/19 12:58:33.559   +0:00:00.340	H5 RX, Receive msg SYNC	
104	07/04/19 12:58:33.559   +0:00:00.340	H5 TX, send msg SYNC_RESPONSE	
105	07/04/19 12:58:33.559   +0:00:00.340	H5 RX, Receive msg SYNC_RESPONSE	
106	07/04/19 12:58:33.559   +0:00:00.340	H5 Error RX, Got unexpected LC msg and ignore it, state=init, msg=7d02, slp_state=0	
107	07/04/19 12:58:33.559   +0:00:00.340	H5 RX, Receive msg SYNC	
108	07/04/19 12:58:33.559   +0:00:00.340	H5 TX, send msg SYNC_RESPONSE	
109	07/04/19 12:58:33.569   +0:00:00.350	H5 RX, Receive msg [0x3e02]	
110	07/04/19 12:58:33.569   +0:00:00.350	H5 RX, Receive msg SYNC	
111	07/04/19 12:58:33.569   +0:00:00.350	H5 TX, send msg SYNC_RESPONSE	
112	07/04/19 12:58:33.569   +0:00:00.350	H5 RX, Receive msg SYNC_RESPONSE	
113	07/04/19 12:58:33.569   +0:00:00.350	H5 Error RX, Got unexpected LC msg and ignore it, state=init, msg=7d02, slp_state=0	
114	07/04/19 12:58:33.569   +0:00:00.350	H5 RX, Receive msg SYNC	
115	07/04/19 12:58:33.569   +0:00:00.350	H5 TX, send msg SYNC_RESPONSE	
116	07/04/19 12:58:33.569   +0:00:00.350	H5 RX, Receive msg SYNC_RESPONSE	
117	07/04/19 12:58:33.569   +0:00:00.350	H5 Error RX, Got unexpected LC msg and ignore it, state=init, msg=7d02, slp_state=0	
118	07/04/19 12:58:33.639   +0:00:00.420	H5 RX, Receive msg CONFIG	
119	07/04/19 12:58:33.639   +0:00:00.420	H5 RX, config, host_param = 17, win=7, sw_flow=0, crc=1	
120	07/04/19 12:58:33.639   +0:00:00.420	H5 TX, config, win=2, sw_flow=0, crc=1	
121	07/04/19 12:58:33.639   +0:00:00.420	H5 TX, send msg CONFIG_RESPONSE	
122	07/04/19 12:58:33.639   +0:00:00.420	H5 TX, send msg CONFIG	
123	07/04/19 12:58:33.889   +0:00:00.670	H5 RX, Receive msg CONFIG	
124	07/04/19 12:58:33.889   +0:00:00.670	H5 RX, config, host_param = 17, win=7, sw_flow=0, crc=1	
125	07/04/19 12:58:33.889   +0:00:00.670	H5 TX, config, win=2, sw_flow=0, crc=1	
126	07/04/19 12:58:33.889   +0:00:00.670	H5 TX, send msg CONFIG_RESPONSE	
127	07/04/19 12:58:33.889   +0:00:00.670	H5 TX, send msg CONFIG	
128	07/04/19 12:58:34.149   +0:00:00.930	H5 RX, Receive msg CONFIG	
129	07/04/19 12:58:34.149   +0:00:00.930	H5 RX, config, host_param = 17, win=7, sw_flow=0, crc=1	
130	07/04/19 12:58:34.149   +0:00:00.930	H5 TX, config, win=2, sw_flow=0, crc=1	
131	07/04/19 12:58:34.149   +0:00:00.930	H5 TX, send msg CONFIG_RESPONSE	
132	07/04/19 12:58:34.149   +0:00:00.930	H5 TX, send msg CONFIG	
133	07/04/19 12:58:34.419   +0:00:01.200	H5 RX, Receive msg CONFIG	
134	07/04/19 12:58:34.419   +0:00:01.200	H5 RX, config, host_param = 17, win=7, sw_flow=0, crc=1	
135	07/04/19 12:58:34.419   +0:00:01.200	H5 TX, config, win=2, sw_flow=0, crc=1	
136	07/04/19 12:58:34.419   +0:00:01.200	H5 TX, send msg CONFIG_RESPONSE	
137	07/04/19 12:58:34.419   +0:00:01.200	H5 TX, send msg CONFIG	
138	07/04/19 12:58:34.679   +0:00:01.460	H5 RX, Receive msg CONFIG	
139	07/04/19 12:58:34.679   +0:00:01.460	H5 RX, config, host_param = 17, win=7, sw_flow=0, crc=1	
140	07/04/19 12:58:34.679   +0:00:01.460	H5 TX, config, win=2, sw_flow=0, crc=1	
141	07/04/19 12:58:34.679   +0:00:01.460	H5 TX, send msg CONFIG_RESPONSE	
142	07/04/19 12:58:34.679   +0:00:01.460	H5 TX, send msg CONFIG	
143	07/04/19 12:58:34.929   +0:00:01.710	H5 RX, Receive msg CONFIG	
144	07/04/19 12:58:34.929   +0:00:01.710	H5 RX, config, host_param = 17, win=7, sw_flow=0, crc=1	
145	07/04/19 12:58:34.929   +0:00:01.710	H5 TX, config, win=2, sw_flow=0, crc=1	
146	07/04/19 12:58:34.929   +0:00:01.710	H5 TX, send msg CONFIG_RESPONSE	
147	07/04/19 12:58:34.929   +0:00:01.710	H5 TX, send msg CONFIG	
148	07/04/19 12:58:35.189   +0:00:01.970	H5 RX, Receive msg CONFIG	
149	07/04/19 12:58:35.189   +0:00:01.970	H5 RX, config, host_param = 17, win=7, sw_flow=0, crc=1	
150	07/04/19 12:58:35.189   +0:00:01.970	H5 TX, config, win=2, sw_flow=0, crc=1	
151	07/04/19 12:58:35.189   +0:00:01.970	H5 TX, send msg CONFIG_RESPONSE	
152	07/04/19 12:58:35.189   +0:00:01.970	H5 TX, send msg CONFIG	
153	07/04/19 12:58:35.459   +0:00:02.240	H5 RX, Receive msg CONFIG	
154	07/04/19 12:58:35.459   +0:00:02.240	H5 RX, config, host_param = 17, win=7, sw_flow=0, crc=1	
155	07/04/19 12:58:35.459   +0:00:02.240	H5 TX, config, win=2, sw_flow=0, crc=1	
156	07/04/19 12:58:35.459   +0:00:02.240	H5 TX, send msg CONFIG_RESPONSE	
157	07/04/19 12:58:35.459   +0:00:02.240	H5 TX, send msg CONFIG	
158	07/04/19 12:58:35.719   +0:00:02.500	H5 RX, Receive msg CONFIG	
159	07/04/19 12:58:35.719   +0:00:02.500	H5 RX, config, host_param = 17, win=7, sw_flow=0, crc=1	
160	07/04/19 12:58:35.719   +0:00:02.500	H5 TX, config, win=2, sw_flow=0, crc=1	
161	07/04/19 12:58:35.719   +0:00:02.500	H5 TX, send msg CONFIG_RESPONSE	
162	07/04/19 12:58:35.719   +0:00:02.500	H5 TX, send msg CONFIG	
163	07/04/19 12:58:35.969   +0:00:02.750	H5 RX, Receive msg CONFIG	
164	07/04/19 12:58:35.969   +0:00:02.750	H5 RX, config, host_param = 17, win=7, sw_flow=0, crc=1	
165	07/04/19 12:58:35.969   +0:00:02.750	H5 TX, config, win=2, sw_flow=0, crc=1	
166	07/04/19 12:58:35.969   +0:00:02.750	H5 TX, send msg CONFIG_RESPONSE	
167	07/04/19 12:58:35.969   +0:00:02.750	H5 TX, send msg CONFIG	
168	07/04/19 12:58:36.229   +0:00:03.010	H5 RX, Receive msg CONFIG	
169	07/04/19 12:58:36.229   +0:00:03.010	H5 RX, config, host_param = 17, win=7, sw_flow=0, crc=1	
170	07/04/19 12:58:36.229   +0:00:03.010	H5 TX, config, win=2, sw_flow=0, crc=1	
171	07/04/19 12:58:36.229   +0:00:03.010	H5 TX, send msg CONFIG_RESPONSE	
172	07/04/19 12:58:36.229   +0:00:03.010	H5 TX, send msg CONFIG	
173	07/04/19 12:58:36.489   +0:00:03.270	H5 RX, Receive msg CONFIG	
174	07/04/19 12:58:36.499   +0:00:03.280	H5 RX, config, host_param = 17, win=7, sw_flow=0, crc=1	
175	07/04/19 12:58:36.499   +0:00:03.280	H5 TX, config, win=2, sw_flow=0, crc=1	
176	07/04/19 12:58:36.499   +0:00:03.280	H5 TX, send msg CONFIG_RESPONSE	
177	07/04/19 12:58:36.499   +0:00:03.280	H5 TX, send msg CONFIG	
178	07/04/19 12:58:36.759   +0:00:03.540	H5 RX, Receive msg CONFIG	
179	07/04/19 12:58:36.759   +0:00:03.540	H5 RX, config, host_param = 17, win=7, sw_flow=0, crc=1	
180	07/04/19 12:58:36.759   +0:00:03.540	H5 TX, config, win=2, sw_flow=0, crc=1	
181	07/04/19 12:58:36.759   +0:00:03.540	H5 TX, send msg CONFIG_RESPONSE	
182	07/04/19 12:58:36.759   +0:00:03.540	H5 TX, send msg CONFIG	
183	07/04/19 12:58:37.019   +0:00:03.800	H5 RX, Receive msg CONFIG	
184	07/04/19 12:58:37.019   +0:00:03.800	H5 RX, config, host_param = 17, win=7, sw_flow=0, crc=1	
185	07/04/19 12:58:37.019   +0:00:03.800	H5 TX, config, win=2, sw_flow=0, crc=1	
186	07/04/19 12:58:37.019   +0:00:03.800	H5 TX, send msg CONFIG_RESPONSE	
187	07/04/19 12:58:37.019   +0:00:03.800	H5 TX, send msg CONFIG	
188	07/04/19 12:58:37.269   +0:00:04.050	H5 RX, Receive msg CONFIG	
189	07/04/19 12:58:37.269   +0:00:04.050	H5 RX, config, host_param = 17, win=7, sw_flow=0, crc=1	
190	07/04/19 12:58:37.269   +0:00:04.050	H5 TX, config, win=2, sw_flow=0, crc=1	
191	07/04/19 12:58:37.269   +0:00:04.050	H5 TX, send msg CONFIG_RESPONSE	
192	07/04/19 12:58:37.269   +0:00:04.050	H5 TX, send msg CONFIG	
193	07/04/19 12:58:37.519   +0:00:04.300	H5 RX, Receive msg CONFIG	
194	07/04/19 12:58:37.519   +0:00:04.300	H5 RX, config, host_param = 3d, win=5, sw_flow=1, crc=1	
195	07/04/19 12:58:37.519   +0:00:04.300	H5 TX, config, win=2, sw_flow=1, crc=1	
196	07/04/19 12:58:37.519   +0:00:04.300	H5, set uart flow control into: SW (XON/XOFF)	
197	07/04/19 12:58:37.519   +0:00:04.300	H5 TX, send msg CONFIG_RESPONSE	
198	07/04/19 12:58:37.519   +0:00:04.300	H5 TX, send msg CONFIG	
199	07/04/19 12:58:37.799   +0:00:04.580	H5 RX, Receive msg CONFIG	
200	07/04/19 12:58:37.799   +0:00:04.580	H5 RX, config, host_param = 17, win=7, sw_flow=0, crc=1	
201	07/04/19 12:58:37.799   +0:00:04.580	H5 TX, config, win=2, sw_flow=0, crc=1	
202	07/04/19 12:58:37.799   +0:00:04.580	H5 TX, send msg CONFIG_RESPONSE	
203	07/04/19 12:58:37.799   +0:00:04.580	H5 TX, send msg CONFIG	
204	07/04/19 12:58:38.059   +0:00:04.840	H5 RX, Receive msg CONFIG	
205	07/04/19 12:58:38.059   +0:00:04.840	H5 RX, config, host_param = 17, win=7, sw_flow=0, crc=1	
206	07/04/19 12:58:38.059   +0:00:04.840	H5 TX, config, win=2, sw_flow=0, crc=1	
207	07/04/19 12:58:38.059   +0:00:04.840	H5 TX, send msg CONFIG_RESPONSE	
208	07/04/19 12:58:38.059   +0:00:04.840	H5 TX, send msg CONFIG	
209	07/04/19 12:58:38.309   +0:00:05.090	H5 RX, Receive msg CONFIG	
210	07/04/19 12:58:38.309   +0:00:05.090	H5 RX, config, host_param = 17, win=7, sw_flow=0, crc=1	
211	07/04/19 12:58:38.309   +0:00:05.090	H5 TX, config, win=2, sw_flow=0, crc=1	
212	07/04/19 12:58:38.309   +0:00:05.090	H5 TX, send msg CONFIG_RESPONSE	
213	07/04/19 12:58:38.309   +0:00:05.090	H5 TX, send msg CONFIG	
214	07/04/19 12:58:38.559   +0:00:05.340	H5 RX, Receive msg CONFIG	
215	07/04/19 12:58:38.569   +0:00:05.350	H5 RX, config, host_param = 17, win=7, sw_flow=0, crc=1	
216	07/04/19 12:58:38.569   +0:00:05.350	H5 TX, config, win=2, sw_flow=0, crc=1	
217	07/04/19 12:58:38.569   +0:00:05.350	H5 TX, send msg CONFIG_RESPONSE	
218	07/04/19 12:58:38.569   +0:00:05.350	H5 TX, send msg CONFIG

Many Thanks,

0 Vihang Parmar over 4 years ago in reply to haim e2e

TI__Mastermind 29250 points

Please see the attached example logs for comparison. They were captured on CC2564MODA running the SPPDemo from the SDK, with only change of cp3Wire instead of cpHCILL_RTS_CTS.

CC2564MODA_init_using_H5.lgr

From the logger05_s.txt, it appears that you have a bug in Receiving data on the host. The Host sends the SYNC msg that is received by the controller and the controller responds with the SYNC_RESPONSE msg. However, the host keeps re-transmitting the SYNC msg after that as if the HCI drivers never got the SYNC_RESPONSE.

BR,

Vihang

Bluetooth®︎

Bluetooth forum

CC2564MODA: We are stuck at the HCI_Reset function (int BTPSAPI HCI_Reset(unsigned int BluetoothStackID, Byte_t *StatusResult)