@chrishamm I am as sure as I can be. I've flashed the board 2 ways:

1. Put 3.4.6 on the board with BOSSA. DWC tells me there's a file incompatibility and I need to update the board. I run M997 S0 to do so. Board goes down and never reconnects even after a power cycle

2. Manually flash 3.5.0rc3 SBC from the git repo onto the board using BOSSA. BOSSA thinks the board flashes correctly, but when powered on DWC is never able to connect to the board.

If there's another technique or something I'm missing I'm happy to try it.

@chrishamm

Feb 18 14:40:14 duet3 systemd[1]: Starting duetcontrolserver.service - Duet Control Server...
Feb 18 14:40:15 duet3 DuetControlServer[2666]: Duet Control Server v3.5.0-rc.3
Feb 18 14:40:15 duet3 DuetControlServer[2666]: Written by Christian Hammacher for Duet3D
Feb 18 14:40:15 duet3 DuetControlServer[2666]: Licensed under the terms of the GNU Public License Version 3
Feb 18 14:40:16 duet3 DuetControlServer[2666]: [info] Settings loaded
Feb 18 14:40:16 duet3 DuetControlServer[2666]: [info] Environment initialized
Feb 18 14:40:16 duet3 DuetControlServer[2666]: [info] Connection to Duet established
Feb 18 14:40:16 duet3 DuetControlServer[2666]: [info] IPC socket created at /run/dsf/dcs.sock
Feb 18 14:40:16 duet3 systemd[1]: Started duetcontrolserver.service - Duet Control Server.
Feb 18 14:40:17 duet3 DuetControlServer[2666]: [fatal] Abnormal program termination
Feb 18 14:40:17 duet3 DuetControlServer[2666]: [fatal] SPI task faulted
Feb 18 14:40:17 duet3 DuetControlServer[2666]:    System.InvalidOperationException: Stack underrun on channel File2
Feb 18 14:40:17 duet3 DuetControlServer[2666]:    at DuetControlServer.SPI.Channel.Processor.Pop() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Channel/Processor.cs:line 128
Feb 18 14:40:17 duet3 DuetControlServer[2666]:    at DuetControlServer.SPI.Channel.Processor.MacroFileClosed() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Channel/Processor.cs:line 1121
Feb 18 14:40:17 duet3 DuetControlServer[2666]:    at DuetControlServer.SPI.Interface.HandleMacroFileClosed() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 1321
Feb 18 14:40:17 duet3 DuetControlServer[2666]:    at DuetControlServer.SPI.Interface.ProcessPacket(PacketHeader packet) in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 970
Feb 18 14:40:17 duet3 DuetControlServer[2666]:    at DuetControlServer.SPI.Interface.Run() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 772
Feb 18 14:40:17 duet3 DuetControlServer[2666]:    at DuetControlServer.Utility.PriorityThreadRunner.<>c__DisplayClass0_0.<Start>b__0() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/Utility/PriorityThreadRunner.cs:line 25
Feb 18 14:40:17 duet3 DuetControlServer[2666]: [fatal] SPI task faulted
Feb 18 14:40:17 duet3 DuetControlServer[2666]:    System.InvalidOperationException: Stack underrun on channel File2
Feb 18 14:40:17 duet3 DuetControlServer[2666]:    at DuetControlServer.SPI.Channel.Processor.Pop() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Channel/Processor.cs:line 128
Feb 18 14:40:17 duet3 DuetControlServer[2666]:    at DuetControlServer.SPI.Channel.Processor.MacroFileClosed() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Channel/Processor.cs:line 1121
Feb 18 14:40:17 duet3 DuetControlServer[2666]:    at DuetControlServer.SPI.Interface.HandleMacroFileClosed() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 1321
Feb 18 14:40:17 duet3 DuetControlServer[2666]:    at DuetControlServer.SPI.Interface.ProcessPacket(PacketHeader packet) in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 970
Feb 18 14:40:17 duet3 DuetControlServer[2666]:    at DuetControlServer.SPI.Interface.Run() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 772
Feb 18 14:40:17 duet3 DuetControlServer[2666]:    at DuetControlServer.Utility.PriorityThreadRunner.<>c__DisplayClass0_0.<Start>b__0() in /home/runner/work/DuetSoftwareFramework/DuetSoftwareFramework/src/DuetControlServer/Utility/PriorityThreadRunner.cs:line 25
Feb 18 14:40:17 duet3 DuetControlServer[2666]: [info] Application has shut down
Feb 18 14:40:17 duet3 systemd[1]: duetcontrolserver.service: Main process exited, code=exited, status=70/SOFTWARE
Feb 18 14:40:17 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'exit-code'.
Feb 18 14:40:17 duet3 systemd[1]: duetcontrolserver.service: Consumed 4.124s CPU time.

Also updating the newest build did not in fact fix this issue.

Figured it out - Needed to be using the latest OS image (bookwork), not the old stable image.

I haven't ruled out this is user error but I can't figure where I'm going wrong.

Hardware is known good.

DSF works when using the stable branch.

I upgrade to unstable and update the pi side, everything works fine until it tries to update the board. It thinks the firmware flash works, but the board never comes back up.

I use bossa to manually flash to 3.5.0rc3. Bossa thinks it flashes successfully but no joy on the DSF side.

I nuke the card and reimage it, and bossa reflash the board to 3.4.6. Run the linux updates (still on the stable branch). Everything's happy, DSF connects no problem.

I switch back to unstable and run the linux updates again. Double check that it's pulling 3.5.0rc3 and it is. Update tries to flash the board and it fails with errors when running apt dist-upgrade.

I use Bossa to reflash 3.5.0rc3. Bossa thinks it works but again, no DSF joy.

I've reviewed the release notes and everything else I can find and I can't figure out what I'm missing. Help?

EDIT - and yes I am BOSSA flashing the SBC builds not the standard firmware.