firmware crash

[hartytp]

I believe I just saw a firmware crash/watchdog timeout/whatever. I had yellow and green LEDs on for all channels. I pressed the interlock reset button and all LEDs turned off and the fans came on to max briefly.

Are there any logs / debugging tools I should use to narrow this down? Or is this likely to just be another watchdog issue (maybe the timings are marginal during interlock resets?)

[ryan-summers]

Related to #93 - we do not yet have any crash/reset post-mortem/persistent logging implementation to help with this, but I would really like to add it.

One of the difficulties is the lack of a (larger) external non-volatile memory for storing logs in, which limits our logging capabilities to internal flash or RAM. I'll have to give some thought into a good design here.

[hartytp]

It's been a while since I looked at this, but isn't it possible to read out whether the watchdog tripped at boot and just go into an error state instead of starting up normally? That at least gives some level of visibility over the issue.

[ryan-summers]

It's been a while since I looked at this, but isn't it possible to read out whether the watchdog tripped at boot and just go into an error state instead of starting up normally? That at least gives some level of visibility over the issue.

Yes, and I believe we already currently check and reset the necessary bits, we just don't transition to an error state (although I have other projects where the firmware transitions into "service mode", where it remains not operational for safety reasons) - that may be appropriate here, although would require further design.

[hartytp]

okay. Well, I know that time is limited here, so I'm not insisting on any of this. Hopefully the new release will remove the crashes and this won't be so important.

[jordens]

@hartytp which firmware version and release/debug was this? I.e. is it known to be distinct from #94?

[hartytp]

Current release binaries. It is not known to be distinct from 94 (which is what I was trying to imply in the initial post).

[hartytp]

let's assume this is a duplicate of #94 for now