/dev/btt-manta-m4p no such file or directory
I went through the main trouble shooting list, and have confirmed wiring / no shorts. Everything is properly updated w/ updating RatOs first. My moonraker log is fine but my klippy log gets stuck. I properly went through the cfg and have the m4p uncommented (and all my hardware). Do I need to upload a bin file for the m4p to get past this error, or is this telling me I still have a physical error somewhere?
![No description](https://cdn.answeroverflow.com/1076641379867959326/41668c6b00d6a7a4c9bec87bc8fd477c.png)
43 Replies
Did you flash your manta board?
Not the cb1 attached to the manta, but the manta board itself
Ah. nope.
Since you are using the beta, be sure to use the beta documentation
All board firmware related things are done through /configure now
still in a spot of trouble, can't get it to make the bin file
![No description](https://cdn.answeroverflow.com/1076649126365761616/d99e5193b8b0bc45d0fa6022129d67eb.png)
Update the configurator through mainsail and try again
Actually update RatOS too (through mainsail)
(both were a part of the instructions btw)
everything was already updated before I did this.
![No description](https://cdn.answeroverflow.com/1076649601169367120/0c5b8f0d0e7eb44c3e2d2c4f83028866.png)
Okay, then it's a new thing. What's the issue exactly?
Trying to flash the control board. im in the configure, klipper is red and moonraker is green in the corner, and the configure says manta M4p was not detected so it won't compile the firmware so I can laod the firmare.bin file onto the SD card.
Did you click the "compile firmware" button?
Did you click the button?
yes. and nothing happens
Just a sec
Works fine here
Open developer tools