Armbian for Amlogic S9xxx kernel 5.x

[Reddwarf]

WHAT NOW??

scripts/package/Makefile:79: recipe for target 'bindeb-pkg' failed
Makefile:1442: recipe for target 'bindeb-pkg' failed
mv: missing destination file operand after '/home/karstein/Build-Armbian/output/debs/'
Try 'mv --help' for more information.
[ error ] ERROR in function compile_kernel [ compilation.sh:429 ]
[ error ] Failed moving kernel DEBs
[ o.k. ] Process terminated
karstein@ceres:~/Build-Armbian$

 

[balbes150]

14 hours ago, Reddwarf said:

Any idea what option that could be?

I don't do guesswork.

 

1 hour ago, Reddwarf said:

WHAT NOW??

Kernel build failed.

[Reddwarf]

5 minutes ago, balbes150 said:

I don't do guesswork.

 

Kernel build failed.

Yeah, I can see the obvious! But why oh why? I thought this was a tested reliable procedure?

 

[Peyton]

21 hours ago, balbes150 said:

You have something not working correctly ?

CPU affinity isn't working on docker.

 

On my S912 is it.

 

It's not a big deal anyway it was just to inform about that.  :)

[Reddwarf]

6 hours ago, balbes150 said:

I don't do guesswork.

 

Kernel build failed.

The exact same thing happens even if I don't touch the kernel configuration at all. I'm trying to build Armbian Ubuntu disco with kernel 5.2

[Reddwarf]

3 hours ago, Reddwarf said:

The exact same thing happens even if I don't touch the kernel configuration at all. I'm trying to build Armbian Ubuntu disco with kernel 5.2

No matter what version I try to build I get this error, even if I don't touch the kernel configuration, so the script for building Armbial is obviously useless.

@balbes150 Can you please fix it since I need to build my own image?

 

[ .... ] Creating packages
/bin/bash ./scripts/package/mkdebian
scripts/package/Makefile:79: recipe for target 'bindeb-pkg' failed
Makefile:1439: recipe for target 'bindeb-pkg' failed
mv: missing destination file operand after '/home/karstein/Build-Armbian/output/debs/'
Try 'mv --help' for more information.
[ error ] ERROR in function compile_kernel [ compilation.sh:429 ]
[ error ] Failed moving kernel DEBs
[ o.k. ] Process terminated
karstein@ceres:~/Build-Armbian$

 

[balbes150]

13 hours ago, Reddwarf said:

so the script for building Armbial is obviously useless.

If you don't know how to use the tools, that's your problem. Look for what is wrong in your system.

[Reddwarf]

12 hours ago, balbes150 said:

If you don't know how to use the tools, that's your problem. Look for what is wrong in your system.

I would appreciate some tip about what and where to look. I have done exactly as described, not changed any config and still it does not work.

[SteeMan]

3 hours ago, Reddwarf said:

I would appreciate some tip about what and where to look. I have done exactly as described, not changed any config and still it does not work.

I did a build last night of Armbian_5.91_Aml-s905_Ubuntu_disco_default_5.2.0.img without any problems.  So it isn't that case that as you said "the script for building Armbial is obviously useless," because it works fine for me.  So there is something in your environment that is causing a failure as balbes150 stated.  Have you tried building on a different host?

[Reddwarf]

10 hours ago, SteeMan said:

I did a build last night of Armbian_5.91_Aml-s905_Ubuntu_disco_default_5.2.0.img without any problems.  So it isn't that case that as you said "the script for building Armbial is obviously useless," because it works fine for me.  So there is something in your environment that is causing a failure as balbes150 stated.  Have you tried building on a different host?

I can't imagine what would be different, I set up a virtual environment with Ubuntu 18.04.2 64bit desktop, plenty of virtual disk space and the needed resources. can't see what's wrong with that as that is the recommended. Any other ideas is greatly appreciated

[martinayotte]

3 hours ago, Reddwarf said:

Any other ideas is greatly appreciated

 

On 7/17/2019 at 12:51 PM, Reddwarf said:

mv: missing destination file operand after '/home/karstein/Build-Armbian/output/debs/'

Maybe the destination path already exist and not overwritable.

Manually deleting previous DTB before doing new build should fix the issue.

[balbes150]

2 hours ago, martinayotte said:

Maybe the destination path already exist and not overwritable.

.... or no free space  

[Reddwarf]

28 minutes ago, balbes150 said:

.... or no free space  

Nope, there is 80Gb of free space...

