topic jn5169 restart in Wireless MCU

jn5169 restart

1516998341 — Mon, 15 Jul 2019 01:49:29 GMT

I have been developing jn5169 zigbee recently, using jn-an-1220 as an example.But I found that the program was restarted after running for a period of time. I didn't understand that the program was already running normally. Why did I suddenly restart the chip?

Re: jn5169 restart

Sebastian_Del_Rio — Mon, 15 Jul 2019 20:53:29 GMT

Hi Xiansheng Zhou, I hope you're doing well!

There is an API command that resets the device when certain events are detected during program execution in JN devices.

Examples of when these events happen are:

When the device is issued a Request to Leave
When a factory reset is issued to a device
When the watchdog timer runs out because an issue happened

Could you please provide the terminal log for the device that's resetting itself?

Best regards,

Sebastian

Re: jn5169 restart

1516998341 — Fri, 19 Jul 2019 01:23:52 GMT

[20:01:40]APP_ZCL: Stopped Poll
[20:01:40]APP Stopping poll timer
[20:01:40]APP NWK Event Handler: Poll Response
[20:01:40]APP NWK Event Handler: Poll Response
[20:01:40]APP Sleep Handler: Osc on, sleeping for 384000 ticks
[20:01:47]APP Start: Sleeping, Tick Timer = 255PP Start: Switch Power Up
[20:01:47]APP Entering APP_vSetUpHardware()
[20:01:47]APP Entering APP_vInitResources()APP: Entering APP_vInitialise()
[20:01:47]APP Sensor Node: APP_vInitialiseNode*eStatusOTAReload=0 size 176
[20:01:47]APP Sensor Node: ZPS_eAplAfInit
[20:01:47]APP_ZCL: Chan Mask 07fff800
[20:01:47]APP_ZCL: RxIdle TRUEMAC Address at address = 00080040
[20:01:47]ff ff ff ff ff ff ff ff
[20:01:47] Link Key 5a 69 67 42 65 65 41 6c 6c 69 61 6e 63 65 30 39
[20:01:47]Current Image Details
[20:01:47]File ID = 0x0beef11e
[20:01:47]Header Ver ID = 0x0100
[20:01:47]Header Length ID = 0x0000

Above is my running log. I don't know what caused the program to restart suddenly.I found that the program sometimes crashed directly, the log output is as follows：

[20:01:50]File ID = 0x0beef11e
[20:01:50]Header Ver ID = 0x0100
[20:01:50]Header Length ID = 0x0000
[20:01:50]Header Control Filed = 0x0000
[20:01:50]Manufac Code = 0x1037
[20:01:50]Image Type = 0x0400
[20:01:50]File Ver = 0x00000001
[20:01:50]Stack Ver = 0x0002
[20:01:50]Image Len = 0x000286de
[20:01:50]
[20:01:50]ERROR: Extended status 89
[20:01:50]
[20:01:50]!!! Bus error
[20:01:50]u32PICMR = 0 : u32PICSR = 8008
[20:01:50]u32PICMSR = 0 : u32IPMR = 0
[20:01:50]u32IHPR = f : u32AINT = 8008 u32PINT 0
[20:01:50]EPCR = 82804 : EEAR = badadd04
[20:01:50]Stack dump:
[20:01:50] 4007b74 : 000828dd
[20:01:50] 4007b78 : 0008276f
[20:01:50] 4007b7c : 04000220
[20:01:50] 4007b80 : 00082804
[20:01:50] 4007b84 : badadd04
[20:01:50] 4007b88 : 00000000
[20:01:50] 4007b8c : 0000000f
[20:01:50] 4007b90 : 00000000
[20:01:50] 4007b94 : 00008008
[20:01:50] 4007b98 : 00000000
[20:01:50] 4007b9c : 00000000

Re: jn5169 restart

Sebastian_Del_Rio — Fri, 19 Jul 2019 20:06:22 GMT

Hi Xiansheng Zhou,

The error the log is reporting is related to APSD configuration (you can check the meaning of error codes like this in the Zigbee PRO Stack User Guide document, on chapter 9.2).

On that same document, there is a list of the configurable parameters regarding APSD, and the one that seems to be related to your problem is the "Maximum Number of Simultaneous Data Requests" value (which by default is 5). Could you please try changing that value to a higher number and see if that helps the problem? Depending on if you're using acknowledge, you'll need to either modify the Maximum Number of Simultaneous Data Requests or the Maximum Number of Simultaneous Data Requests with Acks values.

Best regards,

Sebastian