ZDO_STARTUP_FROM_APP_SRSP (0x6540) Status: FAIL (0x1)

sivasankar sekar

Intellectual 745 points

Other Parts Discussed in Thread: CC2531, CC2530, CC2531EMK

Hi Friends.

<TX>03:52:10.27 COM9 ZDO_STARTUP_FROM_APP (0x2540)
Mode: 0x00

<RX>03:52:10.57 COM9 ZDO_STARTUP_FROM_APP_SRSP (0x6540)
Status: FAIL (0x1)

<RX>03:52:10.58 COM9 ZDO_STATE_CHANGE_IND (0x45C0)
State: 8 (0x8)

<RX>03:52:11.09 COM9 ZDO_STATE_CHANGE_IND (0x45C0)
State: 8 (0x8)

<RX>03:52:11.6 COM9 ZDO_STATE_CHANGE_IND (0x45C0)
State: 8 (0x8)

<RX>03:52:12.62 COM9 ZDO_STATE_CHANGE_IND (0x45C0)
State: 9 (0x9)

<RX>03:52:12.62 COM9 ZB_START_CONFIRM (0x4680)
Status: SUCCESS (0x0)

My Q:

How to avoid the Fail error?

over 11 years ago

0 TopCat over 11 years ago

TI__Genius 9180 points

I think you have miss understood the response code for ZDO_STARTUP_FROM_APP:

0x00 – Restored network state
0x01 – New network state
0x02 – Leave and not Started

Regards, TC.

0 sivasankar sekar over 11 years ago in reply to TopCat

Intellectual 745 points

Hi TopCat,

I copy the text message what i have in my Z Tool 2.0.

<RX>10:34:56.12 COM7 ZB_WRITE_CONFIGURATION_RSP (0x6605)
    Status: SUCCESS (0x0)

<TX>10:34:56.12 COM7 ZB_WRITE_CONFIGURATION (0x2605)
    ConfigId: 0x87
    Len: 0x01
    Value: . (0x00)

<TX>10:35:11.29 COM7 ZB_WRITE_CONFIGURATION (0x2605)
    ConfigId: 0x84
    Len: 0x04
    Value: .... (0x00, 0x00, 0x08, 0x00)

<RX>10:35:11.29 COM7 ZB_WRITE_CONFIGURATION_RSP (0x6605)
    Status: SUCCESS (0x0)

<TX>10:35:27.77 COM7 ZB_WRITE_CONFIGURATION (0x2605)
    ConfigId: 0x83
    Len: 0x02
    Value: .. (0xFF, 0xFF)

<RX>10:35:27.77 COM7 ZB_WRITE_CONFIGURATION_RSP (0x6605)
    Status: SUCCESS (0x0)

<TX>10:35:42.15 COM7 ZB_WRITE_CONFIGURATION (0x2605)
    ConfigId: 0x8F
    Len: 0x01
    Value: . (0x01)

<RX>10:35:42.16 COM7 ZB_WRITE_CONFIGURATION_RSP (0x6605)
    Status: SUCCESS (0x0)

<TX>10:36:04.37 COM7 ZB_APP_REGISTER_REQUEST (0x260A)
    AppEndPoint: 0x01
    AppProfileID: 0x0001
    DeviceId: 0x0000
    DeviceVersion: 0x00
    Unused: 0x00
    InputCommandsNum: 0x01
    InputCommandsList: 0x0001
    OutputCommandsNum: 0x01
    OutputCommandsList: 0x0001

<RX>10:36:04.38 COM7 ZB_APP_REGISTER_RSP (0x660A)
    Status: afStatus_SUCCESS (0x0)

<TX>10:38:00.27 COM7 ZB_START_REQUEST (0x2600)

<RX>10:38:00.82 COM7 ZB_START_REQUEST_RSP (0x6600)

<RX>10:38:00.82 COM7 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 8 (0x8)

<RX>10:38:01.85 COM7 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 9 (0x9)

<RX>10:38:01.85 COM7 ZB_START_CONFIRM (0x4680)
    Status: SUCCESS (0x0)

<TX>10:38:18.37 COM7 ZDO_STARTUP_FROM_APP (0x2540)
Mode: 0x00

