[Arm-dev] Cubieboard5 performance

Robert Moskowitz rgm at htt-consult.com
Thu Aug 9 15:31:44 UTC 2018



On 08/09/2018 11:21 AM, arm_ml at rirasoft.de wrote:
> Am 2018-08-09 16:57, schrieb Robert Moskowitz:
>> On 08/09/2018 10:31 AM, arm_ml at rirasoft.de wrote:
>>> Am 2018-08-09 13:58, schrieb Robert Moskowitz:
>>>> On 08/09/2018 07:34 AM, arm_ml at rirasoft.de wrote:
>>>>> Am 2018-08-07 12:23, schrieb Pablo Sebastián Greco:
>>>>>> <snip>
> snip
>>>
>>>
>>> Okay, I give CentOs on this device a try. What have I done:
>>> 1. write Fedora-Minimal-armhfp-Rawhide-20180802.n.0-sda.raw.xz on 
>>> the SD-card
>>> 2. delete all 4 partions
>>> 3. mount CentOS-Userland-7-armv7hl-Minimal-1611-CubieTruck.img as 
>>> loop device
>>> 4. create 3 new partions on SD-Card (same size as CentOS-Image)
>>> 5. copy 1. and 3. partion from CentOS to SD-Card
>>> 6. copy sun8i-a83t-cubietruck-plus.dtb From Fedora to 
>>> /mnt/SDCard/1/dtb-4.4.34-201.el7.armv7hl/
>>> 7. boot from SD-Card
>>>
>>> boot log:
>>> U-Boot SPL 2018.09-rc1 (Jul 31 2018 - 12:18:07 +0000)
>>> DRAM: 2048 MiB
>>> Trying to boot from MMC1
>>>
>>>
>>> U-Boot 2018.09-rc1 (Jul 31 2018 - 12:18:07 +0000) Allwinner Technology
>>
>> OK.  You are using the latest uboot.  Centos build only has 2018.03
>>
>> Another way is to copy the uboot from Fedora:
>>
>> /usr/share/uboot/Cubietruck_plus/
>>
>> and dd that onto the Centos 1804 image (why are you using the old 1611
>> image?  There were problems with it an Cubietruck+ as I recall).
>
> I'm using CentOS-Userland-7-armv7hl-Minimal-1611-CubieTruck.img.xz 
> because of the CubieTruck in the name. With the 
> CentOS-Userland-7-armv7hl-generic-Minimal-1804-sda.raw.xz the boot 
> process complains about missing vmlinuz-4.14.28-201.el7.centos.armv7hl

Read the instructions on: 
https://wiki.centos.org/SpecialInterestGroup/AltArch/armhfp for 
installing Centos generic userland.

But follow my recommendation to swipe the newer uboot from your 
Fedora-rawhide image, rather than installing the uboot-images on your 
system and only getting the 2018.03 version.

It runs fine on my Cubieboard2 and Cubietruck.  I do not have a plus.

