# After upgrade mcu Unable to connect

**URL:** <https://klipper.discourse.group/t/after-upgrade-mcu-unable-to-connect/11094>\
**Category:** General Discussion\
**Created:** [October 21, 2023, 7:17am UTC](https://klipper.discourse.group/t/after-upgrade-mcu-unable-to-connect/11094 "2023-10-21T07:17:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Trev](https://avatars.discourse-cdn.com/v4/letter/t/dc4da7/32.png) [@Trev](https://klipper.discourse.group/u/Trev)\
**Post date:** [October 21, 2023, 7:17am UTC](https://klipper.discourse.group/t/after-upgrade-mcu-unable-to-connect/11094/1 "2023-10-21T07:17:51Z")

</div>

### Basic Information:

Printer Model: Voron 2.4r2  
 MCU / Printerboard: Octopus v1.1  
 `klippy.log`

### Describe your issue:

So I have decided to upgrade to the voron tap, btt sb 2240 can bus with the U2C board. I did do an update thinking that I might need that with these extra mods being installed.  
Since the update I am unable to connect to the mcu. After I flashed the octopus I can get connected until i reboot the printer. Also having troubles with a hand full of other things, but first thing is first. I have tried to re-flash my octopus through usb using CanBoot ( Katapult ) and as well as winscp with Micro sd card many times with no luck. I have re installed Klipper and Mainsial on my raspberry pi 4, I have gone through the trouble shooting and it seams its over my head. I feel like my issue is in this Printer.cfg area…

Very new to this, any help would be greatly appreciated.

serial: /tmp/klipper\_host\_mcu  
[mcu]

## Obtain definition by “ls -l /dev/serial/by-id/” then unplug to verify

##--------------------------------------------------------------------  
serial: /dev/serial/by-id/usb-katapult\_stm32f446xx\_2B0040001750344D30353320-if00  
restart\_method: command

[klippy (48).log](https://klipper.discourse.group/uploads/short-url/qhMBYr88WAd7AUg58KRNVYucr1A.log) (215.8 KB)

---

<div class="post-metadata">

**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\
**Post date:** [October 21, 2023, 7:50am UTC](https://klipper.discourse.group/t/after-upgrade-mcu-unable-to-connect/11094/2 "2023-10-21T07:50:18Z")

</div>

```auto
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/by-id/usb-katapult_stm32f446xx_2B0040001750344D30353320-if00: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-katapult_stm32f446xx_2B0040001750344D30353320-if00'

```

- The error is pretty clear: there is no `/dev/serial/by-id/usb-katapult_stm32f446xx_2B0040001750344D30353320-if00`
- Also since this serial contains `katapult`, it is a strong indication that you obtained it when the board was in bootloader mode

Reboot / Reset your board, then try again with `ls -l /dev/serial/by-id/*`

---

<div class="post-metadata">

**Author:** ![Trev](https://avatars.discourse-cdn.com/v4/letter/t/dc4da7/32.png) [@Trev](https://klipper.discourse.group/u/Trev)\
**Post date:** [October 23, 2023, 1:26am UTC](https://klipper.discourse.group/t/after-upgrade-mcu-unable-to-connect/11094/3 "2023-10-23T01:26:27Z")

</div>

Thankyou sir for your time… Greatly appreciated.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/klipper/original/1X/64419bf2aac6639e6ef5cef200dcd456b0a01ac3.png) [@system](https://klipper.discourse.group/u/system)\
**Post date:** [December 22, 2023, 1:27am UTC](https://klipper.discourse.group/t/after-upgrade-mcu-unable-to-connect/11094/4 "2023-12-22T01:27:08Z")

</div>

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