search

Rappetor / Sovol-SV08-Mainline

Getting the Sovol SV08 onto mainline Klipper
GNU General Public License v3.0
101 stars 25 forks source link

Emmc question. #41

Closed sanpedrox2 closed 2 months ago

sanpedrox2 commented 3 months ago

Hi 🙂

In theory.. or practice... whats stopping me from preparing the mmc over shh with it installed in the machine if I want to do sd --> emmc?

And also.... can i install a fully setup/working install from sd to emmc? Or does it need to be a untouched minimal install?

Also 2.. great work! Got mine mainlined and running with an eddy probe (from sd so far) It works great and was really pretty easy by following your guide 🙂👍

Rappetor commented 3 months ago

Thanks! It started out as just keeping track of my steps and sharing those and with multiple contributing as well it has become quite the guide 😄

Good questions. Not sure to be honest, havent tried that yet (a working setup from sd to the emmc). I think nand-sata-install copies the whole SD to the eMMC, so a working install might just be copied over and work on the eMMC as well.

And I guess just prepare the eMMC from ssh would work as well (without the need of an emmc usb adapter). As far as I've gathered just remove the partitions and then call the nand-sata-install command, it should make all the necessary stuff for you (although I have limited experience with that one).

Getting the eMMC bootable and recognized by the system has been a bit of a trouble for some, which has been quite difficult to diagnose and fix so far. Especially on the original 8GB module.. Nothing seems to work just 100% foolproof. So give it a try but don't forget to make a proper image/backup of the original 😃

sanpedrox2 commented 3 months ago

Ok :) im going to try them both and see what happens then :)

edit: that didnt work... for some reason my mmc isnt recognized when running fdisk -l i only see the sd-card

Rappetor commented 3 months ago

You do have the fdtfile=sun50i-h616-biqu-emmc in the BoardEnv.txt ? That is needed for emmc support as far as I know (I assume also when running from SD you have to add this for emmc support).

sanpedrox2 commented 3 months ago

I tried with that, in sd BoardEnv.txt It didnt boot at all so changed it back.

Or do i need both fdtfile= lines?

Rappetor commented 3 months ago

Oh, that is weird. According to the CB1 docs 'NOTE: The CB1 eMMC version can also use the SD card as the OS image source, and the priority of the SD card is higher than on-board eMMC, so when using the eMMC, remember not to insert the OS SD card' (which makes me wonder why we have two different examples in the guide anyway)

So you would expect it to boot from the SD card 🤔 And only have to use one fdtfile line, not two so that is ok. Afraid I'm not sure then what the issue might be. Not sure where to look for an error log, quick search on Google says try this: cat /var/log/boot.log But I don't do enough Linux to know this..

sanpedrox2 commented 3 months ago

Ok, thanks :) I'll try again in a while. Maybe I had something missconfigured

sanpedrox2 commented 3 months ago

Tried Some more now... Cant get it to recognize the emmc no matter what. And it doesnt boot from it either (sd card out and original OS on emmc)

Windows sees and can interact with the emmc, no problem

Suspecting my mainboard is broken maybe :/ I guess i'll have a chat with sovol support

Oh well, atleast it works well with the SD for the time being

Rappetor commented 3 months ago

Well I've seen more people on the discord stating the same thing, the emmc doesn't show up with fdisk -l.

And does it boot from the original eMMC? If you no longer have a good image of the original you can grab that from their wiki and re-create the original emmc (although that becomes difficult without a emmc usb adapter 🤔 ).

sanpedrox2 commented 3 months ago

It doesnt boot with original. I have the USB adapter. I was just curious about if it could be done without. Going to mess around some more after work maybe,and see if i can get it working.

Rappetor commented 3 months ago

Oh, if it doesn't boot with the original (image) then something else might be wrong yes. Usually that is the version that should always work 😄

WZ9V commented 3 months ago

I'm one of those on Discord. The Sovol image boots fine from either the 8GB or 32GB eMMC. The CB1 minimal or Klipper won't boot from either and cannot be seen with fdisk -l when booted from SD card. Still have not figured it out.

sanpedrox2 commented 3 months ago

Thats strange indeed.

Shouldnt it be possible to nuke sovols klipper version from their image and install mainline on that though? And if not. Why?

