Hi Robert,

*Where "exactly" is the "boot" folder on the partition in raw terms? Is it 
fat? etc.. *
There are 2 folders in sdcard root:

   - boot
   - rootfs

The file system is FAT. Here is *lsblk* on my host Ubuntu

pavel@ALABAMA:~$ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop0         7:0    0    97M  1 loop /snap/core/9665
loop1         7:1    0   2,2M  1 loop /snap/gnome-system-monitor/145
loop2         7:2    0    55M  1 loop /snap/core18/1880
loop3         7:3    0  55,3M  1 loop /snap/core18/1885
loop4         7:4    0  96,6M  1 loop /snap/core/9804
loop5         7:5    0   956K  1 loop /snap/gnome-logs/100
loop6         7:6    0   956K  1 loop /snap/gnome-logs/93
loop7         7:7    0   276K  1 loop /snap/gnome-characters/550
loop8         7:8    0   276K  1 loop /snap/gnome-characters/539
loop9         7:9    0 255,6M  1 loop /snap/gnome-3-34-1804/36
loop10        7:10   0 161,4M  1 loop /snap/gnome-3-28-1804/128
loop11        7:11   0   2,4M  1 loop /snap/gnome-calculator/730
loop12        7:12   0   2,2M  1 loop /snap/gnome-system-monitor/148
loop13        7:13   0   2,4M  1 loop /snap/gnome-calculator/748
loop14        7:14   0 140,7M  1 loop /snap/gnome-3-26-1604/98
loop15        7:15   0 255,6M  1 loop /snap/gnome-3-34-1804/33
loop16        7:16   0  54,8M  1 loop /snap/gtk-common-themes/1502
loop17        7:17   0 160,2M  1 loop /snap/gnome-3-28-1804/116
loop18        7:18   0  62,1M  1 loop /snap/gtk-common-themes/1506
loop19        7:19   0 140,7M  1 loop /snap/gnome-3-26-1604/100
sda           8:0    1  14,9G  0 disk 
├─sda1        8:1    1    64M  0 part /media/pavel/boot
└─sda2        8:2    1     1G  0 part /media/pavel/rootfs
nvme0n1     259:0    0 238,5G  0 disk 
└─nvme0n1p1 259:1    0 238,5G  0 part /
pavel@ALABAMA:~$

Here is fragment of *fdisk*:
Device     Boot  Start     End Sectors Size Id Type
/dev/sda1  *      2048  133119  131072  64M  c W95 FAT32 (LBA)
/dev/sda2       133120 2230271 2097152   1G 83 Linux

To format sdcard I used script from here:
format-sdcard.sh 
<https://github.com/PacktPublishing/Mastering-Embedded-Linux-Programming-Second-Edition>

Thanks,

Sincerely,

Pavel
On Thursday, August 13, 2020 at 8:46:17 PM UTC+2, RobertCNelson wrote:
>
> On Thu, Aug 13, 2020 at 12:58 PM Pavel Yermolenko <[email protected] 
> <javascript:>> wrote: 
> > 
> > Hello, 
> > 
> > After copying MLO and u-boot.img in the boot folder of microSD and then 
> powering BeagleBone Black ((1) press and hold the Boot Switch button, (2) 
> power up the board; (3) release the Boot Switch button after about 5 
> seconds) I don't see U-Boot# prompt in terminal. 
> > Instead, I see continuous activity in the terminal. 
>
> "continuous activity"  can you share what you actually get over serial? 
>
> The BootRom on the AM335x is actually more picky than that..  Where 
> "exactly" is the "boot" folder on the partition in raw terms? Is it 
> fat? etc.. 
>
> In the old days, when we used FAT and real files, the FAT partition 
> must be at the very start of the medium, size really doesn't matter, 
> we used a partition size of 96MB thru 16MB over the years. Next, after 
> formatting, it's was always way more reliable to write the "MLO" file 
> 1st, then the "u-boot.img"...  Fun ROM bugs.. 
>
> Today we just leave a 4MB hole and dd the files to a very specific 
> address on the medium..  It's more reliable, (unless you use a Linux 
> Virtual machine on top of Windows, then it seems to never be correctly 
> written..) 
>
> sudo dd if=./MLO of=/dev/sdb count=1 seek=1 bs=128k 
> sudo dd if=./u-boot.img of=/dev/sdb count=2 seek=1 bs=384k 
>
> 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/c25d9a93-3ba7-46cf-a242-26922cf7465bo%40googlegroups.com.

Reply via email to