Configure can't find MCU but lsusb does
As the title states....
Been through all of the manuals, firmware updates, cable swaps, etc. etc. etc. over the past 24 hours. Always comes down to Configure does not see any MCU while lsusb shows they are connected.
rpi 4b
octopus v1.1
ebb42 v1.2
14 Replies
Show the results of
lsusb, ls -la /dev/serial/by-id/* and what board you're selecting in the configurator (there are 2 octopus's, one is for the STM32F407 the other for the STM32F446).foreign-sapphire•2y ago
pi@ratos:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 009: ID 1d50:614e OpenMoko, Inc. stm32f446xx
Bus 001 Device 012: ID 1d50:614e OpenMoko, Inc. stm32g0b1xx
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@ratos:~ $ ls -la /dev/serial/by-id/*
lrwxrwxrwx 1 root root 13 Apr 19 00:28 /dev/serial/by-id/usb-Klipper_stm32f446xx_300056000E51313133353932-if00 -> ../../ttyACM0
lrwxrwxrwx 1 root root 13 Apr 19 00:32 /dev/serial/by-id/usb-Klipper_stm32g0b1xx_38002E000C50425539393020-if00 -> ../../ttyACM1
Did you flash it using the SD card?
foreign-sapphire•2y ago
that is all i could do was sd card flash, configure just sits here:
Did you confirm that the file changed to firmware.cur?
foreign-sapphire•2y ago
foreign-sapphire•2y ago
yes, sd card showed .cur afterwards
Your serial indicates you didn't flash it
Try a different SD card.
And follow the steps in the configurator (formatting correctly is important)
also step 1
foreign-sapphire•2y ago
hmm, ok, I will find app to reformat the sdcard. If you could, please explain why the MCU would update the file suffix to '.cur' if it was not successful in performing the flash process? Afterall, that is the benchmark given in all of the documentation.
For some reason it'll write bad data and be like "we good", but in reality it's not. That's about as much explanation i've got, i've never been able to reproduce it myself, but y'all seem to get it quite often and it's always fixed by following the steps in the documentation 😄
Actually there's one other fix, and that's trying different SD cards (but i'm sorta suspecting it's just missing steps in the other tries, but i dno).
If you're on windows, it can do this out of the box btw. Right click -> format in the explorer.
foreign-sapphire•2y ago
I used the windows format to begin with.
That should be fine
Just use the settings in step 2
foreign-sapphire•2y ago
eh, I find it odd that you are referring to steps. The steps in the ratrig instructions guide you through the build of the machine, and assembly of electronics, then send you to the ratos pages, where it then tells you that is is highly recommended that you follow those directions before the build instructions, while at the same time not actually labeling or outlining steps, rather it is list of procedures with caveats, which actually increase the likelyhood that people will mis-understand the directions layed out in the process, while still not finding the step numbers that you seem to be referring to.
digging through the ratos website I found no other references to steps, so reading ahead through several pages I went ahead and had the rpi compile the firmware for everything, reformated the sdcard, downloaded the btt-octopus-v1.1 bin and put it on the sdcard, flashed the octopus, and it did not work at all, no status lights and it did not show up in lsusb or ls serial, I put the btt klipper firmware on the sdcard then tried the flash process again and now the status light is back and lsusb ls serial from rpi work again
So, I have lost track of the flash attempts at this point, I just hit the compile firmware again as shown above, loaded it to the sdcard and flashed the octopus again. This time it worked.
look at the screenshot you posted.
I'm talking about steps in the text in the configurator
Good 👍