sanpedrox2 commented 3 months ago

To anser my own question: Yes and why not 🙂

You were right. The emmc works on sovols image. Flashed with rpi-imager.

I nuked sovols klipper install and the sovol user entirelly and made a new user and installed kiauh. Running mainline on sovols image now and it seems to be working well

Rappetor commented 3 months ago

Yeah, already wanted to answer that installing mainline on the sovol default image is also an option (that's the first thing I tried and that worked).

But for some that was causing some issues on the Discord and so far the CB1 image proved to be kind of the most reliable way to get everything working. (also because the Sovol image is based on the CB1 image, to keep things interesting 😛 ).

Might add a note at the image part that it's also possible to use the stock Sovol image, clear the whole user directory and then go from there. Although I haven't found a really good way/command of clearing the user directory. So if you have a good way of nuking everything I gladly hear it 😄 Maybe we can even make a script that does this for us and then just use the Sovol image (think @Agash was working on something like that? Not 100% sure, maybe it was just a random idea 😄 ).

sanpedrox2 commented 3 months ago

i just did sudo userdel -rf sovol from my new user. that deletes the whole directory and the account of the user "sovol" ignoring processes the user has running.

i did also edit /etc/sudoers first so that my new user has sudo rights.

WZ9V commented 2 months ago

I suspect my situation was a mismatch between fdtfile and the uuid. This time I left the uuid from the original instead of copy paste. I was about to resort to a fresh Armbian install for the CB1.

Rotule666 commented 2 months ago

I tried fresh Armbian and the emmc problem is still there, when trying to boot, I have the emmc data error on the picture. image

also notice the PCB version image

The stock image was booting allrigth, I overwritten it on the emmc because I tought it was a problem with my emmc V1.0 I tried to use but it does the same with eMMC V1.1 from the SV08.

Fallback is to use the SD card.

I am trying to find answers on different embedded linux discussions, some seems to say adding a capacitor to the emmc clock fixes the issue. (Hardware solution to a software problem).

I will pursue my quest and report if I find anything worth.

sanpedrox2 commented 2 months ago

Try stock image. And install mainline klipper on that if all else fails. That worked for me. I made a new user but im not sure that is needed. But I would uninstall everything klipper related using kiauh on stock. Then delete kiauh folder and then follow this guide from step 4 - install mainline klipper

sanpedrox2 commented 2 months ago

Btw. I got best result using raspberry pi imager (no device selected, use custom os. No saved configuration)

That seems to be what sovol recommends aswell

Rotule666 commented 2 months ago

I would try this, anyone have a dump of the stock image? lol...

sanpedrox2 commented 2 months ago

Sovol has it on their page

https://wiki.sovol3d.com/en/SV08

Or....

https://drive.google.com/drive/folders/10CdLCMd5jGHhtjPqmnJGEteK2nnGQku2?usp=drive_link

cyaneo commented 2 months ago

I want use a 2nd eMMC module but can't find a eMMC V1.2 (where to buy?) - but I have a eMMC v1.0 32g laying arround - could I use this also?

ss1gohan13 commented 2 months ago

I want use a 2nd eMMC module but can't find a eMMC V1.2 (where to buy?) - but I have a eMMC v1.0 32g laying arround - could I use this also?

Yes, this should work.

Rappetor commented 2 months ago

I have an update for you guys (and I've updated the guide accordingly). It seems when you use the Sovol dtb emmc file it (the CB1 image) will work with the stock 8GB eMMC.

Also I tried to make the whole boardenv.txt piece a bit more clear so maybe that will also fix of the issues you were having. If you are still interested in all of that, because it's been a while 😄

sanpedrox2 commented 2 months ago

Nice 😀 I have sort of moved on now. Got it setup on a 32g no issues whatsoever. Amd my curiosity has dimmed a bit. Now I just want to print 😉

Good for future tinkerers though 👍

Rappetor commented 2 months ago

Good to hear you got it up and running. This whole thing is, usually, a one time event and then back to enjoying the printer. And that's a good thing! 😄

Rappetor commented 2 months ago

I think this can be closed now. Especially after updating the guide with the sovol dtb file. That seemed to have fixed some issues for people using the stock eMMC. But also read reports of people being able to mainline after using this dtb file.