MCU not connecting

Does it work with the rpi4? I've removed the power jumper on my octopus 1.1, installed the firmware which returned the .cur file. Is it an issue with the cable that came with the octopus maybe? I unplugged everything from the board except for the power cables and steppers. I remembering having this issue as well on the vcore 300 (This is a 400) and I ended up wiring the RPI to the board using the rx/tx wires. I would like to get the USB running now.
15 Replies
blacksmithforlife
blacksmithforlife•2y ago
it works fine with rpi4 (that is what I am using) have you worked through https://discord.com/channels/582187371529764864/1046952693480038500 ? it deals with a bunch of the common issues
AsicResistor
AsicResistorOP•2y ago
Yes I worked through those except for removing all stepper wires and the power wires at the bottom When I run the dmesg -w command and I plug and unplug the board, nothing changes
blacksmithforlife
blacksmithforlife•2y ago
I have seen issues where the firmware that was flashed was wrong, or even though it changed to .CUR it didn't really complete and needed to be flashed again have you also tried different USB cords and different ports on the PI?
AsicResistor
AsicResistorOP•2y ago
I have flashed 2 times already, I can try it again tomorrow. I tried different ports but not another cable yet. I would think the one supplied with the octopus board should be good? Or is it a power only cable?
blacksmithforlife
blacksmithforlife•2y ago
Not sure, but there are USB cables that are power only you can also try plugging in something else to the USB ports and make sure it is showing up in dmseg -w
AsicResistor
AsicResistorOP•2y ago
Yes that works It is probably a power cable supplied with the Octopus board. I'll report back tomorrow Hmm nevermind it's not that, when I connect my phone to the octopus cable the pi recognises it as the pixel6 The jumper that needs to be pulled out is the one in the middle of the board marked with power right>?
blacksmithforlife
blacksmithforlife•2y ago
you need to remove all the jumpers unless it has a green box over it in the wiring diagram https://os.ratrig.com/docs/boards/btt/octopus-11#wiring so only those 11 green boxes should have jumpers everything else needs them removed
AsicResistor
AsicResistorOP•2y ago
I did that, but the part cooling fan port has the jumper different and only the blue pwm wire as in the guide for the 4028 fan Endstops are also wired correctly I don't have a controller fan either, should I remove the jumper above that port?
blacksmithforlife
blacksmithforlife•2y ago
while you are troubleshooting this I would disconnect everything except for power to octopus and USB to PI. That way you aren't also potentially dealing with shorts or other electrical weirdness
AsicResistor
AsicResistorOP•2y ago
No description
AsicResistor
AsicResistorOP•2y ago
I disconnected everything except for the power on the board (other cables are disconnected on the other end) Still nothing being detected on the usb ports of the pi I also tried a rpi 3b but same result Also reflashed the board and I have the .cur file on my sd card I'll do a reflash of the rpi ratos as well to compile the firmware for the board again Fixed it, after compiling the firmware.bin through ssh I got a .bin file that was half of the one that I generated through my first RatOS install. The new .bin was around 25kb en the older one around 40kb Now it's connecting!
blacksmithforlife
blacksmithforlife•2y ago
@miklschmidt take look above, that doesn't make sense to me
miklschmidt
miklschmidt•2y ago
Me neither 🤨 literally the same process (same script).. I have never been able to reproduce this either. First compile has always worked for me, and i've done this hundreds of times.
EternalPath
EternalPath•2y ago
@blacksmithforlife @miklschmidt I just experienced the exact same problem. Solved the same way as @asicresistor . Also noted the difference in file size between the auto compiled firmware file and the manually compiled firmware file. it's 2 am now stare
miklschmidt
miklschmidt•2y ago
I believe 2.0 will fix this

Did you find this page helpful?