after rebuild kernel then machine stop to Waiting for here root device /dev/mmcblk0p6...

[bkwak]

I am tring to rebuild kenel for STM32MP157C-DK2 using below url. ​

https://wiki.st.com/stm32mpu/wiki/Getting_started/STM32MP1_boards/STM32MP157C-DK2/Develop_on_Arm%C2%AE_Cortex%C2%AE-A7/Modify,_rebuild_and_reload_the_Linux%C2%AE_kernel

After I did 5.4 but it does not work and stop to this point ( root device /dev/mmcblk0p6...).

Let me know how to can rebuild kernel for working.

Thank you.

[   1.857417] can: netlink gateway (rev 20170425) max_hops=1

[   1.863493] Key type dns_resolver registered

[   1.867295] ThumbEE CPU extension supported.

[   1.871370] Registering SWP/SWPB emulation handler

[   1.877193] registered taskstats version 1

[   1.880218] Loading compiled-in X.509 certificates

[   1.909860] stm32-cpufreq stm32-cpufreq: Failed to get chip info: -517

[   1.916712] mmci-pl18x 58007000.sdmmc: allocated mmc-pwrseq

[   1.930026] stm32-cpufreq stm32-cpufreq: Failed to get chip info: -517

[   1.936906] mmci-pl18x 58007000.sdmmc: allocated mmc-pwrseq

[   1.942262] stm32_rtc 5c004000.rtc: setting system clock to 2020-02-29 01:00:23 UTC (1582938023)

[   1.952596] Waiting for root device /dev/mmcblk0p6...

[MNoor.1]

I have the same problem. I selected all sd/mmc related drivers from menuconfig to be built and installed, but still not working.

Boot logs are attached.

[YAY.1]

I think boot is not contuniuing (there is no code) so there is this problem.

If you can, download newest version on the net.

[bkwak]

Thanks for info. ​

Is there more new version than linux-4.19.94.tar.xz ?  (I used linux-4.19.94.tar.xz ) 

[YAY.1]

You can look at this site...

https://linuxlists.cc/l/10/linux-kernel-announce/search/%20Linux%20kernel%205

[Dzhon.11]

我在使用DK1的时也�?�到这个问题，对比�?程是一致的，目�?怀疑相关的命令有细微的错误。

https://blog.csdn.net/Ambitious_Man/article/details/103699146

�?�以结�?�使用这个网站的命令�?��?程，​就能正常�?�动了。

[mleo]

Hi,

Issue confirmed - reproduced, investigation ongoing.

Milan

[Bernard PUEL]

Hi all,

Just to double check:

did you well update your DK2 board with the V1.2.0 starter package (before updating the uimage with drm modification) ? I mean reflashing completely your sd card with V1.2.0.

[Bernard PUEL]

The pb was found in the wiki article:

PC $> make ARCH=arm multi_v7_defconfig

should be:

PC $> make ARCH=arm multi_v7_defconfig fragment*.config

The article was updated accordingly. Thanks for pointing this and sorry for the inconvenience !

[MNoor.1]

When I try:

PC $> make ARCH=arm multi_v7_defconfig fragment*.config

inside kernel source folder I get:

no matches found: fragment*.config

But, when I execute the command with the right fragment path:

PC $> make ARCH=arm multi_v7_defconfig ../fragment*.config

I get the following errors:

HOSTCC scripts/basic/fixdep

HOSTCC scripts/kconfig/conf.o

YACC  scripts/kconfig/zconf.tab.c

LEX   scripts/kconfig/zconf.lex.c

HOSTCC scripts/kconfig/zconf.tab.o

HOSTLD scripts/kconfig/conf

#

# configuration written to .config

#

scripts/kconfig/Makefile:109: *** No configuration exists for this target on this architecture. Stop.

Makefile:532: recipe for target '../fragment-03-systemd.config' failed

make[1]: *** [../fragment-03-systemd.config] Error 2

Makefile:286: recipe for target '__build_one_by_one' failed

make: *** [__build_one_by_one] Error 2

[Bernard PUEL]

you have some fragments inside the source tree and outside the source tree. This is 2 different steps.

Your first trial was correct and should lead to merge these configs:

./arch/arm/configs/fragment-01-multiv7_cleanup.config

./arch/arm/configs/fragment-02-multiv7_addons.config

I suggest to remove your .config and redo the config (follow the updated wiki article).

[MNoor.1]

Thanks for pointing out the config files under ./arch/arm/configs/

Turns out that using zsh as shell I should have executed the command as:

PC $>make ARCH=arm multi_v7_defconfig "fragment*.config"

[Bernard PUEL]

moreover:

./arch/arm/configs/fragment-01-multiv7_cleanup.config

./arch/arm/configs/fragment-02-multiv7_addons.config

These configs come with ST patches applied on top of the vanilla kernel (see the step before the config). So if you don't have them, its because ST patches were not (or wrongly) applied on the kernel.

Let me know if not clear.

[Bernard PUEL]

@MNoor.1​ , Ok caught it.

[建胡.1]

[   1.794692] sdhci: Copyright(c) Pierre Ossman

[   1.801210] Synopsys Designware Multimedia Card Interface Driver

[   1.807563] sdhci-pltfm: SDHCI platform and OF driver helper

[   1.815486] ledtrig-cpu: registered to indicate activity on CPUs

[   1.820963] usbcore: registered new interface driver usbhid

[   1.825627] usbhid: USB HID core driver

[   1.833630] stm32-ddr-pmu: probed (ID=0x00140061 VER=0x00000010), DDR@533MHz

[   1.840775] optee: probing for conduit method from DT.

[   1.844463] optee: api uid mismatch

[   1.848396] NET: Registered protocol family 17

[   1.852418] can: controller area network core (rev 20170425 abi 9)

[   1.858764] NET: Registered protocol family 29

[   1.863049] can: raw protocol (rev 20170425)

[   1.867355] can: broadcast manager protocol (rev 20170425 t)

[   1.872999] can: netlink gateway (rev 20170425) max_hops=1

[   1.879164] Key type dns_resolver registered

[   1.882955] ThumbEE CPU extension supported.

[   1.887142] Registering SWP/SWPB emulation handler

[   1.892786] registered taskstats version 1

[   1.895937] Loading compiled-in X.509 certificates

[   1.925546] stm32-cpufreq stm32-cpufreq: Failed to get chip info: -517

[   1.932467] mmci-pl18x 58007000.sdmmc: allocated mmc-pwrseq

[   1.945772] stm32-cpufreq stm32-cpufreq: Failed to get chip info: -517

[   1.952638] mmci-pl18x 58007000.sdmmc: allocated mmc-pwrseq

[   1.958096] stm32_rtc 5c004000.rtc: setting system clock to 2000-01-01 00:34:37 UTC (946686877)

[   1.968214] Waiting for root device /dev/mmcblk0p6...

Waiting for root device /dev/mmcblk0p6...^C