SolidRun - A38X ClearFog

Description

Some ads I guess from the manufacturer:

Discover the endless potential of the powerful ARM based boards of ClearFog. The family includes the ClearFog Pro and ClearFog Base. Harnessing the robust processing abilities of the ARMADA 38x SoC from Marvell, the ClearFog offers vast application potential as a flexible development board or a ready to deploy solution. Alongside the powerful ARMADA 38x SoC, the ClearFog includes a variety of I/O and connectivity technologies such as multiple mini-PCIe/mSATA sockets, audio/telephony module header, PoE expansion header, mikroBUS™ – a simple socket allowing you to integrate a wide range of MikroElektronika click boards™ modular extensions.

Comparison Table

Description/Model Clearfog Base Clearfog Pro
MicroSOM A380 / A388 SoM A380 / A388 SoM
Memory and Storage 256MB / 1GB
M.2*
µSD / eMMC (optional) 		256MB / 1GB
M.2
µSD / eMMC (optional)
Connectivity 1 x mSATA/mPCIE
1 x USB 3.0 port
2 x Port dedicated Ethernet
1 x SFP (A388 only) 		2 x mSATA/mPCIE
1 x USB 3.0 port
1 x Port dedicated Ethernet
6 x Port switched Ethernet
1 x SFP (A388 only)
I/O and Misc. Analog Audio
GPIO Header (MikroBus)
Indication LEDs
User Push Buttons
PoE expansion header
RTC Battery
FTDI (Console Only) / Debug Header 		Analog Audio/TDM module support
GPIO Header (MikroBus)
Indication LEDs
User Push Buttons
PoE expansion header
RTC Battery
FTDI (Console Only) / Debug Header
JTAG Header
OS Support Linux Kernel 3.x, OpenWrt, Yocto Linux Kernel 3.x, OpenWrt, Yocto
Power Wide range 9V - 32V Wide range 9V - 32V
Advanced Power Control
Fan Control
Dimensions 100mm x 74mm (TBD) 225mm x 100mm
Enclosure available available

* M.2 includes USB 3.0 support (in carrier Base only)

MicroSom available in Commercial (0°C ~ 70°C ambient) and Industrial grade (-40°C ~ 85°C ambient).
ARMADA 38x SoC maximum die temperature must be below 115°C in both Commercial and Industrial grades.
ARMADA 38x SoC processor maximum speed for industrial grade devices is 1.3GHz

Supported Versions

Hardware Highlights

Installation

→ Install OpenWrt (generic explanation)

U-Boot

To get the device bootable you need an additional u-boot Image suited for the boot device of your choice.
Choose beetwen “SolidRun” Builds or “OpenWRT” Builds.

u-boot image boot device
u-boot-clearfog-base-emmc-boot0.kwb
u-boot-clearfog-pro-emmc-boot0.kwb 		eMMC boot from “boot0” Partition (4MiB, 2MiB used - Start: 0, End: 4095)
device: /dev/mmcblk0boot0
u-boot-clearfog-base-emmc-boot1.kwb
u-boot-clearfog-pro-emmc-boot1.kwb 		eMMC boot from “boot1” Partition (4MiB, 2MiB used - Start: 0, End: 4095)
device: /dev/mmcblk0boot1
u-boot-clearfog-base-emmc.kwb
u-boot-clearfog-pro-emmc.kwb 		eMMC boot from Data Partition (2MiB used - Start: 4096, End: 8191) !!! MBR on Sector 0. Keep Sector 4096 to 8192 free. First Partition needs to begin on Sector 8192. Do not use GPT. !!!
device: /dev/mmcblk0
u-boot-clearfog-base-sata.kwb
u-boot-clearfog-pro-sata.kwb 		SATA boot from Boot Sector (Size of “kwb” File used - Start: 1, End: <2048)
device: /dev/sda
u-boot-clearfog-base-sd.kwb
u-boot-clearfog-pro-sd.kwb 		SD Card boot from Boot Sector (Size of “kwb” File used - Start: 1, End: <2048)
device: /dev/mmcblk0
u-boot-clearfog-base-spi.kwb
u-boot-clearfog-pro-spi.kwb		 SPI boot from NOR Flash Boot Sector (2MiB used, Start: 0, End: 4095)
device: /dev/mtdblock0
u-boot-clearfog-base-uart.kwb
u-boot-clearfog-pro-uart.kwb		 UART Recovery Boot
u-boot image boot device
u-boot-with-spl.kwb
(same image for Base and Pro and all Boot Devices) 		see SolidRun U-Boot table

DIP Switches

Before powering up the board for the first time it is recommended to select the boot media.

Note: Use either an SD card _or_ the optional eMMC Flash on A388 SOM.

Switch 1 Switch 2 Switch 3 Switch 4 Switch 5
SPI Off Off Off On Off
SD/eMMC Off Off On On On
M.2 SATA SSD On On On Off Off
UART Off On Off Off On

Clearfog Pro Rev 2.1

Switch 1 Switch 2 Switch 3 Switch 4 Switch 5
UART On On On On Off

Serial Connection

Connect a Mikro-USB to USB Cable and Setup a your Terminal Client.

https://solidrun.atlassian.net/wiki/spaces/developer/pages/287801409/Serial+Connection

UART

