Unable to connect to MCU after update

Thanks Sineos and NAPCAL so far.

I downloaded the bootloader and programmer
uploaded the bootloader, compared memory with the bootloader file, it is ok.
so i assumed the bootloader is uploaded, but stil i can’t no connection with the normal usb.

very strange.

Isn’t it not strange that when i type "ls /dev/serial/by-id/"
i get
ls: cannot access '/dev/serial/by-id/
': No such file or directory

when i look with winscp on the odroid, there is no dev/serial map

Is it an possibility to connect the board with uart ?
i read something about that, i only don’t know how i have to connect the odroid and skr 3 ez board

The SKR3 have a push button switch to switch the USB-B connector between USB and CAN bus, try switching this.

Yes, i do know this button, an i have already tried to switch between USB and CAN BUS, but also this has no effect.

I realy don’t understand what is going on, the only thing i have done is on the mainsail machine page installed the klipper, klipperschreen updates, afther that there was no communication with the MCU

After that i have updated Armbian on the odroid C2

Maybe some other tips what i can try ?

  1. Do you have re-flashed a new klipper.bin after doing the bootloader stuff?
  2. Concentrate on the dmesg output instead of messing around with the ls command. As long as your board does not show up in dmesg all other actions are futile
  1. yes, i have reflashed a new firmware.bin after the bootloader, filename has changed from firmware.bin to FIRMWARE.CUR
  2. this is the last section of the dmesg output first rules usb 1-1: reset high speed … (many rules)
    and then pushing the buttons to go into dfu mode
[38675.710880] usb 1-1: reset high-speed USB device number 2 using dwc2
[38676.570766] usb 1-1.4: new full-speed USB device number 5 using dwc2
[38676.673299] usb 1-1.4: not running at top speed; connect to a high speed hub
[38676.679952] usb 1-1.4: New USB device found, idVendor=0483, idProduct=df11, b                                                                                                   cdDevice= 2.00
[38676.679972] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber                                                                                                   =3
[38676.679980] usb 1-1.4: Product: DFU in FS Mode
[38676.679986] usb 1-1.4: Manufacturer: STMicroelectronics
[38676.679992] usb 1-1.4: SerialNumber: 306235623231
[38677.005986] usb 1-1.4: USB disconnect, device number 5
[38677.438839] usb 1-1: reset high-speed USB device number 2 using dwc2
[38677.942736] usb 1-1.4: new full-speed USB device number 6 using dwc2
[38678.045309] usb 1-1.4: not running at top speed; connect to a high speed hub
[38678.052246] usb 1-1.4: New USB device found, idVendor=0483, idProduct=df11, b                                                                                                   cdDevice= 2.00
[38678.052276] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber                                                                                                   =3
[38678.052283] usb 1-1.4: Product: DFU in FS Mode
[38678.052289] usb 1-1.4: Manufacturer: STMicroelectronics
[38678.052294] usb 1-1.4: SerialNumber: 306235623231

this is the dmesg ouput in usb mode:

[43893.339935] usb 1-1: reset high-speed USB device number 2 using dwc2
[43894.943885] usb 1-1: reset high-speed USB device number 2 using dwc2
[43897.675881] usb 1-1: reset high-speed USB device number 2 using dwc2
[43899.267823] usb 1-1: reset high-speed USB device number 2 using dwc2

Try reflashing the board with the whole procedure again. Once you have flashed the bootloader you should repower the board and then never again touch the BOOT button.
We do not need nor do we want the board to be in DFU mode. This is for programming and nothing else.

i have repeated the complete proces, but it is al the same.
first flashed the bootloader in dfu mode
repowered the board
firmware.bin on the sd card
flashed firmeware bin is renamed to firmware.cur

i think i have done the hole process right. I don’t know anymore

i have also a bigtreetech touchscreen with an usb port on it, is it possible to acces the controller board trough the screen usb port?

@Dutchronnie

Please provide us with a screenshot of the Klipper firmware settings you are using; thanks.

Also, provide the processor number STM32xxxx

1 Like

napcal, THANKS

This was very very stupid of me.
I thought all the time i had a STM32H743 processor, but it was a STM32H723

I do see some red lines in the dmesg

so i compiled the klipper firmware again, and now i get an MCU id.
but when i want to connect klipper i get an error again. see the screen shot.

1 Like

Well, the error message should be self-explaining. You have a mismatch between the different Klipper versions. Recompile and install the Linux process as per RPi microcontroller - Klipper documentation

I think i understand, i have to update the firmware for the odroid to use the eccelerometer.

I have to search the net how to do that, it is a time ago i did this, and never thought about this.

Just follow the information given in the link above

Thanks Sineos for all your help.
Without you i think i have ordered a new board.

Klipper an the controllerboard are up and running again :grinning:

1 Like