Direct usb flashing

Sovol SV07 Plus
1

Does the SV07 plus mainboard support direct usb flashing, im getting a klipper error that it cant connect to mcu, ive tried to reflash it with sd card that is on the side of the mainboard but its not taking it, and im not sure what firmware its on. Ive looked over the board and checked the connections, and ive even tried a new cable but cant seem to get it right

2

No it does not (in native configuration) support USB flashing.

Rename your .bin file on the card. Name can be anythingyouwant.bin EXCEPT sameaslasttime.bin

3

so i cant just keep renaming in firmware.bin, it has to be something different then last time.

4

Exactly. To prevent reflashing over and over if someone leaves it on the card the bord remembers and IGNORES the last used filename. I use the 6 digit date plus a letter. A for 1st try B next and so on

I’ve never seen it but there are reports that high capacity cards can fail even formatted fat32. Use the smallest card you have

5

can i use the sd card slot on the mainboard itself, or use one of the usb ports on the mks pi, also where can i find the settings for the config to make the .bin file

6

Has to be on the main board (un screw the front panel. unplug the usb at the klipad as sometimes power backfeeds keeping the board “awake”. Insert the card, switch on the PS, wait 90 seconds and power off. Remove card and reconnect usb and hope…

7

It’s a no go, still wont take a firmware reflash, i’m not sure what i can do at this point.

8

SSH into the clipad and do a lsusb

9

it reports back
mks@mkspi:~$ lsusb
Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 1a86:e5e3 QinHeng Electronics
Bus 002 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

11

mks@mkspi:~$ lsusb
Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 1a86:e5e3 QinHeng Electronics
Bus 002 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

12

What does

lsusb /dev/serial/by-id/*

get you?

13

mks@mkspi:~$ lsusb /dev/serial/by-id/*
Usage: lsusb [options]…
List USB devices
-v, --verbose
Increase verbosity (show descriptors)
-s [[bus]:][devnum]
Show only devices with specified device and/or
bus numbers (in decimal)
-d vendor:[product]
Show only devices with the specified vendor and
product ID numbers (in hexadecimal)
-D device
Selects which device lsusb will examine
-t, --tree
Dump the physical USB device hierarchy as a tree
-V, --version
Show version of program
-h, --help
Show usage and help

14

i also swapped out the cable and I’m still getting the same thing

15

Okay we’ve reached the end of my ability

I think the serial converter (built into motherboard) is connecting but the board is not attaching a serial connection to it.

Double/tipple check the makemenu settings and remake a bin file

16

I’m not sure what the makemenu setting are, I’ve seen a couple of different one, how do i know what’s what.

17

i just checked it again and it reported back this
mks@mkspi:~$ ls /dev/serial/by-id/
usb-1a86_USB_Serial-if00-port0

18

It’s the same on my printer.cfg file as well.

20

I’d still reroll the firmware

21

MT SV07 uses this

#To use this config, during "make menuconfig" select the
# STM32F103 with a "28KiB bootloader" and serial (on USART1 PA10/PA9)
# communication.

# See docs/Config_Reference.md for a description of parameters.
22

I think at this point the board might be bad. The back story is a few days ago I started a print and came back 30 min’s later to the printer off mid print. It wouldnt come back on, I checked the wireing and couldnt find anything wrong. when i put it back together and tried it again it fired back up. So I had the stupid idea that I would try and install klipper a different way by using a spare emmc i had, I flashed the mcu but it couldnt connect. Now Ive sence gone back and installed the firmware that sovol has but for some reason the mcu wont take a firmware flash, when i pull out the sd card i use the firmware file doesnt change leting me know it took the firmware, I really do thank yall for the help, ive learned a good bit about this printer and some setups for klipper. The sad thing is Ive had this printer for a while and have worked on it more then printed.