[Reddwarf]

What does DTB's have to do with debs?

[martinayotte]

5 minutes ago, Reddwarf said:

What does DTB's have to do with debs?

During builds, a DTB package is generated ...

Did you tried to empty the output/debs folder before doing a new build ?

[Janaboy]

Hi @balbes150,

 

I hope i can ask a little help from you.

I have a Beelink Mini MXIII box (S905, 2G/16). 

I have downloaded this img: Armbian_5.91_Aml-s905_Ubuntu_disco_default_5.1.0_desktop_20190708.img installed on a 8gb sd card and renamed the dtb in uenv.ini and extlinux.conf to meson-gxbb-p200.dtb.

From Android i have selected the Update&Backup and used the aml_script.zip to install/start my linux.

It is starting just fine, but i would like to move the whole thing to the eMMC.

I saw in the dmesg that my emmc is mmcblk0, so i renamed it in install.sh, which ran without error but after restart there is nothing, not even black screen (basically no signal).

Can you please help me to figure out what could be the problem?

 

Thank you 

[Reddwarf]

21 hours ago, martinayotte said:

During builds, a DTB package is generated ...

Did you tried to empty the output/debs folder before doing a new build ?

debs and DTB's are not the same, or what? 

Emptying the output folders should be done by the script, that's the accepted way of doing things, or there should be a "make clean" option.

 

Now, I'v done a lot more testing and it turns out that if you enable an option with build error, resetting the configuration dos not help, the script will crash on the next build. Even deleting the whole Build-Armbian folder and cloning it fresh does not help. This suggests that there are temp- or working-folders left behind that are not cleared before the next build. So some more work needed on the script(s). Since I have no way of knowing where those resides the only way of resetting I found is to delete the whole virtual machine and create it again. Anyway, the script works for some kernel configurations but some (useful ones) crashes.

[martinayotte]

23 minutes ago, Reddwarf said:

debs and DTB's are not the same, or what?

They are not the same, but there is packages which includes dtb, like this one for example : output/debs/linux-dtb-dev-rk3399_5.91_arm64.deb

[Reddwarf]

1 hour ago, martinayotte said:

They are not the same, but there is packages which includes dtb, like this one for example : output/debs/linux-dtb-dev-rk3399_5.91_arm64.deb

So why nag about dtb's when the problem is with the packages, I don't follow the reasoning.

[martinayotte]

1 hour ago, Reddwarf said:

So why nag about dtb's when the problem is with the packages, I don't follow the reasoning.

Simply because if that DTB package is holded by another zombie process, the new build process won't be able to overwrite it !

 

mv: missing destination file operand after '/home/karstein/Build-Armbian/output/debs/'

I've faced the same issue few weeks ago, and I've resolved it by deleting the previously corrupted package...

 

[Reddwarf]

3 hours ago, martinayotte said:

Simply because if that DTB package is holded by another zombie process, the new build process won't be able to overwrite it !

 

mv: missing destination file operand after '/home/karstein/Build-Armbian/output/debs/'

I've faced the same issue few weeks ago, and I've resolved it by deleting the previously corrupted package...

 

Easy enough if you know where they are found. This should be cleaned out by the build script as a first step. Not good enough. Besides, the "build" directory of /lib/modules/<vesion>/ needed for compiling 3rd party drivers is completely missing from Armbian...

[skyfly555]

Can @balbes150 armbian be installed on Odroid C2? If it's possible, which DTB must be used?

[Janaboy]

On 7/20/2019 at 8:22 AM, Janaboy said:

Hi @balbes150,

 

I hope i can ask a little help from you.

I have a Beelink Mini MXIII box (S905, 2G/16). 

I have downloaded this img: Armbian_5.91_Aml-s905_Ubuntu_disco_default_5.1.0_desktop_20190708.img installed on a 8gb sd card and renamed the dtb in uenv.ini and extlinux.conf to meson-gxbb-p200.dtb.

From Android i have selected the Update&Backup and used the aml_script.zip to install/start my linux.

It is starting just fine, but i would like to move the whole thing to the eMMC.

I saw in the dmesg that my emmc is mmcblk0, so i renamed it in install.sh, which ran without error but after restart there is nothing, not even black screen (basically no signal).

Can you please help me to figure out what could be the problem?

 

Thank you 

Okay very-very insteresting situation..

So i am working to resolve the booting issue, so i looked for some solutions. 

I've used the AML Boot SD card maker software to recover my android.

