v0.85 firmware upgrade causes spin loop reset

I've had an extra board laying around for a while (v0.8.5) that was running 1.16 firmware. I wanted to start using it again for a new machine so I grabbed it and verified it still worked. I could connect it to the web interface and communicate with it without issue. I then decided to upgrade firmware as it looks like some pretty cool things are coming out recently. I tried the 2.0 first. I made sure the config file had the same network settings I had previously which was basically all the generic settings, like all zeros for M552. Then I did the firmware update. I'm on a mac and I decided to use the terminal method with bossac. Seemed to work fine. I was then able to successfully connect to the board in pronterface. Everything looked good. Then I plugged in the network cable and when I send M552 to try to get at the IP address, I get the following:

SENDING:M552
Network is enabled, configured IP address: 0.0.0.0, actual IP address: 0.0.0.0

Then I noticed the board was resetting itself every 30 seconds or so. I then tried installing 1.21 firmware. Same result. Then 1.20 firmware Same thing. Has anyone else experienced this? Here is the result of an M122 command sent to the board just before posting this if it helps:

SENDING:M122
=== Diagnostics ===
Used output buffers: 1 of 32 (1 max)
=== Platform ===
RepRapFirmware for Duet version 1.20 running on Duet 0.85
Static ram used: 44836
Dynamic ram used: 40788
Recycled dynamic ram: 392
Stack ram used: 3520 current, 4360 maximum
Never used ram: 7928
Last reset 00:08:48 ago, cause: software
Last software reset time unknown, reason: Stuck in spin loop, spinning module Network, available RAM 7892 bytes (slot 3)
Software reset code 0x2041 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0440f80f, BFAR 0xe000ed38, SP 0x20087e6c
Stack: 000bf693 200711f8 fffffff9 00000000 20087ebc 20070fe8 200711f8 20087ebc 000a5df5 000a66da 21000000 20087ea0 2007a938 00000000 2007376c 200737a8 20087ebc 00000151 2007aea8 00000045 f50ca8c0 2007376c 000a570d 2001376c
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 21.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 32.9, current 35.1, max 35.5
Date/time: 1970-01-01 00:00:00
Slowest main loop (seconds): 0.000397; fastest: 0.000100
=== Move ===
MaxReps: 0, StepErrors: 0, FreeDm: 100, MinFreeDm 100, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0, chamberHeaters = -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is ready with "M122" in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Free connections: 16 of 16
Free transactions: 24 of 24
Locked: 0, state: 2, listening: 0x0, 0x0, 0x0

My apologies. It's been a long day. Just realized I made a mistake in the above description. I actually didn't try firmware 2.0. I thought about going for that one first but after I read about it for a quite a while I wasn't sure it supported the older boards so I decided to start with 1.21. After having a lot of trouble there I then tried 1.20 as I said previously.

A few users have reported this problem with recent firmware running on the Duet 06 and 085. I can tell from the M122 reports that it is crashing inside the DHCP code in Lwip, but I can't see anything wrong in that code that would account for it, nor can I repoduce the problem. Setting a static IP address avoids the problem.

Have you tried firmware 1.21.1RC1? That release has more free memory, which may help.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

No, I didn’t try that one. I will try it next week when I get back from vacation and report the results. However,for what it’s worth, after I tried 1.20 I skipped back to 1.18.1 and that one worked.

It's been replaced by 1.21.1RC2.

If you still get a reboot loop with that version when you are using DHCP, please share your config.g file in case that helps me to reproduce the problem.

Edited 1 time(s). Last edit at 05/11/2018 03:38PM by dc42.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].