Does anyone actually have a stable system?


tommitytom
 Share

5 5

Recommended Posts

Just a heads up that I reinstalled my Helios 64 with the latest armbian buster (currently running from SD) and it has been running solid as a rock for 7 days.  No longer using OMV and I don't really miss it

Link to post
Share on other sites

Armbian is a community driven open source project. Do you like to contribute your code?

Posted (edited)
On 3/25/2021 at 4:57 AM, gprovost said:

@SIGSEGV During boot up, the first messages output on the serial will show if it's U-boot TPL/SPL our Rockchip blob.

 

This is the output with U-boot TPL/SPL

 



U-Boot TPL 2020.10-armbian (Mar 14 2021 - 07:07:37)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=16/15 CS=1 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=16/15 CS=1 Die BW=16 Size=2048MB
256B stride
lpddr4_set_rate: change freq to 400000000 mhz 0, 1
lpddr4_set_rate: change freq to 800000000 mhz 1, 0
Trying to boot from BOOTROM
Returning to boot ROM...

U-Boot SPL 2020.10-armbian (Mar 14 2021 - 07:07:37 +0700)
Trying to boot from MMC2
NOTICE:  BL31: v2.2(release):a04808c-dirty
NOTICE:  BL31: Built : 07:07:20, Mar 14 2021

 

 

This is the output with Rockchip blob

 

 

 

@gprovost I took a quick look at your previous reply in the thread. It looks like I have the Rockchip blob (line "DDR Version 1.24 20191016") since I haven't updated since 2020.07 LK 5.9.X and initially my LK 5.10.X upgrades had issues. Is there a way to update the UBoot without losing the rest of the system? Perhaps that was my issue and since I didn't reboot in a while, I avoided that scenario...?

 

Modified the armbianEnv.txt on a spare Linux machine. Output below:

Spoiler

picocom v2.2

 

port is        : /dev/ttyUSB0

flowcontrol    : none

baudrate is    : 1500000

parity is      : none

databits are   : 8

stopbits are   : 1

escape is      : C-a

local echo is  : no

noinit is      : no

noreset is     : no

nolock is      : no

send_cmd is    : sz -vv

receive_cmd is : rz -vv -E

imap is        : 

omap is        : 

emap is        : crcrlf,delbs,

 

Type [C-a] [C-h] to see available commands

 

Terminal ready

DDR Version 1.24 20191016

In

channel 0

CS = 0

MR0=0x18

MR4=0x1

MR5=0x1

MR8=0x10

MR12=0x72

MR14=0x72

MR18=0x0

MR19=0x0

MR24=0x8

MR25=0x0

channel 1

CS = 0

MR0=0x18

MR4=0x1

MR5=0x1

MR8=0x10

MR12=0x72

MR14=0x72

MR18=0x0

MR19=0x0

MR24=0x8

MR25=0x0

channel 0 training pass!

channel 1 training pass!

change freq to 416MHz 0,1

Channel 0: LPDDR4,416MHz

Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB

Channel 1: LPDDR4,416MHz

Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB

256B stride

channel 0

CS = 0

MR0=0x18

MR4=0x1

MR5=0x1

MR8=0x10

MR12=0x72

MR14=0x72

MR18=0x0

MR19=0x0

MR24=0x8

MR25=0x0

channel 1

CS = 0

MR0=0x18

MR4=0x1

MR5=0x1

MR8=0x10

MR12=0x72

MR14=0x72

MR18=0x0

MR19=0x0

MR24=0x8

MR25=0x0

channel 0 training pass!

channel 1 training pass!

channel 0, cs 0, advanced training done

channel 1, cs 0, advanced training done

change freq to 856MHz 1,0

ch 0 ddrconfig = 0x101, ddrsize = 0x40

ch 1 ddrconfig = 0x101, ddrsize = 0x40

pmugrf_os_reg[2] = 0x32C1F2C1, stride = 0xD

ddr_set_rate to 328MHZ

ddr_set_rate to 666MHZ

ddr_set_rate to 928MHZ

channel 0, cs 0, advanced training done

channel 1, cs 0, advanced training done

ddr_set_rate to 416MHZ, ctl_index 0

ddr_set_rate to 856MHZ, ctl_index 1

support 416 856 328 666 928 MHz, current 856MHz

OUT

Boot1: 2019-03-14, version: 1.19

CPUId = 0x0

ChipType = 0x10, 254

SdmmcInit=2 0

BootCapSize=100000

UserCapSize=14910MB

FwPartOffset=2000 , 100000

mmc0:cmd5,20

SdmmcInit=0 0

BootCapSize=0

UserCapSize=121942MB

FwPartOffset=2000 , 0

StorageInit ok = 77912

SecureMode = 0

SecureInit read PBA: 0x4

SecureInit read PBA: 0x404

SecureInit read PBA: 0x804

SecureInit read PBA: 0xc04

SecureInit read PBA: 0x1004

SecureInit read PBA: 0x1404

SecureInit read PBA: 0x1804

SecureInit read PBA: 0x1c04