Use UART to boot a U-Boot Bootloader via Serial Connection. Use Cases: Initial Setup, recover broken U-Boot Version, Testing etc.

  1. Install “u-boot-tools” Package from your Linux Distribution Repository to get 'kwboot'.
  2. Load “U-Boot” via Serial Connection

Note: terminate any Terminal Client Connection (minicom, tmux, screen etc.) before 

$ kwboot -t -B 115200 /dev/ttyUSB0 -b u-boot-with-spl.kwb
kwboot version 2024.01
Detected kwbimage v1 with SDIO boot signature
Patching image boot signature to UART
Aligning image header to Xmodem block size
Removing gap between image header and data
Sending boot message. Please reboot the target...\
Sending boot image header (113792 bytes)...
  0 % [......................................................................]
[..]
 94 % [.................................................                     ]
Done

U-Boot SPL 2024.04-OpenWrt-r26829-8ef4d78582 (Jul 01 2024 - 20:04:41 +0000)
High speed PHY - Version: 2.0
EEPROM TLV detection failed: Using static config for Clearfog Pro.
Detected Device ID 6828
board SerDes lanes topology details:
 | Lane # | Speed |  Type       |
 --------------------------------
 |   0    |   3   | SATA0	|
 |   1    |   0   | SGMII1	|
 |   2    |   5   | PCIe1	|
 |   3    |   5   | USB3 HOST1	|
 |   4    |   5   | PCIe2	|
 |   5    |   0   | SGMII2	|
 --------------------------------
High speed PHY - Ended Successfully
mv_ddr: 14.0.0 
DDR3 Training Sequence - Switching XBAR Window to FastPath Window
mv_ddr: completed successfully
Trying to boot from BOOTROM
Returning to BootROM (return address 0xffff05c4)...

Sending boot image data (472280 bytes)...
  0 % [......................................................................]
[..]
 98 % [..................................................                    ]
Done
Finishing transfer
[Type Ctrl-\ + c to quit]


U-Boot 2024.04-OpenWrt-r26829-8ef4d78582 (Jul 01 2024 - 20:04:41 +0000)

SoC:   MV88F6828-A0 at 1600 MHz
DRAM:  1 GiB (800 MHz, 32-bit, ECC not enabled)
Core:  38 devices, 22 uclasses, devicetree: separate
MMC:   mv_sdh: 0
Loading Environment from MMC... OK
Model: SolidRun Clearfog A1
Board: SolidRun Clearfog Pro
Net:   eth1: ethernet@70000, eth2: ethernet@30000, eth3: ethernet@34000
Hit any key to stop autoboot:  5
[..]

Upgrade U-Boot

  1. Upgrade U-Boot from U-Boot Prompt and use 'bubt'.
    1. get file via 'tftp'
    2. get file via 'usb stick'
  2. Inline Upgrade U-Boot from OpenWrt.

bubt

Upgrade U-Boot on SD Card

⇒ tftp to sd card 

setenv ipaddr 192.168.1.1
setenv netmask 255.255.255.0
setenv serverip 192.168.1.100
bubt u-boot-clearfog-pro-sata.kwb sata tftp

M.2 SATA SSD

SPI

eMMC - boot0 partition

eMMC - boot1 partition

eMMC - data partition

manual

SD Card

⇒ tftp to sd card 

setenv ipaddr 192.168.1.20
setenv netmask 255.255.255.0
setenv serverip 192.168.1.1
bubt u-boot-clearfog-pro-sata.kwb sata tftp

⇒ already running openwrt 

root@OpenWrt:~# dd if=u-boot-clearfog-pro-sd.kwb of=/dev/mmcblk0 bs=512 seek=1 conv=sync

M.2 SATA SSD

SPI

eMMC - boot0 partition

eMMC - boot1 partition

eMMC - data partition

Installation

SD Card

  1. Prepare SD Card and install OpenWrt Image on it _or_ see tftp Installation
  2. set DIP Switch to boot from “SD/eMMC”
  3. connect Serial Console and Power-On

Note: The U-Boot Loader is already included in the SD Card Image.

Extract the OpenWrt Image and write it to the SD Card and existing data will be overwritten. Be patient and use correct device to write data. 

 # zcat <image>-sdcard.img.gz | dd of=/dev/mmcblkX bs=4k conv=sync status=progress

M.2 SATA SSD

  1. Prepare M.2 SATA SSD and install OpenWrt Image on it _or_ see tftp Installation
  2. set DIP Switch to boot from “M.2 SATA SSD”
  3. connect Serial Console and Power-On

Note: The U-Boot Loader is already included in the SD Card Image.

Extract the OpenWrt Image and write it to the SD Card and existing data will be overwritten. Be patient and use correct device to write data. 

 # zcat <image>-sdcard.img.gz | dd of=/dev/sdX bs=4k conv=sync status=progress

eMMC

  1. see tftp Installation
  2. set DIP Switch to boot from “SD/eMMC”
  3. connect Serial Console and Power-On

TFTP

  1. Setup a tftp Server and store “solidrun_clearfog-base-a1-initramfs-kernel.bin” or “solidrun_clearfog-pro-a1-initramfs-kernel.bin”. see: generic.flashing.tftp
  2. Use UART Boot Mode to boot initial U-Boot _or_ use SPI Boot Mode for factory installed U-Boot
  3. connect Serial Console and get a U-Boot prompt
  4. eMMC only: configure boot device
  5. configure tftp client settings on U-Boot
  6. load and boot OpenWrt “initramfs” Image

