Compiler/CC2538: How to compile CC2538 UART?

Georgi Ivanov78

Part Number: CC2538
Other Parts Discussed in Thread: Z-STACK, TIDC-ZNP-HOST-SW3, Z-STACK-ARCHIVE

Tool/software: TI C/C++ Compiler

Hello,

I haved tryed ZNP-Host-Framework\bin\cc2538-znp-120-uart-noflow-tclk.hex and work as well and I succeed to pair ZigBee device.

I want to compile the same project and I tryed ZStack_3.0.2\Projects\zstack\ZNP\CC2538 IAR project in CC2538ZNP- Debug mode with following defined setting:

xHAL_UART_USB
xUSB_SETUP_MAX_NUMBER_OF_INTERFACES=5
xHAL_SPI=TRUE
HAL_UART=TRUE
BDB_FINDING_BINDING_CAPABILITY_ENABLED=1
DISABLE_GREENPOWER_BASIC_PROXY
TC_LINKKEY_JOIN
ewarm
CC2538_USE_ALTERNATE_INTERRUPT_MAP=1
CC2538ZNP
ZNP_ALT
xPOWER_SAVING
FEATURE_SYSTEM_STATS
FEATURE_RESET_MACRO
ZDNWKMGR_MIN_TRANSMISSIONS=0
MT_UART_DEFAULT_OVERFLOW=FALSE
ASSERT_RESET
FAKE_CRC_SHDW
ZCL_READ
ZCL_DISCOVER
ZCL_WRITE
ZCL_BASIC
ZCL_IDENTIFY
ZTOOL_P1