SecureInit ret = 0, SecureMode = 0

atags_set_bootdev: ret:(0)

GPT 0x3380ec0 signature is wrong

recovery gpt...

GPT 0x3380ec0 signature is wrong

recovery gpt fail!

LoadTrust Addr:0x4000

No find bl30.bin

No find bl32.bin

Load uboot, ReadLba = 2000

Load OK, addr=0x200000, size=0xdd6b0

RunBL31 0x40000

NOTICE:  BL31: v1.3(debug):42583b6

NOTICE:  BL31: Built : 07:55:13, Oct 15 2019

NOTICE:  BL31: Rockchip release version: v1.1

INFO:    GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3

INFO:    Using opteed sec cpu_context!

INFO:    boot cpu mask: 0

INFO:    plat_rockchip_pmu_init(1190): pd status 3e

INFO:    BL31: Initializing runtime services

WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK

ERROR:   Error initializing runtime service opteed_fast

INFO:    BL31: Preparing for EL3 exit to normal world

INFO:    Entry point address = 0x200000

INFO:    SPSR = 0x3c9

 

 

U-Boot 2020.07-armbian (Dec 11 2020 - 22:44:41 +0100)

 

SoC: Rockchip rk3399

Reset cause: POR

DRAM:  3.9 GiB

PMIC:  RK808 

SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB

MMC:   mmc@fe320000: 1, sdhci@fe330000: 0

Loading Environment from MMC... *** Warning - bad CRC, using default environment

 

In:    serial

Out:   serial

Err:   serial

Model: Helios64

Revision: 1.2 - 4GB non ECC

Net:   eth0: ethernet@fe300000

scanning bus for devices...

Hit any key to stop autoboot:  0 

switch to partitions #0, OK

mmc1 is current device

Scanning mmc 1:1...

Found U-Boot script /boot/boot.scr

3185 bytes read in 6 ms (517.6 KiB/s)

## Executing script at 00500000

Boot script loaded from mmc 1

235 bytes read in 5 ms (45.9 KiB/s)

9809293 bytes read in 434 ms (21.6 MiB/s)

22460424 bytes read in 954 ms (22.5 MiB/s)

81696 bytes read in 14 ms (5.6 MiB/s)

2698 bytes read in 8 ms (329.1 KiB/s)

Applying kernel provided DT fixup script (rockchip-fixup.scr)

## Executing script at 09000000

## Loading init Ramdisk from Legacy Image at 06000000 ...

   Image Name:   uInitrd

   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)

   Data Size:    9809229 Bytes = 9.4 MiB

   Load Address: 00000000

   Entry Point:  00000000

   Verifying Checksum ... OK

## Flattened Device Tree blob at 01f00000

   Booting using the fdt blob at 0x1f00000

   Loading Ramdisk to f558b000, end f5ee5d4d ... OK

   Loading Device Tree to 00000000f550e000, end 00000000f558afff ... OK

 

Starting kernel ...

 

Edited by hartraft
Added more detail
Link to post
Share on other sites

@hartraft Yeah you could try to update the uboot on the microSD card using your spare linux computer.(Note: This can mess up your sdcard if you do it wrongly)

 

You will need again to mount the microSD.

 

cd  <sdcard-mount>/usr/lib/linux-u-boot-current-helios64*

dd if=idbloader.bin of=<sd-card device> seek=64 conv=notrunc
dd if=uboot.img of=<sd-card device> seek=16384 conv=notrunc
dd if=trust.bin of=<sd-card device> seek=24576 conv=notrunc

 

where <sd-card device> is something like /dev/mmcblk1

Link to post
Share on other sites

On 5/9/2021 at 5:54 AM, FloBaoti said:

For people running fine, are you using 2.5G NIC ?

I do, and this interface crashes every few days. I setup a cron to check every minute and down&up it if necessary.

 

I'm using both the 1g and 2.5g nics.  Before my recent reinstall, using OMV, the 2.5g NIC would constantly drop, and after a while it just stopped working completely.  After reinstall without OMV it has been solid.  Not sure if it was OMV causing the issue, but its the largest difference between my 2 installs.

Link to post
Share on other sites

On 5/8/2021 at 9:54 PM, FloBaoti said:

For people running fine, are you using 2.5G NIC ?

I do, and this interface crashes every few days. I setup a cron to check every minute and down&up it if necessary.

I'm using the 2.5Gbps NIC exclusively with a 2.5Gbps switch for a month with no issues so far.

Link to post
Share on other sites

This is what my uptime looks like. OMV5, plex and r/rutorrent with 5 12TB WDC disks (LVM).
None of these reboots were triggered by me...
Wish I could find were the problem lies, can't read the logs for debugging as the reboot is so abrupt that nothing gets written to disk.

armbian.PNG

Link to post
Share on other sites

3 hours ago, barnumbirr said:

Wish I could find were the problem lies, can't read the logs for debugging as the reboot is so abrupt that nothing gets written to disk.

Can't you connect a logger to serial out?

Link to post
Share on other sites

 Share

5 5