Jump to content

Error building for orangepi lite2

junnikokuki

By junnikokuki
in Armbian build framework

 Share

Recommended Posts

junnikokuki

junnikokuki

Posted
Posted

Hi,

I recently set up an ubuntu 16.04 parallels machine for armbian building. 

I use 

./compile.sh BRANCH=dev

to build orange pi lite2 dev images.

But it failed, here is the log:

 

[ o.k. ] Downloading sources 

[ o.k. ] Checking git sources [ u-boot h6-hdmi-rebased-1 ]

[ .... ] Up to date 

[ o.k. ] Checking git sources [ linux-mainline h6-integrate-2-ugly ]

[ .... ] Up to date 

[ o.k. ] Checking git sources [ arm-trusted-firmware-sunxi-mainline sun50i_h6_pmic ]

[ .... ] Up to date 

[ o.k. ] Checking git sources [ sunxi-tools master ]

[ .... ] Up to date 

[ o.k. ] Checking git sources [ rkbin-tools master ]

[ .... ] Up to date 

[ o.k. ] Checking git sources [ marvell-tools A3700_utils-armada-18.09 ]

[ .... ] Up to date 

[ o.k. ] Checking git sources [ marvell-ddr mv_ddr-armada-18.09 ]

[ .... ] Up to date 

[ o.k. ] Checking git sources [ odroidc2-blobs master ]

[ .... ] Up to date 

[ o.k. ] Checking git sources [ testing-reports master ]

[ .... ] Up to date 

[ o.k. ] Cleaning output/debs for [ orangepilite2 dev ]

ls: cannot access '/usr/local/src/armbian/cache/rootfs/*.lz4': No such file or directory

[ o.k. ] Cleaning [ arm-trusted-firmware-sunxi-mainline/sun50i_h6_pmic ]

[ o.k. ] Compiling ATF 

[ o.k. ] Compiler version [ aarch64-linux-gnu-gcc 6.4.1 ]

[ o.k. ] Started patching process for [ atf sunxi64-orangepilite2-dev ]

[ o.k. ] Looking for user patches in [ userpatches/atf/atf-sunxi64 ]

[ warn ] * [l][c] enable-additional-regulators.patch [ failed ]

[ warn ] * [l][c] set-rsb-to-nonsec.patch [ failed ]

[ error ] ERROR in function compile_atf [ compilation.sh:81 ]

[ error ] ATF file not found [ bl31.bin ]

[ o.k. ] Process terminated 

 

So what is the problem? Thank you.

Link to comment
Share on other sites
Werner

Werner

Posted
Posted

Will test this against the OPi One Plus. From earlier nightlies we know that 4.18.x has some issues. 4.18.0-rc7 from Icenowy works though.  Lets see what happens.

As far for now build did not fail at ATF. That's a good sign.

Link to comment
Share on other sites
Igor

Igor

Posted
Posted
1 hour ago, Werner said:

Will test this against the OPi One Plus. From earlier nightlies we know that 4.18.x has some issues. 4.18.0-rc7 from Icenowy works though.  Lets see what happens.

As far for now build did not fail at ATF. That's a good sign.


I actually build and boot Opi Lite 2, but before adding this https://github.com/armbian/build/commit/9fcb58b8f17b128dc305d76264830140d5a80c62

Link to comment
Share on other sites
Werner

Werner

Posted
Posted
14 minutes ago, Igor said:


I actually build and boot Opi Lite 2, but before adding this https://github.com/armbian/build/commit/9fcb58b8f17b128dc305d76264830140d5a80c62

This basically changed the kernel source from Icenowy sources to mainline. For me this results in an unbootable image. No clue if this affects Lite2 too or OPi One Plus only.

 

Link to comment
Share on other sites
martinayotte

martinayotte

Posted
Posted
1 hour ago, Werner said:

This basically changed the kernel source from Icenowy sources to mainline. For me this results in an unbootable image. No clue if this affects Lite2 too or OPi One Plus only.

As said in the other thread, my build done during lunch time with latest Igor's commit is working perfectly for me, including WiFi ...

 

Link to comment
Share on other sites
martinayotte

martinayotte

Posted
Posted
1 hour ago, Werner said:

This answers the question if OPi One Plus is affected only I guess

You're right ! My resulting build faced the same "oops" issue :



Starting kernel ...

