12864 constant reboot - Mini 5+ and SBC
-
Enabling the 12864 screen on the current 3.2 beta results in a constant reboot and DWC reporting a transfer pin issue.
This is usingM918 P2 ; enable ST7567-based 12864 display M150 X2 R255 U255 B255 S3 ; set all 3 LEDs to whiteThe screen was working fine in standalone mode.
As soon as those two lines are removed, the printer works fine.
-
Please post a M122 report taken after one of those uncommanded reboots.
-
@jay_s_uk said in 12864 constant reboot - Mini 5+ and SBC:
M918 P2 ; enable ST7567-based 12864 display M150 X2 R255 U255 B255 S3 ; set all 3 LEDs to white
i am unable to get an M122 output as the board is rebooting every 3 to 4 seconds
-
I have narrowed it down further to the
M918 P2The other command works find for controlling the LCD colour
-
Please try the new build at https://www.dropbox.com/s/4mtjx1oo73nwv69/Duet3Firmware_Mini5plus_v02.uf2?dl=0. If the problem persists, please provide a M122 report taken after one of those reboots.
-
@dc42 I can confirm this issue still exists in 3.2 beta 2.
This time I managed to get an M122 output.=== Diagnostics === RepRapFirmware for Duet 3 Mini 5+ prototype v0.2 version 3.2-beta2 running on Duet 3 Mini5plus WiFi (SBC mode) Board ID: 8ULVP-1D6P9-F65J0-401FQ-2A03Z-RJW1V Used output buffers: 1 of 40 (8 max) === RTOS === Static ram: 88664 Dynamic ram: 108080 of which 20 recycled Exception stack ram used: 224 Never used ram: 65156 Tasks: Linux(ready,144) HEAT(blocked,370) TMC(blocked,69) MAIN(running,630) IDLE(ready,20) AIN(blocked,272) Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:00:00 ago, cause: software Last software reset at 2020-10-05 20:45, reason: HardFault bfarValid precise, Display spinning, available RAM 59776, slot 1 Software reset code 0x406f HFSR 0x40000000 CFSR 0x00008200 ICSR 0x04433803 BFAR 0xc5a8afc0 SP 0x20008480 Task MAIN Stack: c5a8afc2 c5a8afc0 00000000 00000000 ffffffff 0006dda7 0007c7ae 210f0000 20006f6c 00000000 a5a5a5a5 2001b958 2001a568 20006f6c 200084f8 00071679 2000854c 200084e4 2000858c 2000858b 000900b0 0007fae4 00000000 00073b7f 00000101 00000000 c5a8afc2 Error status: 0x00 Supply voltage: min 0.0, current 12.6, max 12.6, under voltage events: 0, over voltage events: 0, power good: yes Driver 0: position 0, ok, SG min/max not available, read errors 0, write errors 1, ifcnt 247, reads 0, writes 1, timeouts 0, DMA errors 0 Driver 1: position 0, ok, SG min/max not available, read errors 0, write errors 1, ifcnt 246, reads 0, writes 0, timeouts 0, DMA errors 0 Driver 2: position 0, ok, SG min/max not available, read errors 0, write errors 1, ifcnt 249, reads 0, writes 0, timeouts 0, DMA errors 0 Driver 3: position 0, ok, SG min/max not available, read errors 0, write errors 1, ifcnt 249, reads 0, writes 0, timeouts 0, DMA errors 0 Driver 4: position 0, ok, SG min/max not available, read errors 0, write errors 1, ifcnt 246, reads 0, writes 0, timeouts 0, DMA errors 0 Driver 5: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 1, DMA errors 0, failedOp 0x80 Driver 6: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 1, DMA errors 0, failedOp 0x80 Driver 7: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 1, DMA errors 0, failedOp 0x80 Date/time: 1970-01-01 00:00:00 Slowest loop: 0.15ms; fastest: 0.00ms === Storage === Free file entries: 10 SD card 0 not detected, interface speed: 11.2MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms Bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === AuxDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === Heat === Bed heaters = -1 -1, chamberHeaters = -1 -1 === GCodes === Segments left: 0 Movement lock held by null HTTP* is ready with "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 0, running macro 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. === SBC interface === State: 0, failed transfers: 0 Last transfer: 11ms ago RX/TX seq numbers: 270/6 SPI underruns 0, overruns 0 Number of disconnects: 0 Buffer RX/TX: 24/924-0 === Duet Control Server === Duet Control Server v3.2.0-beta2 Trigger: Buffered code: M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation Buffered code: M92 X100.00 Y100.00 Z400.00 E837 ; set steps per mm Buffered code: M566 X1000.00 Y1000.00 Z24.00 E120.00 ; set maximum instantaneous speed changes (mm/min) Buffered code: M203 X6000.00 Y6000.00 Z300.00 E1200.00 ; set maximum speeds (mm/min) Buffered code: M201 X1000.00 Y1000.00 Z200.00 E250.00 ; set accelerations (mm/s^2) ==> 288 bytes Executing macro config.g, started by system Pending code: M906 X1200 Y1200 Z1200 E1100 I30 ; set motor currents (mA) and motor idle factor in per cent Pending code: M84 S30 ; Set idle timeout > Next stack level Code buffer space: 3808 Configured SPI speed: 8000000 Hz Full transfers per second: 12.42 -
@jay_s_uk, please share your config.g file.
-
@dc42 please see below
; Configuration file for Duet 3 (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.1.4 on Tue Sep 22 2020 14:08:43 GMT+0100 (British Summer Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder move ; Drives M569 P0.0 S0 D3 V40 ; physical drive 0.0 goes forwards M569 P0.1 S1 D3 V40 ; physical drive 0.1 goes forwards M569 P0.2 S1 D3 V40 ; physical drive 0.2 goes forwards M569 P0.3 S0 D3 V40 ; physical drive 0.3 goes forwards M569 P0.4 S1 D3 V40 ; physical drive 0.3 goes forwards M584 X0.0 Y0.1 Z0.2:0.3 E0.4 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X100.00 Y100.00 Z400.00 E837 ; set steps per mm M566 X1000.00 Y1000.00 Z24.00 E120.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z300.00 E1200.00 ; set maximum speeds (mm/min) M201 X1000.00 Y1000.00 Z200.00 E250.00 ; set accelerations (mm/s^2) M906 X1200 Y1200 Z1200 E1100 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X270 Y260 Z350 S0 ; set axis maxima M671 X-130:400 Y150:150 S10 ; Endstops M574 X1 S1 P"io1.in" M574 Y1 S1 P"io2.in" ; Z-Probe M558 P1 C"!io3.in" H2 A5 F120 T20000 S0.02 ; Set Z probe type to switch and the dive height + speeds G31 P1000 X-25 Y0 Z3.895 ; Set Z probe trigger value, offset and trigger height M557 X15:230 Y15:230 S20 ; define mesh grid ; Heaters M308 S0 P"temp0" Y"thermistor" T100000 B4092 ; configure sensor 0 as thermistor on pin temp0 M950 H0 C"out2" T0 ; create bed heater output on out0 and map it to sensor 0 M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M308 S1 P"temp1" Y"thermistor" T100000 B4276 ; configure sensor 1 as thermistor on pin temp1 M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit ; Fans ;############## Tool 0 Fans ########################## M950 F0 C"out6" Q500 ; Create fan 0 on pin out3 and set its frequency M106 P0 S0 H-1 ; Set fan 0 value. Thermostatic control is turned off M950 F1 C"out5" Q500 ; Create fan 1 on pin out4 and set its frequency M106 P1 S1 H1 T45 ; Set fan 1 value. Thermostatic control is turned on ; Tools M563 P0 D0 H1 F0 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C ; Custom settings are not defined ;M918 P2 ; enable ST7567-based 12864 display M150 X2 R255 U255 B255 S3 ; set all 3 LEDs to white M501 ; load saved parameters from non-volatile memory T0 ; select first tool M207 S5.0 R0.02 F2400 Z0.5 M950 P0 Q500 C"out0" -
Thanks. I think the problem is that the display manager can't read menu files when the Duet is in SBC mode. We didn't consider the combination of 12864 and SBC. I think it probably makes most sense to allow the 12864 code to read the menu files from the local SD card on the Duet. You would still be able to force SBC mode by not having a config.g file on it.
I have logged this as bug to be fixed in the next 3.2beta or RC.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 that would probably work.
Let me know when it's ready to test and give you an update. -
@dc42 said in 12864 constant reboot - Mini 5+ and SBC:
I think it probably makes most sense to allow the 12864 code to read the menu files from the local SD card on the Duet.
reading between the lines that printing and running macros from SD card and PanelDue isn't the same issue or will not be fixed?