<RX>10:38:18.68 COM7 ZDO_STARTUP_FROM_APP_SRSP (0x6540)

    Status: FAIL (0x1)

<RX>10:38:18.68 COM7 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 8 (0x8)

<RX>10:38:19.7 COM7 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 9 (0x9)

<RX>10:38:19.71 COM7 ZB_START_CONFIRM (0x4680)
    Status: SUCCESS (0x0)

Why It sending FAIL (0x1)?

<TX>10:38:30.32 COM7 ZDO_ACTIVE_EP_REQ (0x2505)
    DstAddr: 0x0000
    NWKAddrOfInterest: 0x0000

<RX>10:38:30.34 COM7 ZDO_ACTIVE_EP_REQ_SRSP (0x6505)
    Status: afStatus_SUCCESS (0x0)

<RX>10:38:30.34 COM7 ZDO_ACTIVE_EP_RSP (0x4585)
    SrcAddr: 0x0000
    Status: ZDP_SUCCESS (0x0)
    NwkAddr: 0x0000
    ActiveEPCount: 0x01
    ActiveEPList: . (0x01)

<TX>10:39:17.34 COM7 UTIL_GET_DEVICE_INFO (0x2700)

<RX>10:39:17.34 COM7 UTIL_GET_DEVICE_INFO_RESPONSE (0x6700)
    Status: SUCCESS (0x0)
    IEEEAddr: 0x00124B0002F265FE
    ShortAddress: 0x0000
    DeviceType: COORDINATOR, ROUTER, END_DEVICE (0x7)
    DeviceState: DEV_ZB_COORD (0x9)
    NumAssocDevices: 0x00
    AssocDevicesList
My Q:

We doesn't get the ZED NWK.ADDRESS in AssocDevicesList also?

What are the steps i need to use to add the ZED to AssocDevicesList in ZC?

0 Hector_r over 11 years ago in reply to sivasankar sekar

TI__Genius 12415 points

Hi,

As TopCat already said 0x01 does not mean FAIL for ZDO_STARTUP_FROM_APP_SRSP, Ignore the FAIL message and take a look at the ZNP Interface Specification document to look at the correct meaning.

The reason why you don't see the ZED nwk address in the AssocDevicesList is because your ZED is not connected to the ZC. Your ZC seems to be set up correctly, my guess is that your ZED is not set up the right way and that is why it is not connecting to your ZC. As soon as ZED connects to the ZC, the ZED will be added to the AssocDevicesList automatically.

0 sivasankar sekar over 11 years ago in reply to Hector_r

Intellectual 745 points

Hi Friend,

Before i have ZED Nwk.Address list in AssocDevicesList automatically in Z Tool.But after i reprogram the Packet Sniffer once again as ZNP.Then my ZED Nwk.Address doesn't come to in AssocDevicesLisc in my ZC.

Give me any idea whats happening and how to overcome the problem?

0 YiKai Chen over 11 years ago in reply to sivasankar sekar

Guru 735695 points

If you reprogram the Packet Sniffer once again as ZNP, all the network info on the dongle will be erased.

0 sivasankar sekar over 11 years ago in reply to YiKai Chen

Intellectual 745 points

Hi YiKai Chen,

Yes friend,but i tried the same configuration setting from first in ZNP and same in my ZED also.

Previously it show the NWK.Address list of ZED in ZNP Association list,but i tried the same settings know but i doesn't got the NWK.Address now.

My Q:

1.What i need to do to get the NWK.Address?

I copy the text message what i have in my Z Tool 2.0.

<TX>10:38:18.37 COM7 ZDO_STARTUP_FROM_APP (0x2540)
Mode: 0x00

<RX>10:38:18.68 COM7 ZDO_STARTUP_FROM_APP_SRSP (0x6540)

<TX>10:38:30.32 COM7 ZDO_ACTIVE_EP_REQ (0x2505)

    DstAddr: 0x0000
    NWKAddrOfInterest: 0x0000

<RX>10:38:30.34 COM7 ZDO_ACTIVE_EP_REQ_SRSP (0x6505)
    Status: afStatus_SUCCESS (0x0)

<RX>10:38:30.34 COM7 ZDO_ACTIVE_EP_RSP (0x4585)
    SrcAddr: 0x0000
    Status: ZDP_SUCCESS (0x0)
    NwkAddr: 0x0000
    ActiveEPCount: 0x01
    ActiveEPList: . (0x01)