[    0.883666] Internal error: Oops: 96000004 [#1] SMP
[    0.888539] Modules linked in:
[    0.891599] CPU: 3 PID: 36 Comm: kworker/3:1 Not tainted 4.18.10-sunxi64 #39
[    0.898639] Hardware name: Orange Pi One+ (DT)
[    0.903090] Workqueue: events deferred_probe_work_func
[    0.908227] pstate: 80000005 (Nzcv daif -PAN -UAO)
[    0.913017] pc : sun8i_dwmac_probe+0x164/0x518
[    0.917457] lr : sun8i_dwmac_probe+0x20c/0x518
[    0.921896] sp : ffff00000907bb30
[    0.925208] x29: ffff00000907bb30 x28: 0000000000000000
[    0.930518] x27: 0000000000000000 x26: ffff000008b7d790
[    0.935827] x25: ffff800037fe4558 x24: ffff800036ac4010
[    0.941137] x23: ffff800036ac4000 x22: ffff8000353fd018
[    0.946447] x21: ffff8000352a0618 x20: ffff000008bcf000
[    0.951756] x19: ffff000008d08000 x18: 0000000000008000
[    0.957066] x17: 0000000000000001 x16: ffff0000089f8c98
[    0.962376] x15: ffff800037fdf600 x14: ffff000008c0d000
[    0.967686] x13: 00000000000000e0 x12: 0000000000000030
[    0.972995] x11: 0101010101010101 x10: 7f7f7f7f7f7f7f7f
[    0.978305] x9 : 6061686d68656d68 x8 : ffff00000907b808
[    0.983615] x7 : 0000000000000000 x6 : 0000000000000003
[    0.988925] x5 : 0000000000000002 x4 : 0000000000000003
[    0.994234] x3 : 0000000000000000 x2 : ffff00000907bba0
[    0.999544] x1 : ffff8000353fd400 x0 : ffff800036ac4010
[    1.004855] Process kworker/3:1 (pid: 36, stack limit = 0x(____ptrval____))
[    1.011812] Call trace:
[    1.014260]  sun8i_dwmac_probe+0x164/0x518
[    1.018357]  platform_drv_probe+0x50/0xa0
[    1.022365]  driver_probe_device+0x21c/0x2f8
[    1.026633]  __device_attach_driver+0x98/0xf0
[    1.030991]  bus_for_each_drv+0x64/0xc8
[    1.034826]  __device_attach+0xd8/0x130
[    1.038660]  device_initial_probe+0x10/0x18
[    1.042841]  bus_probe_device+0x90/0x98
[    1.046675]  deferred_probe_work_func+0x9c/0x140
[    1.051295]  process_one_work+0x1e8/0x338
[    1.055304]  worker_thread+0x240/0x478
[    1.059053]  kthread+0x128/0x130
[    1.062283]  ret_from_fork+0x10/0x18
[    1.065859] Code: f94012a3 9101c3a2 aa1803e0 f9400463 (a9401464)
[    1.071949] ---[ end trace 029a1edcd6a69c51 ]---
[    1.125208] mmc0: host does not support reading read-only switch, assuming write-enable
[    1.136755] mmc0: new high speed SDHC card at address 59b4
[    1.143147] mmcblk0: mmc0:59b4       29.8 GiB
[    1.149804]  mmcblk0: p1

 

I don't know why since it was running fine using @Icenowy h6-integrate-2-ugly branch, but it crash here with 4.18.10, but not on the Lite2 (since it doesn't have ETH port).

 

1
Link to comment
Share on other sites
martinayotte

martinayotte

Posted
Posted
4 hours ago, martinayotte said:

running fine using @Icenowy h6-integrate-2-ugly branch

@Icenowy , do you have any hint why our h6-integrate-2-ugly branch is working fine, but not 4.18.10 ?

Is one of your patches end up into something higher such 4.19.y that we missed ? Or is that a patch from @montjoie that we also missed that you commited into your own h6-integrate-2-ugly branch ?

 

Link to comment
Share on other sites
Icenowy

Icenowy

Posted
Posted
1 minute ago, martinayotte said:

@Icenowy , do you have any hint why our h6-integrate-2-ugly branch is working fine, but not 4.18.10 ?

Is one of your patches end up into something higher such 4.19.y that we missed ? Or is that a patch from @montjoie that we also missed that you commited into your own h6-integrate-2-ugly branch ?

 

I'm not sure, my distro uses 4.19 and omitted 4.18.

1
Link to comment
Share on other sites
martinayotte

martinayotte

Posted
Posted
1 minute ago, Werner said:

Did you find a solution for the unbootable OPi 1+ yet?

On my side, I kept my previous OPiOne+ build done with h6-integrate-2-ugly branch.

I didn't investigate further about Mainline 4.18.10 since Icenowy suggested to check with 4.19.y, but I didn't take the time to check ...

 

1
Link to comment
Share on other sites
Werner

Werner

Posted
Posted
11 minutes ago, martinayotte said:

On my side, I kept my previous OPiOne+ build done with h6-integrate-2-ugly branch.

 I didn't investigate further about Mainline 4.18.10 since Icenowy suggested to check with 4.19.y, but I didn't take the time to check ...

 

Did just a quick look at 4.19 but did not come very far... I leave it that way as well and wait for @Igor to push sunxi64 to 4.19. Thank you anyways.

Link to comment
Share on other sites
martinayotte

martinayotte

Posted
Posted
2 minutes ago, Werner said:

Thank you anyways.

I've just started new build with 4.18.12, and when finished, I will disable the dwmac and check if it boot properly, I think it will.

This would mean that patches for dwmac added in 4.19.y would need to be backported, or we wait for 4.19, which can still take awhile ...

1
Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept