Jump to content

Banana Pi Zero

CliffB

By CliffB
in Off-topic

 Share

Recommended Posts

@lex

@lex

Posted
Posted (edited)
  On 11/23/2017 at 6:10 AM, lvmc said:

I don't have the board yet, it's on the way. Nora Lee has kindly sent one, so i will try to help here with some hints.

Below are the hints to fix the errors (or warnings):

  

[    0.000000] cma: dma_declare_contiguous(266): ION reserve size should be 4m align! adjust size to 128MBytes

Try to increase ion_memsize: Change #define DEFAULT_SUNXI_ION_RESERVE_SIZE    96 to 128 

[    0.786562] mousedev: PS/2 mouse device common for all mice
[    0.786807] sunxikbd_init failed.
[    0.787376] ls_fetch_sysconfig_para: type err  device_used = -1073057264.
[    0.787388] =========script_get_err============
[    0.787397] ltr_init: ls_fetch_sysconfig_para err.

Change Kernel config to:

CONFIG_KEYBOARD_SUNXI=m

CONFIG_INPUT_LTR501ALS=m 

[    0.789001] sunxi_i2c_do_xfer()985 - [i2c0] incomplete xfer (status: 0x20, dev addr: 0x18)
[    0.789171] sunxi_i2c_do_xfer()985 - [i2c0] incomplete xfer (status: 0x20, dev addr: 0x19)
[    0.789338] sunxi_i2c_do_xfer()985 - [i2c0] incomplete xfer (status: 0x20, dev addr: 0x1a)
[    0.789503] sunxi_i2c_do_xfer()985 - [i2c0] incomplete xfer (status: 0x20, dev addr: 0x29)
[    0.789669] sunxi_i2c_do_xfer()985 - [i2c0] incomplete xfer (status: 0x20, dev addr: 0x2a)
[    0.789835] sunxi_i2c_do_xfer()985 - [i2c0] incomplete xfer (status: 0x20, dev addr: 0x2b)
[    0.790001] sunxi_i2c_do_xfer()985 - [i2c0] incomplete xfer (status: 0x20, dev addr: 0x4c)
[    0.790201] sunxi_i2c_do_xfer()985 - [i2c0] incomplete xfer (status: 0x20, dev addr: 0x4d)
[    0.790371] sunxi_i2c_do_xfer()985 - [i2c0] incomplete xfer (status: 0x20, dev addr: 0x4e)
[    0.790574] sunxi_i2c_do_xfer()985 - [i2c1] incomplete xfer (status: 0x20, dev addr: 0x18)
[    0.790771] sunxi_i2c_do_xfer()985 - [i2c1] incomplete xfer (status: 0x20, dev addr: 0x19)
[    0.790968] sunxi_i2c_do_xfer()985 - [i2c1] incomplete xfer (status: 0x20, dev addr: 0x1a)
[    0.791164] sunxi_i2c_do_xfer()985 - [i2c1] incomplete xfer (status: 0x20, dev addr: 0x29)
[    0.791360] sunxi_i2c_do_xfer()985 - [i2c1] incomplete xfer (status: 0x20, dev addr: 0x2a)
[    0.791555] sunxi_i2c_do_xfer()985 - [i2c1] incomplete xfer (status: 0x20, dev addr: 0x2b)
[    0.791751] sunxi_i2c_do_xfer()985 - [i2c1] incomplete xfer (status: 0x20, dev addr: 0x4c)
[    0.791948] sunxi_i2c_do_xfer()985 - [i2c1] incomplete xfer (status: 0x20, dev addr: 0x4d)
[    0.792144] sunxi_i2c_do_xfer()985 - [i2c1] incomplete xfer (status: 0x20, dev addr: 0x4e)

If i recall correctly, FE has this fixed on their kernel but there was some complain about breaking I2C compatibility with some device/protocol, or something like that, so i am not sure how to fix this.

Or just comment the line but you won't please the hw guys, so leave it as is. 

