Rappetor / Sovol-SV08-Mainline

Getting the Sovol SV08 onto mainline Klipper
GNU General Public License v3.0
82 stars 24 forks source link

Klipper Error: mcu 'mcu': Unable to connect #73

Open VdueHub opened 1 day ago

VdueHub commented 1 day ago

OS: Debian GNU/Linux 11 (bullseye) crowsnest v4.1.9-1 klipper v0.12.0-317 mainsail v2.12.0 mainsail-config v1.2.1-0 moonraker v0.9.3-0

I followed your guide from A-Z. Klipper Mainline install w/o issues. Katapult flash no issues. update_klipper_mcus_sv08.sh updated according to manual. Needed several attempts to run update_klipper_mcus_sv08.sh, compile and flash. Host compiled well, but got stuck at: Attempting to connect to bootloader. Several new boots it flashed host_mcu_klipper.bin and toolhead_mcu_klipper.bin. Now Klipper complains: mcu 'mcu': Unable to connect. If I flash back to the original host and toolhead bins everything works. Now I am a bit clueless.

Rappetor commented 1 day ago

It's rather difficult to diagnose from here but first make sure your serial id's are correct in the the printer.cfg (so they start with /dev/serial/by-id/usb-Klipper_stm32f103xe_ and then contain the correct serial). This seems to be the most common thing when you get mcu connection error. Please make sure you are not using the ttyACM serial in the printer.cfg. And please make sure you have the correct serial for both (if you reverse the serials the toolhead heater will enable 100% and you won't see it, so make sure they are correct; see the warning under step 8).

Some things that have happened in the past and are worth checking: Something that can lead to problems flashing (via the script) as well is not having used 'full chip erase' manually in the STM32CubeProgrammer when flashing katapult (there is an auto option you can select, but that does not seem to do the trick for some reason). But then I am not sure why it was able to flash the host after some new boots 🤔 Although it said unable to connect to mcu, so maybe that wasn't flashed properly after all (maybe it was still in katapult dfu mode?).

When flashing the firmware via the script make sure the programmer is no longer connected (this has also lead to some flashing issues). And also the klipper service is stopped (the script should do this automatically but who knows).

Otherwise if you can post the klippy.log here that would be helpful, maybe we can see something in there.

Also if you have the possibility to go to the Sovol discord that could be handy for you. There you will probably get a faster response and it's more easy to help in general. I'll copy/paste the url from Froh from the other issue (think this is the unofficial sovol discord): https://discord.gg/zzu564CKCe

Rappetor commented 1 day ago

Oh and just to be sure/thorough, you have to flash katapult (with the stlink) on both mcu's. The toolhead mcu ánd the mainboard mcu, otherwise the update script can't update them both as well.

VdueHub commented 1 day ago

Thanx for the quick response, I'll continue on Sovol Discord.

Just to close it here: /dev/serial/by-id/usb-Klipperstm32f103xe with correct serials is done and triple checked (BTW documentation wrt usb-Klipper or usb-katapult is not very clear) I did 'full chip erase' and and get after programming: Download verified successfully (printer is powered off) I made sure that the programmer is not connected with script flash

VdueHub commented 1 day ago

somehow, the discord disconnected me and I can't get back in. The change to 12345 and a hardware reboot did the trick

On 12. Oct 2024, at 15:17, Richard @.***> wrote:

Oh and just to be sure/thorough, you have to flash katapult (with the stlink) on both mcu's. The toolhead mcu ánd the mainboard mcu, otherwise the update script can't update them both as well.

— Reply to this email directly, view it on GitHub https://github.com/Rappetor/Sovol-SV08-Mainline/issues/73#issuecomment-2408562509, or unsubscribe https://github.com/notifications/unsubscribe-auth/BEJWGDPNAABM3FWHRXZIIFLZ3EONJAVCNFSM6AAAAABP2LSDFOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBYGU3DENJQHE. You are receiving this because you authored the thread.

Rappetor commented 1 day ago

Weird that Discord is acting up. Oh wow, so it changed the serial to 12345 but after changing that in Klipper it works? That's awesome! But also very strange haha (it should not change the serial to 12345..).

Maybe after a firmware update later it changes back to it's normal serial, who knows..