CB2 won't boot after canbus setup

[hitman47]

Basic Information:

Printer Model: custom
MCU / Printerboard: Manta m4p
Host / SBC: cb2
non klippy.log cause it’s not klipper related and can’t boot…

Hi guys.

Setting up a CB2 with V3 beta image .
Copying from sd to emmc is ok.
Installing klipper, moonraker etc is ok.

When I try to install my ebb36 with u2c, every time after following the can interface config from Esoterical canbus guide, the CB2 won’t boot!

I’m lost and not techy enough to troubleshoot that…I can’t figure out what’s wrong.

Anyone here having a Manta board with CB2 running a canbus?

Any help appreciated thanks.

[EddyMI3D]

@hitman47

Esoterical canbus guide,

Maybe the guys who made that guide could/should help you?

[mykepredko]

I run with Mantas and CB2s all the time - but I don’t use the eMMC.

Could you try without the eMMC with an SD Card that is at least 64GB in size.

[hitman47]

@mykepredko it happens too after a sudo update & upgrade… seems the BTT system is not stable. just wanted to try the rkdevtool method but my computer doesn’t even recognize my m4p. btt is such a pain sometimes. I’ll go without emmc if I have no choice left…

[mykepredko]

Could you explain a few things that you are doing in more detail:

First off, what OS Image are you loading into the CB2?

@hitman47

@mykepredko it happens too after a sudo update & upgrade…

Can you explain the process you’re using to set up the CB2?

I normally load the BTT OS Image onto an SD Card (with the system name/WiFi credentials specified in the system.cfg file).

Once the system boots up and I can log into it (either using WiFi or Ethernet with the “biqu” UserID), I do:

sudo apt-get update
sudo apt-get upgrade -y
sudo apt-get install git -y

Then I install/run KIAUH, load Klipper, Moonraker and Mainsail followed by going into 4) [Advanced] and creating the Klipper firmware image and loading it into the Manta using DFU.

@hitman47

just wanted to try the rkdevtool method but my computer doesn’t even recognize my m4p.

Again, could you explain this process and why you’re using RKDEVTOOL rather than DFU or the SD Card bootloader method?

Please be as explicit as possible with what you’re doing and what you are seeing.

[hitman47]

So basically, I follow the instructions from BTT.

Trying to use the latest V3 minimal image for CB2.

Flashing the image on an SD card.
Following the steps to create user admin password, select bash etc.
Flashing the image to emmc via sudo nand-sata-install.

During any installation attempt I tried, the CB2 freezes at one point and won’t boot anymore.

It happens randomly on a fresh empty image flash :

• 1 time after installing Klipper with KIAUH; or
• 1 timeafter following the Esoterical guide; or
• 1 time on a basic image with nothing installed, happened after a sudo update&upgrade only…

On a forum, someone advised to clean erase the CB2 with the rkdevtool. I tried with putting the micro switches 3&4 ON, but my computer doesn’t even detect the cb2.

Seems any upgrade or modification of their system leads to the CB2 not booting anymore.

The fact it isn’t recognized by my computer leads to a faulty device maybe.

Thank you for trying to help me.

[hitman47]

@mykepredko so I reinstalled everything on the SD only.and it works! The emmc or bootloader on the CB2 seems f***** up.

Thanks for your time and help.

[hitman47]

And Here we are screwed again! Got everything running until canbus configuration…

Got an error: “MCU ebb an unable to connect to can”.

So I tried going back to Esoterical guide.I missed that step but could flash my ebb with klipper, thinking it was maybe python related so I ran:
Sudo apt update
Sudo apt upgrade
Sudo apt install python3 python3-serial

Now I’m screwed again, after these 3 commands, the sd now doesn’t boot anymore …

[mykepredko]

Have you tried going back through the Esoterical guide again without missing the step?

I’ve found that if you miss a step and try to go back, you often have a problem with the host system.

Sorry it’s giving you so much grief.

[hitman47]

@mykepredko figured out it’s a bug with the board and their linux Bookworm. Used the v 1.0.5 image on Bullseye and everything went well. Thanks again for your help Sir.