Support for "Banana Pi Pro"


sgei
 Share

1 1

Recommended Posts

Hi Igor, hi team,

 

we are using Armbian since the the first version.

We only using it with Banana Pi and Banana Pi Pro.

 

Yesterday I wanted to build a new image for our BananaPro projects, but unfortunately there is no support for Banana Pi Pro anymore. Why?

 

Is it possible to continue supporting this board?

 

What is the difference to the Banana Pi? You still support Banana Pi.

 

Thanks.

 

Steffen

Link to post
Share on other sites

Donate and support the project!

42 minutes ago, sgei said:

Yesterday I wanted to build a new image for our BananaPro projects, but unfortunately there is no support for Banana Pi Pro anymore. Why?

Is it possible to continue supporting this board?

If you user the armbian-build-system with

./compile.sh EXPERT="yes"

you can build (at this time- but for how long) a new image for the Banana Pi Pro

 

Select EOS and then the "Banana Pi Pro"

 

But  from my view the "Pro" has only WiFi-onboard and the Cinch-CVBS/FBAS Connector anymore (maybe CVBS included in 3.5mm port)

CPU A20 DualCore and 1Gb DDDR3 Ram ist the same.

 

EOS_Boards.jpg

Switch_EOS.jpg

 

http://www.banana-pi.org/m1.html = nonPro

Link to post
Share on other sites

30 minutes ago, Tido said:

EOS, something I still don't understand. Now (at Kernel 4.20) that Mainline Kernel supports almost every function of that SoC, making this electronic waste.

My Banana Pi (non-Pro) is playing his role a Pi-Hole fine here ;)
 


Welcome to ARMBIAN 5.67 user-built Debian GNU/Linux 9 (stretch) 4.19.4-sunxi
System load:   0.11 0.15 0.10   Up time:       13:33 hours
Memory usage:  9 % of 998MB     IP:            192.168.6.3
CPU temp:      31°C
root@bpi-pihole(192.168.6.3):~#

 

Link to post
Share on other sites

Got an error message when trying to build an image for BPi-Pro:

  AR      drivers/usb/built-in.a
  CC [M]  drivers/net/wireless/rtl88x2bu/hal/phydm/phydm_rssi_monitor.o
  CC [M]  drivers/net/wireless/rtl88x2bu/hal/phydm/phydm_auto_dbg.o
  CC [M]  drivers/net/wireless/rtl88x2bu/hal/phydm/phydm_math_lib.o
  CC [M]  drivers/net/wireless/rtl88x2bu/hal/phydm/phydm_api.o
  CC [M]  drivers/net/wireless/rtl88x2bu/hal/phydm/phydm_pow_train.o
  CC [M]  drivers/net/wireless/rtl88x2bu/hal/phydm/halrf/halrf.o
  CC [M]  drivers/net/wireless/rtl88x2bu/hal/phydm/halrf/halphyrf_ce.o
  CC [M]  drivers/net/wireless/rtl88x2bu/hal/phydm/halrf/halrf_powertracking_ce.o
  CC [M]  drivers/net/wireless/rtl88x2bu/hal/phydm/halrf/halrf_powertracking.o
  CC [M]  drivers/net/wireless/rtl88x2bu/hal/phydm/halrf/halrf_kfree.o
  CC [M]  drivers/net/wireless/rtl88x2bu/hal/phydm/rtl8822b/halhwimg8822b_bb.o
  CC [M]  drivers/net/wireless/rtl88x2bu/hal/phydm/rtl8822b/halhwimg8822b_mac.o
  CC [M]  drivers/net/wireless/rtl88x2bu/hal/phydm/rtl8822b/halhwimg8822b_rf.o
  CC [M]  drivers/net/wireless/rtl88x2bu/hal/phydm/halrf/rtl8822b/halrf_8822b.o
  CC [M]  drivers/net/wireless/rtl88x2bu/hal/phydm/rtl8822b/phydm_hal_api8822b.o
  CC [M]  drivers/net/wireless/rtl88x2bu/hal/phydm/halrf/rtl8822b/halrf_iqk_8822b.o
  CC [M]  drivers/net/wireless/rtl88x2bu/hal/phydm/rtl8822b/phydm_regconfig8822b.o
  CC [M]  drivers/net/wireless/rtl88x2bu/hal/phydm/rtl8822b/phydm_rtl8822b.o
  CC [M]  drivers/net/wireless/rtl88x2bu/hal/phydm/txbf/haltxbf8822b.o
  CC [M]  drivers/net/wireless/rtl88x2bu/hal/btc/halbtc8822bwifionly.o
  CC [M]  drivers/net/wireless/rtl88x2bu/hal/btc/halbtc8822b1ant.o
  CC [M]  drivers/net/wireless/rtl88x2bu/hal/btc/halbtc8822b2ant.o
  CC [M]  drivers/net/wireless/rtl88x2bu/platform/platform_ops.o
  CC [M]  drivers/net/wireless/rtl88x2bu/core/rtw_mp.o
  LD [M]  drivers/net/wireless/rtl88x2bu/88x2bu.o
  AR      drivers/net/wireless/built-in.a
  AR      drivers/net/built-in.a
Makefile:1083: recipe for target 'drivers' failed
[ error ] ERROR in function compile_kernel [ compilation.sh:382 ]
[ error ] Kernel was not built [ @host ]
[ o.k. ] Process terminated

I suppose that there are more logs somewhere?

Edited by ww9rivers
I have been able to signup after this post.
Link to post
Share on other sites

6 hours ago, ww9rivers said:

I suppose that there are more logs somewhere?


We build images every day. How did you build images? Menu driven or only from command line? Which parameters have you used? Where did you build it?

Logs are in output/debug  ... compilation.log is the one we are looking for.

Link to post
Share on other sites

On 9/17/2019 at 1:23 AM, Igor said:

How did you build images? Menu driven or only from command line? Which parameters have you used? Where did you build it?

Logs are in output/debug  ... compilation.log is the one we are looking for.

Thank you very much for responding. I am new to the build process. I just cloned the "build" repository from github, ran "compile.sh", and followed the menus popped up from there.

 

My build environment is a Ubuntu 18.04.3 x86_64 VM with 12GB RAM.

 

The log is attached.

compilation.log

Link to post
Share on other sites

1 minute ago, Igor said:


Not possible to replicate. Remove cache and try again.

 

Thank you again. I will try to remove the cache and try again.

 

But it seems to have worked as I just ran "./compile.sh" without removing the cache:

Quote

[ o.k. ] Done building [ /home/weiwang/oss/armbian/build/output/images/Armbian_5.97_Bananapipro_Ubuntu_bionic_dev_5.3.0.img ]

 

Link to post
Share on other sites

Guest
This topic is now closed to further replies.
 Share

1 1