Zero stuck on boot screen

[Vergo]

@cardoc

if someone needed to flash the main or extra are there precompiled versions someplace? If not what are the parameters to put into “makemenu” to compile them?

I haven’t seen any other precompiled firmware other than that one anywhere so far. Even for that one there appears to be only two versions existing as all 1.4.x versions have the same checksum while 1.3.8 is different.

As for compiling yourself, check /home/sovol/klipper/.config and /home/sovol/klipper/.config750. I suspect those are the configs that have been used. One is for the stm32f103xe chip and the other for stm32h750xx. No idea to which components these map to but looking from each pcb should expose which STM32 chip there is, if any.

[KeiffTi]

im not sure how to do that. am i supposed to open console on the computer and get into the printer that way?

[Vergo]

@KeiffTi - assuming you have Windows, get an SSH client from Download PuTTY: latest release (0.83) for example, connect with it to your printer’s ip by selecting the SSH as protocol (not telnet) and port 22 (which should be the default). Use sovol as username and sovol as password to get in the command line. After that, those instructed commands will work.

[KeiffTi]

its not recognizing the MCU is connected is my assumption. im going to also assume that this is because its fried?

[Vergo]

@KeiffTi

its not recognizing the MCU is connected is my assumption. im going to also assume that this is because its fried?

That or there’s a loose wire or connector somewhere in your printer.

[KeiffTi]

the led on the board is lighting up blue like it has since i first powered it up. i checked the wiring before but i havent tried disconnecting and reconnecting them

[Vergo]

On page 23 of the user manual there’s a connection marked “Can communication interface”. That’s the one you’d want to check. Then on the next page (24) the matching connection is marked “Motherboard communication” for the nozzle adapter board.

[KeiffTi]

can is connected to whats labeled extruder on the mobo.

[cardoc]

Could be the motherboard too. Takes 2 (or more) nodes to make a network. The CAN transceiver chip that powers up first will send clock signals and an ID but not much happens until a 2nd device signs on.

Open Mainsail, go to the [Machine] tab and click [Devices]. I’m not sure how Linux treats CAN interfaces AND it is likely there is a USB<>CAN or RS232<>CAN translator in the chain.

Someone with a functional Zero - Query devices in mainsail and tell us what you see

[Vergo]

Doesn’t allow queries for assigned CAN devices:

USB shows CAN adapter:

[Vergo]

@Vergo

I suspect those are the configs that have been used. One is for the stm32f103xe chip and the other for stm32h750xx. No idea to which components these map to but looking from each pcb should expose which STM32 chip there is, if any.

This answers that question which chip is where:

[KeiffTi]

same but diff location

[KeiffTi]

i now have a different MCU error after the firmware shift

[cardoc]

Here is printer.cfg direct from Sovol

Extracted from SV08mini_Update_Package-05-20_1-4-7.deb

Contains no refrences to extra_mcu
printer.cfg (7.0 KB)

[KeiffTi]

yet another. is that one from comgrow that i can try and ssh the firmware into?

[cardoc]

For those playing along the extra_mcu is the same hardware as the extruder_mcu

Firmware version 1.3.8

[mcu] 
canbus_uuid: 0d1445047cdd

[mcu extra_mcu]
canbus_uuid: 61755fe321ac

[lis2dw]
cs_pin: extra_mcu:PB12
spi_software_sclk_pin: extra_mcu:PB13
spi_software_mosi_pin: extra_mcu:PB15
spi_software_miso_pin: extra_mcu:PB14
axes_map: x,z,y

Firmware 1.4.1

[mcu] 
canbus_uuid: 0d1445047cdd

[mcu extruder_mcu]
canbus_uuid: 61755fe321ac

[lis2dw]
cs_pin: extruder_mcu:PB12
spi_software_sclk_pin: extruder_mcu:PB13
spi_software_mosi_pin: extruder_mcu:PB15
spi_software_miso_pin: extruder_mcu:PB14
axes_map: x,z,y

Both are from the respective printer.cfg files

So the error is still the toolhead not found

[KeiffTi]

could it be possible that the older firmware is the issue? I could try the 1.4.7 firmware just to make certain my toolhead board or the Mobo is cooked.

[Lion]

I don’t mean to disrupt this thread. I admit I don’t know much about Klipper, you all are way smarter than me…so far

So I’m gonna throw 2 other options on the hardware side of things.
They might be stupid, but sometimes stupid is smart or goes down another path.

1: He posted that the LED is working on the board, but still thinks the board might be the issue.
There are 2 fuses for main power on the board, if 1 is blown…would the LED still light up..??

2: Could the Reset button be a 1 time use or just broken..??
Making the printer think it’s still down/being pushed..??

[cardoc]

Why would 2 identical printers show the soldered on CAN <> USB translator on different USB ports?
@KeiffTi do you have ANYTHING plugged into USB?

Also it seems CAN is able to read the microcontroller model number

Try this:
Pull all the power for the machine
Now that you have network working disconnect anything hooked to to ANY port besides Ethernet
Boot up the printer
Connect VIA SSH and que up the flash command (wait)
Unplug 24V power from toolhead
Wait 30 seconds
Plug in 24V and start the flash process

See if the bootloader still refuses to talk

[cardoc]

Lion has an excellent point. Unplug the display and try and boot. I don’t know if Klipper demands a response from the screen to boot but a different error would at least break the monotony.