2023-01-09 05:08 AM
I am upgrading from ecosystem 4.1 to 4.0. after changing every thing properly in the device tree. and now i successfully compiled the image partitions using bitbake how ever when i boot using the flashed images every thing works correctly utill i recive the following error on the boot
Starting version 250.5+
root '/dev/disk/by-partuuid/e91c4e10-16e6-4c0e-bd0e-77becf4a3582' doesn't exist or does not contain a /dev.
the full boot log is in the following .txt file
i did try to flash using :
the compilation generates the following message when i compile the image using bitbake
NOTE: Started PRServer with DBfile: /media/user1/st4_1/kirkstone/build-openstlinuxweston-stm32mp1/cache/prserv.sqlite3, Address: 127.0.0.1:37179, PID: 2053248
Loading cache: 100% |###########################################| Time: 0:00:05
Loaded 4455 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "2.0.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "arm-ostl-linux-gnueabi"
MACHINE = "osd32mp1-brk"
DISTRO = "openstlinux-weston"
DISTRO_VERSION = "4.0.4-snapshot-20230108"
TUNE_FEATURES = "arm vfp cortexa7 neon vfpv4 thumb callconvention-hard"
TARGET_FPU = "hard"
DISTRO_CODENAME = "kirkstone"
GCCVERSION = "11.%"
PREFERRED_PROVIDER_virtual/kernel = "linux-stm32mp"
meta-python
meta-oe
meta-gnome
meta-initramfs
meta-multimedia
meta-networking
meta-webserver
meta-filesystems
meta-perl = "HEAD:05dcac98473402d87e0af73bbc2c5a6a840abe93"
meta-st-stm32mp = "HEAD:ca501bd7dbe023682903ceedddaacd940b0898f4"
meta-qt5 = "HEAD:5b71df60e523423b9df6793de9387f87a149ac42"
meta-st-openstlinux = "HEAD:cb736b403d0fef2a02390695613b6b4bb13ca1b7"
meta = "HEAD:f7766da462905ec67bf549d46b8017be36cd5b2a"
meta-octavo-osd32mp1-kirkstone = "<unknown>:<unknown>"
Initialising tasks: 100% |######################################| Time: 0:00:11
Sstate summary: Wanted 1276 Local 196 Mirrors 0 Missed 1080 Current 1824 (15% match, 65% cSetSetscenWARNING: octavo-image-weston-1.0-r0 do_image_complete: Missing 'EULA_FILE_ST' var : no image license copied...
WARNING: octavo-image-weston-1.0-r0 do_st_write_license_create_summary: IMG LIC SUM: File does not exist with open file /media/user1/st4_1/kirkstone/build-openstlinuxweston-stm32mp1/tmp-glibc/deploy/images/osd32mp1-brk/octavo-image-weston-openstlinux-weston-osd32mp1-brk.license
WARNING: octavo-image-weston-1.0-r0 do_st_write_license_create_summary: IMG LIC SUM: File does not exist with open file /media/user1/st4_1/kirkstone/build-openstlinuxweston-stm32mp1/tmp-glibc/deploy/licenses/st-image-resize-initrd-openstlinux-weston-osd32mp1-brk-20230108193424/package.manifest
NOTE: Tasks Summary: Attempted 7537 tasks of which 5142 didn't need to be rerun and all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 8 seconds
what should i do to make this boot properly ?
2024-02-27 02:57 AM - edited 2024-02-27 02:58 AM
Hi @SScar.2
All SD-Card are supported on STM32MP157F-DK2 board and there is no UHS-I support (i.e. no specific PMIC voltage change as no SDMMC IO level shifter on the board). So your issue is unlikely due to your specific PMIC.
From Device Tree, I think UHS-I modes (the ones requiring to switch to 1.8V) should be defined as 'not supported' by removing the following lines:
sd-uhs-sdr12;
sd-uhs-sdr25;
sd-uhs-sdr50;
sd-uhs-ddr50;
Maybe probably putting the right supply name aligned with your HW (i.e. the supply you use which is not switchable by SW from 3.3V to 1.8V) would be enough too to tell SW that 1.8V supply is not possible.
vqmmc-supply = <&xxxxx>;
See also https://wiki.st.com/stm32mpu/wiki/SDMMC_device_tree_configuration#DT_bindings_documentation
Regards.
2024-02-27 03:01 AM
Please refer to SDMMC1 device tree example on STM32MP157F-DK2
2024-02-27 03:12 AM
Hi Patrick!
Cool! This may be the best solution (with this specific hw). I thought it could be possible to modify the dts to not execute the voltage switch, but I didn't know where to look. I will try that!
Thanks a lot
Simone
2024-03-01 05:49 AM
Hi Patrick!
Great news ! You were right, it works!
Thanks again for the support