>>
>> Boot this and see what it does.  If it fails, then copy the dtb from 
>> Fedora:
>>
>> /usr/lib/modules/4.18.0-0.rc8.git0.1.fc29.armv7hl/dtb/sun8i-a83t-cubietruck-plus.dtb 
>>
>>
>>>
>>> CPU:   Allwinner A83T (SUN8I 1673)
>>> Model: Cubietech Cubietruck Plus
>>> I2C:   ready
>>> DRAM:  2 GiB
>>> MMC:   SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
>>> Loading Environment from FAT... *** Warning - bad CRC, using default 
>>> environment
>>>
>>> Failed (-5)
>>> In:    serial
>>> Out:   serial
>>> Err:   serial
>>> Net:   No ethernet found.
>>> starting USB...
>>> USB0:   failed to get usb PHY
>>> Port not available.
>>> USB1:   failed to get usb at 01c1a000 usb PHY
>>> Port not available.
>>> USB2:   failed to get usb at 01c1b000 usb PHY
>>> Port not available.
>>> Hit any key to stop autoboot:  0
>>> switch to partitions #0, OK
>>> mmc0 is current device
>>> Scanning mmc 0:1...
>>> Found /extlinux/extlinux.conf
>>> Retrieving file: /extlinux/extlinux.conf
>>> 336 bytes read in 13 ms (24.4 KiB/s)
>>> Ignoring unknown command: ui
>>> Ignoring malformed menu command:  autoboot
>>> Ignoring unknown command: totaltimeout
>>> centos Options
>>> 1:      centos
>>> Enter choice: 1:        centos
>>> Retrieving file: /initramfs-4.4.34-201.el7.armv7hl.img
>>> 35020663 bytes read in 22174 ms (1.5 MiB/s)
>>> Retrieving file: /vmlinuz-4.4.34-201.el7.armv7hl
>>> 6051744 bytes read in 620 ms (9.3 MiB/s)
>>> append: enforcing=0 root=UUID=ad25a528-baf4-469c-bd12-5276e8f5f9ae
>>> Retrieving file: 
>>> /dtb-4.4.34-201.el7.armv7hl/sun8i-a83t-cubietruck-plus.dtb
>>> 548864 bytes read in 260 ms (2 MiB/s)
>>> ERROR: Did not find a cmdline Flattened Device Tree
>>> Could not find a valid device tree
>>> SCRIPT FAILED: continuing...
>>> Found U-Boot script /boot.scr
>>> 2 bytes read in 12 ms (0 Bytes/s)
>>> ## Executing script at 43100000
>>> Wrong image format for "source" command
>>> SCRIPT FAILED: continuing...
>>> switch to partitions #0, OK
>>> mmc1(part 0) is current device
>>> Scanning mmc 1:1...
>>> starting USB...
>>> USB0:   failed to get usb PHY
>>> Port not available.
>>> USB1:   failed to get usb at 01c1a000 usb PHY
>>> Port not available.
>>> USB2:   failed to get usb at 01c1b000 usb PHY
>>> Port not available.
>>> USB is stopped. Please issue 'usb start' first.
>>> starting USB...
>>> USB0:   failed to get usb PHY
>>> Port not available.
>>> USB1:   failed to get usb at 01c1a000 usb PHY
>>> Port not available.
>>> USB2:   failed to get usb at 01c1b000 usb PHY
>>> Port not available.
>>> No ethernet found.
>>> missing environment variable: pxeuuid
>>> Retrieving file: /extlinux/pxelinux.cfg/00000000
>>> No ethernet found.
>>> Retrieving file: /extlinux/pxelinux.cfg/0000000
>>> No ethernet found.
>>> Retrieving file: /extlinux/pxelinux.cfg/000000
>>> No ethernet found.
>>> Retrieving file: /extlinux/pxelinux.cfg/00000
>>> No ethernet found.
>>> Retrieving file: /extlinux/pxelinux.cfg/0000
>>> No ethernet found.
>>> Retrieving file: /extlinux/pxelinux.cfg/000
>>> No ethernet found.
>>> Retrieving file: /extlinux/pxelinux.cfg/00
>>> No ethernet found.
>>> Retrieving file: /extlinux/pxelinux.cfg/0
>>> No ethernet found.
>>> Retrieving file: /extlinux/pxelinux.cfg/default-arm-sunxi
>>> No ethernet found.
>>> Retrieving file: /extlinux/pxelinux.cfg/default-arm
>>> No ethernet found.
>>> Retrieving file: /extlinux/pxelinux.cfg/default
>>> No ethernet found.
>>> Config file not found
>>> starting USB...
>>> USB0:   failed to get usb PHY
>>> Port not available.
>>> USB1:   failed to get usb at 01c1a000 usb PHY
>>> Port not available.
>>> USB2:   failed to get usb at 01c1b000 usb PHY
>>> Port not available.
>>> No ethernet found.
>>> No ethernet found
>>>
>>> Greetings
>>> Andreas
>>>
>
> Andreas
>



More information about the Arm-dev mailing list