Skip to main content
Associate
November 3, 2023
Solved

STM32MP157dk uboot ums seen in virtualbox Macos, bootfs, vendorfs etc. are a read only file systems

  • November 3, 2023
  • 1 reply
  • 1800 views

Having doing a workshop regarding OpenST linux boot customisation (https://www.youtube.com/watch?v=hqGA5Krk0mU), I stumbled on a problem with a mass storage mount. Doing "ums 0 mmc 0" in uboot gives me partitions within an sdcard but only to see them as read only, unable to be mounted.

Mounting sdb1 via terminal gave me error of "wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program or other error".

St link is working, only problem is with usb download gadget.

Unfortunately I am a beginner within the stm ecosystem so any help is greatly appreciated.

Host is Macos Ventura 13.6, virtual virtualbox 7.0.6 as sudo (because of a problem with VERR_SHARING_VIOLATION in usb in regards to st link) 

This topic has been closed for replies.
Best answer by michh

Thanks for the response! As it turns out there was a problem with a virtual box on Macos. I switched to a linux host, the problem subsided.

1 reply

Erwan SZYMANSKI
Technical Moderator
November 3, 2023

Hello @michh ,
First of all, the workshop you shared above is quite old, and I advise you to follow steps of https://wiki.st.com/stm32mpu/wiki/STM32MP15_Discovery_kits_-_Starter_Package article. Wiki will be your best friend during your explorations !

Secondly, you may have some issue with your virtual machine on which it is difficult for us to help. However, please try to follow the article above, and let me know if you still face troubles. Make sure to get the latest Starter package available on st.com, on try to go forward.

Regards,
Erwan.

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
michhAuthorBest answer
Associate
November 3, 2023

Thanks for the response! As it turns out there was a problem with a virtual box on Macos. I switched to a linux host, the problem subsided.