This software reformatted my sd card (i have a 16 mb unknown at the beginning of the card), and copied 3 files, i have deleted all the three files and without doing anything special step (like using the reset button) the Armbian on the eMMC just booting fine.

 

Any idea why? Or how i can solve this without using the SD Card?

 

Update: I've tried to compare my /boot partition (fat16) with the SD card partition (fat32) and the only different that from my /boot was missing the boot flag, (it has only lba), I've added, but did not solve the issue.

Thinking testing, but not sure which way to go. 

 

Thanks

[Reddwarf]

On 7/20/2019 at 9:24 PM, skyfly555 said:

Can @balbes150 armbian be installed on Odroid C2? If it's possible, which DTB must be used?

There is a separate build for Odroid C2, https://www.armbian.com/odroid-c2/

[Cinerar]

Running Armbian_5.91_Aml-g12_Ubuntu_bionic_default_5.2.0_desktop_20190715.img

on x96 max 2 gb using meson-g12a-x96-max-rmii.dtb unable to install on emmc

Spoiler

dmesg | grep mmc
[    3.169973] meson-gx-mmc ffe05000.sd: Got CD GPIO
[    3.203842] meson-gx-mmc ffe07000.mmc: allocated mmc-pwrseq
[    3.355249] mmc1: switch to high-speed failed, err:-84
[    3.355324] mmc1: error -84 whilst initialising MMC card
[   13.730765] meson-gx-mmc ffe03000.sd: allocated mmc-pwrseq
[   13.781642] mmc2: new high speed SDIO card at address 0001

