Zigbee debugging

[mathiasvanbelle]

Hi,

I'm using the NRF52840 with the "nRF5_SDK_for_Thread_and_Zigbee_2.0.0".

I tested the zigbee light_bulb example and zigbee light_bulb + ble. It works fine so my next step was to do combination with my own ble service in a existing project.
In my new project the ble part works fine. The zigbee (still the light bulb example) part does not work at the moment. When i sniff, i don't see the Beacon request frames.

When i look at the uart logging i still see "Production config is not present or invalid" and "Failed to join network. Status: -1".

extra info:
i used sd_softdevice_vector_table_base_set((uint32_t) vector_table) to change the vector table to RAM. For the Zigbee part i registered the following interrupts: 

SysInt_RegisterIsr(TIMER3_IRQn, (ISR_CALLBACK) TIMER3_IRQHandler);
SysInt_RegisterIsr(SWI3_EGU3_IRQn, (ISR_CALLBACK) SWI3_IRQHandler);
SysInt_RegisterIsr(RTC2_IRQn, (ISR_CALLBACK) RTC2_IRQHandler);

this is needed if i look at the documentation. 

My goal is to let the zigbee and the BLE part to work together in my code. Any tips how to debug the Zigbee part so i can figure out the problem?

Best regards,

Mathias

[Dimitri G]

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:

[Dimitri G]

Hi

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.