Zigbee debugging

RE: Zigbee debugging

Dimitri G — Fri, 03 May 2019 10:54:08 GMT

It seems we have solved the problem. Our systick timer was using TIMER_1, which is also used by the radio driver.

I see the APS packets coming and Alexa recognizes our device.

Thanks for your help anyway.

RE: Zigbee debugging

Dimitri G — Thu, 02 May 2019 11:15:04 GMT

Hello

Thanks for the suggestion, but I'm afraid it doesn't work.

I have erased the chip with nrfjprog and programmed my project.
My project and 'eddystone' both running on same zigbee channel (25)

The 'eddystone' connects with Alexa immediately again.
My project doesn't connect with Alexa.

The difference I see in the packet sniffer is that, for the eddystone project, a APS packet is send after the successful association. While in my project, this packet is never send. The source of that packet is 0x0000 (this packet is probably coming from Alexa) - The destination is 0x0f2c (probably the address of my development board ?)

It might be that Alexa rejects the connection from my project for some reason ?

edit:

Another difference is that in my project I always get 4x an association response. While in the eddystone example, there is only 1 association response:

RE: Zigbee debugging

Edvin — Thu, 02 May 2019 09:03:38 GMT

Hello,

I have forwarded your logs for decryption. Maybe they can give some more hints on what's going on.

You have the same network settings in your application as it was in the unmodified eddystone example? Same zigbee channel?

It may be if you are running the examples on the same board that your device thinks it is already commisioned, if the flash is not erased properly. Can you make sure that you erase all the flash before you try to run your custom example? You can use "nrfjprog -e" if you have the Nordic's command line tools installed. Then try to flash your application.

If the board thinks it is commissioned, and tries to join the network as another device, Alexa may reject it.

Can you try to erase the chip, run your application, and let me know if that makes any difference?

Best regards,

Edvin

RE: Zigbee debugging

Dimitri G — Thu, 02 May 2019 07:29:28 GMT

Further investigation from my part reveils that in my project, the call to zboss_signal_handler(zb_uint8_t param) for signal ZB_BDB_SIGNAL_DEVICE_REBOOT, the param argument is 0x0B. The status becomes RET_ERROR.

While in the example project, the param argument is 0x0A and the status becomes RET_OK.

Maybe this information helps to give some support from the Nordic engineers ?

Thanks

The screenshot below shows my current call stack, cpu registers and coe dissambly

RE: Zigbee debugging

Dimitri G — Tue, 30 Apr 2019 13:32:40 GMT

Could it be possible that the commissioning is failing ? This could explain why I don't see the APS packets in my project, while I do see some APS packets in the "eddystone" example.

But how can I figure out what is going wrong now ?

RE: Zigbee debugging

Dimitri G — Tue, 30 Apr 2019 09:40:55 GMT

This is a Zboss log of a successful connection with the eddystone to Alexa:

<info> zboss: 0B 00 00 00 FF FF FF FF|........

<info> app: Failed to join network. Status: -1

<info> zboss: 05 00 00 00 DE AD 1E 02|........

<info> zboss: 49 08 3C 00 AA 01 A0 01|I.<.....

<info> zboss: 01 00 00 00 00 00 00 00|........

<info> zboss: 00 00 00 00 00 00 00 00|........

<info> zboss: 00 00 00 00 DE AD 12 02|........

<info> zboss: 59 0A 3D 00 2B 08 73 05|Y.=.+.s.

<info> zboss: 00 00 00 00 01 00 00 00|........

<info> zboss: DE AD 16 02 59 0A 3E 00|....Y.>.

<info> zboss: 45 01 1D 01 5C D3 00 00|E...\...

<info> zboss: 19 00 00 00 00 00 00 00|........

<info> zboss: DE AD 1A 02 79 0A 3F 00|....y.?.

<info> zboss: 2B 08 2E 07 00 00 00 00|+.......

<info> zboss: 19 21 00 00 19 00 00 00|.!......

<info> zboss: 00 00 00 00 DE AD 12 02|........

<info> zboss: 79 0A 40 00 2B 08 2F 07|y.@.+./.

<info> zboss: DA DD B1 0B 1D 53 CF 95|.....S..

<info> zboss: DE AD 1A 02 80 0A 43 00|......C.

<info> zboss: 44 01 49 00 00 00 00 00|D.I.....

<info> zboss: 00 00 00 00 00 00 00 00|........

<info> zboss: 00 00 00 00 DE AD 0E 02|........

<info> zboss: 7A 0A 41 00 7A 6E 08 03|z.A.zn..

<info> zboss: 05 00 00 00 DE AD 0E 02|........

<info> zboss: 7A 0A 42 00 7A 6E 08 03|z.B.zn..

<info> zboss: 05 00 00 00 DE AD 16 02|........

<info> zboss: AC 0A 45 00 2B 08 FA 03|..E.+...

<info> zboss: 0D 00 00 00 00 00 00 00|........

<info> zboss: 05 00 00 00 DE AD 0E 02|........

<info> zboss: A4 0A 44 00 7A 6E 75 02|..D.znu.

<info> app: Joined network successfully

<info> zboss: 02 00 00 00 DE AD 0E 02|........

<info> zboss: 5C 0B 46 00 2F 08 6B 01|\.F./.k.

<info> zboss: 02 00 00 00 DE AD 0E 02|........

<info> zboss: 12 13 4D 00 2F 08 8C 01|..M./...

<info> zboss: 0A 00 00 00 DE AD 0E 02|........

<info> zboss: 41 0D 47 00 7A 6E 08 03|A.G.zn..

<info> zboss: 03 00 00 00 DE AD 0E 02|........

<info> zboss: 52 0D 48 00 7A 6E 08 03|R.H.zn..

<info> zboss: 03 00 00 00 DE AD 0E 02|........

<info> zboss: 67 0D 49 00 7A 6E 08 03|g.I.zn..

<info> zboss: 03 00 00 00 DE AD 0E 02|........

<info> zboss: 7A 0D 4A 00 7A 6E 08 03|z.J.zn..

<info> zboss: 03 00 00 00 DE AD 0E 02|........

<info> zboss: 3F 0E 4B 00 7A 6E 08 03|?.K.zn..

<info> zboss: 03 00 00 00 DE AD 0E 02|........

<info> zboss: A8 12 4C 00 7A 6E 08 03|..L.zn..

RE: Zigbee debugging

Dimitri G — Tue, 30 Apr 2019 09:35:19 GMT

devzone.nordicsemi.com/.../sniffer_5F00_ourproject_5F00_zigbee_5F00_alexa_5F00_fail.pcapng

Packet sniffing while connecting to Alexa over zigbee - no connection happened

devzone.nordicsemi.com/.../sniffer_5F00_eddystone_5F00_zigbee_5F00_alexa_5F00_success.pcapng

This is a packet sniffing with the eddystone example - connection successfull.

The MAC of our nRF52840 DK is 40 02 2B A8 6A 0E 01 0B

The MAC of Alexa is 5C:41:5A:E4:F0:D7

RE: Zigbee debugging

Dimitri G — Tue, 30 Apr 2019 09:22:19 GMT

Hello

We are still unable to connect with zigbee using "nRF5_SDK_for_Thread_and_Zigbee_3.0.0". However, with the "eddystone" example (multiprotocol / zigbee / ble), we see that the NRF52840 DK almost immediately a zigbee-connection can be made with our Amazon Alexa.

When we use the SDK for our own project, also BLE+zigbee, the BLE stack is up and running and advertising. The zigbee stack also is up and running, but we always get the message "Failed to join network. Status: -1". Our own project is derived from the "eddystone" example.

This is wat we have tried:

- We stripped the eddystone example from cryptography, pwm and the eddystone functionality itself. What remains is the BLE stack init, scheduler init and zigbee init. Zigbee connection still works.

- Our project uses exact the same sdk_config.h file

- Our project uses exact the same "system_nrf52840.c" file. We also use the "multiprotocol_802451_config.h" file.

- Our Zigbee initialisation is exact the same as in the eddystone example. The stack runs because the "zboss_signal_handler" is periodically called.

- Beacon requests are send too. The "zb_set_network_router_role" is set to ZB_TRANSCEIVER_ALL_CHANNELS_MASK.

- I have enable the Zboss logging. This is what we get out from it. I hope you can help us in some way. If you need some other info / code fragments,... , please ask.

<info> app: Stack init done

<info> app: StartAdvPublic

<info> zboss: DE AD 0E 02 00 00 00 00|........

<info> zboss: 7A 00 00 0F 00 F8 FF 07|z.......

<info> zboss: DE AD 0A 02 00 00 01 00|........

<info> zboss: 47 01 6F 00 DE AD 0A 02|G.o.....

<info> zboss: 00 00 02 00 47 01 99 00|....G...

<info> zboss: DE AD 0A 02 00 00 03 00|........

<info> zboss: 47 01 F1 00 DE AD 0A 02|G.......

<info> zboss: 00 00 04 00 48 01 36 00|....H.6.

<info> zboss: DE AD 0A 02 00 00 05 00|........

<info> zboss: B9 08 83 00 DE AD 0A 02|........

<info> zboss: 00 00 06 00 B9 08 86 00|........

<info> zboss: DE AD 0A 02 00 00 07 00|........

<info> zboss: B9 08 8A 00 DE AD 0A 02|........

<info> zboss: 00 00 08 00 B9 08 8D 00|........

<info> zboss: DE AD 0A 02 00 00 09 00|........

<info> zboss: 47 01 94 00 DE AD 0A 02|G.......

<info> zboss: 00 00 0A 00 69 00 5C 00|....i.\.

<info> zboss: DE AD 16 02 00 00 0B 00|........

