Closed plcs2eco closed 1 year ago
setenv bootargs console=ttyO0,115200n8 noinitrd rootfstype=ext3 root=/dev/mmcblk0p2 rw mem=512M boot_delay=3 rootdelay=5
Why the odd boot_delay and rootdelay values?
just swap them for rootwait
..
console=ttyO0,115200n8
you should use console=ttyS0,115200n8
Please post your full serial boot log with those changes..
PS... why Linux-5.18.0-rc4+, smells like a random choice.. If you need 5.18.x use 5.18.19 over 5.18.0-rc4...
Regards,
Hi Robert, Thank you very much for your advice. I have been battling this issue for over a week by myself by googling and a lot of trial&errors.
1) Linux-5.18.0-rc4+ You are collect. This version is not my choice. I don't know why I am using this Linux-5.18.0-rc4+. I was going through Udemy course. I thought that I downloaded it from https://github.com/beagleboard/linux without selecting the version around beginning of November 2022. I might have gotten it from elsewhere. Anyway, I extracted it and built the kernel with it. The version happened to be just Linux-5.18.0-rc4+. I couldn't find out how to specify 5.18.19 so I downloaded linux-5.10.zip. I will try it and let you know the result probably tomorrow.
2) I replaces "boot_delay " and "root_delay" with "rootwait" with 2) Linux-5.18.0-rc4+. The error message changed to the below message. And the message doesn't change even after minutes.
[ 33.760875] vmmcsd_fixed: disabling
And D2 LED started flashing. So it might have been successfully booted but I can't tell since there is no output in minicom. This phenomena is same with ttyO0 or ttyS0.
3) ttyO0 In the Udemy course, they use ttyO0 instead of ttyS0. I kind of knew that ttyO0 was replaced by ttyS0 in newer system. But in the serial boot log message, kernel replaced ttyO0 witth ttyS0. So I thought that it doesn't hurt keeping ttyO0. But I changed ttyO0 to ttyS0.
I also added /etc/init.d/rcS and it has echo. But the echo is not displayed. So either the tty got lost when kernel mounted the serial as /dev.
Best regards, Junji config.txt boot_scr_from_sd.txt
U-Boot SPL 2022.10 (Nov 25 2022 - 14:10:15 +0900)
Trying to boot from MMC1
U-Boot 2022.10 (Nov 25 2022 - 14:10:15 +0900)
CPU : AM335X-GP rev 2.1
Model: TI AM335x BeagleBone Black
DRAM: 512 MiB
Core: 160 devices, 18 uclasses, devicetree: separate
WDT: Started wdt@44e35000 with servicing (60s timeout)
NAND: 0 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1...
Thanks for the printdump..
Well everything looks fine except for the mmc not coming up.. So it's either 5.18.0-rc4 or your defconfig..
Ah... Udemy, that makes sense.. Why don't you ask them?
Anyways throw everything you've done out, your just going to spin your wheels.
git clone -b 5.10 https://github.com/beagleboard/linux
^ that'll get you a proper linux source to build from..
Stop downloading *.zip files from github..
Edit, the 5.10 branch even tells you how to build things (for debian)..
https://github.com/beagleboard/linux/blob/5.10/jenkins_build.sh
Hi Robert,
It worked!
Here is what I did.
1) did git clone to get 5.10
2) built kernel image as
sudo make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- uImage dtbs LOADADDR=0x80008000 -j4
3) built modules
sudo make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- modules -j4
4) built busybox as build-static in menuconfig 5) installed modules from linux to root file system 6) added rcS for init
And it showed the # console. I am super excited now. Yesterday, I downloaded zip and extracted and built the kernel image and modules and installed modules into root file system made by busybox. I didn't choose "build static". This improved from the last error and didn't mount fs last time. It mounted and free unnecessary memory of kernel. But it failed on init process from init/main.c. I even tried to include init=/etc/init.d/rcS in cmdline. I read https://docs.kernel.org/admin-guide/init.html. I think that sbin/init was not properly built. I thought that only difference in "download zip file" or "git clone" is same except for git clone install git access. So I am suspecting that building busybox with static made it work from the init not found problem.
I need a lot of customization in the future so I need busybox. When I ran jenkins_build.sh, I realized that it builds everything without any room to work with busybox. Or at least I couldn't figure out how. So I did this way. Anyway, I am very happy and truly appreciate your professional help. Just in case I attach my log. I added debug to bootargs in order to get little bit more information.
By the way, I posted to get help few times at Udemy including this problem 4 days ago but anyone unfortunately never replied. I was googling and reading a lot of sites and became desperate and posted here knowing my question was too dummy.
Anyway, Thank you very much, Robert! Junji
U-Boot SPL 2022.10 (Nov 25 2022 - 14:10:15 +0900) Trying to boot from MMC1
U-Boot 2022.10 (Nov 25 2022 - 14:10:15 +0900)
CPU : AM335X-GP rev 2.1 Model: TI AM335x BeagleBone Black DRAM: 512 MiB Core: 160 devices, 18 uclasses, devicetree: separate WDT: Started wdt@44e35000 with servicing (60s timeout) NAND: 0 MiB MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1...
Hi, I am trying to boot from microSD on beaglebone black.
I downloaded zip file from this site around Nov 5th, 2022. Using below combination
I install all generated modules into the rootfile system which was generated by busybox. And I added /dev, /etc, /root, /sys, /config and /proc. Kernel started but became kernel panic and stopped and didn't even reach the point where it requires those directories with below errors. [ 9.463643] /dev/root: Can't open blockdev [ 9.475606] VFS: Cannot open root device "mmcblk0p2" or unknown-block(0,0): 6
I powered the beaglebone black on while holding down S2(SYSBOOT[2]) button.
mmcblk0p2 is the second partition on the microSD where the rootfile system resides.
When I do "ls mmc 0:1" and "ls mmc 0:2", u-boot returns with below. So u-boot is recognizing microSD card. So I think that either dtb is bad or kernel doesn't have right device drivers.
109084 MLO
1425784 u-boot.img
667 boot.scr
108564 u-boot-spl.bin
.Trash-1000/
4 file(s), 1 dir(s)