Date: Tue, 25 Oct 2022 09:25:13 +0200 From: Johan Henselmans <johan@netsense.nl> To: Mark Millard <marklmi@yahoo.com> Cc: freebsd-arm@freebsd.org Subject: Re: BeagleBone uboot: BeagleBone Green Gateway not defined in uboot? Message-ID: <1D4FD611-7420-4E52-9414-67F282DDA4C6@netsense.nl> In-Reply-To: <50347B94-0B6D-463C-9B87-499EBEA537D7@yahoo.com> References: <0EDDBAEA-CA91-4A64-BB93-BCB5D067BE00@netsense.nl> <467642CD-DF11-448C-AACA-43F7FB4DB572@yahoo.com> <50347B94-0B6D-463C-9B87-499EBEA537D7@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_1A0FD4BD-C46F-4AD8-8ABB-07EE0EDC2E97 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 I made some comments in between on both mails. > On 24 Oct 2022, at 23:30, Mark Millard <marklmi@yahoo.com> wrote: >=20 > On 2022-Oct-24, at 14:05, Mark Millard <marklmi@yahoo.com> wrote: >=20 >> On 2022-Oct-24, at 12:35, Johan Henselmans <johan@netsense.nl> wrote: >>=20 >>> I have tried to boot a Beaglebone Green Gateway via the current = GenericSD.img.xz at = https://download.freebsd.org/ftp/releases/arm/armv7/ISO-IMAGES/13.0/FreeBS= D-13.0-RELEASE-arm-armv7-GENERICSD.img.xz >>=20 >> You list 13.0-RELEASE 's image instead of 13.1-RELEASE 's image: >>=20 Sorry, my mistake, the one I downloaded was 13.1, I copied the wrong = link. Sorry for the confusion. >> = http://ftp3.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/13.1/FreeBSD-13.1-= RELEASE-arm-armv7-GENERICSD.img.xz >>=20 >> (I've no clue if it makes a difference.) >>=20 >>> The board booted, but it did not have anything functional in the = sense of wland or ethernet. >>>=20 >>> So I installed (after putting the SD-card in a BeagleBone Green, = which was able to find an ethernet port and a working internet = connection) the beaglebone uboot: >>> =3D=3D=3D=3D=3D >>> pkg install sysutils/u-boot-beaglebone >>> =3D=3D=3D=3D=3D >>=20 >> pkg install sysutils/u-boot-beaglebone >>=20 >> only puts things in the likes of: >>=20 >> /usr/local/share/u-boot/u-boot-beaglebone/ >>=20 >> /usr/local/share/u-boot/u-boot-beaglebone/ probably ended up >> with a README or some such file name for the content shown >> below. >>=20 >> # more /usr/ports/sysutils/u-boot-beaglebone/pkg-descr >> U-Boot loader for BeagleBone and BeagleBone Black. >>=20 >> To install this bootloader, copy the files MLO and bb-uboot.img to = the FAT >> partition on an SD card or the eMMC. Normally this is partition 1, = but >> different partitions can be set with U-Boot environment variables. >>=20 >> This version is patched so that: >> * API features are enabled. >> * A boot.scr (U-Boot scripts ) that loads ubldr.bin and execute it is = included >>=20 >> For information about running FreeBSD on BeagleBone or BeagleBone = Black, see >> https://wiki.freebsd.org/FreeBSD/arm/BeagleBone >>=20 >>=20 >>=20 >> You were not explicit. Did you do as described with MLO >> and bb-uboot.img ? >>=20 Yes I did. Only thing I did not know how to do was where to put the = boot.scr that the READMe mentions. That is why I reran the script on a Beaglebone, hoping that would = install the script. Mind you, I am not a pkg specialist. I do not know how to find out how this script is created = and where it is supposed to put. I looked in /usr/port/sysutils/u-boot-master and = /usr/port/sysutils/u-boot-beaglebone, but could not understand where this boot.scr was supposed to go >>=20 >>> That resulted in the message that there was no device tree: >>> =3D=3D=3D=3D=3D >>> Loading Environment from EXT4... >>> ** Unable to use mmc 0:1 for loading the env ** >>> Board: BeagleBone Black >>> <ethaddr> not set. Validating first E-fuse MAC >>> BeagleBone Black: >>> Model: SeeedStudio BeagleBone Green Gateway: >>> BeagleBone: cape eeprom: i2c_probe: 0x54: >>> BeagleBone: cape eeprom: i2c_probe: 0x55: >>> BeagleBone: cape eeprom: i2c_probe: 0x56: >>> BeagleBone: cape eeprom: i2c_probe: 0x57: >>> Net: eth0: MII MODE >>> cpsw, usb_ether >>> Press SPACE to abort autoboot in 0 seconds >>> board_name=3D[A335BNLT] ... >>> board_rev=3D[GG1A] ... >>> switch to partitions #0, OK >>> mmc0 is current device >>> SD/MMC found on device 0 >>> switch to partitions #0, OK >>> mmc0 is current device >>> Scanning mmc 0:1... >>> Found EFI removable media binary efi/boot/bootarm.efi >>> libfdt fdt_check_header(): FDT_ERR_BADMAGIC >>>=20 >>> <snip> >>> No valid device tree blob found! >>> WARNING! Trying to fire up the kernel, but no device tree blob = found! >>> =3D=3D=3D=3D=3D >>>=20 >>>=20 >>> How can I add a device tree blob for the BeagleBone Green Gateway? >>>=20 >>=20 >> Note: I've no experience with any BeagleBone variant. >> My comments are rather generic. >>=20 >=20 > Hmm, I do not see am335x-bonegreen-gateway.dts in any > of the source code trees I've got for releng/13.0 , > releng/13.1 , stable/13 , or main [so: 14] : >=20 > /usr/13_0R-src/sys/contrib/device-tree/src/arm/am335x-bone.dts > = /usr/13_0R-src/sys/contrib/device-tree/src/arm/am335x-boneblack-wireless.d= ts > /usr/13_0R-src/sys/contrib/device-tree/src/arm/am335x-boneblack.dts > /usr/13_0R-src/sys/contrib/device-tree/src/arm/am335x-boneblue.dts > = /usr/13_0R-src/sys/contrib/device-tree/src/arm/am335x-bonegreen-wireless.d= ts > /usr/13_0R-src/sys/contrib/device-tree/src/arm/am335x-bonegreen.dts >=20 > /usr/13_1R-src/sys/contrib/device-tree/src/arm/am335x-bone.dts > = /usr/13_1R-src/sys/contrib/device-tree/src/arm/am335x-boneblack-wireless.d= ts > /usr/13_1R-src/sys/contrib/device-tree/src/arm/am335x-boneblack.dts > /usr/13_1R-src/sys/contrib/device-tree/src/arm/am335x-boneblue.dts > = /usr/13_1R-src/sys/contrib/device-tree/src/arm/am335x-bonegreen-wireless.d= ts > /usr/13_1R-src/sys/contrib/device-tree/src/arm/am335x-bonegreen.dts >=20 > /usr/13S-src/sys/contrib/device-tree/src/arm/am335x-bone.dts > = /usr/13S-src/sys/contrib/device-tree/src/arm/am335x-boneblack-wireless.dts= > /usr/13S-src/sys/contrib/device-tree/src/arm/am335x-boneblack.dts > /usr/13S-src/sys/contrib/device-tree/src/arm/am335x-boneblue.dts > = /usr/13S-src/sys/contrib/device-tree/src/arm/am335x-bonegreen-wireless.dts= > /usr/13S-src/sys/contrib/device-tree/src/arm/am335x-bonegreen.dts >=20 > /usr/main-src/sys/contrib/device-tree/src/arm/am335x-bone.dts > = /usr/main-src/sys/contrib/device-tree/src/arm/am335x-boneblack-wireless.dt= s > /usr/main-src/sys/contrib/device-tree/src/arm/am335x-boneblack.dts > /usr/main-src/sys/contrib/device-tree/src/arm/am335x-boneblue.dts > = /usr/main-src/sys/contrib/device-tree/src/arm/am335x-bonegreen-wireless.dt= s > /usr/main-src/sys/contrib/device-tree/src/arm/am335x-bonegreen.dts >=20 > Looks like you would have to establish am335x-bonegreen-gateway.dtb > another way as things are. >=20 > I also did not find am335x-bonegreen-gateway.dtb in: >=20 > https://github.com/torvalds/linux/tree/master/arch/arm/boot/dts/ >=20 > so it would likely be some time before it shows up there for FreeBSD > to later import. >=20 > =3D=3D=3D > Mark Millard > marklmi at yahoo.com >=20 >=20 It seems the Beaglebne stuf is located at = https://github.com/beagleboard/BeagleBoard-DeviceTrees/ There is a am335x-bonegreen-gateway.dts available over there. I don=E2=80=99= t know why that stuff is not in torvalds tree. I know that the debian version is created from = https://github.com/RobertCNelson/omap-image-builder So my question would be then revolve around: how can I add that version = to FreeBSD arm? Is there some procedure documented somehwere how I should do this? Kind Regards, Johan Henselmans --Apple-Mail=_1A0FD4BD-C46F-4AD8-8ABB-07EE0EDC2E97 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQSodLt4EnpKN6iAlsNa7fo9b51glAUCY1ePWQAKCRBa7fo9b51g lNoeAJ0Uoa5+mwRozFu660ni2vprm+etHwCePHIdeYG58iVUEWTo6/fzuqrf7vc= =pFAV -----END PGP SIGNATURE----- --Apple-Mail=_1A0FD4BD-C46F-4AD8-8ABB-07EE0EDC2E97--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1D4FD611-7420-4E52-9414-67F282DDA4C6>