Reboot loop with MPU enabled



  • This is a continuation of an earlier thread...

    @dc42 Now when I boot with the SBC connected, I get a boot loop. It happens somewhere in the middle of processing config.g with a "Controller has been reset" message.
    The end of the M122 output may be a little wonky because it was also capturing the GCode output from config.g

    M122
    === Diagnostics ===
    RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 version 3.0beta12+1 running on Duet 3 MB6HC
    Board ID: 08DGM-9T66A-G63SJ-6J9F4-3SD6S-1U03B
    Used output buffers: 1 of 32 (5 max)
    === RTOS ===
    Static ram: 122240
    Dynamic ram: 167708 of which 0 recycled
    Exception stack ram used: 212
    Never used ram: 103056
    Tasks: NETWORK(ready,2068) HEAT(blocked,1456) CanReceiv(suspended,3804) CanSender(suspended,1480) CanClock(blocked,1464) TMC(suspended,256) MAIN(running,4492) IDLE(ready,200)
    Owned mutexes:
    === Platform ===
    Last reset 00:00:00 ago, cause: software
    Last software reset at 2019-11-10 09:11, reason: Memory protection fault, spinning module GCodes, available RAM 101704 bytes (slot 1)
    Software reset code 0x4163 HFSR 0x00000000 CFSR 0x00000082 ICSR 0x04432804 BFAR 0x00000086 SP 0x20415c9c Task 0x4e49414d
    Stack: 00452a63 0043baf0 81000000 00000000 0042a57b 20422404 20424f38 00000004 0046e568 20423d00 00000000 01000000 00000000 0042b091 00000000 00000000 00429c25 00000000 20422300 20423d00 0043ae01 00000000 20415e2a
    Error status: 0
    Free file entries: 10
    SD card 0 not detected, interface speed: 37.5MBytes/sec
    SD card longest block write time: 0.0ms, max retries 0
    MCU temperature: min 70.0, current 8.9, max -284.0
    Supply voltage: min 0.9, current 1.0, max 1.0, under voltage events: 0, over voltage events: 0, power good: no
    12V rail voltage: min 0.3, current 0.3, max 0.4, under voltage events: 0
    Driver 0: ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
    Driver 1: ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
    Driver 2: ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
    Driver 3: ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
    Driver 4: ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
    Driver 5: ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
    Date/time: 1970-01-01 00:00:00
    Slowest loop: 2.16ms; fastest: 0.17ms
    === Move ===
    Hiccups: 0, FreeDm: 375, MinFreeDm: 375, 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
    === AuxDDARing ===
    Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
    === GCodes ===
    Segments left: 0
    Stack records: 1 allocated, 1 in use
    Movement lock held by null
    http is idle in state(s) 0
    telnet is idle in state(s) 0
    file is idle in state(s) 0
    serial is idle in state(s) 0
    aux is assembling a command in state(s) 0
    daemon* is ready with "M122" in state(s) 0 0, running macro
    queue is idle in state(s) 0
    lcd is idle in state(s) 0
    spi is idle in state(s) 0
    autopause is idle in state(s) 0
    Code queue is empty.
    === Network ===
    Slowest loop: 0.24ms; fastest: 0.01ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 0 of 8
    - Ethernet -
    State: 0
    Socket states: 0 0 0 0 0 0 0 0
    === CAN ===
    Messages sent 0, longest wait 0ms for type 0
    === Linux interface ===
    State: 0, failed transfers: 0
    Last transfer: 13ms ago
    RX/TX seq numbers: 45063/5
    SPI underruns 0, overruns 0
    Number of disconnects: 0
    Buffer RX/TX: 20/180-0
    === Duet Control Server ===
    Duet Control Server v1.1.0.5
    Daemon:
    => 596 bytes
    > Suspended code level
    Code buffer space: 3500
    Configured SPI speed: 2000000 Hz
    Full transfers per second: 9.85
    

  • administrators

    I'm sorry, I no longer have symbol files for that build. Please try the firmware now at https://www.dropbox.com/sh/3azy1njy3ayjsbp/AACquxr2m00eV568RZg5QG5wa?dl=0 and assuming the problem still occurs, post the M122 report again. Also please post your config.g file as I suspect that some command in it that is missing from my config.g may be triggering the reboot.


  • administrators

    I'm sorry, I no longer have symbol files for that build. Please try the firmware now at https://www.dropbox.com/sh/3azy1njy3ayjsbp/AACquxr2m00eV568RZg5QG5wa?dl=0 and assuming the problem still occurs, post the M122 report again. Also please post your config.g file as I suspect that some command in it that is missing from my config.g may be triggering the reboot.



  • @dc42 It looks like that build fixed it.


Log in to reply