eMMC only - configure boot partition

The eMMC itself must also be configured for selecting the correct boot partition.
Responsible for changing this setting is the mmc partconf command. It takes either 1, or 4 paramaters:

print configuration of mmc 0 

> mmc partconf 0
BOOT_ACK: 0x0
BOOT_PARTITION_ACCESS: 0x0
PARTITION_ACCESS: 0x0

The most relevant piece here is the BOOT_PARTITION_ACCESS field. It takes one of the following values: 

  0 : do not boot from eMMC
  1 : boot from boot0
  2 : boot from boot1
  7 : boot from data partition

PARTITION_ACCESS is supposed to control access to the boot partitions where 0 means no access, 1 means read-write for boot0 and 2 read-write for boot1. However this currently does not appear to have any effect. It is suggested to set this to 1 when booting from boot0, 2 when booting from boot1 and 0 when booting from the data partition.

So finally this is how a new configuration is applied:

configure mmc 0 to boot from, and enable access to, boot0 (/dev/mmcblk0boot0) 

> mmc partconf 0 0 1 1

configure mmc 0 to boot from, and enable access to, boot1 (/dev/mmcblk0boot1) 

> mmc partconf 0 0 2 2

configure mmc 0 to boot from the data partition, and disable access to boot partitions (/dev/mmcblk0) 

> mmc partconf 0 0 7 0

TFTP Boot

Setup U-Boot tftp settings, load “initramfs” and boot up OpenWrt. 

> setenv ipaddr 192.168.1.1
> setenv netmask 255.255.255.0
> setenv serverip 192.168.1.100
> setenv ethact egiga1
> setenv ethprime egiga1
> tftpboot solidrun_clearfog-pro-a1-initramfs-kernel.bin
[..]
> bootm
[..]

After successful boot copy “solidrun_clearfog-base-a1-squashfs-sdcard.img.gz” or “solidrun_clearfog-pro-a1-squashfs-sdcard.img.gz” to the System and sysupgrade. 

root@OpenWrt# sysupgrade -v /tmp/solidrun_clearfog-pro-a1-squashfs-sdcard.img.gz
[..]

Upgrading OpenWrt

→ generic.sysupgrade

LuCI Web Upgrade Process

  • Browse to http://192.168.1.1/cgi-bin/luci/mini/system/upgrade/ LuCI Upgrade URL
  • Upload image file for sysupgrade to LuCI
  • Wait for reboot

Terminal Upgrade Process

If you don't have a GUI (LuCI) available, you can alternatively upgrade via the command line.

Note: It is important that you put the firmware image into the ramdisk (/tmp) before you start flashing.

sysupgrade

  • Login as root via SSH on 192.168.1.1, then enter the following commands:

Clearfog Base 

root@OpenWrt:/tmp# cd /tmp
root@OpenWrt:/tmp# uclient-fetch https://downloads.openwrt.org/releases/23.05.3/targets/mvebu/cortexa9/openwrt-23.05.3-mvebu-cortexa9-solidrun_clearfog-base-a1-
squashfs-sdcard.img.gz
[..]
root@OpenWrt:/tmp# sysupgrade -v openwrt-23.05.3-mvebu-cortexa9-solidrun_clearfog-base-a1-
squashfs-sdcard.img.gz

Clearfog Pro 

root@OpenWrt:/tmp# cd /tmp
root@OpenWrt:/tmp# uclient-fetch https://downloads.openwrt.org/releases/23.05.3/targets/mvebu/cortexa9/openwrt-23.05.3-mvebu-cortexa9-solidrun_clearfog-pro-a1-
squashfs-sdcard.img.gz
[..]
root@OpenWrt:/tmp# sysupgrade -v openwrt-23.05.3-mvebu-cortexa9-solidrun_clearfog-pro-a1-
squashfs-sdcard.img.gz

Debricking

→ generic.debrick

Failsafe mode

→ failsafe_and_factory_reset

Basic configuration

→ Basic configuration After flashing, proceed with this.
Set up your Internet connection, configure wireless, configure USB port, etc.

Specific Configuration

FIXME Please fill in real values for this device, then remove the EXAMPLEs

Network interfaces

The default network configuration for the ClearFog Base is:

Interface Name Description Default configuration
br-lan eth1 192.168.1.1/24
br-wan eth0 and eth2 DHCP

The default network configuration for the ClearFog Pro I guess:

Interface Name Description Default configuration
br-lan EXAMPLE vlan0 EXAMPLE 192.168.1.1/24
br-wan EXAMPLE vlan1 EXAMPLE DHCP
vlan0 (eth1.0) EXAMPLE LAN ports (1 to 4) EXAMPLE None
vlan1 (eth0.0) EXAMPLE WAN port EXAMPLE None

Switch Ports (for VLANs)

FIXME Please fill in real values for this device, then remove the EXAMPLEs

Guessed values for the ClearFog Pro, the ClearFog Base don't have any switch capabilities.

Numbers 0-5 are Ports 1-6 as labeled on the unit, number 6 is the internal connection to the router itself. The separated port is connected separately to the CPU and has no switch on it, the SFP cage has also a separate ethernet lane to the CPU, it's in the default configuration files of OpenWrt bridged with the separated port.