<info> zboss: 69 00 77 00 0C 00 00 00|i.w.....

<info> zboss: 8A 02 00 00 C3 00 00 00|........

<info> zboss: DE AD 0A 02 00 00 0C 00|........

<info> zboss: 69 00 79 00 DE AD 0E 02|i.y.....

<info> zboss: 00 00 0D 00 2B 08 96 00|....+...

<info> zboss: 01 00 00 00 DE AD 0A 02|........

<info> zboss: 00 00 0E 00 90 0C DD 00|........

<info> zboss: DE AD 16 02 00 00 0F 00|........

<info> zboss: 90 0C A8 00 00 80 00 00|........

<info> zboss: 00 00 00 00 08 00 00 00|........

<info> zboss: DE AD 16 02 00 00 10 00|........

<info> zboss: 90 0C A8 00 01 80 00 00|........

<info> zboss: 01 00 00 00 08 00 00 00|........

<info> zboss: DE AD 16 02 00 00 11 00|........

<info> zboss: 90 0C A8 00 02 80 00 00|........

<info> zboss: 02 00 00 00 08 00 00 00|........

<info> zboss: DE AD 16 02 00 00 12 00|........

<info> zboss: 90 0C A8 00 03 80 00 00|........

<info> zboss: 03 00 00 00 08 00 00 00|........

<info> zboss: DE AD 16 02 00 00 13 00|........

<info> zboss: 90 0C A8 00 04 80 00 00|........

<info> zboss: 04 00 00 00 08 00 00 00|........

<info> zboss: DE AD 16 02 00 00 14 00|........

<info> zboss: 90 0C A8 00 05 80 00 00|........

<info> zboss: 05 00 00 00 08 00 00 00|........

<info> zboss: DE AD 16 02 00 00 15 00|........

<info> zboss: 90 0C A8 00 06 80 00 00|........

<info> zboss: 06 00 00 00 08 00 00 00|........

<info> zboss: DE AD 16 02 00 00 16 00|........

<info> zboss: 90 0C A8 00 1F 80 00 00|........

<info> zboss: 07 00 00 00 08 00 00 00|........

<info> zboss: DE AD 16 02 00 00 17 00|........

<info> zboss: 90 0C B6 00 00 00 00 00|........

<info> zboss: 00 00 00 00 09 00 00 00|........

<info> zboss: DE AD 16 02 00 00 18 00|........

<info> zboss: 90 0C B6 00 01 00 00 00|........

<info> zboss: 01 00 00 00 09 00 00 00|........

<info> zboss: DE AD 16 02 00 00 19 00|........

<info> zboss: 90 0C B6 00 02 00 00 00|........

<info> zboss: 02 00 00 00 09 00 00 00|........

<info> zboss: DE AD 16 02 00 00 1A 00|........

<info> zboss: 90 0C B6 00 03 00 00 00|........

<info> zboss: 03 00 00 00 09 00 00 00|........

<info> zboss: DE AD 16 02 00 00 1B 00|........

▫[1;31mLogs dropped (162)▫[0m

<info> zboss: BC 08 22 01 DE AD 0A 02|..".....

<info> zboss: 41 00 66 00 B9 08 23 04|A.f...#.

<info> zboss: DE AD 0A 02 41 00 67 00|....A.g.

RE: Zigbee debugging

mathiasvanbelle — Thu, 25 Apr 2019 12:00:37 GMT

devzone.nordicsemi.com/.../capture-zigbee.pcapng

Thx for looking. I hope you find something.

RE: Zigbee debugging

Edvin — Thu, 25 Apr 2019 08:04:06 GMT

Hello.

Can you send the sniffer trace? The .pcapng file that the screenshot is from?

RE: Zigbee debugging

mathiasvanbelle — Wed, 24 Apr 2019 11:14:04 GMT

Hello,

Ok, we will start to update the SDK.

We looked at the multiprotocol examples with SKD 2.0.0 and they worked.
But when i port the code to my my project only the BLE part works.

mmmm strange, if i init the clock before i init S140 stack in don't get zigbee messages.
If i don't init the clock i get my beacon request. Are there other thing i need to be aware of?

I want to connect to my echo plus (amazon alexa). But i don't get "Joined network successfully"
Any ideas on this. I see communication with my sniffer. See image below.

Thx

RE: Zigbee debugging

Edvin — Tue, 23 Apr 2019 14:41:23 GMT

Hello Mathias,

I suggest that you port to the nRF5_SDK_for_Thread_and_Zigbee_3.0.0, which was recently released. In addition to bugfixes, there are more examples, and more documentation in this SDK.

If you want to look at how to set up the Zigbee + BLE project, I suggest that you look at one of the examples from the SDK\examples\multiprotocol\ble_zigbee folder. Perharps the ble_zigbee_light_bulb_eddystone or the ble_zigbee_light_switch_nus is a good starting point from your application?

Best regards,

Edvin