0 YiKai Chen over 11 years ago in reply to sivasankar sekar

Guru 735695 points

I only see you init your ZC. How about ZED? You need to init ZED and make it join ZC. After that, you can see it on the association list.

0 sivasankar sekar over 11 years ago in reply to YiKai Chen

Intellectual 745 points

Hi YiKai Chen,

In my project we are using Packet Sniffer as ZNP COORDINATOR and i am using my own board as normal ZED and i load my GenericApp program in my board(not as ZNP END DEVICE program).So i configure only ZNP COORDINATOR.

My Q:

1.Are u get big picture about my hard wares?

2.If yes see our configuration?

1.What i need to do to get the NWK.Address?

I copy the text message what i have in my Z Tool 2.0.

<TX>10:38:18.37 COM7 ZDO_STARTUP_FROM_APP (0x2540)
Mode: 0x00

<RX>10:38:18.68 COM7 ZDO_STARTUP_FROM_APP_SRSP (0x6540)

<TX>10:38:30.32 COM7 ZDO_ACTIVE_EP_REQ (0x2505)

0 YiKai Chen over 11 years ago in reply to sivasankar sekar

Guru 735695 points

Yes, I know your configuration and HW settings. Since you think you have ZC and ZED initialized, could you use packet sniffer to check if ZED joins your ZC correctly? I suppose it doesn't otherwise you will see it on your association list.

0 sivasankar sekar over 11 years ago in reply to YiKai Chen

Intellectual 745 points

Hi YiKai Chen,

We have one packet sniffer so we use as ZNP COORDINATOR and my own board as ZNP END DEVICE.

So we cant check using one more packet sniffer.Actually before it showing the ZED NWK.Address in the Association List but after reprogram the sniffer and tried the same settings but the ZED NWK.Address doesn't come into the Association list.

My Q:

1.Can u give some idea how to overcome the problem?

0 YiKai Chen over 11 years ago in reply to sivasankar sekar

Guru 735695 points

You can try to send ZDO_MGMT_PERMIT_JOIN_REQUEST with duration set to 0xFF which means permit join to all devices. Then, see if your ZED joins to ZC.

0 Hector_r over 11 years ago in reply to sivasankar sekar

TI__Genius 12415 points

Hi,

From what I understand, in your setup you have a USB dongle flashed with ZNP and you are using that as a coordinator, and a board flashed as a ZED. What is not clear to me is if you have a separate USB dongle flashed with the sniffer firmware so you can check the packets sent over the air. If you do, then you should check if your ZED is sending messages over the air and see what is the reason why the ZED is not connecting to ZC. Also, make sure you have the same channel enabled in your ZED and your ZC.

0 sivasankar sekar over 11 years ago in reply to YiKai Chen

Intellectual 745 points

Hi YiKai Chen,

<RX>05:28:30 COM3 ZB_WRITE_CONFIGURATION_RSP (0x6605)

Status: SUCCESS (0x0)

<TX>05:28:30 COM3 ZB_WRITE_CONFIGURATION (0x2605)

ConfigId: 0x87

Len: 0x01

Value: . (0x00)

<TX>05:28:43.42 COM3 ZB_WRITE_CONFIGURATION (0x2605)

ConfigId: 0x84

Len: 0x04

Value: .... (0x00, 0x00, 0x08, 0x00)

<RX>05:28:43.43 COM3 ZB_WRITE_CONFIGURATION_RSP (0x6605)

Status: SUCCESS (0x0)

<TX>05:29:03.46 COM3 ZB_WRITE_CONFIGURATION (0x2605)

ConfigId: 0x83

Len: 0x02

Value: .. (0xFF, 0xFF)

<RX>05:29:03.46 COM3 ZB_WRITE_CONFIGURATION_RSP (0x6605)

Status: SUCCESS (0x0)

<TX>05:29:18.59 COM3 ZB_WRITE_CONFIGURATION (0x2605)

ConfigId: 0x8F

Len: 0x01

Value: . (0x01)

<RX>05:29:18.6 COM3 ZB_WRITE_CONFIGURATION_RSP (0x6605)

Status: SUCCESS (0x0)