lsblk  
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    1   7.4G  0 disk 
|-sda1   8:1    1   128M  0 part /boot
`-sda2   8:2    1   7.1G  0 part /
zram0  253:0    0    50M  0 disk /var/log
zram1  253:1    0 928.8M  0 disk [SWAP]

and for sure install.sh is failing with 

UNABLE TO FIND ANY EMMC OR SD DRIVES ON THIS SYSTEM!!! 

Any ideas?

 

update: if i use meson-g12a-x96-max-2gb.dtb from this link https://yadi.sk/d/QHmrwhbZ8wRvOA i have same problem.

 

update2: if i use Armbian_5.82_Aml-s905_Ubuntu_bionic_default_5.1.0-rc1_desktop_20190427.img with meson-g12a-x96-max-2gb.dtb everything looks like ok

 

update3: failed after trying to install on emmc now stucked in loop of via UART

 G12A:BL:0253b8:61aa2d;FEAT:E0F83180:2000;POC:F;RCY:0;EMMC:0;READ:0;CHK:1F;READ:0;CHK:1F;READ:0;CHK:1F;SD?:20000;USB:8;G12A:BL:0253b8:61aa2d;FEAT:E0F83180:2000;POC:F;RCY:0;EMMC:0;READ:0;CHK:1F;READ:0;CHK:1F;READ:0;CHK:1F;SD?:20000;USB:8;LOOP:1;EMMC:0;READ:0;.........

And no ability to boot anything.  if i use USB burning tool it fails with "romcode/bl2_boot stage error"  on 1-3%

If i try to boot via sd card made with Burn_Card_Maker from https://yadi.sk/d/L__XmiAEBaTsug it cycles with 

 

Spoiler

G12A:BL:0253b8:61aa2d;FEAT:E0F83180:2000;POC:F;RCY:0;EMMC:0;READ:0;CHK:1F;READ:0;CHK:1F;READ:0;CHK:1F;SD?:0;SD:0;READ:0;0.0;

bl2_stage_init1

no sdio debug board detected
L0:00000000
L1:00000703
L2:00008067
L3:04000000
S1:00000000
B2:00002000
B1:e0f83180

TE: 189547

BL2 Built : 15:37:08, Oct 16 2018. g12a g2efb180 - xiaobo.gu@droid12

Board ID = 1
Set cpu clk to 24M
Set clk81 to 24M
CPU clk: 1200 MHz
Set clk81 to 166.6M
smccc: 00031ff5
boot_device: 4
DDR driver_vesion: LPDDR4_PHY_V_0_1_5 build time: Oct 16 2018 15:37:03
board id: 1
Load FIP HDR from SD, src: 0x00010200, des: 0xfffd0000, size: 0x004000, part: 0
fw parse done
Load ddrfw from SD, src: 0x00060200, des: 0xfffd0000, size: 0x00c000, part: 0
Load ddrfw from SD, src: 0x00038200, des: 0xfffd0000, size: 0x004000, part: 0
PIEI prepare done
Cfg max: 5, cur: 1. Board id: 255. Force loop cfg
DDR4 probe
Set ddr clk to 912MHz
Load ddrfw from SD, src: 0x00014200, des: 0xfffd0000, size: 0x00c000, part: 0
Check phy result
INFO : End of initialization
INFO : End of read enable training
INFO : End of fine write leveling
INFO : STREAM 0x00490002 - 0x00000000 0x00000000
INFO : STREAM 0x04020000 -
INFO : ERROR : Training has failed!
1D training failed
Cfg max: 5, cur: 2. Board id: 255. Force loop cfg
DDR3 probe
Set ddr clk to 912MHz
Load ddrfw from SD, src: 0x0002c200, des: 0xfffd0000, size: 0x00c000, part: 0
Check phy result
INFO : End of initialization
INFO : STREAM 0x00670000 -
INFO : STREAM 0x04020000 -
INFO : ERROR : Training has failed!
1D training failed
Cfg max: 5, cur: 3. Board id: 255. Force loop cfg
LPDDR4 probe
Set ddr clk to 912MHz
Load ddrfw from SD, src: 0x0003c200, des: 0xfffd0000, size: 0x00c000, part: 0
5113Check phy result
INFO : STREAM 0x00b00001 - 0x00001000
INFO : STREAM 0x00a70001 - 0x00000014
INFO : STREAM 0x00540003 - 0x00000004 0x00000008 0x0000000a
INFO : STREAM 0x00560006 - 0x00000003 0x00000003 0x00001001 0x0000000a 0x00000000 0x00000720
INFO : STREAM 0x005b0005 - 0x00000000 0x00000034 0x0000009b 0x00000032 0x00000000
INFO : STREAM 0x00a10000 -
INFO : STREAM 0x04020000 -
INFO : ERROR : Training has failed!
Check phy result
INFO : STREAM 0x00b00001 - 0x00001000
INFO : STREAM 0x00a70001 - 0x00000014
INFO : STREAM 0x00540003 - 0x00000004 0x00000008 0x0000000a
INFO : STREAM 0x00560006 - 0x00000003 0x00000003 0x0000031f 0x0000000a 0x00000000 0x00000720
INFO : STREAM 0x005b0005 - 0x00000000 0x00000034 0x0000009b 0x00000032 0x00000000
INFO : End of initialization
INFO : STREAM 0x00670000 -
INFO : STREAM 0x04020000 -
INFO : ERROR : Training has failed!
1D training failed
Cfg max: 5, cur: 4. Board id: 255. Force loop cfg
LPDDR4 probe
Set ddr clk to 1392MHz
Load ddrfw from SD, src: 0x0003c200, des: 0xfffd0000, size: 0x00c000, part: 0
5084Check phy result
INFO : STREAM 0x00b00001 - 0x00001000
INFO : STREAM 0x00a70001 - 0x0000001c
INFO : STREAM 0x00540003 - 0x00000004 0x00000008 0x0000000a
INFO : STREAM 0x00560006 - 0x00000001 0x00000001 0x00001001 0x0000000a 0x00000000 0x00000ae0
INFO : STREAM 0x005b0005 - 0x00000000 0x00000054 0x000000ad 0x00000032 0x00000000
INFO : STREAM 0x00a10000 -
INFO : STREAM 0x04020000 -
INFO : ERROR : Training has failed!
Check phy result
INFO : STREAM 0x00b00001 - 0x00001000
INFO : STREAM 0x00a70001 - 0x0000001c
INFO : STREAM 0x00540003 - 0x00000004 0x00000008 0x0000000a
INFO : STREAM 0x00560006 - 0x00000001 0x00000001 0x0000031f 0x0000000a 0x00000000 0x00000ae0
INFO : STREAM 0x005b0005 - 0x00000000 0x00000054 0x000000ad 0x00000032 0x00000000
INFO : End of initialization
INFO : STREAM 0x00670000 -
INFO : STREAM 0x04020000 -
INFO : ERROR : Training has failed!
1D training failed
Cfg max: 5, cur: 5. Board id: 255. Force loop cfg
LPDDR3 probe
Set ddr clk to 600MHz
Load ddrfw from SD, src: 0x000101ff, des: 0xfffd0000, size: 0xffffff, part: 0
sd/emmc cmd 18 arg 0x00000180 status 01ff3000 pinmux0 11111111 pinmux1 00100101 ds_reg0 ffffffff
sdio read data fail
 

 

Looks like i stuck for now with bricked device.  Any help would be appreciated. 

 

update4: was able to reflash with USB_Burning_tool with stock firmware 15.03.2019 from this post https://4pda.ru/forum/index.php?showtopic=925461&view=findpost&p=82632243 going to try with armbian again

 

update5: found that if i remove cap-mmc-highspeed; 

in mmc@ffe07000 {} block

of meson-g12a-x96-max-rmii.dts and recompile it back to dtb 

mmc start working on vontar x96 max 2g/16 

Spoiler

lsblk
NAME         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda            8:0    1   7.4G  0 disk 
|-sda1         8:1    1   128M  0 part /boot
`-sda2         8:2    1   7.1G  0 part /
mmcblk1      179:0    0  14.7G  0 disk 
mmcblk1boot0 179:32   0     4M  1 disk 
mmcblk1boot1 179:64   0     4M  1 disk 
zram0        253:0    0    50M  0 disk /var/log
zram1        253:1    0 928.8M  0 disk [SWAP]
 

 