[    0.799377] no green_led, ignore it!
[    0.799386] no blue_led, ignore it!
[    0.799651] Registered led device: red_led
[    0.799668] no led_0, ignore it!
[    0.799676] no led_1, ignore it!
[    0.799683] no led_2, ignore it!
[    0.799690] no led_3, ignore it!
[    0.799697] no led_4, ignore it!
[    0.799704] no led_5, ignore it!
[    0.799711] no led_6, ignore it!
[    0.799718] no led_7, ignore it!

Change kernel config to:

CONFIG_SUNXI_LEDS=m
CONFIG_SUNXI_LEDS_COM=m
 

and load at boot time the sunxi-leds module or just chose one of the two and mark one as built in. (=y)

If you choose sunxi-leds-com, make sure you setup led_x in script.bin correctly.

  

[    0.800622] usbcore: registered new interface driver usbhid
[    0.800634] usbhid: USB HID core driver
[    0.801827] [DAUDIO]sunxi-daudio cannot find any using configuration for controllers, return directly!
[    0.802002] [I2S]snddaudio cannot find any using configuration for controllers, return directly!
[    0.802016] [DAUDIO0] driver not init,just return.

This is just a message telling you DAUDIO and I2S are not in use, it's harmless. 

[    0.811799] [HDMI] power vcc-hdmi-18
[    0.842954] ths_fetch_sysconfig_para: type err  device_used = 1.
[    0.844386] CPU Budget:corekeeper enabled
[    0.844639] CPU Budget:Register notifier
[    0.844654] CPU Budget:register Success


Try this in your FEX:

[ths_para]
ths_trend = 0
 


 

Expand  

 

BTW, banana pi zero and nano pi air makes a perfect board for using OV5640 sensor, so i would like to ask @Robert LabTeam if you are going to share your work on the OV5640 to be able to reach 60 fps or 90 fps, will you?

 

 

Edited by @lex
Tried to fix the text format!
1
Robert LabTeam

Robert LabTeam

Posted
Posted

Hi @lex,
To reach 60 FPS, or more, just changa VTS/HTS value. I created some tool (I launch it in DevC++) that shows what is the end FPS and some other parameters. Just play with the registers:
  

#define MCLK (20*1000*1000)  --> usually 24 MHz is used
#define MCLK_DIV 1

#define REG_3034  0x18
#define REG_3037  0x4
#define REG_3036 (4*20)
#define REG_3035 0x11
#define REG_3108 0x01

And VTS /HTS values here:
  

  hts_high = 0x07;    // 0x380c
  hts_low =0xf4;        // 0x380d

  vts_high = 0x07;    //0x380e,
  vts_low = 0xac;     //0x380f

I have also noticed that almost all drivers are not appropriate for OV5640 (it seems they wrtitten based on OV5642 software application note - for example max lines is different for both sensors: 1964/1968). I found this doc for OV5640 and fixed some things. You can also find there 90 FPS for VGA configuration:

https://wenku.baidu.com/view/6b48a191f90f76c661371afa.html

main.cpp

@lex

@lex

Posted
Posted
  On 11/24/2017 at 9:32 AM, Robert LabTeam said:

Hi @lex,
To reach 60 FPS, or more, just changa VTS/HTS value. I created some tool (I launch it in DevC++) that shows what is the end FPS and some other parameters. Just play with the registers:
  

#define MCLK (20*1000*1000)  --> usually 24 MHz is used
#define MCLK_DIV 1

#define REG_3034  0x18
#define REG_3037  0x4
#define REG_3036 (4*20)
#define REG_3035 0x11
#define REG_3108 0x01

And VTS /HTS values here:
  

  hts_high = 0x07;    // 0x380c
  hts_low =0xf4;        // 0x380d

  vts_high = 0x07;    //0x380e,
  vts_low = 0xac;     //0x380f

I have also noticed that almost all drivers are not appropriate for OV5640 (it seems they wrtitten based on OV5642 software application note - for example max lines is different for both sensors: 1964/1968). I found this doc for OV5640 and fixed some things. You can also find there 90 FPS for VGA configuration:

https://wenku.baidu.com/view/6b48a191f90f76c661371afa.html