<TX>05:29:30.03 COM3 ZB_APP_REGISTER_REQUEST (0x260A)

AppEndPoint: 0x01

AppProfileID: 0x0001

DeviceId: 0x0000

DeviceVersion: 0x00

Unused: 0x00

InputCommandsNum: 0x01

InputCommandsList: 0x0001

OutputCommandsNum: 0x01

OutputCommandsList: 0x0001

<RX>05:29:30.03 COM3 ZB_APP_REGISTER_RSP (0x660A)

Status: afStatus_SUCCESS (0x0)

<TX>05:29:35.07 COM3 ZB_START_REQUEST (0x2600)

<RX>05:29:35.59 COM3 ZB_START_REQUEST_RSP (0x6600)

<RX>05:29:35.6 COM3 ZDO_STATE_CHANGE_IND (0x45C0)

State: 8 (0x8)

<RX>05:29:36.11 COM3 ZDO_STATE_CHANGE_IND (0x45C0)

State: 8 (0x8)

<RX>05:29:36.62 COM3 ZDO_STATE_CHANGE_IND (0x45C0)

State: 8 (0x8)

<RX>05:29:37.13 COM3 ZDO_STATE_CHANGE_IND (0x45C0)

State: 8 (0x8)

<RX>05:29:38.15 COM3 ZDO_STATE_CHANGE_IND (0x45C0)

State: 9 (0x9)

<RX>05:29:38.16 COM3 ZB_START_CONFIRM (0x4680)

Status: SUCCESS (0x0)

<TX>05:29:47.88 COM3 ZDO_STARTUP_FROM_APP (0x2540)

Mode: 0x00

<RX>05:29:48.18 COM3 ZDO_STARTUP_FROM_APP_SRSP (0x6540)

Status: FAIL (0x1)

<RX>05:29:48.18 COM3 ZDO_STATE_CHANGE_IND (0x45C0)

State: 8 (0x8)

<RX>05:29:49.21 COM3 ZDO_STATE_CHANGE_IND (0x45C0)

State: 9 (0x9)

<RX>05:29:49.21 COM3 ZB_START_CONFIRM (0x4680)

Status: SUCCESS (0x0)

<TX>05:30:34.72 COM3 ZDO_NWK_DISCOVERY_REQ (0x2526)

ScanChannels: ALL_CHANNELS (0x7FFF800)

ScanDuration: 0x05

<RX>05:30:34.73 COM3 ZDO_NWK_DISCOVERY_REQ_SRSP (0x6526)

Status: ZNWK_INVALID_REQUEST (0xC2)

<TX>05:31:00.94 COM3 ZDO_NWK_DISCOVERY_REQ (0x2526)

ScanChannels: ALL_CHANNELS (0x7FFF800)

ScanDuration: 0x05

<RX>05:31:00.95 COM3 ZDO_NWK_DISCOVERY_REQ_SRSP (0x6526)

Status: ZNWK_INVALID_REQUEST (0xC2)

<TX>05:31:26.51 COM3 ZDO_MGMT_PERMIT_JOIN_REQUEST (0x2536)

AddrMode: 0x00 (ADDRESS_NOT_PRESENT) (0x0)

DstAddr: 0x0000

Duration: 0x03

TCSignificance: 0x00

<RX>05:31:26.51 COM3 ZDO_MGMT_PERMIT_JOIN_REQ_SRSP (0x6536)

Status: SUCCESS (0x0)

<TX>05:32:12.48 COM3 ZDO_ACTIVE_EP_REQ (0x2505)

DstAddr: 0x0000

NWKAddrOfInterest: 0x0000

<RX>05:32:12.49 COM3 ZDO_ACTIVE_EP_REQ_SRSP (0x6505)

Status: afStatus_SUCCESS (0x0)

<RX>05:32:12.49 COM3 ZDO_ACTIVE_EP_RSP (0x4585)

SrcAddr: 0x0000

Status: ZDP_SUCCESS (0x0)

NwkAddr: 0x0000

ActiveEPCount: 0x01

ActiveEPList: . (0x01)

<TX>05:32:22.04 COM3 UTIL_GET_DEVICE_INFO (0x2700)

<RX>05:32:22.04 COM3 UTIL_GET_DEVICE_INFO_RESPONSE (0x6700)

