Perier

December 18, 2018

Hi people,

I need your help, I have been struggling to make this method work (https://github.com/zador-blood-stained/fel-mass-storage or https://github.com/ThomasKaiser/sunxi-armbian-flasher-osx) on the A20 processor for several days, but nothing works, I use Einstein-A20 (https://mega.nz/#F!ZtwxCCJC!AIYHcTqz-ucjuzKnE9qD7A?5xZ3iT4J) and enter the FEL mode using the special button UBOOT_SELECT.

I made my own support for this board for uboot (_defconfig, .dts) and compiled u-boot-sunxi-with-spl.bin (Scroll down).
script.bin took from cubietruck.

That is, I use the h3 folder, only:
zImage, uInitrd, boot.scr

Сonnect the board in FEL mode to a virtual machine on VMvare Worstation 12.5.9. Ubuntu Bionic (armbian build system).

j @ ubuntu: ~ / fel-mass-storage $ sudo ./start.sh
[sudo] password for j:
Connect device in FEL mode and press <Enter>

100% [=============================================== =] 4575 kB, 545.8 kB / s
100% [=============================================== =] 47 kB, 478.2 kB / s
100% [=============================================== =] 2230 kB, 548.6 kB / s
100% [=============================================== =] 0 kB, 15.3 kB / s

U-boot log:

Spoiler

U-Boot 2018.11-rc1-g09e1061df6-dirty (Dec 18 2018 - 17:55:28 +0300) Allwinner Ty

CPU: Allwinner A20 (SUN7I)
Model: Einstein-A20
I2C: ready
DRAM: 1 GiB
MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
Loading Environment from FAT... *** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
Allwinner mUSB OTG (Peripheral)
SCSI: SATA link 0 timeout.
AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part ccc apst

Net:
Warning: usb_ether MAC addresses don't match:
Address in ROM is de:ad:be:ef:00:01
Address in environment is 02:19:08:02:44:80
eth0: usb_ether
starting USB...
USB0: USB EHCI 1.00
USB1: USB OHCI 1.0
USB2: USB EHCI 1.00
USB3: USB OHCI 1.0
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot: 0
(FEL boot)
## Executing script at 43100000
## Loading init Ramdisk from Legacy Image at 43300000 ...
Image Name: uInitrd
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 2229486 Bytes = 2.1 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
EHCI failed to shut down host controller.
EHCI failed to shut down host controller.
Loading Ramdisk to 49ddf000, end 49fff4ee ... OK
Using machid 0x1029 from environment

Starting kernel ...

After that, in Windows 10, a device appears with an error in getting the descriptor (USB\VID_0000&PID_0002\5&330350CB&0&5).

I have already reread all the topics on the forum related to uploading an image to eMMC, but as a rule, they are addressed to the H3 board.

The goal I’m following is to download a previously compiled armbian image to eMMc. With the preliminary partitioning of the file system using LUKS.

Perhaps there are some other ways to work with eMMC (without preloading and subsequent transfer from sd card)?

Please check files on my Git:

https://github.com/evgenyhawk/einstein-a20

December 16, 2018

On 12/5/2018 at 11:43 PM, martinayotte said:
Yes ! Using the method explained in the Guide you've mentioned ...

Grab this source https://bootlin.com/pub/mirror/devmem2.c , compile it, and use this from the Guide :
d0=`./devmem2 0x01c14200 w|grep Value|sed 's/^.*: 0x/ /'`
d1=`./devmem2 0x01c14204 w|grep Value|sed 's/^.*: 0x/ /'`
d2=`./devmem2 0x01c14208 w|grep Value|sed 's/^.*: 0x/ /'`
d3=`./devmem2 0x01c1420c w|grep Value|sed 's/^.*: 0x/ /'`
echo $d0 $d1 $d2 $d3

Thanks for your reply! It was very useful for me and I will definitely apply it in the future.

December 5, 2018

Friends, tell me is it possible to get the SID on the device itself?

With the article, read:
http://linux-sunxi.org/SID_Register_Guide

In my sun50i-h5.dtsi:

soc {
	sid: eeprom @ 1c14000 {
                 compatible = "allwinner, sun50i-h5-sid";
                 reg = <0x1c14000 0x400>;
    }
}

#: sunxi-fel sid
> ERROR: Allwinner USB FEL device not found!

As I understand it, this utility retrieves from a remote device connected in FEL mode.

But is it possible to somehow get the SID directly on the summit device?

December 5, 2018

1 hour ago, Igor said:

Great, it works. I still have 230mA draft in "powered down" state but I guess we solve the overheating problem.

Thank you.

Yes, overheating and error messages eliminated.

17 minutes ago, Tido said:

P = U x I

5V x 0,23A = 1,15 Watt for the whole board I guess ? (sounds better, did you do the 'hot finger' test? )

Does this also affect H3 or only H5 ?

Not tested on H3 (sunxi), since this fix covers mainly A64, H5, H6 (sunxi64).

"Hot finger" test was performed on sun50i-h5-orangepi-zero-plus.

December 5, 2018

On 8/19/2018 at 1:19 AM, sametkocatepe said:

there are a lot of things about AR100. unfortunately I dont have time to dig that real time processor. anyway i wont implement "shutdown " or "halt" to my project.

Solved.

Please check this.

December 5, 2018

On 12/3/2018 at 5:42 PM, Igor said:

Community will be helpful for the implementation ... if you managed to get it working as expected. We are slowly moving to 4.19.y kernel so it has to work there as well. (Its expected)

https://github.com/armbian/build/pull/1176

Glad to help people who have encountered this problem.

P.S. For the tip, thanks to Andre Przywara. :beer:

December 3, 2018

1 hour ago, Igor said:

By studying:

http://linux-sunxi.org/AR100
https://forum.armbian.com/search/?q=AR100
and implementing.

As I understand it, this is my case - https://github.com/crust-firmware/crust/tree/master

Did I try to figure it out myself, maybe I used this repository?

P.S. Thanks for the tip. :thumbup:

December 3, 2018

Hello Community,

Now I encountered the following problem when testing my "orange pi zero plus":

I tested the processor load (stress-ng) at a working frequency of 624mhz for 25 minutes.

Settings: mainline sunxi64-next (4.14.y)

Spoiler

armbianmonitor -m

10:53:44: 624MHz 4.50 100% 0% 99% 0% 0% 0% 100.1°C 1/1

[ 3314.299373] thermal thermal_zone0: critical temperature reached (105 n

Message from syslogd@localhost at Dec 3 10:53:51 ...
kernel:

[ 3314.299373] thermal thermal_zone0: critical temperature reached (105 C), shutting down
Stopping Session 1 of user root..
[ OK ] Stopped Session 1 of user root.
[ OK ] Removed slice User Slice of root.
Stopping Login Service...
Stopping Permit User Sessions...
[ OK ] Stopped Login Service.
[ OK ] Stopped Permit User Sessions.
[ OK ] Stopped target Remote File Systems.
[ OK ] Stopped Unattended Upgrades Shutdown.
[ OK ] Stopped target Network.
Stopping Network Manager...
Stopping Raise network interfaces...
[ OK ] Stopped Network Manager.
Stopping D-Bus System Message Bus...
[ OK ] Stopped D-Bus System Message Bus.
[ OK ] Stopped target Basic System.
[ OK ] Stopped target Slices.
[ OK ] Removed slice User and Session Slice.
[ OK ] Stopped target Paths.
[ OK ] Stopped target Sockets.
[ OK ] Closed Syslog Socket.
[ OK ] Closed D-Bus System Message Bus Socket.
[ OK ] Stopped target System Initialization.
Stopping Armbian memory supported logging...
Stopping Restore / save the current clock...
Stopping Update UTMP about System Boot/Shutdown...
[ OK ] Stopped target Swap.
Deactivating swap /dev/zram4...
Deactivating swap /dev/zram1...
Deactivating swap /dev/zram2...
Deactivating swap /dev/zram3...
Stopping Entropy daemon using the HAVEGE algorithm...
[ OK ] Stopped target Encrypted Volumes.
[ OK ] Stopped Forward Password Requests to Wall Directory Watch.
[ OK ] Stopped Dispatch Password Requests to Console Directory Watch.
[ OK ] Stopped Entropy daemon using the HAVEGE algorithm.
[ OK ] Stopped Raise network interfaces.
[ OK ] Stopped Restore / save the current clock.
[ OK ] Stopped Apply Kernel Variables.
Stopping Load/Save Random Seed...
[ OK ] Stopped Update UTMP about System Boot/Shutdown.
[ OK ] Stopped Load/Save Random Seed.
[ OK ] Stopped Create Volatile Files and Directories.
[ OK ] Deactivated swap /dev/zram1.
[ OK ] Deactivated swap /dev/zram4.
[ OK ] Deactivated swap /dev/zram2.
[ OK ] Deactivated swap /dev/zram3.
[ OK ] Unmounted /var/log.
[ OK ] Unmounted /var/log.hdd.
[ OK ] Stopped Armbian memory supported logging.
Stopping Armbian ZRAM config...
[ OK ] Stopped Armbian ZRAM config.
[ OK ] Stopped target Local File Systems.
Unmounting /run/user/0...
Unmounting /tmp...
[ OK ] Unmounted /run/user/0.
[ OK ] Unmounted /tmp.
[ OK ] Reached target Unmount All Filesystems.
[ OK ] Stopped target Local File Systems (Pre).
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Stopped Create Static Device Nodes in /dev.
[ OK ] Reached target Shutdown.
[ 3325.807677] reboot: Power down
INFO: PSCI Affinity Map:
INFO: AffInst: Level 0, MPID 0x0, State ON
INFO: AffInst: Level 0, MPID 0x1, State ON
INFO: AffInst: Level 0, MPID 0x2, State ON
INFO: AffInst: Level 0, MPID 0x3, State ON
ERROR: PSCI system shutdown: still alive ...

"ERROR: PSCI system shutdown: still alive ..."

The development scenario is predictable, but an error at the end prevents the device from rebooting. How to fix it?

Update.1:

Or should a reboot not occur, but only a shutdown?

Update.2:

Still, the device did not turn off and did not restart (just hung), since the processor temperature is still high and the Ethernet LED flashes.

Advanced users - Development · November 25, 2018

9 minutes ago, Igor said:

It's related to wireless drivers, probably showing firmware loading progress. In any case safe to ignore.

But how did you determine that the problem in loading wireless drivers? (for own development)

Advanced users - Development · November 25, 2018

1 hour ago, TonyMac32 said:

@Evgeny would you be able to put the code blocks into the Spoiler containers so they don't hog an entire page?

As to the question, I assume the Opi zero plus has a "dumb" regulator setup with no voltage switching? (OK, found it, it will do 1.1 and 1.3V). Basically you have no voltage to support those higher operating points, the processor will theoretically fall on it's face if you tried.

As for the temp and random hex showing up, I do not know.

Thank you for a hint about a spoiler (corrected)

HEX-error migrated from the mainline 4.14.y

Advanced users - Development · November 24, 2018

Orange Pi Zero Plus (H5)

http://ix.io/1ujE

I can not understand what kind of error or what is it connected with? (present since version 4.14.y)

[    6.888226] 29 
[    6.888237] 81 
[    6.888239] 03 
[    6.888241] CC 
[    6.888243] 00 
[    6.888245] 00 
[    6.888247] 50 
[    6.888249] 00 
[    6.888251] 00 
[    6.888253] 00 
[    6.888255] 04 
[    6.888257] CC 
[    6.888259] 0A 
[    6.888262] 0C 
[    6.888264] 00 
[    6.888266] 00
[    6.888268] FF

and other errors:

Spoiler

[ 2.170832] usb_phy_generic usb_phy_generic.0.auto: usb_phy_generic.0.auto supply vcc not found, using dummy regular

[ 4.042684] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2

[ 4.682287] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator
[ 4.682298] cpu cpu0: _opp_add: OPP not supported by regulators (1056000000)
[ 4.682395] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator
[ 4.682402] cpu cpu0: _opp_add: OPP not supported by regulators (1104000000)
[ 4.682482] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator
[ 4.682488] cpu cpu0: _opp_add: OPP not supported by regulators (1152000000)
[ 4.682592] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator
[ 4.682602] cpu cpu0: _opp_add: OPP not supported by regulators (1200000000)
[ 4.682671] core: _opp_supported_by_regulators: OPP minuV: 1340000 maxuV: 1340000, not supported by regulator
[ 4.682679] cpu cpu0: _opp_add: OPP not supported by regulators (1224000000)
[ 4.682785] core: _opp_supported_by_regulators: OPP minuV: 1340000 maxuV: 1340000, not supported by regulator
[ 4.682793] cpu cpu0: _opp_add: OPP not supported by regulators (1248000000)
[ 4.682862] core: _opp_supported_by_regulators: OPP minuV: 1340000 maxuV: 1340000, not supported by regulator
[ 4.682868] cpu cpu0: _opp_add: OPP not supported by regulators (1296000000)
[ 4.682975] core: _opp_supported_by_regulators: OPP minuV: 1400000 maxuV: 1400000, not supported by regulator
[ 4.682981] cpu cpu0: _opp_add: OPP not supported by regulators (1344000000)
[ 4.683058] core: _opp_supported_by_regulators: OPP minuV: 1400000 maxuV: 1400000, not supported by regulator
[ 4.683065] cpu cpu0: _opp_add: OPP not supported by regulators (1368000000)

[ 4.683579] thermal thermal_zone1: binding zone cpu-thermal with cdev thermal-cpufreq-0 failed:-22
[ 4.797299] thermal thermal_zone0: failed to read out thermal zone (-110)
[ 4.797358] OF: /thermal-zones/cpu-thermal: arguments longer than property
[ 4.797373] thermal thermal_zone2: failed to read out thermal zone (-110)

[ 9.069655] dwmac-sun8i 1c30000.ethernet eth0: PTP not supported by HW

platform regulatory.0 (error) - appeared in the dev branch, there is none in the mainline branch

CPU temp, without heatsink:

Spoiler

root@orangepizeroplus:~# armbianmonitor -m
Stop monitoring using [ctrl]-[c]
Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St.

17:54:07: 480MHz 0.00 2% 0% 1% 0% 0% 0% 65.9°C 3/6
17:54:13: 480MHz 0.00 0% 0% 0% 0% 0% 0% 63.9°C 0/6
17:54:18: 480MHz 0.00 0% 0% 0% 0% 0% 0% 57.2°C 0/6
17:54:23: 480MHz 0.00 0% 0% 0% 0% 0% 0% 60.7°C 0/6
17:54:28: 480MHz 0.00 0% 0% 0% 0% 0% 0% 63.0°C 0/6
17:54:33: 480MHz 0.00 0% 0% 0% 0% 0% 0% 63.5°C 0/6
17:54:38: 480MHz 0.00 0% 0% 0% 0% 0% 0% 62.2°C 0/6
17:54:43: 480MHz 0.00 0% 0% 0% 0% 0% 0% 65.0°C 0/6
17:54:48: 480MHz 0.00 0% 0% 0% 0% 0% 0% 64.1°C 0/6
17:54:54: 480MHz 0.07 0% 0% 0% 0% 0% 0% 63.8°C 0/6
17:54:59: 480MHz 0.07 0% 0% 0% 0% 0% 0% 62.5°C 0/6
17:55:04: 480MHz 0.06 0% 0% 0% 0% 0% 0% 62.7°C 0/6
17:55:09: 480MHz 0.06 0% 0% 0% 0% 0% 0% 64.7°C 0/6
17:55:14: 480MHz 0.05 0% 0% 0% 0% 0% 0% 63.2°C 0/6
Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St.
17:55:19: 480MHz 0.05 0% 0% 0% 0% 0% 0% 63.1°C 0/6
17:55:24: 480MHz 0.04 0% 0% 0% 0% 0% 0% 64.3°C 0/6
17:55:29: 480MHz 0.04 0% 0% 0% 0% 0% 0% 64.1°C 0/6
17:55:34: 480MHz 0.04 0% 0% 0% 0% 0% 0% 62.1°C 0/6
17:55:40: 480MHz 0.03 0% 0% 0% 0% 0% 0% 65.0°C 0/6
17:55:45: 480MHz 0.03 0% 0% 0% 0% 0% 0% 63.4°C 0/6
17:55:50: 480MHz 0.03 0% 0% 0% 0% 0% 0% 63.7°C 0/6
17:55:55: 480MHz 0.02 0% 0% 0% 0% 0% 0% 64.7°C 0/6
17:56:00: 480MHz 0.02 0% 0% 0% 0% 0% 0% 64.5°C 0/6
17:56:05: 480MHz 0.02 0% 0% 0% 0% 0% 0% 63.7°C 0/6
17:56:10: 480MHz 0.02 0% 0% 0% 0% 0% 0% 64.1°C 0/6
17:56:15: 480MHz 0.02 0% 0% 0% 0% 0% 0% 64.5°C 0/6
17:56:21: 480MHz 0.02 0% 0% 0% 0% 0% 0% 63.0°C 0/6
17:56:26: 480MHz 0.01 0% 0% 0% 0% 0% 0% 63.1°C 0/6
17:56:31: 480MHz 0.01 0% 0% 0% 0% 0% 0% 65.1°C 3/6
Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St.
17:56:36: 480MHz 0.01 0% 0% 0% 0% 0% 0% 63.2°C 0/6
17:56:41: 480MHz 0.01 0% 0% 0% 0% 0% 0% 63.0°C 0/6
17:56:46: 480MHz 0.01 0% 0% 0% 0% 0% 0% 64.6°C 0/6
17:56:51: 480MHz 0.01 0% 0% 0% 0% 0% 0% 66.0°C 3/6
17:56:56: 480MHz 0.01 0% 0% 0% 0% 0% 0% 64.4°C 0/6
17:57:01: 480MHz 0.01 0% 0% 0% 0% 0% 0% 64.3°C 0/6
17:57:07: 480MHz 0.01 0% 0% 0% 0% 0% 0% 63.8°C 0/6
17:57:12: 480MHz 0.00 0% 0% 0% 0% 0% 0% 65.1°C 3/6
17:57:17: 480MHz 0.00 0% 0% 0% 0% 0% 0% 63.9°C 0/6
17:57:22: 480MHz 0.00 0% 0% 0% 0% 0% 0% 66.0°C 3/6
17:57:27: 480MHz 0.00 0% 0% 0% 0% 0% 0% 63.3°C 0/6
17:57:32: 480MHz 0.00 0% 0% 0% 0% 0% 0% 65.7°C 3/6
17:57:37: 480MHz 0.00 0% 0% 0% 0% 0% 0% 64.6°C 0/6
17:57:42: 480MHz 0.00 0% 0% 0% 0% 0% 0% 63.8°C 0/6
17:57:48: 480MHz 0.00 1% 0% 0% 0% 0% 0% 64.7°C 0/6
Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St.
17:57:53: 480MHz 0.00 0% 0% 0% 0% 0% 0% 66.5°C 3/6
17:57:58: 480MHz 0.00 0% 0% 0% 0% 0% 0% 65.5°C 3/6
17:58:03: 480MHz 0.00 0% 0% 0% 0% 0% 0% 64.4°C 0/6
17:58:08: 480MHz 0.00 0% 0% 0% 0% 0% 0% 66.0°C 3/6
17:58:13: 480MHz 0.00 0% 0% 0% 0% 0% 0% 63.8°C 0/6
17:58:18: 480MHz 0.00 0% 0% 0% 0% 0% 0% 64.7°C 0/6
17:58:23: 480MHz 0.00 0% 0% 0% 0% 0% 0% 64.7°C 0/6
17:58:28: 480MHz 0.00 0% 0% 0% 0% 0% 0% 64.7°C 0/6
17:58:34: 480MHz 0.00 0% 0% 0% 0% 0% 0% 64.7°C 3/6
17:58:39: 480MHz 0.07 0% 0% 0% 0% 0% 0% 66.3°C 0/6
17:58:44: 480MHz 0.07 0% 0% 0% 0% 0% 0% 66.2°C 0/6
17:58:49: 480MHz 0.06 0% 0% 0% 0% 0% 0% 64.3°C 0/6
17:58:54: 480MHz 0.06 0% 0% 0% 0% 0% 0% 64.0°C 0/6
17:58:59: 480MHz 0.05 0% 0% 0% 0% 0% 0% 64.3°C 0/6
17:59:04: 480MHz 0.05 0% 0% 0% 0% 0% 0% 64.5°C 0/6
Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St.
17:59:09: 480MHz 0.04 0% 0% 0% 0% 0% 0% 64.4°C 0/6
17:59:15: 480MHz 0.04 0% 0% 0% 0% 0% 0% 64.1°C 0/6
17:59:20: 480MHz 0.04 0% 0% 0% 0% 0% 0% 66.4°C 3/6
17:59:25: 480MHz 0.03 0% 0% 0% 0% 0% 0% 65.3°C 3/6
17:59:30: 480MHz 0.03 0% 0% 0% 0% 0% 0% 65.2°C 3/6
17:59:35: 480MHz 0.03 0% 0% 0% 0% 0% 0% 64.9°C 0/6
17:59:40: 480MHz 0.02 0% 0% 0% 0% 0% 0% 65.7°C 3/6
17:59:45: 480MHz 0.02 0% 0% 0% 0% 0% 0% 66.4°C 3/6
17:59:50: 480MHz 0.02 0% 0% 0% 0% 0% 0% 64.9°C 0/6
17:59:55: 480MHz 0.02 0% 0% 0% 0% 0% 0% 62.5°C 0/6
18:00:01: 480MHz 0.02 0% 0% 0% 0% 0% 0% 64.9°C 0/6
18:00:06: 480MHz 0.02 1% 0% 0% 0% 0% 0% 65.6°C 3/6
18:00:11: 480MHz 0.01 0% 0% 0% 0% 0% 0% 66.4°C 3/6
18:00:16: 480MHz 0.01 0% 0% 0% 0% 0% 0% 66.4°C 3/6
18:00:21: 480MHz 0.01 0% 0% 0% 0% 0% 0% 65.7°C 3/6
Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St.
18:00:26: 480MHz 0.01 0% 0% 0% 0% 0% 0% 65.7°C 3/6
18:00:31: 480MHz 0.01 0% 0% 0% 0% 0% 0% 64.7°C 0/6
18:00:36: 480MHz 0.01 0% 0% 0% 0% 0% 0% 64.4°C 0/6
18:00:41: 480MHz 0.01 0% 0% 0% 0% 0% 0% 63.4°C 0/6
18:00:47: 480MHz 0.01 0% 0% 0% 0% 0% 0% 65.6°C 3/6
18:00:52: 480MHz 0.01 0% 0% 0% 0% 0% 0% 65.0°C 0/6
18:00:57: 480MHz 0.00 0% 0% 0% 0% 0% 0% 65.1°C 3/6
18:01:02: 480MHz 0.00 0% 0% 0% 0% 0% 0% 65.3°C 3/6
18:01:07: 480MHz 0.00 0% 0% 0% 0% 0% 0% 65.7°C 3/6
18:01:12: 480MHz 0.00 0% 0% 0% 0% 0% 0% 65.8°C 3/6
18:01:17: 480MHz 0.00 0% 0% 0% 0% 0% 0% 64.4°C 0/6
18:01:22: 480MHz 0.00 0% 0% 0% 0% 0% 0% 63.7°C 0/6
18:01:28: 480MHz 0.00 0% 0% 0% 0% 0% 0% 65.5°C 3/6
18:01:33: 480MHz 0.00 0% 0% 0% 0% 0% 0% 66.2°C 0/6
18:01:38: 480MHz 0.00 0% 0% 0% 0% 0% 0% 65.3°C 0/6
Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St.
18:01:43: 480MHz 0.00 0% 0% 0% 0% 0% 0% 64.1°C 3/6
18:01:48: 480MHz 0.00 0% 0% 0% 0% 0% 0% 65.5°C 3/6
18:01:53: 480MHz 0.00 0% 0% 0% 0% 0% 0% 65.0°C 0/6
18:01:58: 480MHz 0.00 0% 0% 0% 0% 0% 0% 62.5°C 0/6
18:02:03: 480MHz 0.00 0% 0% 0% 0% 0% 0% 64.6°C 0/6
18:02:08: 480MHz 0.00 0% 0% 0% 0% 0% 0% 65.8°C 3/6
18:02:14: 480MHz 0.00 0% 0% 0% 0% 0% 0% 66.3°C 3/6
18:02:19: 480MHz 0.00 0% 0% 0% 0% 0% 0% 64.6°C 0/6
18:02:24: 480MHz 0.08 0% 0% 0% 0% 0% 0% 65.3°C 3/6
18:02:29: 480MHz 0.07 0% 0% 0% 0% 0% 0% 63.8°C 0/6
18:02:34: 480MHz 0.06 0% 0% 0% 0% 0% 0% 66.5°C 3/6
18:02:39: 480MHz 0.06 0% 0% 0% 0% 0% 0% 63.7°C 0/6
18:02:44: 480MHz 0.05 0% 0% 0% 0% 0% 0% 64.6°C 0/6
18:02:49: 480MHz 0.05 0% 0% 0% 0% 0% 0% 63.5°C 0/6
18:02:55: 480MHz 0.04 0% 0% 0% 0% 0% 0% 63.9°C 0/6
Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St.
18:03:00: 480MHz 0.04 0% 0% 0% 0% 0% 0% 64.3°C 0/6
18:03:05: 480MHz 0.04 0% 0% 0% 0% 0% 0% 63.7°C 0/6
18:03:10: 480MHz 0.03 0% 0% 0% 0% 0% 0% 64.4°C 0/6
18:03:15: 480MHz 0.03 0% 0% 0% 0% 0% 0% 63.0°C 0/6
18:03:20: 480MHz 0.03 0% 0% 0% 0% 0% 0% 63.8°C 0/6
18:03:25: 480MHz 0.02 0% 0% 0% 0% 0% 0% 65.1°C 3/6
18:03:30: 480MHz 0.02 0% 0% 0% 0% 0% 0% 64.3°C 0/6
18:03:35: 480MHz 0.02 0% 0% 0% 0% 0% 0% 62.4°C 0/6
18:03:41: 480MHz 0.02 0% 0% 0% 0% 0% 0% 65.5°C 3/6
18:03:46: 480MHz 0.02 0% 0% 0% 0% 0% 0% 64.7°C 0/6
18:03:51: 480MHz 0.02 0% 0% 0% 0% 0% 0% 64.5°C 0/6
18:03:56: 480MHz 0.01 0% 0% 0% 0% 0% 0% 64.4°C 0/6
18:04:01: 480MHz 0.01 0% 0% 0% 0% 0% 0% 65.0°C 0/6^C

October 16, 2018

up

October 1, 2018

Hello community!

I use in my project "Orange Pi Zero Plus (Alwinner H5 - 512mb)". When using the image downloaded from the official site (https://www.armbian.com/orange-pi-zero-plus/ - Armbian Stretch
mainline kernel 4.14.y), I get a set of errors when I boot and when I use the working OS, which I'm straining. The same mistakes I get if I build the kernel and the OS myself through "build" (linux-sunxi64-next).

My equipment:

Memory: SanDisk Ultra microSDHC Class 10 UHS-I 48MB/s 16GB
Power supply: Raspberry Pi 3b+ Power Adapter (STONTRONICS) - 5.1V @ 2.5A

Boot: full log - https://pastebin.com/M9g6ipUp

Loading Environment from EXT4 ... ** File not found /boot/boot.env **

** Unable to read "/boot/boot.env" from mmc0: 1 **
Failed (-5)

dmesg: full log - https://pastebin.com/GyeUTQem

[0.668711] sun4i-usb-phy 1c19400.phy: Could not request ID GPIO
[0.670578] sun8i-h3-r-pinctrl 1f02c00.pinctrl: initialized sunXi PIO driver
[0.674095] sun50i-h5-pinctrl 1c20800.pinctrl: initialized sunXi PIO driver
[0.680561] NOHZ: local_softirq_pending 80

[0.703353] cacheinfo: Unable to detect cache hierarchy for CPU 0

[0.776991] core: _opp_supported_by_regulators: OPP minuV: 1120000 maxuV: 1300000, not supported by regulator
[0.776999] cpu cpu0: _opp_add: OPP not supported by regulators (912000000)
[0.777077] core: _opp_supported_by_regulators: OPP minuV: 1160000 maxuV: 1300000, not supported by regulator
[0.777084] cpu cpu0: _opp_add: OPP not supported by regulators (960000000)
[0.777134] core: _opp_supported_by_regulators: OPP minuV: 1200000 maxuV: 1300000, not supported by regulator
[0.777140] cpu cpu0: _opp_add: OPP not supported by regulators (1008000000)
[0.777218] core: _opp_supported_by_regulators: OPP minuV: 1240000 maxuV: 1300000, not supported by regulator
[0.777224] cpu cpu0: _opp_add: OPP not supported by regulators (1056000000)
[0.777274] core: _opp_supported_by_regulators: OPP minuV: 1260000 maxuV: 1300000, not supported by regulator
[0.777280] cpu cpu0: _opp_add: OPP not supported by regulators (1104000000)
[0.777357] core: _opp_supported_by_regulators: OPP minuV: 1300000 maxuV: 1300000, not supported by regulator
[0.777363] cpu cpu0: _opp_add: OPP is not supported by regulators (1152000000)
[0.777627] thermal thermal_zone0: binding zone cpu-thermal with cdev thermal-cpufreq-0 failed: -22

[0.862337] mmc0: host does not support reading read-only switch, assuming write-enable

[0.862561] NOHZ: local_softirq_pending 80

[1.265962] usb_phy_generic usb_phy_generic.0.auto: usb_phy_generic.0.auto supply vcc not found using dummy regulator

[11.340617] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit = 600, errors = remount-ro
[11.473725] 29
[11.473733] 81
[11.473738] 03
[11.473740] CC
[11.473742] 00
[11.473745] 00
[11.473747] 50
[11.473749] 00
[11.473752] 00
[11.473754] 00
[11.473756] 04
[11.473758] CC
[11.473760] 0A
[11.473762] 0C
[11.473765] 00
[11.473769] 00
[11.473770] FF
[11.473772] FF
[11.473775] FF
...
[11.474899] FF
[11.474901] FF
[11.474904] FF
[11.564425] g_serial gadget: Gadget Serial v2.4

It is difficult for me to estimate how much these errors are critical for stable use of the OS, since I am not an expert in this field. Ready for tight interaction to eliminate these problems, if they are.

Thank you for your attention and your answers - any information on this issue will be useful.

Sign In

Perier

Posts

Joined

Last visited

Content Type

Forums

Store

Crowdfunding

Applications

Events

Raffles

Community Map

Posts posted by Perier

FEL eMMC

Allwinner H5 SID

Allwinner H5 SID

ERROR: PCSI system shutdown

Orange Pi PC2 (H5) overheating after a shutdown

ERROR: PCSI system shutdown

ERROR: PCSI system shutdown

ERROR: PCSI system shutdown

Next LTS kernel 4.19.y Allwinner A10, A20, A64, H2+, H3, H5, H6 debugging party

Next LTS kernel 4.19.y Allwinner A10, A20, A64, H2+, H3, H5, H6 debugging party

Next LTS kernel 4.19.y Allwinner A10, A20, A64, H2+, H3, H5, H6 debugging party

Boot and dmesg errors

Boot and dmesg errors

Forums

My Activity Streams

Download

Store

Important Information