Re: Heads up: TI OMAP3 and AM335x switched to FDT

["John D. Baker" <jdbaker%consolidated.net@localhost>]

On Tue, 3 Dec 2019, Jared McNeill wrote:

> On the FAT partition:
> 
>   /BOOT/EFI/bootarm.efi

Oh?  I copied the layout shown in the FAT partition of "armv7.img" and
it showed:

  /EFI/BOOT/bootarm.efi

(This is NetBSD/evbarm-9.0_RC1, btw.)

>   /dtb/am335x-boneblack.dtb

Or in my case "am335x-bonegreen.dtb".

> In the EFI bootloader, you can get a list of devices with the 'dev'
> command:
> 
>   > dev
>   hd0 (29 GB): VenHw(E61D73B9-A384-4ACC-AEAB-82E828F3628B)/Usb(0x6,0x0)
>     hd0a (29 GB): 4.2BSD
>     hd0e (80 MB): MSDOS
>   hd1 (1832 MB): VenHw(E61D73B9-A384-4ACC-AEAB-82E828F3628B)/Usb(0x6,0x1)
>   net0 90:59:af:5c:d0:94
> 
>   default: hd0a

Mine shows:

  > dev
  hd0 (7600 MB): VenHw(E61D73B9-A384-4ACC-AEAB-82E828F3628B)/Usb(0x6,0x0)
  hd1 (3688 MB): VenHw(E61D73B9-A384-4ACC-AEAB-82E828F3628B)/Usb(0x6,0x1)
  net0 xx:xx:xx:xx:xx:xx

  default: net0

even though both the SD card (hd0) and the on-board eMMC have MBRs,
disklabels and a number of partitions.

> Boot from the network with:
> 
>   boot net0:netbsd
> 
> The kernel will select the network interface with a mac address matching
> the "net0" mac address above as root device by default. You can override
> this with the root= kernel cmdline option.

Mine did not and explicitly requires "root=cpsw0" on the command line
or "setenv bootargs root=cpsw0" before loading "bootarm.efi" or else it
doesn't know what device is the root device and prompts for it.

> > CACHE: Misaligned operation at range [9c701028, 9c7010e8]
> 
> These are debug messages from U-Boot. We can probably just comment
> them out of our pkg.

They are certainly disconcerting when trying something new.


Lacking visibility of my SD/eMMC partitions from 'bootarm.efi', I can
boot from them manually with:

  run findfdt
  fatload mmc 0 ${loadaddr} netbsd-GENERIC.ub
  fatload mmc 0 ${fdtaddr} dtb/${fdtfile}
  setenv bootargs root=ld0a
  bootm ${loadaddr} - ${fdtaddr}

but I get a string of:

[...]
Mon Dec  2 18:24:29 CST 2019
Starting root file system check:
/dev/rld0a: file system is clean; not checking
[   3.8399179] sdhc0: timeout waiting for mask 0x400 value 0x400 (state=0x1e70106)
[   3.9899178] sdhc0: timeout waiting for mask 0x3 value 0 (state=0x1f70506)
[   3.9899178] sdhc0: command or data phase inhibited
[   4.0399180] ld0a: error writing fsbn 1553336 of 1553336-1553343 (ld0 bn 3698360; cn 458 tn 80 sn 8), retrying
[   4.0509067] sdhc0: cmd timeout error
[   4.0509067] ld0a: error writing fsbn 3472080 of 3472080-3472087 (ld0 bn 5617104; cn 696 tn 72 sn 24), retrying
[   4.0602377] sdhc0: cmd timeout error
[   4.0602377] ld0a: error writing fsbn 3311992 of 3311992-3311999 (ld0 bn 5457016; cn 676 tn 91 sn 19), retrying
[...]

and it eventually fails over to single-user mode.

I can still boot the last kernel I built from the BEAGLEBONE config and
it does not have these problems.

I'm operating only on the SD card right now as I'm wary of screwing up
something on the eMMC...

Thanks for the pointers.

-- 
|/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
|\ / jdbaker[snail]consolidated[flyspeck]net  OpenBSD            FreeBSD
| X  No HTML/proprietary data in email.   BSD just sits there and works!
|/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645