Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 18 Oct 2019 11:17:16 -0700
From:      glenn <pygr@sonic.net>
To:        freebsd-arm@freebsd.org
Subject:   Re: ClearFog Base serial console on FreeBSD 11.2?
Message-ID:  <7478894E-DF5D-49D9-AFD5-4D6ADE1A2084@sonic.net>
In-Reply-To: <CAPv3WKekue6o65EyBcbbH7nEUxUY4Yc6Mr6cpN-mUUzdJRRJCA@mail.gmail.com>
References:  <mailman.1601.1566068907.74383.freebsd-arm@freebsd.org> <D89D310F-551C-485B-93F8-13C51960A1CC@sonic.net> <CAPv3WKekue6o65EyBcbbH7nEUxUY4Yc6Mr6cpN-mUUzdJRRJCA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi Marcin,

Thank you for your quick response and suggestion, but it=E2=80=99s not =
clear to me how to proceed. Attempts to compile (with dtc) the file =
armada-388-gp.dts located in 11.2 sys/boot/fdt/dts/arm failed to include =
files (like skeleton.dtsi and =
dt-bindings/interrupt-controller/arm-gic.h) that weren=E2=80=99t there  =
but were in sys/gnu/dts.

If dts files in 12.0 source are used to create dtb files, shouldn=E2=80=99=
t those dtb files work with 11.2?

I=E2=80=99ve also tried to get into a fresh install and boot of the OS =
on the device via ssh, but without success. To that end, there is the =
following /etc/rc.conf:

hostname=3D=E2=80=9CFreeBSD11.2=E2=80=9D
defaultrouter=3D=E2=80=9C10.137.113.1=E2=80=9D
syslog_flags=3D=E2=80=9C-ss=E2=80=9D
sshd_enable=3D=E2=80=9CYES=E2=80=9D
ifconfig_mvneta0=3D=E2=80=9Cinet 10.137.113.200/24=E2=80=9D

Pings to 10.137.113.200 fail as if nothing is there.

Glenn

> On Oct 17, 2019, at 4:03 PM, Marcin Wojtas <mw@semihalf.com> wrote:
>=20
> Hi Glenn,
>=20
> The release/11.2.0 is missing a huge amount of patches for a38x, which
> were merged later. However the initial support should work - please
> try dts from sys/boot/fdt/dts/arm/. At that time the port was not
> compatible with the Linux bindings from sys/gnu/dts/arm.
>=20
> Please let know if it helped.
>=20
> Best regards,
> Marcin
>=20
> pt., 18 pa=C5=BA 2019 o 00:40 glenn <pygr@sonic.net> napisa=C5=82(a):
>>=20
>> FreeBSD12.0 and 12.1 can be made to work properly on a ClearFog Base, =
but so far, for 11.2, I haven=E2=80=99t been able to get an interactive =
serial console after control is passed to the kernel during the boot =
process. U-boot and ubldr.bin seem to work well.
>>=20
>> ...
>> U-Boot env: loaderdev not set, will probe all devices.
>> Found U-Boot device: disk
>>  Probing all disk devices...
>>  Checking unit=3D0 slice=3D<auto> partition=3D<auto>... good.
>> Booting from disk0s3a:
>> /boot/kernel/kernel data=3D0x82c5e4+0xaba1c =
syms=3D[0x4+0x8cd30+0x4+0xe2c1f]
>> /boot/dtb/armada-388-clearfog.dtb size=3D0x675c
>> Loading /boot/defaults/loader.conf
>> /
>> Hit [Enter] to boot immediately, or any other key for command prompt.
>> Booting [/boot/kernel/kernel]...
>> Using DTB from loaded file '/boot/dtb/armada-388-clearfog.dtb'.
>> Kernel entry at 0xc00100...
>> Kernel args: (null)
>>=20
>>=20
>>=20
>> The reason for wanting to get 11.2 working is that, currently, =
OPNsense doesn=E2=80=99t run on 12.0 or 12.1.
>>=20
>> What does it take to get a serial console driver like uart-dev-snps.c =
to work with 11.2?
>>=20
>>=20
>> _______________________________________________
>> freebsd-arm@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
>> To unsubscribe, send any mail to =
"freebsd-arm-unsubscribe@freebsd.org"
>=20




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7478894E-DF5D-49D9-AFD5-4D6ADE1A2084>