Printer Model: Custom Build
MCU / Printerboard: BigTreeTech Manta M8P (V1.1) w/ CB1
Host / SBC: Windows Desktop PC
klippy.log
Ran into an initial issue and everything I read online pointed to starting an install from scratch. So I reformatted both of the SD cards and followed allow with BTT’s installation guide. I was able to get the MCU ID but when I would run the “make flash FLASH_DEVICE…” command I would receive the following error 255
After I run the make flash command the ls /dev/serial/by-id/ command gives me the “no such file of directory” error until I power cycle the board and then I can get the mcu ID again. I verified that the printer.cfg and generic_m8p.cfg files both had the mcu id placed in the correct areas where they are supposed to be. When I log into the board via a web browser I receive the Klipper error “mcu ‘CB1’: Unable to Connect.” Checking the klippy.log it shows:
mcu ‘CB1’: Unable to open serial port: [Errno 11] Could not exclusively lock port /dev/serial/by-id/usb-Klipper_stm32g0b1xx_33001C000B504B4633373520-if00: [Errno 11] Resource temporarily unavailable
Searching for this error brought me to this klipper forum post: Multible klipper(4) instances on btt-pi but I do not understand Sineos’ reply about printer boards registering with the same connection? I have also noticed that the firmware.bin file is not renaming itself to firmware.cur (not sure if this is supposed to happen before or after the make flash command)
I am pretty much at a loss for where to go next. I feel like I have read every post online and reinstalled all of the software like a million times. Any assistance or guidance would be greatly appreciated. Thanks.
@LifeOfBrian Thanks for the link. I tried to flash the board by putting it into DFU mode and verifying that it was set to DFU mode with the lsusb command
and then running through the flash commands using the DFU model address. More “things” happened but unfortunately it ended with the same Error 255 line. I noticed that after I would run the flash commands the directory for the MCU ID would disappear and then once the board was power cycled it would be there again.
I then followed the link that you posted and followed along with his walk through. I flashed a new OS, followed along with all of his commands for CANBUS, and it hung up at the “Attempting to connect to bootloader” line for about a minute or two before it threw an error and the entire flash error-ed out.
Since it hung up on the “connect to bootloader” line I thought that perhaps the bootloader was corrupted. So I started from scratch once again following the BTT guide, and once I created the firmware.bin file I ran the command given in this video (https://www.youtube.com/watch?v=37z1jnZgLsQ) to supposedly reflash the bootloader. No dice, still not working, and I am not not even able to get the MCU ID when running the ls /dev/serial/by-id/ command as I receive the directory not found. In a last ditch effort I just unplugged everything and reseated the CB1 board and still nothing is working. Is there anything else that I can even try or is this board just toast? I’m at my wits end with this. Thanks again for your help.
Your screenshot here looks like it got flashed Download done and the lines above and after that it got some error - a pretty common one is that reseting the board via dfu back to run-time mode (your just flashed klipper mcu fw) does not work and will result in the Error during download get_status.
Just as a test you can try after getting this eroor again pressing the Reset/RST button on your board and test if it appears at /dev/serial/by-id/usb-Klipper...
