Firmware error after EMMC install

Basic Information:

Printer Model: orangestorm giga
MCU / Printerboard:
Host / SBC
klippy.log

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

I installed a new EMMC in my giga, and while I can connect to it with mainsail or fluidd, the printer screen just shows the logo, and I have a firmware error showing in the web interface. Sorry i don’t have access right now to pull the logs, and I am doing this from my phone so I can not attach a zip. I did copy the error section and emailed it to myself before leaving the office. I will paste that. Sorry I wasn’t able to fully follow the instructions.

Extruder max_extrude_ratio=207.875844
mcu ‘mcu’: Starting CAN connect
Created a socket
mcu ‘mcu’: Unable to open CAN port: Failed to transmit: [Errno 100] Network is down
webhooks client 281473719928528: New connection
webhooks client 281473719928528: Client info {‘program’: ‘Moonraker’, ‘version’: ‘v0.9.2-0-gb40751b’}
Created a socket
mcu ‘mcu’: Unable to open CAN port: Failed to transmit: [Errno 100] Network is down
Created a socket
mcu ‘mcu’: Unable to open CAN port: Failed to transmit: [Errno 100] Network is down
Created a socket
mcu ‘mcu’: Unable to open CAN port: Failed to transmit: [Errno 100] Network is down
Created a socket
mcu ‘mcu’: Unable to open CAN port: Failed to transmit: [Errno 100] Network is down
Created a socket
mcu ‘mcu’: Unable to open CAN port: Failed to transmit: [Errno 100] Network is down
Created a socket
mcu ‘mcu’: Unable to open CAN port: Failed to transmit: [Errno 100] Network is down
Created a socket
mcu ‘mcu’: Unable to open CAN port: Failed to transmit: [Errno 100] Network is down
Created a socket
mcu ‘mcu’: Unable to open CAN port: Failed to transmit: [Errno 100] Network is down
Created a socket
mcu ‘mcu’: Unable to open CAN port: Failed to transmit: [Errno 100] Network is down
Created a socket
mcu ‘mcu’: Unable to open CAN port: Failed to transmit: [Errno 100] Network is down
Created a socket
mcu ‘mcu’: Unable to open CAN port: Failed to transmit: [Errno 100] Network is down
Created a socket
mcu ‘mcu’: Unable to open CAN port: Failed to transmit: [Errno 100] Network is down
Created a socket
mcu ‘mcu’: Unable to open CAN port: Failed to transmit: [Errno 100] Network is down
Created a socket
mcu ‘mcu’: Unable to open CAN port: Failed to transmit: [Errno 100] Network is down
Created a socket
mcu ‘mcu’: Unable to open CAN port: Failed to transmit: [Errno 100] Network is down
Created a socket
mcu ‘mcu’: Unable to open CAN port: Failed to transmit: [Errno 100] Network is down
Created a socket
mcu ‘mcu’: Unable to open CAN port: Failed to transmit: [Errno 100] Network is down
MCU error during connect
Traceback (most recent call last):
File “/home/mks/klipper/klippy/mcu.py”, line 787, in _mcu_identify
self._serial.connect_canbus(self._serialport, nodeid,
File “/home/mks/klipper/klippy/serialhdl.py”, line 133, in connect_canbus
self._error(“Unable to connect”)
File “/home/mks/klipper/klippy/serialhdl.py”, line 61, in _error
raise error(self.warn_prefix + (msg % params))
serialhdl.error: mcu ‘mcu’: Unable to connect

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File “/home/mks/klipper/klippy/klippy.py”, line 131, in _connect
self.send_event(“klippy:mcu_identify”)
File “/home/mks/klipper/klippy/klippy.py”, line 223, in send_event
return [cb(*params) for cb in self.event_handlers.get(event, )]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/home/mks/klipper/klippy/klippy.py”, line 223, in
return [cb(*params) for cb in self.event_handlers.get(event, )]
^^^^^^^^^^^
File “/home/mks/klipper/klippy/mcu.py”, line 798, in _mcu_identify
raise error(str(e))
mcu.error: mcu ‘mcu’: Unable to connect
mcu ‘mcu’: Unable to connect
Once the underlying issue is corrected, use the
“FIRMWARE_RESTART” command to reset the firmware, reload the
config, and restart the host software.
Error configuring printer

I had that same error while trying to install EBB42 CAN. The solution that I found was to write the following command in the pi console (via SSH):

sudo ip link set up can0 type can bitrate 500000

In my case, the problem was that the speed of CAN was not properly set.

Thanks! I Found out there are other issues too. Firmware isn’t fully set up.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.