Firmware update CRC32 mismatch (version 0.3.2)

[omzlo]

from the forum https://forum.omzlo.com/forum/nocan/firmware-update-crc32-mismatch-version-0-3-2

I'm seeing regular firmware upload failures.
Restarting nocand fixes the problem every time.
Prior to the upload the canzero is sending bursts of 20+ messages every second. Perhaps the STM is getting confused due to a backlog of messages it is trying to send from the SAMD?
I can see from Nocan.transmitPending() that I'm trying to send faster than what the system can cope with.

2021/02/12 19:09:44 DEBUG++ SEND FRAME EXT@80241600 8: c0 46 c0 46 c0 46 c0 46>
2021/02/12 19:09:44 DEBUG++ SEND FRAME EXT@80241600 8: c0 46 c0 46 c0 46 c0 46>
2021/02/12 19:09:44 DEBUG++ SEND FRAME EXT@80341600 8: c0 46 c0 46 c0 46 c0 46>
2021/02/12 19:09:44 DEBUG ** Received <nocan-sys-bootloader-write-ack node=1, func=23, param=0, len=0, data=> **
2021/02/12 19:09:44 DEBUG+ ** Sending <nocan-sys-bootloader-write node=1, func=22, param=1, len=4, data=a77c3236> **
2021/02/12 19:09:44 DEBUG++ SEND FRAME EXT@90341601 4: a7 7c 32 36>
2021/02/12 19:09:44 DEBUG ** Received <nocan-sys-bootloader-write-ack node=1, func=23, param=255, len=4, data=fb76b398> **
2021/02/12 19:09:44 WARNING Firmware upload failed: SYS_BOOTLOADER_WRITE failed for node 1 at address=0x0, CRC32 mismatch, expected=a77c3236 go fb76fbfb
2021/02/12 19:09:44 DEBUG++ Deleting client 10 (192.168.0.17:55553), closing channel and socket
2021/02/12 19:09:48 DEBUG+ ** Sending <nocan-sys-node-ping node=2, func=8, param=0, len=0, data=> **
2021/02/12 19:09:48 DEBUG++ SEND FRAME EXT@90540800 0:>
2021/02/12 19:09:48 DEBUG ** Received <nocan-sys-node-ping-ack node=2, func=9, param=0, len=0, data=> **
2021/02/12 19:09:48 DEBUG+ Driver voltage=23.9, current sense=27 (~ 41 mA), reference voltage=3.28, status(40)=+powered.
2021/02/12 19:09:58 DEBUG+ Driver voltage=23.8, current sense=31 (~ 47 mA), reference voltage=3.28, status(40)=+powered.

[omzlo]

@mjbmikeb2, I'm not sure yet if this has been fixed, but the new version of nocand/nocanc (0.3.3) corrects several related issues so hopefully this is also gone.