Home
Help
Search
Login
Register
OPNsense Forum
»
English Forums
»
Hardware and Performance
»
OPNsense 20.1 on ESPRESSOBin v4
« previous
next »
Print
Pages: [
1
]
Author
Topic: OPNsense 20.1 on ESPRESSOBin v4 (Read 6128 times)
tsgan
Newbie
Posts: 24
Karma: 6
OPNsense 20.1 on ESPRESSOBin v4
«
on:
December 26, 2019, 04:15:07 am »
OPNsense 20.1 works on Marvell Armada 3720 Community Board ESPRESSOBin v4 arm64 board:
https://dmesgd.nycbug.org/index.cgi?do=view&id=5266
Logged
gandalf
Newbie
Posts: 8
Karma: 0
Re: OPNsense 20.1 on ESPRESSOBin v4
«
Reply #1 on:
September 06, 2020, 09:45:25 am »
Héllo,
Is there any binary image available to test, plz ?
Logged
gandalf
Newbie
Posts: 8
Karma: 0
Re: OPNsense 20.1 on ESPRESSOBin v4
«
Reply #2 on:
September 07, 2020, 10:43:24 am »
https://people.freebsd.org/~ganbold/OPNsense-201912171639-OpenSSL-arm-aarch64.img.xz
«
Last Edit: September 07, 2020, 01:01:53 pm by gandalf
»
Logged
gandalf
Newbie
Posts: 8
Karma: 0
Re: OPNsense 20.1 on ESPRESSOBin v4
«
Reply #3 on:
September 07, 2020, 10:43:47 am »
https://forum.opnsense.org/index.php?action=profile;area=showposts;u=23410
«
Last Edit: September 07, 2020, 01:02:13 pm by gandalf
»
Logged
mimugmail
Hero Member
Posts: 6764
Karma: 494
Re: OPNsense 20.1 on ESPRESSOBin v4
«
Reply #4 on:
September 07, 2020, 12:55:37 pm »
There is no official ARM image yet available
Logged
WWW:
www.routerperformance.net
Support plans:
https://www.max-it.de/en/it-services/opnsense/
Commercial Plugins (German):
https://opnsense.max-it.de/
gandalf
Newbie
Posts: 8
Karma: 0
Re: OPNsense 20.1 on ESPRESSOBin v4
«
Reply #5 on:
September 07, 2020, 02:28:58 pm »
success bootup :
[code]TIM-1.0
WTMI-armada-17.10.5-bb8f823
WTMI: system early-init
SVC REV: 4, CPU VDD voltage: 1.120V
Fill memory before self refresh...done
Now in Self-refresh Mode
Exited self-refresh ...
Self refresh Pass.
DDR self test mode test done!!
Vref read training
===================
Final vdac_value 0x0000001F
Vref write training
===================
Final vref_value 0x0000001F
DLL TUNING
==============
DLL 0xc0001050[21:16]: [a,34,1f]
DLL 0xc0001050[29:24]: [b,2b,1b]
DLL 0xc0001054[21:16]: [10,32,21]
DLL 0xc0001054[29:24]: [11,2e,1f]
DLL 0xc0001074[21:16]: [0,3f,1f]
DLL 0xc0001074NOTICE: Booting Trusted Firmware
NOTICE: BL1: v1.3(release):armada-17.10.3:39a62a1
NOTICE: BL1: Built : 15:40:57, Jun 1 2NOTICE: BL2: v1.3(release):armada-17.10.3:39a62a1
NOTICE: BL2: Built : 15:40:59, Jun 1 201NOTICE: BL31: v1.3(release):armada-17.10.3:39a62a1
NOTICE: BL31:
U-Boot 2017.03-armada-17.10.2-g14aeedc (Jun 01 2018 - 15:39:10 +0800)
Model: Marvell Armada 3720 Community Board ESPRESSOBin
CPU @ 1000 [MHz]
L2 @ 800 [MHz]
TClock @ 200 [MHz]
DDR @ 800 [MHz]
DRAM: 1 GiB
U-Boot DT blob at : 000000003f7161b8
Comphy-0: USB3 5 Gbps
Comphy-1: PEX0 2.5 Gbps
Comphy-2: SATA0 6 Gbps
SATA link 0 timeout.
AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl SATA mode
flags: ncq led only pmp fbss pio slum part sxs
PCIE-0: Link down
MMC: sdhci@d0000: 0, sdhci@d8000: 1
SF: Detected mx25u3235f with page size 256 Bytes, erase size 64 KiB, total 4 MiB
Net: eth0: neta@30000 [PRIME]
Hit any key to stop autoboot: 0
Marvell>> setenv fdt_name 'dtb/marvell/armada-3720-espressobin.dtb'
Marvell>> setenv image_name 'EFI/BOOT/bootaa64.efi'
Marvell>> setenv bootmmc 'mmc dev 0;fatload mmc 0:1 $kernel_addr $image_name;fatload mmc 0:1 $fdt_addr $fdt_name; bootefi $ke'
Marvell>> run bootmmc
switch to partitions #0, OK
mmc0 is current device
reading EFI/BOOT/bootaa64.efi
672160 bytes read in 48 ms (13.4 MiB/s)
reading dtb/marvell/armada-3720-espressobin.dtb
16088 bytes read in 21 ms (748 KiB/s)
## Starting EFI application at 07000000 ...
Scanning disk sdhci@d0000.blk...
Scanning disk sdhci@d8000.blk...
Found 2 disks
Consoles: EFI console
Reading loader env vars from /efi/freebsd/loader.env
FreeBSD/arm64 EFI loader, Revision 1.1
(Sat Dec 14 19:58:45 UTC 2019 tsgan@nanopc-t4)
Command line arguments: loader.efi
Image base: 0x7000000
EFI version: 2.05
EFI Firmware: Das U-boot (rev 0.00)
Console: efi (0x1000)
Load Path: bootefi
Load Device: bootefi
Startup error in /boot/lua/loader.lua:
LUA ERROR: cannot open /boot/lua/loader.lua: invalid argument.
can't load 'kernel'
Type '?' for a list of commands, 'help' for more detailed help.
OK set currdev=disk0p2
OK boot
/boot/kernel/kernel text=0x9af714 data=0x192030 data=0x0+0x7a11e0 syms=[0x8+0x14a228+0x8+0x13450e]
Using DTB provided by EFI at 0x8000000.
---<<BOOT>>---
KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 1992-2019 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 13.0-CURRENT #0 f8a1d78a50c-c265096(master): Sun Dec 15 03:12:14 UTC 2019
tsgan@nanopc-t4:/opt/obj/opt/freebsd/arm64.aarch64/sys/SMP arm64
FreeBSD clang version 9.0.0 (tags/RELEASE_900/final 372316) (based on LLVM 9.0.0)
WARNING: WITNESS option enabled, expect reduced performance.
VT: init without driver.
module firmware already present!
Starting CPU 1 (1)
...CUTTED HERE...
Default interfaces not found -- Running interface assignment option.
Press any key to start the manual interface assignment: 1
Valid interfaces are:
mvneta0 84:fc:85:90:74:00 NETA controller
You now have the opportunity to configure VLANs. If you don't require VLANs
for initial connectivity, say no here and use the GUI to configure VLANs later.
Do you want to configure VLANs now? [y/N]: n
If you do not know the names of your interfaces, you may choose to use
auto-detection. In that case, disconnect all interfaces now before
hitting 'a' to initiate auto detection.
Enter the WAN interface name or 'a' for auto-detection:
Enter the LAN interface name or 'a' for auto-detection
NOTE: this enables full Firewalling/NAT mode.
(or nothing if finished): mvneta0
Enter the Optional interface 1 name or 'a' for auto-detection
(or nothing if finished):
The interfaces will be assigned as follows:
LAN -> mvneta0
Do you want to proceed? [y/N]: y
Writing configuration...done.
Configuring loopback interface...lo0: link state changed to UP
done.
Configuring kernel modules...done.
Setting up extended sysctls...done.
Setting timezone...done.
Writing firmware setting...done.
Writing trust files...done.
Setting hostname: OPNsense.localdomain
Generating /etc/hosts...done.
Configuring system logging...done.
Configuring loopback interface...done.
Creating wireless clone interfaces...done.
Configuring LAN interface...done.
Creating IPsec VTI instances...done.
Generating /etc/resolv.conf...done.
Configuring firewall.......done.
Starting PFLOG...done.
Starting web GUI...done.
Configuring CRON...done.
Setting up routes...done.
Generating /etc/hosts...done.
lock order reversal:
1st 0xfffffd0019cd3ba8 ufs (ufs) @ /opt/freebsd/sys/kern/vfs_mount.c:1006
2nd 0xfffffd0019b07ba8 devfs (devfs) @ /opt/freebsd/sys/kern/vfs_mount.c:1017
stack backtrace:
#0 0xffff00000048cd6c at witness_debugger+0x64
#1 0xffff0000003f863c at lockmgr_lock_fast_path+0x1a8
#2 0xffff0000007c09bc at VOP_LOCK1_APV+0x7c
#3 0xffff000000502798 at _vn_lock+0x58
#4 0xffff0000004e8ae8 at vfs_domount+0xbe8
#5 0xffff0000004e7478 at vfs_donmount+0x7c4
#6 0xffff0000004e6c74 at sys_nmount+0x60
#7 0xffff000000779aac at do_el0_sync+0x514
#8 0xffff00000075f214 at handle_el0_sync+0x90
Starting DHCPv4 service...done.
Starting DHCPv6 service...done.
Starting router advertisement service...done.
Starting Unbound DNS...done.
Setting up gateway monitors...done.
Configuring firewall.......done.
Starting PFLOG...done.
Syncing OpenVPN settings...done.
Starting NTP service...deferred.
Logged
gandalf
Newbie
Posts: 8
Karma: 0
Re: OPNsense 20.1 on ESPRESSOBin v4
«
Reply #6 on:
September 07, 2020, 07:14:35 pm »
Webui access ok
Logged
pablot
Newbie
Posts: 2
Karma: 1
Re: OPNsense 20.1 on ESPRESSOBin v4
«
Reply #7 on:
March 05, 2021, 06:38:26 pm »
Any news about this?
IS anyone actually using OPNSense on an Espressobin ?
Logged
Print
Pages: [
1
]
« previous
next »
OPNsense Forum
»
English Forums
»
Hardware and Performance
»
OPNsense 20.1 on ESPRESSOBin v4