The compiled firmware, can communicate throw UART but I can`t pair any ZigBee device.

How can I compile exactly same firware as ZNP-Host-Framework\bin\cc2538-znp-120-uart-noflow-tclk.hex?

Best regards!

over 6 years ago

0 YiKai Chen over 6 years ago

Guru 735685 points

How do you setup ZNP to act as coordinator and form Zigbee network? Can you elaborate your steps?

0 Georgi Ivanov78 over 6 years ago in reply to YiKai Chen

Intellectual 320 points

Hello,

My steps are:

1. Resetting ZNP

2. Enter device type Coordinator

3. Enter channel 13

4. Set EndPoint 1

5. Start binding

We are using ZNP Host framework, and I will attach you a detailed debug log from the framework.

Thanks!

Fullscreen 5873.test.log Download

Terminal log file
Date: 7/24/2019 - 1:14:07 PM
-----------------------------------------------
=============================================================
13:14:13.557> 
FIRMWARE VERSION: [1.4.8.0]
13:14:13.557> 
=============================================================
13:14:13.557> 

13:14:13.557> 
rpcWaitMqClientMsg: timeout=1000
rpcWaitMqClientMsg: waiting on queue 1000:1:0
Sem timed wait START
13:14:13.802> 
TimeOut: 1000
13:14:13.802> 
SOC IN  <-- 14 Bytes: SOF:FE, Len:09, CMD0:41, CMD1:80, Payload:00:02:00:02:07:02:C2:00:00, FCS:00
rpcProcess: writing 9 bytes AREQ to tail of the que
Sem post
13:14:13.942> 
Sem timed wait - succ
13:14:13.942> 
rpcWaitMqClientMsg: processing MT[9]
sysProcess: processing CMD0:41, CMD1:80
sysProcess: MT_SYS_RESET_IND
rpcWaitMqClientMsg: timeout=1000
rpcWaitMqClientMsg: waiting on queue 1000:1:0
Sem timed wait START
13:14:13.942> 
TimeOut: 1000
13:14:13.942> 
Sem timeout: 1.0
13:14:14.866> 
Flushed 1 message from msg queue
13:14:14.866> 
rpcWaitMqClientMsg: timeout=50
rpcWaitMqClientMsg: waiting on queue 50:2:50000000
Sem timed wait START
13:14:15.869> 
TimeOut: 50
13:14:15.869> 
Sem timeout: 2.50000000
13:14:16.049> 
rpcSendFrame: Blocking on RPC sem
rpcSendFrame: Sending RPC
SOC OUT --> 10 Bytes: SOF:FE, Len:05, CMD0:21, CMD1:09, Payload:03:00:00:01:03, FCS:2C
rpcSendFrame: waiting for SRSP [01]
TimeOut: 2000
13:14:16.049> 
SOC IN  <-- 9 Bytes: SOF:FE, Len:04, CMD0:61, CMD1:09, Payload:00:69:00:02, FCS:07
rpcProcess: processing expected srsp [01]
rpcProcess: writing 4 bytes SRSP to head of the queue
Sem post
13:14:16.049> 
rpcWaitMqClientMsg: timeout=50
rpcWaitMqClientMsg: waiting on queue 50:2:50000000
Sem timed wait START
13:14:16.049> 
TimeOut: 50
13:14:16.049> 
Sem timed wait - succ
13:14:16.049> 
rpcWaitMqClientMsg: processing MT[4]
sysProcess: processing CMD0:61, CMD1:9
processSrsp: unsupported message

NV Write Startup Option cmd sent[0]...

->Resetting ZNP

rpcSendFrame: Blocking on RPC sem
rpcSendFrame: Sending RPC
SOC OUT --> 6 Bytes: SOF:FE, Len:01, CMD0:41, CMD1:00, Payload:01, FCS:41
rpcWaitMqClientMsg: timeout=50
rpcWaitMqClientMsg: waiting on queue 50:2:50000000
Sem timed wait START
13:14:16.049> 
TimeOut: 50
13:14:16.049> 
Sem timeout: 2.50000000
13:14:16.049> 
rpcWaitMqClientMsg: timeout=5000
rpcWaitMqClientMsg: waiting on queue 5000:7:0
Sem timed wait START
13:14:16.049> 
TimeOut: 5000
13:14:16.049> 
SOC IN  <-- 14 Bytes: SOF:FE, Len:09, CMD0:41, CMD1:80, Payload:00:02:00:02:07:02:C2:00:00, FCS:00
rpcProcess: writing 9 bytes AREQ to tail of the que
Sem post
13:14:17.254> 
Sem timed wait - succ
13:14:17.254> 
rpcWaitMqClientMsg: processing MT[9]
sysProcess: processing CMD0:41, CMD1:80
sysProcess: MT_SYS_RESET_IND
ZNP Version: 2.7.2

->Enter device type c: Coordinator, r: Router, e: End Device:

rpcSendFrame: Blocking on RPC sem
rpcSendFrame: Sending RPC
SOC OUT --> 10 Bytes: SOF:FE, Len:05, CMD0:21, CMD1:09, Payload:87:00:00:01:00, FCS:AB
rpcSendFrame: waiting for SRSP [01]
TimeOut: 2000
13:14:17.254> 
SOC IN  <-- 9 Bytes: SOF:FE, Len:04, CMD0:61, CMD1:09, Payload:00:69:00:02, FCS:07
rpcProcess: processing expected srsp [01]
rpcProcess: writing 4 bytes SRSP to head of the queue
Sem post
13:14:17.254> 
rpcWaitMqClientMsg: timeout=50
rpcWaitMqClientMsg: waiting on queue 50:2:50000000
Sem timed wait START
13:14:17.254> 
TimeOut: 50
13:14:17.254> 
Sem timed wait - succ
13:14:17.254> 
rpcWaitMqClientMsg: processing MT[4]
sysProcess: processing CMD0:61, CMD1:9
processSrsp: unsupported message

NV Write Device Type cmd sent... [0]

NV Write PAN ID cmd sending...
rpcSendFrame: Blocking on RPC sem
rpcSendFrame: Sending RPC
SOC OUT --> 11 Bytes: SOF:FE, Len:06, CMD0:21, CMD1:09, Payload:83:00:00:02:FF:FF, FCS:AF
rpcSendFrame: waiting for SRSP [01]
TimeOut: 2000
13:14:17.254> 
SOC IN  <-- 9 Bytes: SOF:FE, Len:04, CMD0:61, CMD1:09, Payload:00:69:00:02, FCS:07
rpcProcess: processing expected srsp [01]
rpcProcess: writing 4 bytes SRSP to head of the queue
Sem post
13:14:17.254> 
rpcWaitMqClientMsg: timeout=50
rpcWaitMqClientMsg: waiting on queue 50:2:50000000
Sem timed wait START
13:14:17.254> 
TimeOut: 50
13:14:17.254> 
Sem timed wait - succ
13:14:17.254> 
rpcWaitMqClientMsg: processing MT[4]
sysProcess: processing CMD0:61, CMD1:9
processSrsp: unsupported message

NV Write PAN ID cmd sent...[0]

->Enter channel 11-26:

rpcSendFrame: Blocking on RPC sem
rpcSendFrame: Sending RPC
SOC OUT --> 13 Bytes: SOF:FE, Len:08, CMD0:21, CMD1:09, Payload:84:00:00:04:00:20:00:00, FCS:80
rpcSendFrame: waiting for SRSP [01]
TimeOut: 2000
13:14:17.254> 
SOC IN  <-- 9 Bytes: SOF:FE, Len:04, CMD0:61, CMD1:09, Payload:00:69:00:02, FCS:07
rpcProcess: processing expected srsp [01]
rpcProcess: writing 4 bytes SRSP to head of the queue
Sem post
13:14:19.379> 
rpcWaitMqClientMsg: timeout=50
rpcWaitMqClientMsg: waiting on queue 50:2:50000000
Sem timed wait START
13:14:19.379> 
TimeOut: 50
13:14:19.379> 
Sem timed wait - succ
13:14:19.379> 
rpcWaitMqClientMsg: processing MT[4]
sysProcess: processing CMD0:61, CMD1:9
processSrsp: unsupported message

NV Write Channel List cmd sent...[0]
rpcSendFrame: Blocking on RPC sem
rpcSendFrame: Sending RPC
SOC OUT --> 26 Bytes: SOF:FE, Len:15, CMD0:24, CMD1:00, Payload:01:04:01:00:01:01:00:03:00:00:03:00:06:00:03:00:00:03:00:06:00, FCS:35
rpcSendFrame: waiting for SRSP [04]
TimeOut: 2000
13:14:19.379> 
SOC IN  <-- 9 Bytes: SOF:FE, Len:04, CMD0:64, CMD1:00, Payload:00:65:00:02, FCS:07
rpcProcess: processing expected srsp [04]
rpcProcess: writing 4 bytes SRSP to head of the queue
Sem post
13:14:19.379> 
rpcWaitMqClientMsg: timeout=50
rpcWaitMqClientMsg: waiting on queue 50:2:50000000
Sem timed wait START
13:14:19.379> 
TimeOut: 50
13:14:19.379> 
Sem timed wait - succ
13:14:19.379> 
rpcWaitMqClientMsg: processing MT[4]
afProcess: processing CMD0:64, CMD1:0
processSrsp: unsupported message [64:0]

->EndPoint: 1

rpcSendFrame: Blocking on RPC sem
rpcSendFrame: Sending RPC
SOC OUT --> 7 Bytes: SOF:FE, Len:02, CMD0:25, CMD1:40, Payload:00:00, FCS:67
rpcSendFrame: waiting for SRSP [05]
TimeOut: 2000
13:14:19.379> 
SOC IN  <-- 9 Bytes: SOF:FE, Len:04, CMD0:65, CMD1:40, Payload:00:24:00:02, FCS:07
rpcProcess: processing expected srsp [05]
rpcProcess: writing 4 bytes SRSP to head of the queue
Sem post
13:14:19.379> 
rpcWaitMqClientMsg: timeout=50
rpcWaitMqClientMsg: waiting on queue 50:2:50000000
Sem timed wait START
13:14:19.379> 
TimeOut: 50
13:14:19.379> 
Sem timed wait - succ
13:14:19.379> 
rpcWaitMqClientMsg: processing MT[4]
zdoProcess: processing CMD0:65, CMD1:40
processSrsp: unsupported message
zdoInit RESTORED_NETWORK
process zdoStatechange callbacks
rpcWaitMqClientMsg: timeout=5000
rpcWaitMqClientMsg: waiting on queue 5000:7:0
Sem timed wait START
13:14:19.379> 
TimeOut: 5000
13:14:19.379> 
SOC IN  <-- 11 Bytes: SOF:FE, Len:06, CMD0:4F, CMD1:80, Payload:01:02:04:CB:07:02, FCS:C2
rpcProcess: writing 6 bytes AREQ to tail of the que
Sem post
13:14:21.538> 
Sem timed wait - succ
13:14:21.538> 
rpcWaitMqClientMsg: processing MT[6]
mtProcess: CMD0:4f, CMD1:80, not handled
rpcWaitMqClientMsg: timeout=5000
rpcWaitMqClientMsg: waiting on queue 5000:9:0
Sem timed wait START
13:14:21.538> 
TimeOut: 5000
13:14:21.538> 
SOC IN  <-- 9 Bytes: SOF:FE, Len:04, CMD0:45, CMD1:C0, Payload:08:8C:04:CB, FCS:07
rpcProcess: writing 4 bytes AREQ to tail of the que
Sem post
13:14:21.538> 
Sem timed wait - succ
13:14:21.538> 
rpcWaitMqClientMsg: processing MT[4]
zdoProcess: processing CMD0:45, CMD1:c0
zdoProcess: MT_ZDO_STATE_CHANGE_IND
Network Starting
mtZdoStateChangeIndCb: Started as Zigbee Coordinator
rpcWaitMqClientMsg: timeout=5000
rpcWaitMqClientMsg: waiting on queue 5000:10:0
Sem timed wait START
13:14:21.538> 
TimeOut: 5000
13:14:21.538> 
SOC IN  <-- 9 Bytes: SOF:FE, Len:04, CMD0:45, CMD1:C0, Payload:09:8D:04:CB, FCS:07
rpcProcess: writing 4 bytes AREQ to tail of the que
Sem post
13:14:21.538> 
SOC IN  <-- 11 Bytes: SOF:FE, Len:06, CMD0:4F, CMD1:80, Payload:00:02:00:CE:07:02, FCS:C2
rpcProcess: writing 6 bytes AREQ to tail of the que
Sem post
13:14:21.538> 
Sem timed wait - succ
13:14:21.538> 
rpcWaitMqClientMsg: processing MT[4]
zdoProcess: processing CMD0:45, CMD1:c0
zdoProcess: MT_ZDO_STATE_CHANGE_IND
Network Started
mtZdoStateChangeIndCb: Started as Zigbee Coordinator
rpcSendFrame: Blocking on RPC sem
rpcSendFrame: Sending RPC
SOC OUT --> 10 Bytes: SOF:FE, Len:05, CMD0:21, CMD1:09, Payload:03:00:00:01:00, FCS:2F
rpcSendFrame: waiting for SRSP [01]
TimeOut: 2000
13:14:21.538> 
SOC IN  <-- 9 Bytes: SOF:FE, Len:04, CMD0:61, CMD1:09, Payload:00:69:00:CE, FCS:07
rpcProcess: processing expected srsp [01]
rpcProcess: writing 4 bytes SRSP to head of the queue
Sem post
13:14:21.538> 
rpcWaitMqClientMsg: timeout=50
rpcWaitMqClientMsg: waiting on queue 50:5:50000000
Sem timed wait START
13:14:21.538> 
TimeOut: 50
13:14:21.538> 
Sem timed wait - succ
13:14:21.538> 
rpcWaitMqClientMsg: processing MT[4]
sysProcess: processing CMD0:61, CMD1:9
processSrsp: unsupported message

NV Write Startup Option cmd sent[0]...
Network up

rpcSendFrame: Blocking on RPC sem
rpcSendFrame: Sending RPC
SOC OUT --> 5 Bytes: SOF:FE, Len:00, CMD0:21, CMD1:04, Payload: FCS:25
rpcSendFrame: waiting for SRSP [01]
TimeOut: 2000
13:14:23.657> 
SOC IN  <-- 16 Bytes: SOF:FE, Len:0B, CMD0:61, CMD1:04, Payload:00:00:00:00:00:00:00:00:6D:00:00, FCS:00
rpcProcess: processing expected srsp [01]
rpcProcess: writing 11 bytes SRSP to head of the queue
Sem post
13:14:23.657> 
rpcWaitMqClientMsg: timeout=50
rpcWaitMqClientMsg: waiting on queue 50:5:50000000
Sem timed wait START
13:14:23.657> 
TimeOut: 50
13:14:23.657> 
Sem timed wait - succ
13:14:23.657> 
rpcWaitMqClientMsg: processing MT[11]
sysProcess: processing CMD0:61, CMD1:4
sysProcess: MT_SYS_GET_EXTADDR
mtSysGetExtAddrSrspCb
ExtAddr: 0x0000000000000000
rpcSendFrame: Blocking on RPC sem
rpcSendFrame: Sending RPC
SOC OUT --> 10 Bytes: SOF:FE, Len:05, CMD0:21, CMD1:09, Payload:8F:00:00:01:01, FCS:A2
rpcSendFrame: waiting for SRSP [01]
TimeOut: 2000
13:14:23.657> 
SOC IN  <-- 9 Bytes: SOF:FE, Len:04, CMD0:61, CMD1:09, Payload:00:69:00:00, FCS:00
rpcProcess: processing expected srsp [01]
rpcProcess: writing 4 bytes SRSP to head of the queue
Sem post
13:14:23.657> 
rpcWaitMqClientMsg: timeout=50
rpcWaitMqClientMsg: waiting on queue 50:5:50000000
Sem timed wait START
13:14:23.657> 
TimeOut: 50
13:14:23.657> 
Sem timed wait - succ
13:14:23.657> 
rpcWaitMqClientMsg: processing MT[4]
sysProcess: processing CMD0:61, CMD1:9
processSrsp: unsupported message
Start Binding
rpcSendFrame: Blocking on RPC sem
rpcSendFrame: Sending RPC
SOC OUT --> 8 Bytes: SOF:FE, Len:03, CMD0:25, CMD1:33, Payload:00:00:00, FCS:15
rpcSendFrame: waiting for SRSP [05]
TimeOut: 2000
13:14:23.657> 
SOC IN  <-- 9 Bytes: SOF:FE, Len:04, CMD0:65, CMD1:33, Payload:00:57:00:00, FCS:00
rpcProcess: processing expected srsp [05]
rpcProcess: writing 4 bytes SRSP to head of the queue
Sem post
13:14:23.657> 
SOC IN  <-- 14 Bytes: SOF:FE, Len:09, CMD0:45, CMD1:B3, Payload:00:00:00:00:00:00:F0:00:6D, FCS:00
rpcProcess: writing 9 bytes AREQ to tail of the que
Sem post
13:14:23.657> 
rpcWaitMqClientMsg: timeout=50
rpcWaitMqClientMsg: waiting on queue 50:5:50000000
Sem timed wait START
13:14:23.657> 
TimeOut: 50
13:14:23.657> 
Sem timed wait - succ
13:14:23.657> 
rpcWaitMqClientMsg: processing MT[4]
zdoProcess: processing CMD0:65, CMD1:33
processSrsp: unsupported message
Start Binding

rpcSendFrame: Blocking on RPC sem
rpcSendFrame: Sending RPC
SOC OUT --> 8 Bytes: SOF:FE, Len:03, CMD0:25, CMD1:33, Payload:00:00:00, FCS:15
rpcSendFrame: waiting for SRSP [05]
TimeOut: 2000
13:14:25.743> 
SOC IN  <-- 9 Bytes: SOF:FE, Len:04, CMD0:65, CMD1:33, Payload:00:57:00:00, FCS:00
rpcProcess: processing expected srsp [05]
rpcProcess: writing 4 bytes SRSP to head of the queue
Sem post
13:14:25.743> 
SOC IN  <-- 14 Bytes: SOF:FE, Len:09, CMD0:45, CMD1:B3, Payload:00:00:00:00:00:00:F0:00:6D, FCS:00
rpcProcess: writing 9 bytes AREQ to tail of the que
Sem post
13:14:25.743> 
rpcWaitMqClientMsg: timeout=50
rpcWaitMqClientMsg: waiting on queue 50:5:50000000
Sem timed wait START
13:14:25.743> 
TimeOut: 50
13:14:25.743> 
Sem timed wait - succ
13:14:25.743> 
rpcWaitMqClientMsg: processing MT[4]
zdoProcess: processing CMD0:65, CMD1:33
processSrsp: unsupported message
rpcWaitMqClientMsg: timeout=1000
rpcWaitMqClientMsg: waiting on queue 1000:11:0
Sem timed wait START
13:14:25.743> 
TimeOut: 1000
13:14:25.743> 
Sem timed wait - succ
13:14:25.743> 
rpcWaitMqClientMsg: processing MT[6]
mtProcess: CMD0:4f, CMD1:80, not handled
Start Binding

rpcSendFrame: Blocking on RPC sem
rpcSendFrame: Sending RPC
SOC OUT --> 8 Bytes: SOF:FE, Len:03, CMD0:25, CMD1:33, Payload:00:00:00, FCS:15
rpcSendFrame: waiting for SRSP [05]
TimeOut: 2000
13:14:25.743> 
SOC IN  <-- 9 Bytes: SOF:FE, Len:04, CMD0:65, CMD1:33, Payload:00:57:00:00, FCS:00
rpcProcess: processing expected srsp [05]
rpcProcess: writing 4 bytes SRSP to head of the queue
Sem post
13:14:25.743> 
SOC IN  <-- 14 Bytes: SOF:FE, Len:09, CMD0:45, CMD1:B3, Payload:00:00:00:00:00:00:F0:00:6D, FCS:00
rpcProcess: writing 9 bytes AREQ to tail of the que
Sem post
13:14:25.743> 
rpcWaitMqClientMsg: timeout=50
rpcWaitMqClientMsg: waiting on queue 50:10:50000000
Sem timed wait START
13:14:25.743> 
TimeOut: 50
13:14:25.743> 
Sem timed wait - succ
13:14:25.743> 
rpcWaitMqClientMsg: processing MT[4]
zdoProcess: processing CMD0:65, CMD1:33
processSrsp: unsupported message
rpcWaitMqClientMsg: timeout=1000
rpcWaitMqClientMsg: waiting on queue 1000:16:0
Sem timed wait START
13:14:29.243> 
TimeOut: 1000
13:14:29.243> 
Sem timed wait - succ
13:14:29.243> 
rpcWaitMqClientMsg: processing MT[9]
zdoProcess: processing CMD0:45, CMD1:b3
zdoProcess: MT_ZDO_MGMT_BIND_RSP
mtZdoMgmtBindRspCb
SrcAddr: 0x0000
Status: 0x00
BindingTableEntries: 0x00
StartIndex: 0x00
BindingTableListCount: 0x00
Start Binding

rpcSendFrame: Blocking on RPC sem
rpcSendFrame: Sending RPC
SOC OUT --> 8 Bytes: SOF:FE, Len:03, CMD0:25, CMD1:33, Payload:00:00:00, FCS:15
rpcSendFrame: waiting for SRSP [05]
TimeOut: 2000
13:14:29.243> 
SOC IN  <-- 9 Bytes: SOF:FE, Len:04, CMD0:65, CMD1:33, Payload:00:57:00:00, FCS:00
rpcProcess: processing expected srsp [05]
rpcProcess: writing 4 bytes SRSP to head of the queue
Sem post
13:14:29.243> 
SOC IN  <-- 14 Bytes: SOF:FE, Len:09, CMD0:45, CMD1:B3, Payload:00:00:00:00:00:00:F0:00:6D, FCS:00
rpcProcess: writing 9 bytes AREQ to tail of the que
Sem post
13:14:29.243> 
rpcWaitMqClientMsg: timeout=50
rpcWaitMqClientMsg: waiting on queue 50:15:50000000
Sem timed wait START
13:14:29.243> 
TimeOut: 50
13:14:29.243> 
Sem timed wait - succ
13:14:29.243> 
rpcWaitMqClientMsg: processing MT[4]
zdoProcess: processing CMD0:65, CMD1:33
processSrsp: unsupported message

-----------------------------------------------
Date: 7/24/2019 - 1:14:34 PM
End log file

0 YiKai Chen over 6 years ago in reply to Georgi Ivanov78

Guru 735685 points

Do you use sniffer to check what happens over the air?

0 Georgi Ivanov78 over 6 years ago in reply to YiKai Chen

Intellectual 320 points

Sorry, I don`t use sniffer.

