I feel a little lost.
In one of your previous mails you mentioned this document:
https://www.digikey.com/eewiki/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-SetupmicroSDcard
And there is no mention on *extlinux.conf*.
So, I don't understand what is its actual role in sd-card setup !
Anyway, I terminated my sd-card setup by this two commands:
cp -v MLO /media/rootfs/
cp -v u-boot.img /media/rootfs/
Then I tried to boot from sd-card and boot process failed ... BBB switched
to eMMC and booted from it.
5 min ago, I repeated to setup the SD card fearing that the previous time I
missed something.
To my amazement I found out that after formatting the card (i.e. sudo
mkfs.ext4 -L rootfs -O ^metadata_csum,^64bit ${DISK}1) the *MLO* and
*u-boot.img* files are still there - in the *rootfs* partition, they
weren't erased during formatting:
pavel@ALABAMA:~/u-boot_chris$ sudo mkfs.ext4 -L rootfs -O
^metadata_csum,^64bit ${DISK}1
mke2fs 1.44.1 (24-Mar-2018)
Creating filesystem with 3888512 4k blocks and 972944 inodes
Filesystem UUID: bd1ae1cd-6b3e-4899-acf5-c4f05e298a9f
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208
Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done
pavel@ALABAMA:~/u-boot_chris$ ls /media/
pavel/ rootfs/
pavel@ALABAMA:~/u-boot_chris$ ls /media/rootfs/
MLO u-boot.img
pavel@ALABAMA:~/u-boot_chris$ ls /media/rootfs/ -l
total 620
-rw-r--r-- 1 root root 108408 août 27 17:04 MLO
-rw-r--r-- 1 root root 523429 août 27 17:05 u-boot.img
pavel@ALABAMA:~/u-boot_chris$
On Thursday, August 27, 2020 at 5:41:55 PM UTC+2, RobertCNelson wrote:
> On Thu, Aug 27, 2020 at 10:36 AM Pavel Yermolenko <[email protected]
> <javascript:>> wrote:
> >
> > I copied MLO and u-boot.img in /rootfs and tried to boot from sd-card.
> > Didn't work -
>
> Correct, the BOOTROM is very picky, i thought, we went over this in
> your discussion thread previously.
>
> > boot from sd-card filed and BBB was booted from eMMC:
>
> > U-Boot 2019.04-00002-g07d5700e21 (Mar 06 2020 - 11:24:55 -0600), Build:
> jenkins-github_Bootloader-Builder-137
> >
>
> > Found /boot/extlinux/extlinux.conf
> > Retrieving file: /boot/extlinux/extlinux.conf
> > 256 bytes read in 14 ms (17.6 KiB/s)
> > 1: Linux 4.19.94-ti-r42
> > Retrieving file: /boot/vmlinuz-4.19.94-ti-r42
> > 10095592 bytes read in 648 ms (14.9 MiB/s)
> > append: console=ttyO0,115200n8 root=/dev/mmcblk1p1 ro rootfstype=ext4
> coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100
> quiet
> > Retrieving file: /boot/dtbs/4.19.94-ti-r42/am335x-boneblack.dtb
> > 59483 bytes read in 25 ms (2.3 MiB/s)
> > ## Flattened Device Tree blob at 88000000
> > Booting using the fdt blob at 0x88000000
> > Loading Device Tree to 8ffee000, end 8ffff85a ... OK
> >
> > Starting kernel ...
> >
> > [ 0.000763] timer_probe: no matching timers found
> > [ 0.115067] l4_wkup_cm:clk:0010:0: failed to disable
> > [ 0.765905] omap_voltage_late_init: Voltage driver support not added
> >
> > Debian GNU/Linux 10 beaglebone ttyS0
> >
> > BeagleBoard.org Debian Buster IoT Image 2020-04-06
> >
> > Support: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian
> >
> > default username:password is [debian:temppwd]
> >
> > beaglebone login:
>
> Congrates, you've got a working /boot/extlinux/extlinux.conf so my
> free job is done. ;)
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/1a0b66f0-7485-4a22-89de-21f7d9da8e80o%40googlegroups.com.
