v0 display stuck at DFU mode after upgrade

[stlfatboy]

Follows flash guide from voron hardware github repo, but ls /dev/serial/by-id/* not showing the device.

Found it boot into DFU mode again.

Using 0.12 klipper

Detailed log can be found here

 

[transonic_gecko]

You won't find it in /dev/serial/by-id/*. Assuming you compiled the firmware for the STM32 board and it flashed successfully, then you need to remove the jumper that you installed and press the reset button on the board. This will bring it out of DFU mode and it will attempt to boot Klipper.

 

[timmit99]

Follows flash guide from voron hardware github repo, but ls /dev/serial/by-id/* not showing the device.

Found it boot into DFU mode again.

Using 0.12 klipper

Detailed log can be found here

Did you remove the boot jumper after flashing? Can you share a screenshot of your `make menuconfig` here?

 

[timmit99]

You won't find it in /dev/serial/by-id/*

you 100% will find it there after flashing with klipper as long as the menuconfig is set correctly and you have removed the boot jumper.

 

[stlfatboy]

Did you remove the boot jumper after flashing? Can you share a screenshot of your `make menuconfig` here?

yes, the jumper is removed.

 

[transonic_gecko]

you 100% will find it there after flashing with klipper as long as the menuconfig is set correctly and you have removed the boot jumper.

You're absolutely right, my apologies -- it shows up as usb-Klipper_stm32f042x6_*. I knew I never had an issue confusing the identifier with my rp2040 boards, so I had mistakenly thought that it didn't enumerate there.

At any rate I agree, hopefully it's just that he forgot to remove the jumper.

 

[transonic_gecko]

yes, the jumper is removed.View attachment 3624View attachment 3625

Check the box next to Support external sensor devices and uncheck the box next to Support software based I2C "bit-banging". Then recompile and reflash.

 

[stlfatboy]

you 100% will find it there after flashing with klipper as long as the menuconfig is set correctly and you have removed the boot jumper.

I had tried like 20+ times. There is only once it successfully booted and recognized by klipper.

 

[transonic_gecko]

I had tried like 20+ times. There is only once it successfully booted and recognized by klipper.

See my post above -- your Optional Features are set incorrectly.

 

[stlfatboy]

See my post above -- your Optional Features are set incorrectly.

Still no luck with these configs

Maybe it is a hardware failure?

 

[transonic_gecko]

Your config is still wrong. Enable SPI bit-banging, but not I2C.

 

[stlfatboy]

Your config is still wrong. Enable SPI bit-banging, but not I2C.

I have tried both, same result

 

[transonic_gecko]

I have tried both, same result

Try it again, with the correct configuration.

 

[stlfatboy]

Try it again, with the correct configuration.

Same result here with no i2c and spi bit-banging, still boot into dfu mode

 

[transonic_gecko]

Which command are you using to flash the board? Can you send us that?

 

[stlfatboy]

Which command are you using to flash the board? Can you send us that?

#lsusb
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 049: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
...
#make flash FLASH_DEVICE=0483:df11
...
sudo dfu-util -d ,0483:df11 -R -a 0 -s 0x8000000:leave -D out/klipper.bin

dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Opening DFU capable USB device...
ID 0483:df11
Run-time device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuERROR, status = 10
dfuERROR, clearing status
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 2048
DfuSe interface name: "Internal Flash "
Downloading to address = 0x08000000, size = 24576
Download [=========================] 100% 24576 bytes
Download done.
File downloaded successfully
dfu-util: Error during download get_status

Failed to flash to 0483:df11: Error running dfu-util

If the device is already in bootloader mode it can be flashed with the
following command:
make flash FLASH_DEVICE=0483:df11
OR
make flash FLASH_DEVICE=1209:beba

If attempting to flash via 3.3V serial, then use:
make serialflash FLASH_DEVICE=0483:df11

make: *** [src/stm32/Makefile:111: flash] Error 255

 

[stlfatboy]

Which command are you using to flash the board? Can you send us that?

I found that if I enable bootloader to 4KB in the config, it will leave dfu mode after flash.
But still boot to dfu if I press reset

 

[transonic_gecko]

Hm. Shouldn't need a bootloader. Everything looked correct to me in the code snippet above, but dfu-util is reporting a failure during the flash...

 

[stlfatboy]

Hm. Shouldn't need a bootloader. Everything looked correct to me in the code snippet above, but dfu-util is reporting a failure during the flash...

Thanks for the reply, I returned the display board to seller

 

[BallisticTech]

Hm. Shouldn't need a bootloader. Everything looked correct to me in the code snippet above, but dfu-util is reporting a failure during the flash...

I believe the DFU Util error is a known problem and mentioned in the V0 Display Docs

Voron-Hardware/V0_Display/Documentation/Setup_and_Flashing_Guide.md at master · VoronDesign/Voron-Hardware

Cool Hardware designed by the Voron Design group. Contribute to VoronDesign/Voron-Hardware development by creating an account on GitHub.

github.com