main.cppFetching info...

Expand  

 

Hi @Robert LabTeam, thank you, good work.  Let's see how far we can go.

@lvmc, there is some work with CSI on mainline kernel for a different board but maybe this could help: https://groups.google.com/forum/#!topic/linux-sunxi/GQC-cXOB1U4[26-50]

 

lvmc

lvmc

Posted
Posted (edited)

booting with kernel 4.14.3-sunix

  Reveal hidden contents

 

Edited by Igor
spoiler
1
@lex

@lex

Posted
Posted

Hmm... Waiting for 4.4 on A64/H5...

 

I asked myself why did i rush to 4.14.y when:

"LTS is LTS. Greg Kroah-Hartman, the LTS maintainer, is committing to do [a six-year LTS]. Not because of Google or Android or Treble, but because everything is on LTS; it’s not on upstream." [itsfoss]

 

 

Larry Bank

Larry Bank

Posted
Posted

I just received my BPI-M2 Zero board and put it through its paces. Seems to perform similar to other H2+ boards. I added a Pin->GPIO map to my SPI_LCD and ArmbianIO projects (https://github.com/bitbank2).

 

Observations:

 

1) The SPI driver has that same odd issue where it occasionally spits out errors and runs a little slower than it should. 

2) It doesn't come with an IPX antenna, but you need to add one to use wifi unless you're sitting on top of your access point.

3) A small passive heat sink seems to be plenty when running the mainline (4.1x) kernel.

4) The default HDMI out resolution is 1920x1080p@60fps. This causes a "jumpy" display on my monitor. Switching to 1280x720 fixed it. I've seen this on other AllWinner H2/H3 boards, so it's probably something strange with the mainline kernel hdmi code.

 

Overall I'm happy with the board.  It would be nice to use the bluetooth. Does anyone know how to enable it?

 

1
ianmbetts

ianmbetts

Posted
Posted

I received a few of these boards recently, I think they are very good value, however to have subsequently discovered this thread is very disappointing.

The lack of formal Armbian support is a big negative, and whilst its clear there is some progress toward resolving the issues that are preventing that, I can not help but observe that the technical obstacles are somewhat obscured by dialogue that is uninteresting to Armbian and BPI users alike.

Please play the ball, not the man.

 

David Lannan

David Lannan

Posted
Posted

Wow. How childish. Having worked in software and electronics most of my working life, the self-entitled attitude here is plain childish.

The only thing I can say to those who think the world should revolve around you: Its a piece of hardware that will be redundant in 12 months, get over it. If you are not happy, change and move on. There is no point or value in being rude or over-bearing about an issue just because you think you are more knowing than others. Buy some humility and grow up. 

The discussion here just shows how much arrogance some people display without thinking about bigger pictures. You all live in a world of choice. So stop complaining, and choose something else.

 

chwe

chwe

Posted
Posted

Wow, what a groundbreaking contribution to this thread. Especially cause you pointed clearly out 

  • What's childish
  • the bigger picture
  • what you think what should change

[/sarcasm]

 

For your notes: I've this board at home,  I did some tests with it and finally lost the interest... I'm not a:

  On 1/28/2018 at 4:00 AM, David Lannan said:

Having worked in software and electronics most of my working life

Expand  

guy, so doing this stuff needs much more time for me than for a professional (and get false or not properly written stuff from professionals annoys me quite fast)... Even before I had the board at hand, we (as armbian community) pushed the vendor to:

  • Fix voltage regulation for CPU
  • Release schematics
  • Figured out that ETH is on CON4 (you could figure it out when reading the schematics carefully, but nowhere else)

So even if this board does not get 'official armbian support', the childish armbian community helped to improve the situation for this board. To my knowledge, neither the boardmaker nor someone else sent a PR with the needed patches for full or csc support for this board to armbians github... 

2
iwl

iwl

Posted
Posted
  On 11/16/2017 at 5:50 AM, Lion Wang said:

we have test image ,it can run success

 

image download link:

http://forum.banana-pi.org/t/bpi-m2-zero-test-image-2017-11-10-armbian-5-34-m2-zero-ubuntu-xenial-default-3-4-113-desktop-beta-build-by-bpi/4157

 

Expand  

 

I'm used to have just debian on my other Pis (Raspbian / Bananian)

 

How do I get close using above image?

 

Looks like somebody has modified Armbian for bpi zero allready for that image, so it's Armbian with Ubuntu on top?

 

Igor

Igor

Posted
Posted
  Quote

 or Armbian officially

Expand  


:wacko::angry: 

 

  Quote

Sadly, Armbian does not support headless config for wifi and since there is no onboard ethernet I have to do the initial setup using monitor, keyboard, and mouse.

Expand  


That actually works, but we obviously lack a properly placed how-to.

tkaiser

tkaiser

Posted
Posted
  On 9/12/2018 at 11:01 AM, Igor said:
  Quote

 or Armbian officially

Expand  


:wacko::angry: 

Expand  

 

Well, as expected.

 

  On 9/12/2018 at 11:01 AM, Igor said:

That actually works, but we obviously lack a properly placed how-to

Expand  

Talking about this https://github.com/armbian/build/blob/master/packages/bsp/common/usr/lib/armbian/armbian-firstrun-config?

 

If so this is as useless for average users as what I do all the time: let customize.sh throw an appropriate NM profile into /etc/NetworkManager/system-connections/ at image creation time. Average users would need a FAT partition so they can access it from Windows or macOS. But instead we should emphasize that on our officially supported boards w/o Ethernet a remote console sits on the MicroUSB port waiting for the user to login.

TonyMac32

TonyMac32

Posted
Posted
  On 9/12/2018 at 12:42 PM, tkaiser said:

But instead we should emphasize that on our officially supported boards w/o Ethernet a remote console sits on the MicroUSB port waiting for the user to login.

Expand  

Quite honestly my favorite feature when I was introduced to this project when hacking music players out of NanoPi Neo's...

chwe

chwe

Posted
Posted
  On 9/12/2018 at 12:42 PM, tkaiser said:

But instead we should emphasize that on our officially supported boards w/o Ethernet a remote console sits on the MicroUSB port waiting for the user to login.

Expand  

never tested but:

https://github.com/armbian/build/blob/8ea0b98845e9759266108e699d11aefd55cac882/config/boards/bananapim2zero.csc#L7 even on the CSC it should be there.. ;) 

Maybe we should point it out in the documentation e.g.

  Quote

How to login?

Login as root on console (HDMI / serial) or via SSH and use password 1234. You will be prompted to change this password at first login. You will then be asked to create a normal user account that is sudo enabled (beware of default QWERTY keyboard settings at this stage). Please use this tool, to find your board IP address.

Expand  

e.g.:

For the following boards:

- nanopineoplus2
- nanopineocore2
- nanopineo2
- nanopim3
- nanopifire3
- bananapim2plus
- orangepizeroplus
- bananapim2zero

Serial console can be accessed via USB with gserial (link to a little how-to to work with gserial). 
 

  On 2/9/2018 at 12:13 AM, iwl said:

Looks like somebody has modified Armbian for bpi zero allready for that image, so it's Armbian with Ubuntu on top?

Expand  

the board is csc supported, even with a patch which shouldn't harm other boards and make sure that your boards survives a kernel and/or u-boot update. https://github.com/armbian/build/blob/8ea0b98845e9759266108e699d11aefd55cac882/patch/u-boot/u-boot-sunxi/add-bananapi-bpi-zero.patch#L184

you've to build it on your own but besides that, the board should work and survive updates (mine is collecting dust since months due to no need for it at the moment, never did long run tests to keep an eye on durability).

 

 

yam1

yam1

Posted
Posted

CSC supported is just as great as any other boards. The only thing I could not get working is hdmi sound, wifi works fine, both spi channels work fine - but not as well as other boards (more 110 errors), perhaps hardware related? I use it as a laptop with my lap dock, and a bluetooth dongle for sound.

 

 

 

_9130751.JPG

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