Now I sow one difference between work firmware and not working firmware. Work firmware make new network while not working framework make a Restored Network. I will attach you a picture of that.

0 YiKai Chen over 6 years ago in reply to Georgi Ivanov78

Guru 735685 points

I think you need to use sniffer to check what happens over the air.

0 Ryan Brown1 over 6 years ago

TI__Guru**** 217687 points

Hello Georgi,

TIDC-ZNP-HOST-SW3 uses Z-Stack HA 1.2.2a and has not been updated for Zigbee 3.0. Therefore the host framework will not be compatible with a Z-Stack 3.0.2 ZNP project, you will need to modify the HA 1.2.2a ZNP instead. (The issue could furthermore involve Zigbee 3.0 BDB commissioning and security measures, such as TCLK where BDB_DEFAULT_TC_REQUIRE_KEY_EXCHANGE set to TRUE, but this most likely makes little difference as compared to the overall incompatibility issue.)

Regards,
Ryan

0 Georgi Ivanov78 over 6 years ago in reply to YiKai Chen

Intellectual 320 points

Hello,

I`m ready with my sniffer, but where can I find the Network key?

Best regards!

0 YiKai Chen over 6 years ago in reply to Georgi Ivanov78

Guru 735685 points

You can join a new device into network and see transport key message on sniffer. The transport key message contains network key.

0 Georgi Ivanov78 over 6 years ago in reply to YiKai Chen

Intellectual 320 points

That`s the problem, I can`t join a new device into network. I can Debug the CC2538, but I can`t find where exactly is the key?

