Manta M8p 2.0
@jurassicplayer | VC3.1 300 setup wont work and it wont detect the board even whan flashed manually, compile firmware doesnt work either
259 Replies
I guess the first thing we can check is to see what serial id the board has now
You'll need to be SSH'd into the CB1
alight im inside
Then just do
ls /dev/serial/by-id/any specific directory i have to do it?
nope, it's an absolute path
Try
lsusb
That's kind of odd
Looks like the CB1 sees the board at least
though I don't know why it didn't populate a serial
You tried to compile klipper manually right? What were the menuconfig settings that you picked?
yes i choose the ones from the manta v2 pdf from btt github
Did you set anything in USB ids?
nope
should i try to reflash?
Yeah, maybe we'll try from there first
get the latest klipper
Err, do you know how to pull the latest stuff using git?
nope
So first we need to change to the klipper folder
cd ~/klipperi in the folder
And then run
make clean like twice
that just cleans up the build files
and then we pull the latest files from github
git pullok
Should look something like that
it says flashing connected mcus
what does?
git pull?
that command
Well that wasn't expected, but sure.
now do the
make menuconfigok.
All the same settings that you've already seen
the bootloader has no other options only the 128kb doesnt matter that i doesnt say
Bootloader offset (128KiB bootloader (SKR SE BX v2.0))?
And then in USB ids we are going to change a small thing
untick the
USB serial number from CHIPID
and then enter a new USB serial number
btt-manta-m8p-20
great, now you can press q to quit
and save the config
done
now make i guess
run
make
yeahok. dumb question. why change the serial?
The main reason is for RatOS to be able to auto-flash
oh ok
It's basically looking for that serial to mount to the static location I was mentioning yesterday
why do we need ratos to autoflash?
I mean, you don't really need to
It's just convenient
When you press update in Mainsail and update klipper, it will pull the latest version, build it, and flash it onto your board
wouldnt that be dangerous incase the ne klipper files have issues?
Well, if you aren't going to be vetting the files when updating manually, then there is little difference
oh ok
well is not flashing xD
let me try in the other board
You haven't sent the flashing command yet
we just built the firmware
i downloaded the firmware and used the sd card
maybe trying dfu?
Oh, and the sd card has firmware.CUR now?
or is it still firmware.bin?
still firmware.bin
hold on
Did you press reset?
ah im an idiot
its klipper.bin
nope it wont flash
Does
ls /dev/serial/by-id/ show anything?let me see
Why does your hostname change?
im trying both boards
non of them flashed
You are swapping the CB1 between the two of them?
Oh, I guess you have 2 CB1s
Both of them are manta m8p v2.0?
radiant anvil was never flashed before
pain forge was autoflashed by klipper with the manta 11 when i first installed and iflicked update all
yes they are both mantas m8p 2.0
each one has a cb1 and a 64gb sd
and both of them don't show any serial ids?
yeah
same thing
:/ maybe we'll try the top folder
ls /dev
There definitely should be stuff herealso btw the one that was autoflashed by klipper when i updated all thggough the update manager on machine tab
said this
Next I guess we'll try flashing by setting the board into DFU mode
I have them marked so i know which is which
Right, we'll just try dfu mode flashing
IIRC it's hold BOOT0 and then press RESET
Then we can confirm by doing
lsusb againok
great
Now go back to your klipper folder and run....
make flash FLASH_DEVICE=0483:df11ok
let me try
ima doit on the painforge one first
cool, we'll assume it actually flashed (following the BTT instructions, apparently only
File downloaded successfully is what we have as verification)
Do a quick check with lsusb and ls /dev/serial/by-id
cool, looks like it flashed
oh then what was the error 255
Try pressing the reset and then checking the serial again
i pressed reset and serial is gone
The error is because the tool used to flash is expecting stuff to happen after the file is transfered to the device, but the device isn't doing that stuff (whether it's because it wasn't important to implement or w/e)
Ok, so there may be two reasons that I experience that might explain what is happening atm
both boards show the same
Either A) your boards aren't getting enough power from your usb-c
or B) the bootloader might need to be reflashed
ok so i should try with a different usb thing
I'm not sure if there are other issues that could happen that cause this sort of thing, since this is just going off of my own troubles
If you can wire it up to the 24V, you can check that way without having to guess if you have enough power
Just make sure you remove the jumper pin
ok
gime ve a moment
ok im already connected to 24v
Yeah, then let's assume your bootloader has something funny going on
GitHub
Manta-M8P/V2.0/Firmware at master · bigtreetech/Manta-M8P
Contribute to bigtreetech/Manta-M8P development by creating an account on GitHub.
Grab the bootloader.bin from here and follow those instructions
if you want to get the file while ssh'd
you can use wget
just wget?
i have no idea about git
wait, let me type out the command
wget https://github.com/bigtreetech/Manta-M8P/raw/master/V2.0/Firmware/M8P_V2_H723_bootloader.bin -O M8P_V2_H723_bootloader.bin
it will download the file to your current directoryok thx
Oh, maybe I shouldn't have renamed it
its odd both boards thave the same issue
There you go
Then you set your board to dfu mode and run the command they have on the github readme
ok
And then reflash klipper with the
make flash FLASH_DEVICE... command from earlierok
ok so i tried something
havent flashed yet
nor restarted the mcu
You should make sure it stays after pressing reset
ok
wel it does now
As long as it does, it's probably fine
i didnt reflash
why would that happen?
just a bootloader problem?
Bootloader magic
For me, it was reverting to an older version that I had flashed
every time I reset
So I could have had different garbage in my bootloader area
so this could be a widspread issue?=
No idea
I've only really got information on myself, and now you
yeah but i have 2 boards
Extrapolating my 3 data points
i got those on november i think
Must be across everything
Lol
Same time frame as me
Maybe it's a batch, or maybe it's just been this way since the beginning
and their documentation is just lacking again
that wouldnt be surprising
or both issues
Yeah, I spent a couple days slowly chatting with BTT support until they gave the suggestion of reflashing the bootloader
well at least was a couple days
i waited almost a year to get support on the hermit crab can toolhead
ok did the same on the other board
both seem to retain the id
Yeah, so if you have the udev rule added in the
/etc/udev/rules.d/ folder
you should be able to see a new mount point in /dev
/dev/btt-manta-m8p-20ah nope the rules file i think is somewhere else
the things that we copied yesterday?
yeah
there should have also been a 98-....something something.rules
Oh, I guess symlink is what is normally done
yeah, in that folder you would want to create a symlink to your m8p-20 rules file
sudo ln -sf 98-btt-manta-m8p-20.rules /home/pi/printer_data/config/RatOS/boards/btt-manta-m8p-20/98-btt-manta-m8p-20.rules
And then I think that's about itwhat does this do?
what is symlink
makes a symlink
uh....
It's like a windows shortcut
sort of
ah ok
The file exists in printer_data/....etc but when the computer wants to look at /etc/udev/... it will look at that file
i dont think it did something
nope
oh, maybe I swapped the arguments
sudo ln -s ~/printer_data/config/RatOS/boards/btt-manta-m8p-20/98-btt-manta-m8p-20.rules 98-btt-manta-m8p-20.rules
other way around
Double check the printer_data/config/RatOS/boards/btt-manta-m8p-20/98-btt-manta-m8p-20.rules file to see that it's actually still a file now xDaight
if it isn't, then just get a fresh copy from github again
ok
You need the udev rules first in order for the CB1 to make the mount point
i think it is a symlink?
yeah, delete it and replace it
ok
done
this is crazy xDtoo much stuff in one go
it should look like this iguess
yeah looks right to me
ok so what is next
I guess just reboot and check /dev
and then check mainsail
ok
That should be everything I think, unless I've forgotten something
this after restart?
yeah
Pretty much udev is a service that checks things that are plugged into the computer and can perform actions based on what is plugged in (the rules are the instructions for what to do)
kinda what the bios does at the power up?
Since the manta mcu and the CB1 are connected at boot, usually this would trigger at boot
if you could disconnect the manta and the cb1
though I think you can also use
udevadm trigger to retrigger the udev rules
looking on the wrong end of the alphabet
i guess this would be like sudo udevadm trigger?
yeah
don't take my word exactly for it though
I'm not well versed in the magic of udev
well im not well versed in linux but i thing weve made it so far but creits to you tho
what u mean
it would be /dev/btt-manta-m8p-20
but there is no btt manta folder
it's not a folder I think
there it is
Yeah, so you should be able to check mainsail and it should show things
this is what mainsail shows
Looks right
good so i should dhit update all?
From what I understand you update RatOS first
ok
ah dude what a trip with this boards
ok so ratos is updated
should i update manually in a specific order?
I don't really think you have to do any other specific order
Aside from RatOS being first
https://os.ratrig.com/docs/installation/
ok got it
well @jurassicplayer | VC3.1 300 thank you very much.
Now ill have to see if is possible to make the hermit crab work with the cb1
Yeah
just make sure you add the include line in your printer.cfg
for the hermit crab?
for the manta-m8p-20
aaa oh
yeah
i guess ill work on the configs tomorrow
[include RatOS/boards/btt-manta-m8p-20/config.cfg]its already 12 here
oh this is different. so aside from this im not required to add it with the serial number=
yeah
btw what printer do you have?
if you check the config.cfg in the manta-m8p-20 folder, you'll actually see the section that the udev rule is partly used for
I have a ratrig VC3.1 300mm and an old Tevo Tarantula (that has never been good)
ill have to dig deeper into ratos stuff
i did trst klipper but the cb1 image was vhey cut out
not rare from btt
cool why na ratrig and not a voron or a zero g
I just like the placement of the electronics more
sorry for asking so much @jurassicplayer | VC3.1 300 i was working on the boards like the config only no electric connections yet and after restarting one of them using the poweroff comand in ssh the board wont come up again, the power led is on but the act never blinks, and the thing after some tiem doesnt connect to the internet at all
Well, can't really tell what is wrong without being able to poke at it, so you'll need to get an ethernet cable
ill get one but im sure something might be done in teh cb1 it might have died idk my guess is that
No idea
You could try re-seating it into manta
i think is dead the ethernet leds do not blink when turning on and now that is connected with the ethernet cable same thing
already did
no luck
Do you have a spare microSD?
yep i did flash it again with another copy of ratos
different sd
no luck
i do have the m8p 1.1 with an extra cb1
Did you try booting the CB1 on the m8p 1.1
yep no luck
and the old cb1 on the new board same thing
im at a loss here
ima turn off the one that is working and use that sd card
well that worked. Manta m8p 1.1 with a new cb1 and the sd that was on the thing and it works. however the power led does not turn on
so the cb1 is not dead
So the CB1 + V2.0 doesn't work, but the same CB1 + V1.1 works?
i think something happened to the sdcards that i plug in the v2
i flashed 2 new sd cards
placed them in the v2 that stoped working
noghing happens
and when i use them in the v2 that works
they do not work
however the pc read them
im not going to try the working sd card
ima flash another one new
test it in the working v2
then move it to the v2 that doesnt work and see if it works
if it doesnt ill move it back to see if it boots
if not i gues the v2 that doesnt work is doing some sketchy stuff to the sd cards
well no. thing works on that one
my guess is that the sd reader is broken or something but is weird the sd cards do work on the pc
but not in the other boards
ill give it a try tomorrow ill leave the board unpowered this night
This doesn’t seem right if it’s v2. Speed should not he 50mhz
I think you flashed the wrong firmware to the board
i selected the options in make menu config that were provided by BTT pdf
i do think it doesnt look right coz there is no name or serial id for the mcu like it did with the v1.1
Board doesn’t show up with the ls command?
Settings seem correct
ill take a look after i get of work
i think it might be caused by the files inside github development. jurassicplayer had to send me one of his files to make this thing worlk
If you can see the board in ls /dev/serial/by-id/
you can flash the firmware via ssh
after you compile it with make config
i do get the serial id
and i added the serial id in teh config file but same thing
it doesnt report the status of the manta
Try flashing manually
Also I must have missed that
But what do you mean by status?
mcu
i did try to flash manually
wouldnt flash
even after bootloader reflash
What does it say
with the sd card=?
it just wont take the firmware
firmware.bin stays like that
no no
i mean
use this
via ssh?
was the only way to flash it
make flash FLASH_DEVICE=/dev/serial/by-id/usb-Klipper_stm32h723xx_btt-manta-m8p-20-if00
ok let me try
i did this before
thats perfect
ignore the error
but again the mcu status on the mainsail page wont change
what does it say now
this is my firmware flashed like 2 mins ago
put in the klipper/out folder
sure ill check i get off work in like 2 hours for a brief moment
nothing happened
It’s make flash_device
it doesnt work
idk what im doing wrong
sorry was sorting the kids
make flash FLASH_DEVICE=/dev/serial/by-id/usb-Klipper_stm32h723xx_btt-manta-m8p-20-if00
I'll give it a try once power is restored. Currently there is a power outage
Jesus
any luck?
im still at work yesterday there was no power. like all night ill ping u once i can try that
thx for the help
no luck
what if i try with the
make flash FLASH_DEVICE=0483:df11
other device id
You aren't in the klipper directory
oh lmao sorry
so im guess i have to restart=
@BulMaster stays the same
used your klipper.bin
OK I'll take a look
ther eis nothjing else
this is the one i had for the v1.1
i added the section MCU with this
/dev/serial/by-id/usb-Klipper_stm32h723xx_btt-manta-m8p-20-if00
nothing changes
ok now it does
im pretty sure the mcu is not comunicating with kipper hence the 50MHz thing
Oh, you never selected a template
RatOS has that selection somewhere of what printer you are using (Voron2.4, RR3.1, etc) that upon selection, would populate your printer.cfg with some default includes
Then normally you go through the printer.cfg afterwards and comment/uncomment sections or make override changes, etc.
Wait do you have a pin out for the board?
It won’t work without one
He has the pinout
His config just isn't referencing anything
I will take a look at work
Toolboard Configuration | RatOS
RatOS supports multiple toolboards connected via USB. They can be flashed initially through the configurator, and will automatically get flashed when klipper is updated. To configure your toolboard, you need to uncomment your board and features in the toolboard section in printer.cfg near the bottom, just before the user overides section.
He just needs to do the initial configuration part
Looks like I mentioned what to include in the printer.cfg
I'll take a look at that one tomorrow
so i did that and i got this
You already selected a template?
new issue arrised, i told it to turn off and now it wont boot upo
Did you power cycle?
Like actually cut off power
IIRC the pi (and I guess CB1) will be in a state where to power the pi back on after shutdown, you need to short a pin
If it's constantly being powered
i told it to restart. same issue as the other one. it stopped booting. i disconnected it for 30 minutes, didnt boot again.
Do you know by any chances what pin must be shorted?
cant find that info in the manual
For the pi it's pin 5 & 6 (reset and ground)
yeah i dont have a pi i have a cb1
issue is that somwhere they state pin 100 is reset
there are only 40 gpio pins
flashed another sd
i just told it to reboot
and is not booting anymore
🤦♂️
at this point i think is a cb1 issue
i tried many different sd cards with different sizes and brands
ruffus or raspi burner
both boards have the same stupid issue
didnt have that problem with the 1.1 board