Home/Support/Support Forum/ConnectPortX2 panics/reboots several times a hour.
Welcome to Digi Forum, where you can ask questions and receive answers from other members of the community.

ConnectPortX2 panics/reboots several times a hour.

0 votes
Box reboots several times an hour. Event log has the following.

----
2014-08-27 13:36:41 boot Unit restarted due to panic.
2014-08-27 13:36:41 yaffs System indicates YAFFS.
2014-08-27 13:36:41 time Applying system time offset of -5 hours, 00 minutes.
2014-08-27 13:36:41 time Applying system time adjustment threshold of 60 seconds.
2014-08-27 13:36:41 time Lost time source recovery is enabled.
2014-08-27 13:36:41 system Product: ConnectPort X2D (ID 0x00B2).
2014-08-27 13:36:41 system Firmware Version: 2.17.1.0 (Version 82002549_F1 11/05/2013).
2014-08-27 13:36:41 system Boot Version: 1.1.3 (release_82002547_A).
2014-08-27 13:36:41 system Post Version: 1.1.3 (release_82002548_B).
2014-08-27 13:36:41 system Product VPD Version: release_82002550_A.
2014-08-27 13:36:41 system Hardware Strapping: 0x0775.
2014-08-27 13:36:41 yaffs checkBootParm: YAFFS 01000000 (eth0)
2014-08-27 13:36:41 dcloud Device ID: 00000000-00000000-00409DFF-FF564672
2014-08-27 13:36:41 dcloud Vendor ID: 0xFE000000
2014-08-27 13:36:41 dcloud Device Type: ConnectPort X2D
2014-08-27 13:36:42 python application 'send_dockwatch.py' started.
2014-08-27 13:36:42 mesh Radio version: HW 0x1a4a FW 0x21a0
2014-08-27 13:37:12 time Jump to new baseline at uptime 31 (src 0, rank 10, delta 1409164601).
2014-08-27 14:12:06 [End of Event Log at +0 days 00:35:25]
---

Anyway to enable additional debugging ?
asked Aug 27, 2014 in ConnectPort Display by rasmussenc New to the Community (2 points)
Found 'show panic' but it doesn't really show my anything useful.
-----
#> show panic p

Boot(s) since last panic:        1  Number of panics detected:       17
Last fault was a panic.
('set panic c' to clear buffers)

PANIC DATA:
Recorded at Python-2.4.3/Python/pythonrun.c line 1531
Reason Py_EndInterpreter: not the last thread
Error code 0:0 (0x00000000:0x00000000)

pc 0x0031df7c
cpsr 0x60000013  [n-Z-C-v--i-f--SVC]
spsr 0x60000013  [n-Z-C-v--i-f--SVC]

r0  0x0043f5e4  r1  0x000005fb  r2  0x0043f230  r3  0x00000000
r4  0x0043f230  r5  0x0074cb98  r6  0x00796100  r7  0x0076b9bc
r8  0x007644e0  r9  0x0065e090  r10 0x00000000  r11 0x007ab790
r12 0x00000000  sp  0x007ab77c  lr  0x0031df7c

System uptime in ms:        0:748951

Build information:

   Tag    : 82002549_F1
   Date   : 11/05/2013
   Time   : 14:01:42 CST
   Machine: mtk-vln-skipjack
---

also found this previous question.
http://www.digi.com/support/forum/231/python-threads-causing-panic

I do use threads in my python code. Is that not supported ?

Please log in or register to answer this question.

1 Answer

0 votes
In the Log file, what is listed before 2014-08-27 13:36:41 boot Unit restarted due to panic. ?

You are running an older version of firmware on the XBee module, have you considered upgrading it?

You may even want to upgrade the firmware for the gateway as well as it a few versions old.
answered Aug 27, 2014 by mvut Veteran of the Digi Community (13,036 points)
There is nothing prior to that entry in the log.

I believe I am at the latest version for a connectport X2 (X2D) Atleast thats the latest I've seen. Updated the XBee module to 0x21a7 which was the latest I could download.

I think this is related to python and using threads in my code. I am going to disable using threads and see if it stays up.
Your above response shows that you were using 21A0 and not 21A7.
...