0 YiKai Chen over 6 years ago in reply to Georgi Ivanov78

Guru 735685 points

Do you refer to Ryan's reply (TIDC-ZNP-HOST-SW3 uses Z-Stack HA 1.2.2a and has not been updated for Zigbee 3.0. Therefore the host framework will not be compatible with a Z-Stack 3.0.2 ZNP project, you will need to modify the HA 1.2.2a ZNP instead. ) and use Z-Stack Home 1.2.2a ZNP instead of Z-Stack 3.0.2 ZNP project?

0 Georgi Ivanov78 over 6 years ago in reply to YiKai Chen

Intellectual 320 points

Hello,

now I use Z-Stack Home 1.2.2a ZNP, but still we can`t join new device. We use this settings:

ewarm
FEATURE_SYSTEM_STATS
xPOWER_SAVING
CC2538_USE_ALTERNATE_INTERRUPT_MAP=1
CC2538ZNP
FEATURE_RESET_MACRO
ASSERT_RESET
FAKE_CRC_SHDW
ZDNWKMGR_MIN_TRANSMISSIONS=0
xHAL_SPI=TRUE
ZNP_ALT
MT_UART_DEFAULT_OVERFLOW=FALSE
xHAL_UART_USB
xUSB_SETUP_MAX_NUMBER_OF_INTERFACES=5
xTC_LINKKEY_JOIN

and when we trying to join a new device we can see this messages throw UART:

15:00:01.452> Start Binding
15:00:01.452>
15:00:01.452> rpcSendFrame: Blocking on RPC sem
15:00:01.452> rpcSendFrame: Sending RPC
15:00:01.452> SOC OUT --> 8 Bytes: SOF:FE, Len:03, CMD0:25, CMD1:33, Payload:00:00:00, FCS:15
15:00:01.452> rpcSendFrame: waiting for SRSP [05]
15:00:01.452> TimeOut: 2000
15:00:01.452>
15:00:01.452> SOC IN <-- 9 Bytes: SOF:FE, Len:04, CMD0:65, CMD1:33, Payload:00:57:8B:00, FCS:00
15:00:01.452> rpcProcess: processing expected srsp [05]
15:00:01.452> rpcProcess: writing 4 bytes SRSP to head of the queue
15:00:01.452> Sem post
15:00:01.452>
15:00:01.452> SOC IN <-- 14 Bytes: SOF:FE, Len:09, CMD0:45, CMD1:B3, Payload:00:00:8B:00:00:00:7B:57:0B, FCS:00
15:00:01.452> rpcProcess: writing 9 bytes AREQ to tail of the que
15:00:01.452>
15:00:01.452> rpcWaitMqClientMsg: timeout=50
15:00:01.452> rpcWaitMqClientMsg: waiting on queue 50:596:50000000
15:00:01.452> Sem timed wait START
15:00:01.452>
15:00:01.452> TimeOut: 50
15:00:01.452>
15:00:01.452>
15:00:01.452> rpcWaitMqClientMsg: processing MT[4]
15:00:01.452> zdoProcess: processing CMD0:65, CMD1:33
15:00:01.452> processSrsp: unsupported message
15:00:03.095> SOC IN <-- 20 Bytes: SOF:FE, Len:0F, CMD0:45, CMD1:CA, Payload:B1:CD:E5:F8:27:FE:FF:57:0B:00:00:00:98:00:00, FCS:00
15:00:03.095> rpcProcess: writing 15 bytes AREQ to tail of the que
15:00:03.095> Sem post
15:00:03.095>
15:00:06.452> rpcWaitMqClientMsg: timeout=1000
15:00:06.452> rpcWaitMqClientMsg: waiting on queue 1000:602:0
15:00:06.452> Sem timed wait START
15:00:06.452>
15:00:06.452> TimeOut: 1000
15:00:06.452>
15:00:06.452> Sem timed wait - succ
15:00:06.452>
15:00:06.452> rpcWaitMqClientMsg: processing MT[9]
15:00:06.452> zdoProcess: processing CMD0:45, CMD1:b3
15:00:06.452> zdoProcess: MT_ZDO_MGMT_BIND_RSP
15:00:06.452> mtZdoMgmtBindRspCb
15:00:06.452> MgmtBindRsp Status: FAIL 0x8B

Thanks!

0 YiKai Chen over 6 years ago in reply to Georgi Ivanov78

Guru 735685 points

What device do you try to join current CC2538 ZNP network now?

0 Georgi Ivanov78 over 6 years ago in reply to YiKai Chen

Intellectual 320 points

I`m trying to join our product device with followin profile:

