bubt u-boot/181226.flash-image-ddr3-2g-2cs-1000_800.bin spi usb
Marvell>> bubt u-boot/181226.flash-image-ddr3-2g-2cs-1000_800.bin spi usb
Burning U-BOOT image "u-boot/181226.flash-image-ddr3-2g-2cs-1000_800.bin" from "usb" to "spi"
USB0: Register 2000104 NbrPorts 2
Starting the controller
USB XHCI 1.00
USB1: USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning bus 1 for devices... 1 USB Device(s) found
SF: Detected w25q32dw with page size 256 Bytes, erase size 4 KiB, total 4 MiB
676040 bytes written, 212992 bytes skipped in 12.491s, speed 72876 B/s
WTMI: system early-init
SVC REV: 3, CPU VDD voltage: 1.155V
NOTICE: Booting Trusted Firmware
NOTICE: BL1: v1.5(release):1f8ca7e (Marvell-devel-18.12.2)
NOTICE: BL1: Built : 13:48:02, Dec 26 2018
NOTICE: BL1: Booting BL2
NOTICE: BL2: v1.5(release):1f8ca7e (Marvell-devel-18.12.2)
NOTICE: BL2: Built : 13:48:04, Dec 26 2018
NOTICE: BL1: Booting BL31
NOTICE: BL31: v1.5(release):1f8ca7e (Marvell-devel-18.12.2)
NOTICE: BL31: Built : 13:4
U-Boot 2018.03-devel-18.12.3-gc9aa92c-armbian (Dec 26 2018 - 13:45:06 +0100)
Model: Marvell Armada 3720 Community Board ESPRESSOBin
CPU 1000 [MHz]
L2 800 [MHz]
TClock 200 [MHz]
DDR 800 [MHz]
DRAM: 2 GiB
Comphy chip #0:
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
Loading Environment from SPI Flash... SF: Detected w25q32dw with page size 256 Bytes, erase size 4 KiB, total 4 MiB
Model: Marvell Armada 3720 Community Board ESPRESSOBin
Net: eth0: neta@30000 [PRIME]
Hit any key to stop autoboot: 0
1119 bytes read in 14 ms (77.1 KiB/s)
## Executing script at 06d00000
243 bytes read in 5 ms (46.9 KiB/s)
15690240 bytes read in 673 ms (22.2 MiB/s)
5981154 bytes read in 270 ms (21.1 MiB/s)
** File not found /boot/dtb/marvell/armada-3720-community.dtb **
8607 bytes read in 10 ms (839.8 KiB/s)
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: uInitrd
Image Type: AArch64 Linux RAMDisk Image (gzip compressed)
Data Size: 5981090 Bytes = 5.7 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 06000000
Booting using the fdt blob at 0x6000000
Loading Ramdisk to 7f076000, end 7f62a3a2 ... OK
Using Device Tree in place at 0000000006000000, end 000000000600519e
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[ 0.000000] Linux version 4.18.8-mvebu64 (root@nightly) (gcc version 7.2.1 20171011 (Linaro GCC 7.2-2017.11)) #259 SMP PREEMPT Wed Sep 19 11:14:00 CEST 2018
[ 0.000000] Machine model: Globalscale Marvell ESPRESSOBin Board
[ 0.000000] earlycon: ar3700_uart0 at MMIO 0x00000000d0012000 (options '')
[ 0.000000] bootconsole [ar3700_uart0] enabled
Loading, please wait...
starting version 239
As mentioned by @mantouboji 5.13 is working well for the moment with the relevant patches. Though we are missing, among others, overlays and wifi.
Regarding overlays, I tried to compile w1-gpio-cl but I had issues with the headers on 5.13. Did anyone manage to compile anything with 5.13?
Regarding wifi, as this is new AW hw, I expect that we need to port the driver from the ventor's legacy sdk. Is anyone familiar with the process?
To my understanding zram is swap substitute. If you re-enable zram then you will have 1giga swap.
Given that you had zram enabled during the first freeze I don't expect that this is a solution.
Does Fhem ram usage increase overtime?
I just used systemctl, after your tests you can enable and start the services again. I also disabled zram not only logging, but you could test by disabling only ram logging. Please note that I did this in order to be able to trace the issue but since i disabled the two services there is no issue
20:17:52 up 12 days, 20:20, 1 user, load average: 2.74, 2.77, 2.67
systemctl stop armbian-ramlog.service
systemctl disable armbian-ramlog.service
systemctl stop armbian-zram-config.service
systemctl disable armbian-zram-config.service
Edit: Well i forgot to say that i did experience 1 issue twice the past 12 days with transmission crashing but I am not sure if this is relevant. Though I never had issues with transmission on cubietrack using armbian for the past few years. We probably need to alter the unit file so that the daemon restarts after crashing. Here is the log:
Oct 25 20:43:39 cubietruck systemd: transmission-daemon.service: Main process exited, code=killed, status=7/BUS
Oct 25 20:43:39 cubietruck systemd: transmission-daemon.service: Failed with result 'signal'.
Hi, both posts updated with a photo. I bought both cards during 2015 and I now realized that they were manufactured during 2012 and 2013.
When it comes to desktop use (i.e. "not headless"), Toshiba exceria is much more responsive and also much faster with software updates.
If you think that these posts are "useless" even for future reference, let me know and I can delete them.
Here are the results for Samsung EVO 16GB, brand new (product code is MB-MP16DA/EU).
Tested on Cubietruck with Armbian_5.07_Bananapipro_Debian_jessie_4.4.6 from the first post (adapted for cubietruck).
Results from pass No 5, 6 & 7.
HW info from armbianmonitor below (due to sprunge overquota)
I will post results for a couple more cards later this week
Update: It seems to me that it is a hardware/kernel issue.
I see that the chip of the StarTech.com USB 3.0 to 2.5â€ SATA is ASMedia ASM1051.
As described here http://linux-sunxi.org/USB/UAS, ASM1051 is blacklisted on the mainline kernel.
Booting legacy kernel works fine.