On Sat, May 28, 2016, at 09:27 AM, Jonathan Gray wrote:
> On Thu, May 26, 2016 at 10:40:29AM -0600, Aaron Bieber wrote:
> >
> >
> > On Mon, May 23, 2016, at 07:41 PM, Jonathan Gray wrote:
> > > On Mon, May 23, 2016 at 01:58:44PM -0600, Aaron Bieber wrote:
> > > > Simply flashing the miniroot image onto an SD card and booting will
> > > > result in:
> > > >
> > > > reading uEnv.txt
> > > > 162 bytes read in 3 ms (52.7 KiB/s)
> > > > Importing environment from mmc0 ...
> > > > Running uenvcmd ...
> > > > reading bsdrd.umg
> > > > 10883512 bytes read in 507 ms (20.5 MiB/s)
> > > > ## Booting kernel from Legacy Image at 82800000 ...
> > > > Image Name: boot
> > > > Image Type: ARM Linux Kernel Image (uncompressed)
> > > > Data Size: 10883448 Bytes = 10.4 MiB
> > > > Load Address: 80300000
> > > > Entry Point: 80300000
> > > > Verifying Checksum ... OK
> > > > Loading Kernel Image ... Image too large: increase
> > > > CONFIG_SYS_BOOTM_LEN
> > > > Must RESET board to recover
> > > > resetting ...
> > > >
> > > > U-Boot SPL 2015.10 (Feb 01 2016 - 13:59:48)
> > > > OMAP4460 ES1.1
> > >
> > > The miniroots are built with u-boot 2016.05 why do you have
> > > this version? There is no uEnv.txt only a boot.scr
> >
> > I built a version of u-boot with CONFIG_SYS_BOOTM_LEN bumped, to get
> > past this initial error.
> >
> > >
> > > Can you send the output of printenv and try
> > >
> > > setenv loadaddr 0x82800000 ;
> > > run findfdt ;
> > > load mmc ${mmcdev}:1 ${loadaddr} bsd.umg ;
> > > load mmc ${mmcdev}:1 ${fdt_addr_r} ${fdtfile} ;
> > > bootm ${loadaddr} - ${fdt_addr_r} ;
> > >
> >
> > Net: No ethernet found.
> > Hit any key to stop autoboot: 0
> > switch to partitions #0, OK
> > mmc0 is current device
> > SD/MMC found on device 0
> > reading boot.scr
> > 213 bytes read in 3 ms (69.3 KiB/s)
> > Running bootscript from mmc0 ...
> > ## Executing script at 82000000
> > reading bsd.umg
> > 10883556 bytes read in 480 ms (21.6 MiB/s)
> > reading omap4-panda-es.dtb
> > 57353 bytes read in 6 ms (9.1 MiB/s)
> > ## Booting kernel from Legacy Image at 82000000 ...
> > Image Name: boot
> > Image Type: ARM Linux Kernel Image (uncompressed)
> > Data Size: 10883492 Bytes = 10.4 MiB
> > Load Address: 80300000
> > Entry Point: 80300000
> > Verifying Checksum ... OK
> > ## Flattened Device Tree blob at 88000000
> > Booting using the fdt blob at 0x88000000
> > Loading Kernel Image ... Image too large: increase
> > CONFIG_SYS_BOOTM_LEN
> > Must RESET board to recover
> > resetting ...
> >
> > U-Boot SPL 2016.05 (May 17 2016 - 17:10:59)
> > OMAP4460 ES1.1
> > Trying to boot from MMC1
> > SPL: Please implement spl_start_uboot() for your board
> > SPL: Direct Linux boot not active!
> > reading u-boot.img
> > reading u-boot.img
> >
> >
> > U-Boot 2016.05 (May 17 2016 - 17:10:59 +1000)
> >
> > CPU : OMAP4460 ES1.1
> > Board: OMAP4 Panda
> > I2C: ready
> > DRAM: 1 GiB
> > MMC: OMAP SD/MMC: 0
> > reading uboot.env
> >
> > ** Unable to read "uboot.env" from mmc0:1 **
> > Using default environment
> >
> > Net: No ethernet found.
> > Hit any key to stop autoboot: 0
> > => setenv loadaddr 0x82800000 ;
> > => run findfdt ;
> > => load mmc ${mmcdev}:1 ${loadaddr} bsd.umg ;
> > reading bsd.umg
> > 10883556 bytes read in 480 ms (21.6 MiB/s)
> > => load mmc ${mmcdev}:1 ${fdt_addr_r} ${fdtfile} ;
> > reading omap4-panda-es.dtb
> > 57353 bytes read in 7 ms (7.8 MiB/s)
> > => bootm ${loadaddr} - ${fdt_addr_r} ;
> > ## Booting kernel from Legacy Image at 82800000 ...
> > Image Name: boot
> > Image Type: ARM Linux Kernel Image (uncompressed)
> > Data Size: 10883492 Bytes = 10.4 MiB
> > Load Address: 80300000
> > Entry Point: 80300000
> > Verifying Checksum ... OK
> > ## Flattened Device Tree blob at 88000000
> > Booting using the fdt blob at 0x88000000
> > Loading Kernel Image ... Image too large: increase
> > CONFIG_SYS_BOOTM_LEN
> > Must RESET board to recover
> > resetting ...
>
> The latest snapshot has the miniroots switched to use efiboot as
> well, which at only 64KB is quite a bit smaller than a kernel image.
>
Now the boot stuff still works, but the issue with the disk stuff is
still there:
Available disks are: sd0.
Which disk is the root disk? ('?' for details) [sd0]
Disk: sd0 geometry: 1936/255/63 [31116288 Sectors]
Offset: 0 Signature: 0xAA55
Starting Ending LBA Info:
#: id C H S - C H S [ start: size ]
-------------------------------------------------------------------------------
*0: 0C 0 32 33 - 0 97 33 [ 2048: 4096 ]
Win95 FAT32L
1: 00 0 0 0 - 0 0 0 [ 0: 0 ]
unused
2: 00 0 0 0 - 0 0 0 [ 0: 0 ]
unused
3: A6 0 97 34 - 2 75 9 [ 6144: 30720 ]
OpenBSD
Use (W)hole disk$ or (E)dit the MBR? [whole]
Creating a msdos partition and an OpenBSD partition for rest of
sd0...done.
/dev/rsd0i: 32668 sectors in 8167 FAT16 clusters (2048 bytes/cluster)
bps=512 spc=4 res=1 nft=2 rde=512 sec=32768 mid=0xf8 spf=32 spt=63
hds=255 hid=2048
The auto-allocated layout for sd0 is:
# size offset fstype [fsize bsize cpg]
a: 480.4M 34816 4.2BSD 2048 16384 1 # /
b: 880.8M 1018720 swap
c: 15193.5M 0 unused
d: 760.7M 2822720 4.2BSD 2048 16384 1 # /tmp
e: 1121.1M 4380544 4.2BSD 2048 16384 1 # /var
f: 1300.4M 6676544 4.2BSD 2048 16384 1 # /usr
g: 752.2M 9339808 4.2BSD 2048 16384 1 #
/usr/X11R6
h: 2848.8M 10880416 4.2BSD 2048 16384 1 #
/usr/local
i: 16.0M 2048 MSDOS
j: 1184.2M 16714848 4.2BSD 2048 16384 1 #
/usr/src
k: 1620.3M 19140000 4.2BSD 2048 16384 1 #
/usr/obj
l: 4227.4M 22458432 4.2BSD 2048 16384 1 # /home
Use (A)uto layout, (E)dit auto layout, or create (C)ustom layout? [a]
newfs: reduced number of fragments per cylinder group from 61488 to
61248 to enlarge last cylinder group
/dev/rsd0a: 480.4MB in 983904 sectors of 512 bytes
5 cylinder groups of 119.62MB, 7656 blocks, 15360 inodes each
newfs: wtfs: write error on block 416: Input/output error
newfs: 28f87dcc8651edd5.l: No such file or directory
newfs: 28f87dcc8651edd5.d: No such file or directory
newfs: 28f87dcc8651edd5.f: No such file or directory
newfs: 28f87dcc8651edd5.g: No such file or directory
newfs: 28f87dcc8651edd5.h: No such file or directory
newfs: 28f87dcc8651edd5.k: No such file or directory
newfs: 28f87dcc8651edd5.j: No such file or directory
newfs: 28f87dcc8651edd5.e: No such file or directory
mount_ffs: 28f87dcc8651edd5.a on /mnt: No such file or directory
mount_ffs: 28f87dcc8651edd5.l on /mnt/home: No such file or directory
mount_ffs: 28f87dcc8651edd5.d on /mnt/tmp: No such file or directory
mount_ffs: 28f87dcc8651edd5.f on /mnt/usr: No such file or directory
mount_ffs: 28f87dcc8651edd5.g on /mnt/usr/X11R6: No such file or
directory
mount_ffs: 28f87dcc8651edd5.h on /mnt/usr/local: No such file or
directory
mount_ffs: 28f87dcc8651edd5.k on /mnt/usr/obj: No such file or directory
mount_ffs: 28f87dcc8651edd5.j on /mnt/usr/src: No such file or directory
mount_ffs: 28f87dcc8651edd5.e on /mnt/var: No such file or directory
WARNING! The following filesystems were not properly mounted:
/mnt (28f87dcc8651edd5.a)
/mnt/home (28f87dcc8651edd5.l)
/mnt/tmp (28f87dcc8651edd5.d)
/mnt/usr (28f87dcc8651edd5.f)
/mnt/usr/X11R6 (28f87dcc8651edd5.g)
/mnt/usr/local (28f87dcc8651edd5.h)
/mnt/usr/obj (28f87dcc8651edd5.k)
/mnt/usr/src (28f87dcc8651edd5.j)
/mnt/var (28f87dcc8651edd5.e)
Continue anyway? [no]
