I use the recommended Debian image from github.com/milkv-mars/mars-buildroot-sdk, which works nicely. However I cannot find and/or access the eMMC on my Mars CM module. It won’t show up via lsblk, nor can I find anything obvious in /dev. dmesg lists the following errors periodically
[87121.373922] mmc0: cache flush error -110
[87121.377930] mmc_host mmc0: Bus speed (slot 0) = 49500000Hz (slot req 400000Hz, actual 399193HZ div = 62)
[87121.451169] mmc_host mmc0: Bus speed (slot 0) = 49500000Hz (slot req 100000000Hz, actual 49500000HZ div = 0)
Anyone has an idea how I can get the eMMC running? I would already be happy to somehow have the ability to flash it from external. Thank you!
I tried to flash my Mars CM via a Waveshare CM4-IO-Base-A Board and via an updated Turing Pi v2, and in both cases it doesn’t work.
The CM4-IO-Base-A Board doesn’t show up on my laptop when connecting it via USB-C (yes I put it into Boot mode) and the Turing Pi (after updating to BMC 2.0 RC1) states “No supported devices found”
I think I slowly make some progress by following Boot the Mars CM | Milk-V, instead of relying on Linux tools. After several unsuccessful attempts, it looks like the image burning is slowly progressing, yay knocks on wood
Note to my future self: If something goes wrong during flashing (e.g. timeouts), do a system reboot.
I think data transmission is through USB, otherwise why install USB driver software? I think serial port is used to control the related operations of sending instructions to configure USB transmission. However, I don’t understand why there is no significant improvement in the running speed of the system installed in EMMC compared to TF cards