dmesg | grep mmc
[    3.170361] meson-gx-mmc ffe05000.sd: Got CD GPIO
[    3.204176] meson-gx-mmc ffe07000.mmc: allocated mmc-pwrseq
[    3.381094] mmc1: new MMC card at address 0001
[    3.394550] mmcblk1: mmc1:0001 016GE2 14.7 GiB 
[    3.399773] mmcblk1boot0: mmc1:0001 016GE2 partition 1 4.00 MiB
[    3.405534] mmcblk1boot1: mmc1:0001 016GE2 partition 2 4.00 MiB
[    3.410874] mmcblk1rpmb: mmc1:0001 016GE2 partition 3 4.00 MiB, chardev (241:0)
[   13.871673] meson-gx-mmc ffe03000.sd: allocated mmc-pwrseq
[   13.928853] mmc2: new high speed SDIO card at address 0001
 

 

@balbes150 can this update5 somehow be implemented in future firmwares?

[skyfly555]

On 7/22/2019 at 7:57 AM, Reddwarf said:

There is a separate build for Odroid C2, https://www.armbian.com/odroid-c2/

I know, thank you, but it's Stretch, and I'd like to use Buster. I have several ATVs running @balbes150 images, and I'd like to use the same version of Buster in all of them, and in my Odroid C2, too.

So... do you know if it's possible?

[Reddwarf]

3 hours ago, skyfly555 said:

I know, thank you, but it's Stretch, and I'd like to use Buster. I have several ATVs running @balbes150 images, and I'd like to use the same version of Buster in all of them, and in my Odroid C2, too.

So... do you know if it's possible?

I don't know but you could try to download one of the images for Odroid C2 and see if there is a DTB,  then try to use that DTB with Balbes image(s).

BTW: Does the C2 have the same cpu type as the Amlogic TV-boxes?

[balbes150]

New version of Armbian 5.91_20190724.
Fixed CPU operation in HTOP\armbianmonitor commands for VIM3 (a311d).

 

https://yadi.sk/i/uHPZYvvGNIO2SQ

[balbes150]

On 7/20/2019 at 9:22 AM, Janaboy said:

I hope i can ask a little help from you.

I have a Beelink Mini MXIII box (S905, 2G/16). 

I have downloaded this img: Armbian_5.91_Aml-s905_Ubuntu_disco_default_5.1.0_desktop_20190708.img installed on a 8gb sd card and renamed the dtb in uenv.ini and extlinux.conf to meson-gxbb-p200.dtb.

From Android i have selected the Update&Backup and used the aml_script.zip to install/start my linux.

It is starting just fine, but i would like to move the whole thing to the eMMC.

I saw in the dmesg that my emmc is mmcblk0, so i renamed it in install.sh, which ran without error but after restart there is nothing, not even black screen (basically no signal).

Can you please help me to figure out what could be the problem?

1. You do not need to change anything in the installation scripts, they should automatically determine the correct name of the eMMC.

2. A prerequisite for installation in the eMMC, the use of the latest versions of multi-boot (reactivation using the latest images).

If this does not help - need a log UART console.

 

On 7/20/2019 at 10:24 PM, skyfly555 said:

armbian be installed on Odroid C2? If it's possible, which DTB must be used?

Specify whether you want to run from SD card or from eMMC ?

[balbes150]

On 7/23/2019 at 12:47 AM, Cinerar said:

 can this update5 somehow be implemented in future firmwares? 

Maybe it's a problem of bad components for the clones.