JN 5169 Hang Up

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

JN 5169 Hang Up

1,366 Views
weisheng
Contributor III

1.My quetion:JN 5169 Coordinator hang up when Roter joining the newwork.When the chip hang up ,there is no uart signal,no RF signal,and watchdog not reboot the device.When I reboot the device 2 days later, the  problem disappear.

2.My envirorment:

1) SDK:JN-SW-4170 v1840
2)Coordinator:Base on JN-AN-1216-Zigbee-3-0-IoT-ControlBridge-v1011, we modify code about Uart1,RF signal handle,table size, etc.

3)the router is zigbee test tool, not real device.

3.My  Operational steps:

1)Coordinator form the network

2) join other router in to the network

3) when the chip han up, there has joined 20 nodes.

4.The problem is similar to Chip JN5169 hanging in Runing 

5.The Coordinator Table Size:(we want to support 30 child nodes only)

Maximun Number of Nodes 30

Mac Table Size 35

Active Neighbour Table Size 35

Address Map Table Size 35

Broadcast Transaction Table Size 9

Child Table Size 35

Discovery Neighbour Table Size 8

Nwk Fc Save Count Bit Shift 10

Route Discovery Table Size 3

Route Record Table Size 1

Routing Table Size 60

6.when problem occur, there was no any ERROR in the uart log

7.The siffer log "5169hangUpLog.cubx"was attached below,(channel 11, panid 0x22DF) line 15469 was the last packet that coordinator sended.

8.How to find the root cause of the problem and solve it?

Labels (1)
8 Replies

1,096 Views
mario_castaneda
NXP TechSupport
NXP TechSupport

Hi Wei,

What is the error that you are seeing after the JN device? Could you please share your terminal log?

https://www.nxp.com/docs/en/data-sheet/JN5169.pdf  9.5 Interrupt system

Regards,

Mario

0 Kudos

1,096 Views
weisheng
Contributor III

Hi Mario,

      When problem occur, there was no any ERROR in the terminal log.

Regards,

Wei

0 Kudos

1,096 Views
mario_castaneda
NXP TechSupport
NXP TechSupport

Hi WEI,

How do you know that the watchdog was activated?

Are you working with the ZGWUI?

What is the message that you see in the debug port?

Regards,

Mario

0 Kudos

1,096 Views
weisheng
Contributor III

Hi Mario,

Thank you for taking the time to help me analyze the problem.

   

We had tested the watchdog before, it was activated and work fine.

We did't work with the ZGWUI, we work with our gateway in fact.

When this problem  occured,all terminal log was in the "JN5169HangUp.txt" log, and the sniffer log"5169HangUpLog.cubx" was attached below.

Look forward to your reply.

Regards,

wei

0 Kudos

1,096 Views
mario_castaneda
NXP TechSupport
NXP TechSupport

Hi Wei,

After looking at the sniffer log, it seems like the radio is still alive as there is MAC Ack activity from the coordinator until packet 15552... "Network Status: Many-to-one Route Failure".

I am not sure if you have a blocking code in your application and that is the reason for a few time the radio is active.

Could you please increase the Broadcast Transaction table size?

Regards,

Mario

0 Kudos

1,096 Views
weisheng
Contributor III

Hi Mario,

   May be  the coordinator was hang up until packet 15552.

    I check the application code this morning, there is no blocking code, I will check it again to confirm that.

    Is that the Broadcast Transaction table size cause this problem? How many changes are appropriate?

Regards,

Wei

0 Kudos

1,096 Views
mario_castaneda
NXP TechSupport
NXP TechSupport

Hi Wei,

Please look at the Broadcast Transaction table size.

Size of broadcast transaction table. The broadcast transaction table stores the broadcast transaction records, which are records of the broadcast messages received by the node.

https://www.nxp.com/docs/en/user-guide/JN-UG-3048.pdf 

Your table size is equal to 9.

Regards,

Mario

0 Kudos

1,096 Views
weisheng
Contributor III

Hi Mario,

   I am checking the Broadcast Transaction table size and try to increase  it.

   Thank you for your advice!

Regards,

   Wei