-End point 1

-device ID: 0x0101

-Home automation [0x0104]

-Clusters (Server): 0x000, 0x0003, 0x0006

-Clusters (Client): 0x0003, 0x0006

Also we have and another ZigBee devices from others companies, but we only succeed to join them with ZNP-Host-Framework\bin\cc2538-znp-120-uart-noflow-tclk.hex.

0 YiKai Chen over 6 years ago in reply to Georgi Ivanov78

Guru 735685 points

But you have disable TC LINK KEY by “xTC_LINKKEY_JOIN”. TC link key is mandatory in Zigbee HA profile so your coordinator doesn’t form Zigbee HA network.

0 Georgi Ivanov78 over 6 years ago in reply to YiKai Chen

Intellectual 320 points

Okay, now my settings are:

And we still cannot join the devices.

Any other idea why?

Thanks!

0 YiKai Chen over 6 years ago in reply to Georgi Ivanov78

Guru 735685 points

I suggest you to run Z-Stack Home 1.2.2a original SampleLight example on your CC2538 to act as coordinator to form network and make sure other HA device can join it first. While doing this, you can turn on your sniffer to get complete joining process.

0 Ryan Brown1 over 6 years ago in reply to Georgi Ivanov78

TI__Guru**** 217687 points

I do not see a cc2538-znp-120-uart-noflow-tclk.hex file from https://git.ti.com/znp-host-framework. I also noticed that the README actually states that the binary images were generated from Z-Stack HA 1.2.0, as TI does not maintain this version in Z-STACK-ARCHIVE it may not be possible for you to re-generate the ZNP images meant for ZNP-Host-Framework. To get this working you will have to further set up your sniffer software and debug.

Regards,
Ryan

0 Georgi Ivanov78 over 6 years ago in reply to Ryan Brown1

Intellectual 320 points

This is bad news.

We need a fast solution for a ZigBee project who working like a ZNP-Host-Framework\bin\cc2538-znp-120-uart-noflow-tclk.hex. I was thinking that is ready example who we can compile with few options for the project. It seems we have to spend some time to better understand the ZigBee stack and trying to compile similar firmware like a ZNP-Host-Framework\bin\cc2538-znp-120-uart-noflow-tclk.hex.

Thanks!

Zigbee & Thread

Zigbee & Thread forum

Compiler/CC2538: How to compile CC2538 UART?