motherboard resets



  • can someone help me with the print does not start and the motherboard resets?
    M122
    === Diagnostics ===
    RepRapFirmware for LPC176x based Boards (biquskr_1.4) version 3.01-RC12 running on LPC176x at 120Mhz
    Used output buffers: 3 of 16 (10 max)
    === RTOS ===
    Static ram: 3840
    Dynamic Memory (RTOS Heap 5): 3256 free, 3232 never used
    Exception stack ram used: 304
    Never used ram: 204
    Tasks: NETWORK(ready,296) HEAT(blocked,1360) MAIN(running,1420) IDLE(ready,80)
    Owned mutexes: WiFi(NETWORK)
    === Platform ===
    Last reset 00:02:23 ago, cause: [software]
    LPC Flash Slot[101]:
    Last software reset at 2020-08-27 15:49, reason: Watchdog timeout, spinning module GCodes, available RAM 0 bytes (slot 0)
    Software reset code 0x08a3 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0442d010 BFAR 0xe000ed38 SP 0x10007fa4 Task MAIN
    Stack: 00005ed7 00009dd8 0100502d 00000000 2007c1dc 2007d9af fffffffd 10007fe0 e000e014 e000e010 10000010
    Error status: 0
    Driver 0: standstill, read errors 0, write errors 1, ifcount 48, reads 896, timeouts 0
    Driver 1: standstill, read errors 0, write errors 1, ifcount 48, reads 895, timeouts 0
    Driver 2: standstill, read errors 0, write errors 1, ifcount 48, reads 895, timeouts 0
    Driver 3: standstill, read errors 0, write errors 1, ifcount 34, reads 895, timeouts 0
    Driver 4: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 902
    Date/time: 2020-08-27 15:52:22
    Slowest loop: 101.36ms; fastest: 0.27ms
    === Storage ===
    Free file entries: 4
    SD card 0 detected
    SD card longest read time 36.4ms, write time 0.0ms, max retries 0
    === Move ===
    Hiccups: 0, FreeDm: 100, MinFreeDm: 100, MaxWait: 0ms
    Bed compensation in use: none, comp offset 0.000
    === DDARing ===
    Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
    === Heat ===
    Bed heaters = 0, chamberHeaters = -1
    === GCodes ===
    Segments left: 0
    Movement lock held by null
    HTTP 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
    Daemon is idle in state(s) 0
    Autopause is idle in state(s) 0
    Code queue is empty.
    === Network ===
    Slowest loop: 8.68ms; fastest: 0.00ms
    Responder states: HTTP(2) HTTP(0)
    HTTP sessions: 1 of 2

    • WiFi -
      Network state is active
      WiFi module is connected to access point
      Failed messages: pending 0, notready 0, noresp 0
      WiFi firmware version 1.23-01L-D
      WiFi MAC address 40:0d:10:89:dd:c1
      WiFi Vcc 64.00, reset reason Unknown
      WiFi flash size 4194304, free heap 37296
      WiFi IP address 192.168.0.39
      WiFi signal strength -51dBm, reconnections 0, sleep mode modem
      Socket states: 4 0


  • @Iony3d watchdog means the firmware hangs. I suspect it has to do with driver's 4 timeouts. Is there a newer firmware available for the LPC port, like 3.1.1. Then I would recommend to update to this version, because 3.01-RC12 is a beta version.


  • administrators

    I'm moving this thread to the "RepRapFirmware on other controllers" section, where the person who maintains the LPC port is more likely to see it.



  • I see you are running the LPC port of RRF. The version you are running is pretty old. I'd strongly recommend that you update to the most recent version 3.1.1-14 (which is available here: https://github.com/gloomyandy/RepRapFirmware/releases/tag/LPC_RRFv3.1.1-14). I can't be sure that the old version is the cause of the reset, but there have been many fixes and changes since V3.01-RC12.

    If you are still having problems you may get a faster response using the LPC discord server (the LPC Wiki has the details).



  • Oh and looking at the M122 output I'd guess that either you don't have a driver 4 or it is not a TMC driver? If that is the case you can tell the firmware to ignore that device by setting: stepper.numSmartDriver=4 in your board.txt file.



  • thank you guys ... I'm going to update ... and i run 4 tmc2209 drivers ..can be the cable from motors?


Log in to reply