Issue seems to persist on BeagleV-Fire.
Unbelievable…
Failed ALL my sd cards, including:
my gosh… it’s almost 2024… How come the SD card won’t work with a BeagleV-Fire board ???
haven’t had a chance to test it yet, but there is a 6.6, 6.7 version of the kernel that has been patched. might be something to look at.
The BeagleV-Fire’s eMMC/microSD port is multiplexed in the MPFS250T the PolarFire SoC Icicle has the same issue… You get a choice between eMMC or microSD with the MPFS250T for the FIre we chose to use an internal eMMC, and export the microSD as a “spi-mmc” device in Linux.
So for booting, you need to use the eMMC.
Regards,
Hi, Robert. Thank you for your reply.
In that case, is there a way to flash the onboard eMMC directly via SPL from my built sdcard.img on my Desktop Ubuntu?
We do it thru hss, mount the eMMC as a USB flash drive. readme.md · main · BeagleV-Fire / BeagleV-Fire-ubuntu · GitLab
Regards,
Hi, Robert:
why my trying hangs here:
[5.454973] L2 Cache Configuration:
L2-Scratchpad: 4 ways (512 KiB)
L2-Cache: 8 ways (1024 KiB)
L2-LIM: 4 ways (512 KiB)
[5.469469] DDR-Lo size is 32 MiB
[5.473722] DDR-Hi size is 1888 MiB
[5.497557] Design Info:
Design Name: CI_DEFAULT_FD28A2CA1789CDC1137
Design Version: 02.00.2
[5.507973] Attempting to select eMMC ... Passed
[5.763530] User button NOT pressed
Press a key to enter CLI, ESC to skip
Timeout in 1 second
.[6.311056] Character 13 pressed
[6.315222] Type HELP for list of commands
[6.320083] >> mmc
[9.278964] Selecting SDCARD/MMC (fallback) as boot source ...
[9.285561] Attempting to select eMMC ... Passed
[9.718242] >> usbdmsc
[13.991146] initialize MMC
[13.994704] Attempting to select eMMC ... Passed
[14.250356] MMC - 512 byte pages, 512 byte blocks, 30621696 pages
Waiting for USB Host to connect... (CTRL-C to quit)
. 0 bytes written, 0 bytes read
It would never proceed the exposing of eMMC.
Can you check that your USB cable supports data transfers and is not your anti-hacking USB power-only cable?
Hi, @Vauban Thank you for your prompt reply.
Switched to another USB cable, which is not working neither.
[6.99847] >> mmc
[9.02622] Selecting SDCARD/MMC (fallback) as boot source ...
[9.09132] Attempting to select eMMC ... Passed
[9.264619] >> help
Supported commands:
QUIT BOOT RESET HELP VERSION UPTIME DEBUG MEMTEST QSPI EMMC MMC SDCARD PAYLOAD SPI USBDMSC SCRUB
[11.306103] >> sdcard
[17.394602] Selecting SDCARD as boot source ...
[17.399984] >> usbdmsc
[22.666278] initialize MMC
[22.669837] Attempting to select eMMC ... Passed
[22.925498] MMC - 512 byte pages, 512 byte blocks, 30621696 pages
Waiting for USB Host to connect... (CTRL-C to quit)
. 0 bytes written, 0 bytes read
usbdmsc still hangs.
However, I noticed there is a sdcard. Is it implemented? Can I choose to boot directly from sdcard?
Anyway, I’m 100% sure the current HSS is from within on-board eMMC. Is it possible that this HSS is broken???
Finally, I’m using a FT232RL:
Please also refer to Amazon, exactly this device:
Thank you
Plug in the ‘other’ usb port… (aka the type-c port)
The USB you currently have plugged into the FT232RL is ‘serial’ debug only. Once you tell HSS:
sdcard
usbdmsc
The other usb type-c port will become a usb-flash drive with the eMMC being it’s media…
Regards,
Thank you Robert… Thank you …
I was thinking the other USB port is just the power …
Well, Thank you sooooooo much… Thanks
I have noticed that under WIN11 it is impossible to mount the device as USB storage, the script hangs when waiting to USB Host to connect but surprisingly under WIN10 everything worked and I can see the 3 partitions mounted.
It is possible that HSS prompt only works properly for WIN10? is anybody tried it under WIN11? for me does not work.
I had an issue with the HSS USB file system mount failing under Win 10. I turned out the issue was that I had the Fire plugged into a USB 3 hub. When I plugged it into as USB 2 hub it worked properly. I have seen this problem with other USB 2 devices, particularly if they are devices that reconfigure and re-enumerate. When this happens, it can often be fixed by inserting a USB 2 hub between the device and the USB 3 hub, i.e. you do not necessarily need to plug into a USB 2 root hub.
So it may be that your Win11 problem is really a hub compatibility problem.