Port Switch port
LAN 1 EXAMPLE 0
LAN 2 EXAMPLE 1
LAN 3 EXAMPLE 2
LAN 4 EXAMPLE 3
LAN 5 EXAMPLE 4
LAN 6 EXAMPLE 5

Buttons

→ hardware.button on howto use and configure the hardware button(s). Here, we merely name the buttons, so we can use them in the above Howto.

FIXME Please fill in real values for this device, then remove the EXAMPLEs

The ClearFog has the following buttons:

BUTTON Event
Reset Reset
Push button Unknown

Hardware

ClearFog Base:

ClearFog Pro:

Photos

Opening the case

The Case of the ClearFog is optional, if you purchased a version with a Case there are screws on the front and the back side of the cover, unscrew them and pull the cover away. Normally that would'nt be needed, all you need to put OpenWrt on it are accessible without. Only if you want to install a SATA device, switch over to an other boot device or such things you have to open the case.

Main PCB:
Insert photo of PCB

Serial

→ port.serial general information about the serial port, serial port cable, etc.

The serial console is populated on the micro-USB port located beneeth the USB port on the ClearFog Base and next to the Micro SD card slot on the ClearFog Pro. Internally there is a FTDI Chip connected to.

Serial connection parameters
for both of the devices 		115200, 8N1

JTAG

There is no known JTAG port on the ClearFog Base, on the ClearFog Pro there is a 20-pin male header populated right next to the SoM.

Bootloader mods

→ bootloader

Hardware mods

None so far.

Bootlogs

the Device don't have any preinstalled OEM firmware

OpenWrt bootlog