Status: SUCCESS (0x0)

IEEEAddr: 0x00124B0002F265FE

ShortAddress: 0x0000

DeviceType: COORDINATOR, ROUTER, END_DEVICE (0x7)

DeviceState: DEV_ZB_COORD (0x9)

NumAssocDevices: 0x00

AssocDevicesList (I doesn't get the ZED address in that List?)

<TX>05:33:15.17 COM3 ZDO_MSG_CB_REGISTER (0x253E)

ClusterID: 0x0000

<RX>05:33:15.17 COM3 ZDO_MSG_CB_REGISTER_RESPONSE (0x653E)

Status: SUCCESS (0x0)

<TX>05:33:24.15 COM3 UTIL_GET_DEVICE_INFO (0x2700)

<RX>05:33:24.16 COM3 UTIL_GET_DEVICE_INFO_RESPONSE (0x6700)

Status: SUCCESS (0x0)

IEEEAddr: 0x00124B0002F265FE

ShortAddress: 0x0000

DeviceType: COORDINATOR, ROUTER, END_DEVICE (0x7)

DeviceState: DEV_ZB_COORD (0x9)

NumAssocDevices: 0x00

AssocDevicesList

My Q:

1.How to I get the ZED NWK.Address ?

0 YiKai Chen over 11 years ago in reply to sivasankar sekar

Guru 735695 points

When you use ZDO_MGMT_PERMIT_JOIN_REQUEST, you should choose AddrMode: 0x03(ADDRESS_16_BIT). By the way, I suggest you to buy another CC2531 usb dongle for packet sniffer usage. Otherwise, you don't know what happens over the air.

0 sivasankar sekar over 11 years ago in reply to YiKai Chen

Intellectual 745 points

Hi YiKai Chen,

I will get the same result now also I doesn't get the NWK.Address in Association List.

My Q:

1.And my company they don't by the another CC2531 usb dongle for packet sniffer so can you give me any other ideas?

0 YiKai Chen over 11 years ago in reply to sivasankar sekar

Guru 735695 points

If you have two customized CC2530 boards, you can make one act as ZC and another as ZED. Use the CC2531 dongle as sniffer to check your issue.

0 sivasankar sekar over 11 years ago in reply to YiKai Chen

Intellectual 745 points

Hi YiKai Chen,

I checked using 2 boards one as ZC and another one as ZED. Now i use the packet sniffer and two boards are sending unicast data and my ZED NWK.Address also in my ZC Association List.

But I reprogram the Packet Sniffer as ZNP and my customized board as ZED and i am using Z Tool in PC now my ZED NWK.Address not in my ZC Association List.

Can u give some idea how to solve the issue?

0 TheDarkSide over 11 years ago in reply to sivasankar sekar

TI__Genius 16570 points

Hi,

addrMode field in ZDO_MGMT_PERMIT_JOIN_REQ needs to be set to 0x2 for the address to be 16 bit.

Anyhow, please make sure when your dongle is configured as ZNP (and not as a packet sniffer), the MAC channel is the same as the one where the end device is and also there is no PANID mask.

We are happy to help, but basic protocol debugging requires a sniffer to see OTA traffic. We can't proceed blindly.

If you are limited, then what i suggest as a workaround is that you start a step by step approach and start first the dongle as a coordinator and see the OTA traffic programming the other board as a packet sniffer.

If one of your board has a USB interface and mounts the CC2531, you can try to program that board with packet sniffer firmware (the firmware can be found in C:\Program Files (x86)\Texas Instruments\SmartRF Tools\Packet Sniffer\bin\general\firmware\sniffer_fw_cc2531.hex) of your TI Packet sniffer install.

Or if your board has a CC2530 mounted and UART interface to the PC available, you can use the sniffer_fw_cc2530.hex.

Sorry, we can't direct you much without a sniffer and I strongly advise you have this always available. The CC2531EMK costs only $49 so it is an investment which really pays off.

http://www.ti.com/tool/cc2531emk?keyMatch=CC2531emk&tisearch=Search-EN

Thanks,

TheDarkSide

Zigbee & Thread

Zigbee & Thread forum

ZDO_STARTUP_FROM_APP_SRSP (0x6540) Status: FAIL (0x1)