Cannot flash Duet Toolboard v1.1
-
I have a Duet 3 with RPI 4 as a SBC. I recently installed a Duet toolboard v1.1. I did solder the pad on the back and I have verified it is wired correctly to the CAN. I was able to communicate with it but noticed the it had a higher version than I was running. While trying to down grade the firmware the boards became unresponsive. After an hour I power cycled the printer. Now I cannot communicate with the toolboard with M115 B121(I never changed the address).
I tried holding both buttons down and powering on the board but no change. The blue and the red led on the toolboard are solid.
m115 FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.2 ELECTRONICS: Duet 3 MB6HC v1.01 or later FIRMWARE_DATE: 2021-01-05
M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.2 running on Duet 3 MB6HC v1.01 or later (SBC mode) Board ID: 08DJM-956L2-G43S8-6J9D0-3S46T-9U2LF Used output buffers: 1 of 40 (10 max) === RTOS === Static ram: 149788 Dynamic ram: 62048 of which 176 recycled Never used RAM 146820, free system stack 190 words Tasks: Linux(ready,95) HEAT(blocked,297) CanReceiv(blocked,927) CanSender(blocked,371) CanClock(blocked,352) TMC(blocked,53) MAIN(running,1179) IDLE(ready,19) Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:09:32 ago, cause: power up Last software reset at 2021-05-24 20:39, reason: User, none spinning, available RAM 146428, slot 1 Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task Linu Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 Aux1 errors 0,0,0 MCU temperature: min 29.2, current 34.0, max 34.9 Supply voltage: min 0.4, current 24.6, max 25.2, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 0.1, current 12.1, max 12.3, under voltage events: 2 Driver 0: position 0, standstill, reads 7386, writes 33 timeouts 0, SG min/max 0/0 Driver 1: position 0, standstill, reads 7383, writes 36 timeouts 0, SG min/max 0/0 Driver 2: position 0, standstill, reads 7383, writes 36 timeouts 0, SG min/max 0/0 Driver 3: position 0, standstill, reads 7383, writes 36 timeouts 0, SG min/max 0/0 Driver 4: position 0, standstill, reads 7384, writes 36 timeouts 0, SG min/max 0/0 Driver 5: position 0, standstill, reads 7384, writes 36 timeouts 0, SG min/max 0/0 Date/time: 2021-05-24 21:03:47 Slowest loop: 1050.76ms; fastest: 0.04ms === Storage === Free file entries: 10 SD card 0 not detected, interface speed: 37.5MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === DMs created 125, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 === GCodes === Segments left: 0 Movement lock held by null HTTP* is doing "M122" in state(s) 0 Telnet is idle in state(s) 0 File is idle in state(s) 0 USB is idle in state(s) 0 Aux is idle in state(s) 0 Trigger* is idle in state(s) 0 Queue is idle in state(s) 0 LCD is idle in state(s) 0 SBC is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === CAN === Messages queued 2174, send timeouts 5032, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 48 === SBC interface === State: 4, failed transfers: 0 Last transfer: 1ms ago RX/TX seq numbers: 19160/19160 SPI underruns 0, overruns 0 Number of disconnects: 0, IAP RAM available 0x2c8a8 Buffer RX/TX: 0/0-0 === Duet Control Server === Duet Control Server v3.2.0 Code buffer space: 4096 Configured SPI speed: 8000000 Hz Full transfers per second: 14.91 Maximum length of RX/TX data transfers: 4472/444
-
@dhusolo the older firmware is not compatible with the tool board 1.1. However, if you disconnect CAN, then hold down both buttons while powering up (which is quite difficult to do), then the bootloader should attempt to load new firmware. This will be indicated by the Status LED flashing a specific number of times. It will continue to try to load new firmware for as long as you hold down the buttons.
-
@dc42 Thanks for the response. I disconnected the board completely and tried powering on the board with both buttons pressed. however the only LEDs that are lit is the blue VIN led and the red 5v led. The ACT and STATUS LEDs do not light up at all
-
-
@dhusolo we will replace the board. Please send an email to warranty@duet3d.com and cc your supplier. You will receive a reply with a link to a form to fill in.