High speed PHY - Version: 2.0 Detected Device ID 6828 board SerDes lanes topology details: | Lane # | Speed | Type | -------------------------------- | 0 | 3 | SATA0 | | 1 | 0 | SGMII1 | | 2 | 5 | PCIe1 | | 3 | 5 | USB3 HOST1 | | 4 | 5 | USB3 HOST0 | | 5 | 0 | SGMII2 | -------------------------------- PCIe, Idx 1: detected no link High speed PHY - Ended Successfully DDR3 Training Sequence - Ver TIP-1.29.0 DDR3 Training Sequence - Switching XBAR Window to FastPath Window DDR3 Training Sequence - Ended Successfully Trying to boot from MMC1 U-Boot 2018.01-02337-gdc4398fdb8 (May 14 2018 - 18:25:17 +0200), Build: jenkins-u-boot-clearfog-model=base,variant=sdhc-10 SoC: MV88F6828-?? (a) at 1600 MHz DRAM: 1 GiB (800 MHz, 32-bit, ECC not enabled) MMC: mv_sdh: 0 *** Warning - bad CRC, using default environment Model: SolidRun Clearfog Board: SolidRun ClearFog Base SCSI: SATA link 0 timeout. AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode Net: Warning: ethernet@70000 (eth1) using random MAC address - d2:63:b4:fd:54:97 eth1: ethernet@70000 Warning: ethernet@30000 (eth2) using incremented MAC address - d2:63:b4:fd:54:98 , eth2: ethernet@30000 Warning: ethernet@34000 (eth3) using incremented MAC address - d2:63:b4:fd:54:99 , eth3: ethernet@34000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot.scr 941 bytes read in 40 ms (22.5 KiB/s) ## Executing script at 00200000 Booting Linux with root=PARTUUID=82a900ba-02 rootfstype=auto rootwait console=ttyS0,115200 18760 bytes read in 31 ms (590.8 KiB/s) 3293768 bytes read in 186 ms (16.9 MiB/s) ## Flattened Device Tree blob at 00100000 Booting using the fdt blob at 0x100000 Loading Device Tree to 0fff8000, end 0ffff947 ... OK Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 5.10.120 (builder@buildhost) (arm-openwrt-linux-muslgnueabi-gcc (OpenWrt GCC 11.2.0 r19426-2b1941e47d) 11.2.0, GNU ld (GNU Binutils) 2.37) #0 SMP Fri Jun 10 07:20:21 2022 [ 0.000000] CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7), cr=10c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] OF: fdt: Machine model: SolidRun Clearfog Base A1 [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] Zone ranges: [ 0.000000] Normal [mem 0x0000000000000000-0x000000002fffffff] [ 0.000000] HighMem [mem 0x0000000030000000-0x000000003fffffff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000000000000-0x000000003fffffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000003fffffff] [ 0.000000] percpu: Embedded 11 pages/cpu s16268 r8192 d20596 u45056 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 260416 [ 0.000000] Kernel command line: root=PARTUUID=82a900ba-02 rootfstype=auto rootwait console=ttyS0,115200 [ 0.000000] Bootloader command line not present [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, linear) [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, linear) [ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off [ 0.000000] Memory: 1026244K/1048576K available (8192K kernel code, 640K rwdata, 1100K rodata, 1024K init, 241K bss, 22332K reserved, 0K cma-reserved, 262144K highmem) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 [ 0.000000] rcu: Hierarchical RCU implementation. [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2. [ 0.000000] Tracing variant of Tasks RCU enabled. [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies. [ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2 [ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 [ 0.000000] L2C: DT/platform modifies aux control register: 0x06070000 -> 0x16070000 [ 0.000000] L2C-310 enabling early BRESP for Cortex-A9 [ 0.000000] L2C-310 full line of zeros enabled for Cortex-A9 [ 0.000000] L2C-310 D prefetch enabled, offset 1 lines [ 0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled [ 0.000000] L2C-310 Coherent cache controller enabled, 16 ways, 1024 kB [ 0.000000] L2C-310 Coherent: CACHE_ID 0x410054c9, AUX_CTRL 0x56070001 [ 0.000007] sched_clock: 64 bits at 800MHz, resolution 1ns, wraps every 4398046511103ns [ 0.000019] clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0xb881274fa3, max_idle_ns: 440795210636 ns [ 0.000032] Switching to timer-based delay loop, resolution 1ns [ 0.000159] Ignoring duplicate/late registration of read_current_timer delay [ 0.000166] clocksource: armada_370_xp_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 76450417870 ns [ 0.000296] Calibrating delay loop (skipped), value calculated using timer frequency.. 1600.00 BogoMIPS (lpj=8000000) [ 0.000305] pid_max: default: 32768 minimum: 301 [ 0.000367] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear) [ 0.000374] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear) [ 0.000727] CPU: Testing write buffer coherency: ok [ 0.000740] CPU0: Spectre v2: using BPIALL workaround [ 0.000834] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.001074] Setting up static identity map for 0x100000 - 0x100060 [ 0.001150] mvebu-soc-id: MVEBU SoC ID=0x6828, Rev=0xA [ 0.001230] mvebu-pmsu: Initializing Power Management Service Unit [ 0.001286] rcu: Hierarchical SRCU implementation. [ 0.001354] dyndbg: Ignore empty _ddebug table in a CONFIG_DYNAMIC_DEBUG_CORE build [ 0.001417] smp: Bringing up secondary CPUs ... [ 0.001572] Booting CPU 1 [ 0.001732] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 [ 0.001736] CPU1: Spectre v2: using BPIALL workaround [ 0.001791] smp: Brought up 1 node, 2 CPUs [ 0.001797] SMP: Total of 2 processors activated (3200.00 BogoMIPS). [ 0.001800] CPU: All CPU(s) started in SVC mode. [ 0.003448] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 [ 0.003507] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.003516] futex hash table entries: 512 (order: 3, 32768 bytes, linear) [ 0.003577] pinctrl core: initialized pinctrl subsystem [ 0.004165] NET: Registered protocol family 16 [ 0.004774] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.005265] thermal_sys: Registered thermal governor 'step_wise' [ 0.005431] cpuidle: using governor ladder [ 0.005589] mvebu-pmsu: CPU hotplug support is currently broken on Armada 38x: disabling [ 0.005596] mvebu-pmsu: CPU idle is currently broken on Armada 38x: disabling [ 0.018878] cryptd: max_cpu_qlen set to 1000 [ 0.020076] SCSI subsystem initialized [ 0.020650] usbcore: registered new interface driver usbfs [ 0.020673] usbcore: registered new interface driver hub [ 0.020700] usbcore: registered new device driver usb [ 0.021618] clocksource: Switched to clocksource arm_global_timer [ 0.022027] NET: Registered protocol family 2 [ 0.022156] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear) [ 0.022775] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear) [ 0.022796] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear) [ 0.022834] TCP bind hash table entries: 8192 (order: 4, 65536 bytes, linear) [ 0.022894] TCP: Hash tables configured (established 8192 bind 8192) [ 0.022946] UDP hash table entries: 512 (order: 2, 16384 bytes, linear) [ 0.022974] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear) [ 0.023078] NET: Registered protocol family 1 [ 0.023095] PCI: CLS 0 bytes, default 64 [ 0.024262] workingset: timestamp_bits=14 max_order=18 bucket_order=4 [ 0.025978] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 0.025984] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc. [ 0.026396] bounce: pool size: 64 pages [ 0.026421] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250) [ 0.027373] armada-38x-pinctrl f1018000.pinctrl: registered pinctrl driver [ 0.027779] gpio-19 (phy1-reset): hogged as output/low [ 0.028339] mvebu-pcie soc:pcie: host bridge /soc/pcie ranges: [ 0.028362] mvebu-pcie soc:pcie: MEM 0x00f1080000..0x00f1081fff -> 0x0000080000 [ 0.028375] mvebu-pcie soc:pcie: MEM 0x00f1040000..0x00f1041fff -> 0x0000040000 [ 0.028386] mvebu-pcie soc:pcie: MEM 0x00f1044000..0x00f1045fff -> 0x0000044000 [ 0.028397] mvebu-pcie soc:pcie: MEM 0x00f1048000..0x00f1049fff -> 0x0000048000 [ 0.028408] mvebu-pcie soc:pcie: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0100000000 [ 0.028418] mvebu-pcie soc:pcie: IO 0xffffffffffffffff..0x00fffffffe -> 0x0100000000 [ 0.028428] mvebu-pcie soc:pcie: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0200000000 [ 0.028438] mvebu-pcie soc:pcie: IO 0xffffffffffffffff..0x00fffffffe -> 0x0200000000 [ 0.028448] mvebu-pcie soc:pcie: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0300000000 [ 0.028458] mvebu-pcie soc:pcie: IO 0xffffffffffffffff..0x00fffffffe -> 0x0300000000 [ 0.028467] mvebu-pcie soc:pcie: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0400000000 [ 0.028474] mvebu-pcie soc:pcie: IO 0xffffffffffffffff..0x00fffffffe -> 0x0400000000 [ 0.028698] mv_xor f1060800.xor: Marvell shared XOR driver [ 0.082047] mv_xor f1060800.xor: Marvell XOR (Descriptor Mode): ( xor cpy intr ) [ 0.082203] mv_xor f1060900.xor: Marvell shared XOR driver [ 0.151999] mv_xor f1060900.xor: Marvell XOR (Descriptor Mode): ( xor cpy intr ) [ 0.152198] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled [ 0.152938] printk: console [ttyS0] disabled [ 0.173029] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 31, base_baud = 15625000) is a 16550A [ 0.911454] printk: console [ttyS0] enabled [ 0.936036] f1012100.serial: ttyS1 at MMIO 0xf1012100 (irq = 32, base_baud = 15625000) is a 16550A [ 0.947064] loop: module loaded [ 0.950218] Loading iSCSI transport class v2.0-870. [ 0.956205] ahci-mvebu f10a8000.sata: supply ahci not found, using dummy regulator [ 0.963883] ahci-mvebu f10a8000.sata: supply phy not found, using dummy regulator [ 0.971404] ahci-mvebu f10a8000.sata: supply target not found, using dummy regulator [ 0.979232] ahci-mvebu f10a8000.sata: AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl platform mode [ 0.988307] ahci-mvebu f10a8000.sata: flags: 64bit ncq sntf led only pmp fbs pio slum part sxs [ 0.997581] scsi host0: ahci-mvebu [ 1.001257] scsi host1: ahci-mvebu [ 1.004775] ata1: SATA max UDMA/133 mmio [mem 0xf10a8000-0xf10a9fff] port 0x100 irq 54 [ 1.012721] ata2: SATA max UDMA/133 mmio [mem 0xf10a8000-0xf10a9fff] port 0x180 irq 54 [ 1.020754] ahci-mvebu f10e0000.sata: supply ahci not found, using dummy regulator [ 1.028426] ahci-mvebu f10e0000.sata: supply phy not found, using dummy regulator [ 1.035964] ahci-mvebu f10e0000.sata: supply target not found, using dummy regulator [ 1.043786] ahci-mvebu f10e0000.sata: AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl platform mode [ 1.052860] ahci-mvebu f10e0000.sata: flags: 64bit ncq sntf led only pmp fbs pio slum part sxs [ 1.062150] scsi host2: ahci-mvebu [ 1.065768] scsi host3: ahci-mvebu [ 1.069262] ata3: SATA max UDMA/133 mmio [mem 0xf10e0000-0xf10e1fff] port 0x100 irq 55 [ 1.077208] ata4: SATA max UDMA/133 mmio [mem 0xf10e0000-0xf10e1fff] port 0x180 irq 55 [ 1.086153] spi-nor spi1.0: w25q32 (4096 Kbytes) [ 1.092995] hwmon hwmon0: temp1_input not attached to any thermal zone [ 1.099946] hwmon hwmon1: temp1_input not attached to any thermal zone [ 1.106743] mvneta_bm f10c8000.bm: Buffer Manager for network controller enabled [ 1.115960] mvneta f1070000.ethernet eth0: Using device tree mac address d2:63:b4:fd:54:97 [ 1.125591] mvneta f1030000.ethernet eth1: Using device tree mac address d2:63:b4:fd:54:98 [ 1.135235] mvneta f1034000.ethernet eth2: Using device tree mac address d2:63:b4:fd:54:99 [ 1.143659] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.150204] ehci-pci: EHCI PCI platform driver [ 1.154687] ehci-platform: EHCI generic platform driver [ 1.160008] ehci-orion: EHCI orion driver [ 1.164117] orion-ehci f1058000.usb: EHCI Host Controller [ 1.169537] orion-ehci f1058000.usb: new USB bus registered, assigned bus number 1 [ 1.177172] orion-ehci f1058000.usb: irq 50, io mem 0xf1058000 [ 1.221624] orion-ehci f1058000.usb: USB 2.0 started, EHCI 1.00 [ 1.227791] hub 1-0:1.0: USB hub found [ 1.231563] hub 1-0:1.0: 1 port detected [ 1.235893] xhci-hcd f10f8000.usb3: xHCI Host Controller [ 1.241225] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 2 [ 1.248788] xhci-hcd f10f8000.usb3: hcc params 0x0a000990 hci version 0x100 quirks 0x0000000000010010 [ 1.258058] xhci-hcd f10f8000.usb3: irq 57, io mem 0xf10f8000 [ 1.264109] hub 2-0:1.0: USB hub found [ 1.267880] hub 2-0:1.0: 1 port detected [ 1.271926] xhci-hcd f10f8000.usb3: xHCI Host Controller [ 1.277255] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 3 [ 1.284774] xhci-hcd f10f8000.usb3: Host supports USB 3.0 SuperSpeed [ 1.291169] usb usb3: We don't know the algorithms for LPM for this host, disabling LPM. [ 1.299451] hub 3-0:1.0: USB hub found [ 1.303241] hub 3-0:1.0: 1 port detected [ 1.307369] usbcore: registered new interface driver usb-storage [ 1.313847] armada38x-rtc f10a3800.rtc: registered as rtc0 [ 1.319556] i2c /dev entries driver [ 1.323557] pca953x 0-0020: supply vcc not found, using dummy regulator [ 1.330255] pca953x 0-0020: using no AI [ 1.334442] gpio-496 (pcie1.0-clkreq): hogged as input [ 1.339866] gpio-499 (pcie1.0-w-disable): hogged as output/low [ 1.345807] gpio-501 (usb3-current-limit): hogged as input [ 1.351469] gpio-502 (usb3-power): hogged as output/high [ 1.352880] ata2: SATA link down (SStatus 0 SControl 300) [ 1.362234] ata1: SATA link down (SStatus 0 SControl 300) [ 1.367938] gpio-507 (m.2 devslp): hogged as output/low [ 1.375238] orion_wdt: Initial timeout 171 sec [ 1.379934] sdhci: Secure Digital Host Controller Interface driver [ 1.386144] sdhci: Copyright(c) Pierre Ossman [ 1.390614] sdhci-pltfm: SDHCI platform and OF driver helper [ 1.397210] marvell-cesa f1090000.crypto: CESA device successfully registered [ 1.404843] NET: Registered protocol family 10 [ 1.409845] Segment Routing with IPv6 [ 1.412828] ata4: SATA link down (SStatus 0 SControl 300) [ 1.413575] NET: Registered protocol family 17 [ 1.418954] ata3: SATA link down (SStatus 0 SControl 300) [ 1.423407] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this. [ 1.428817] mmc0: SDHCI controller on f10d8000.sdhci [f10d8000.sdhci] using ADMA [ 1.449504] 8021q: 802.1Q VLAN Support v1.8 [ 1.453763] Registering SWP/SWPB emulation handler [ 1.460964] mvebu-pcie soc:pcie: host bridge /soc/pcie ranges: [ 1.466890] mvebu-pcie soc:pcie: MEM 0x00f1080000..0x00f1081fff -> 0x0000080000 [ 1.474670] mvebu-pcie soc:pcie: MEM 0x00f1040000..0x00f1041fff -> 0x0000040000 [ 1.479941] mmc0: new high speed SDXC card at address 0001 [ 1.482442] mvebu-pcie soc:pcie: MEM 0x00f1044000..0x00f1045fff -> 0x0000044000 [ 1.488340] mmcblk0: mmc0:0001 EE8QT 239 GiB [ 1.495708] mvebu-pcie soc:pcie: MEM 0x00f1048000..0x00f1049fff -> 0x0000048000 [ 1.495719] mvebu-pcie soc:pcie: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0100000000 [ 1.500967] mmcblk0: p1 p2 [ 1.507847] mvebu-pcie soc:pcie: IO 0xffffffffffffffff..0x00fffffffe -> 0x0100000000 [ 1.507855] mvebu-pcie soc:pcie: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0200000000 [ 1.535505] mvebu-pcie soc:pcie: IO 0xffffffffffffffff..0x00fffffffe -> 0x0200000000 [ 1.543799] mvebu-pcie soc:pcie: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0300000000 [ 1.552090] mvebu-pcie soc:pcie: IO 0xffffffffffffffff..0x00fffffffe -> 0x0300000000 [ 1.560379] mvebu-pcie soc:pcie: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0400000000 [ 1.568671] mvebu-pcie soc:pcie: IO 0xffffffffffffffff..0x00fffffffe -> 0x0400000000 [ 1.576996] mvebu-pcie soc:pcie: /soc/pcie/pcie@2,0: reset gpio is active low [ 4.851612] pcie1.0: reset completed in 100000us [ 4.856304] mvebu-pcie soc:pcie: PCI host bridge to bus 0000:00 [ 4.862248] pci_bus 0000:00: root bus resource [bus 00-ff] [ 4.867749] pci_bus 0000:00: root bus resource [mem 0xf1080000-0xf1081fff] (bus address [0x00080000-0x00081fff]) [ 4.877953] pci_bus 0000:00: root bus resource [mem 0xf1040000-0xf1041fff] (bus address [0x00040000-0x00041fff]) [ 4.888155] pci_bus 0000:00: root bus resource [mem 0xf1044000-0xf1045fff] (bus address [0x00044000-0x00045fff]) [ 4.898356] pci_bus 0000:00: root bus resource [mem 0xf1048000-0xf1049fff] (bus address [0x00048000-0x00049fff]) [ 4.908557] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xe7ffffff] [ 4.915452] pci_bus 0000:00: root bus resource [io 0x1000-0xeffff] [ 4.921833] pci 0000:00:02.0: [11ab:6828] type 01 class 0x060400 [ 4.928615] PCI: bus0: Fast back to back transfers disabled [ 4.934209] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring [ 4.942896] PCI: bus1: Fast back to back transfers enabled [ 4.948397] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01 [ 4.955047] pci 0000:00:02.0: PCI bridge to [bus 01] [ 4.960624] sfp sfp: Host maximum power 2.0W [ 4.969972] VFS: Mounted root (squashfs filesystem) readonly on device 179:2. [ 4.977690] Freeing unused kernel memory: 1024K [ 5.011738] Run /sbin/init as init process [ 5.144992] init: Console is alive [ 5.148489] init: - watchdog - [ 5.220206] kmodloader: loading kernel modules from /etc/modules-boot.d/* [ 5.260146] kmodloader: done loading kernel modules from /etc/modules-boot.d/* [ 5.272577] init: - preinit - [ 5.567205] random: jshn: uninitialized urandom read (4 bytes read) [ 5.613321] random: jshn: uninitialized urandom read (4 bytes read) [ 5.628801] random: jshn: uninitialized urandom read (4 bytes read) [ 5.684815] mvneta f1030000.ethernet eth1: PHY [f1072004.mdio-mii:01] driver [Marvell 88E1510] (irq=POLL) [ 5.694639] mvneta f1030000.ethernet eth1: configuring for phy/sgmii link mode Press the [f] key and hit [enter] to enter failsafe mode Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level [ 9.787937] urandom_read_iter: 4 callbacks suppressed [ 9.787941] random: procd: uninitialized urandom read (4 bytes read) [ 9.831999] mvneta f1030000.ethernet eth1: Link is Up - 1Gbps/Full - flow control rx/tx [ 9.840261] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [ 10.116756] F2FS-fs (loop0): Mounted with checkpoint version = d70cad7 [ 10.123802] mount_root: switching to f2fs overlay [ 10.222256] EXT4-fs (mmcblk0p1): mounted filesystem without journal. Opts: (null) [ 10.241103] urandom-seed: Seeding with /etc/urandom.seed [ 10.276118] mvneta f1030000.ethernet eth1: Link is Down [ 10.287931] procd: - early - [ 10.290869] procd: - watchdog - [ 10.828626] procd: - watchdog - [ 10.863717] procd: - ubus - [ 10.889354] random: ubusd: uninitialized urandom read (4 bytes read) [ 10.917639] random: ubusd: uninitialized urandom read (4 bytes read) [ 10.924177] random: ubusd: uninitialized urandom read (4 bytes read) [ 10.931352] procd: - init - Please press Enter to activate this console. [ 11.151506] urngd: v1.0.2 started. [ 11.163103] kmodloader: loading kernel modules from /etc/modules.d/* [ 11.185962] random: crng init done [ 11.189375] random: 22 urandom warning(s) missed due to ratelimiting [ 11.216388] PPP generic driver version 2.4.2 [ 11.221116] NET: Registered protocol family 24 [ 11.227616] kmodloader: done loading kernel modules from /etc/modules.d/* [ 13.961878] mvneta f1030000.ethernet eth1: PHY [f1072004.mdio-mii:01] driver [Marvell 88E1510] (irq=POLL) [ 13.976541] mvneta f1030000.ethernet eth1: configuring for phy/sgmii link mode [ 13.987312] br-lan: port 1(eth1) entered blocking state [ 13.992640] br-lan: port 1(eth1) entered disabled state [ 13.998055] device eth1 entered promiscuous mode [ 14.026293] mvneta f1070000.ethernet eth0: PHY [f1072004.mdio-mii:00] driver [Marvell 88E1510] (irq=POLL) [ 14.036581] mvneta f1070000.ethernet eth0: configuring for phy/rgmii-id link mode [ 14.049782] br-wan: port 1(eth0) entered blocking state [ 14.055120] br-wan: port 1(eth0) entered disabled state [ 14.060549] device eth0 entered promiscuous mode [ 14.066556] br-wan: port 1(eth0) entered blocking state [ 14.071819] br-wan: port 1(eth0) entered forwarding state [ 14.091989] mvneta f1034000.ethernet eth2: configuring for inband/sgmii link mode [ 14.102211] br-wan: port 2(eth2) entered blocking state [ 14.107456] br-wan: port 2(eth2) entered disabled state [ 14.119878] device eth2 entered promiscuous mode [ 14.124642] br-wan: port 2(eth2) entered blocking state [ 14.129884] br-wan: port 2(eth2) entered forwarding state [ 15.047478] br-wan: port 1(eth0) entered disabled state [ 15.077946] br-wan: port 2(eth2) entered disabled state [ 17.111990] mvneta f1030000.ethernet eth1: Link is Up - 1Gbps/Full - flow control rx/tx [ 17.120036] br-lan: port 1(eth1) entered blocking state [ 17.125286] br-lan: port 1(eth1) entered forwarding state [ 17.131032] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready BusyBox v1.35.0 (2022-06-10 07:20:21 UTC) built-in shell (ash) _______ ________ __ | |.-----.-----.-----.| | | |.----.| |_ | - || _ | -__| || | | || _|| _| |_______|| __|_____|__|__||________||__| |____| |__| W I R E L E S S F R E E D O M ----------------------------------------------------- OpenWrt 22.03.0-rc4, r19426-2b1941e47d ----------------------------------------------------- === WARNING! ===================================== There is no root password defined on this device! Use the "passwd" command to set up a new password in order to prevent unauthorized SSH logins. -------------------------------------------------- root@OpenWrt:/#


Notes

Space for additional notes, links to forum threads or other resources.

External Links

Tags

How to add tags

, , , ,
This website uses cookies. By using the website, you agree with storing cookies on your computer. Also you acknowledge that you have read and understand our Privacy Policy. If you do not agree leave the website.More information about cookies
  • Last modified: 2024/07/03 19:11
  • by sf.openwrt