diff options
| author | Z8MAN8 <[email protected]> | 2024-07-25 15:14:16 +0800 |
|---|---|---|
| committer | Meco Man <[email protected]> | 2024-07-25 21:35:48 +0800 |
| commit | a1b01ee86582811cfec569376dd5815d9b43eda9 (patch) | |
| tree | 57ee48062f48245472b683d59fbe1610ffd9b24d /components/drivers | |
| parent | bde4817b9e46bf0b1c2b9bac476c01d02b88618a (diff) | |
bsp: cvitek: fix cv18xx_aarch64 mnt init blocking
The aarch64 core of duo on the master cannot enter the
console interface. It can only print the RT flag and hold it.
Analysis: The latest commit that can work is ae6a328 ("Add
psoc62, 61 config"). This phenomenon will occur after adding
754c59a ("[Feature] DFS mount auto by kernel parameters").
The specific reason is that when aarch bsp enables the device
tree, the current u-boot will pass in bootargs, which contains
"root=/dev/mmcblk0p2 rootwait rw", which means that the
kernel is required to wait until the rootfs in /dev/mmcblk0p2
loaded successfully. However, the current aarch64 bsp default
does not implement sdmmc device mounting, causing the
kernel file system mounting module (rootfs_mnt_init() of
components/drivers/core/mnt.c) to enter an infinite loop waiting.
Solution: At present, we do not plan to modify the startup
parameters of u-boot. The temporary solution adopted is to
create a pseudo /dev/mmcblk0p2 device during the board
initialization process, and then cancel the pseudo device
after mnt is completed. This allows the kernel boot to be
completed successfully.
Signed-off-by: Shicheng Chu <[email protected]>
Reviewed-by: Chen Wang <[email protected]>
Diffstat (limited to 'components/drivers')
0 files changed, 0 insertions, 0 deletions
