• Announcements

    • 1. Check power supply, check SD card and check other people experiences

      Power supply issues are one of the three biggest issues you'll face when starting with Single Board Computers (SBCs). SD card issues, whether fake or faulty, are another and issues resulting from poor board design is the other common issues you can encounter.   Power supply issues can be tricky. You might have a noisy power supply that works with one board because it has extra filtering, but won't work with another. Or you're using that cheap phone charger because your board has a microUSB connector, and it is either erratic, or doesn't start up, or even becomes the cause of some SD card issues.    Some tips to avoid the most common causes of problems reported:   Don't power via micro USB  - unless you have optimised your setup for low power requirements. Micro USB is great for mobile phones because they are simply charging a battery. It's bad for SBCs. Yes, it does work for a lot of people, but it also causes more problems and headaches over time than it is worth, unless you know exactly what you are doing. If you have a barrel jack power connector on your SBC, use it instead! If there is an option for powering via header connections, use that option!
        Don't use mobile phone chargers. They might be convenient and cheap, but this is because they are meant for charging phones, not powering your SBC which has particular power requirements.
        When you are evaluating a power supply, make sure you run some stress tests on your system to ensure that it will not cause issues down the path.   (Micro) SD card issues can be sneaky. They might appear right at the start causing strange boot and login errors, or they might cause problems over time. It is best to run a test on any new SD card you use, to ensure that it really is what it is, and to ensure that isn't faulty. Armbian provides you a simple way to do this   --   armbianmonitor -c /path/to/device/to/test  
    • 2. Make sure to collect and provide all necessary information

      We can only help if you provide quality information for us to work with. All stable images from the download section are tested, most stable upgrades are tested and we have tens of thousands of users. Even with regular and extensive testings, bugs sometimes do slip through. This is a voluntary support service and is unrelated to board makers, and is not obligated to provide you any answers. Repeated asking the same questions because you're not happy with the answers will result in you being ignored.

      Before you post a question, use the forum search as someone else might have already had the same problem and resolved it. And make sure you've read the Armbian documentation. If you still haven't found an answer, make sure you include the following in your post:   1. Logs when you can boot the board: armbianmonitor -u (paste URL to your forum post)   2. If your board does not boot, provide a log from serial console or at least make a picture, where it stops.   3. Describe the problem the best you can and provide all necessary info that we can reproduce the problem. We are not clairvoyant or mind readers. Please describe your setup as best as possible so we know what your operating environment is like.     We will not help in cases you are not using stable official Armbian builds, you have a problem with 3rd party hardware or reported problem would not be able to reproduced.

Armbian 5.25 on OrangePI PC: The gc2035 video camera doesn't work
10 10

80 posts in this topic

Recommended Posts

It turns out that after a few hours of running motion the captured image have a green tint (not like the above sample at 1600x1200, just a normal image with almost no red-blue components). Since I'm using the beta repository I though it was a problem of the kernel of the day, in fact updating and rebooting solved the issue.

It turns out that's enough to stop and start motion to get a normally coloured image.

Do you think it's an hardware or driver issue?

Share this post


Link to post
Share on other sites

So, if I'm reading things correctly, the problem is resolved with an older version? I can't test this out due to the fact that 5.2.0 is no longer available in the archive. Would anyone be so kind as to upload it elsewhere?

Share this post


Link to post
Share on other sites
On 01.09.2017 at 6:36 PM, garlic said:

I had solved this problem by my friend.

Run this script


sunxi-pio -m "PG11<1><0><1><1>"
modprobe gc2035
modprobe vfe_v4l2

The most import is that don't load gc2035 & vfe_v4l2 before. So you had better remove it in /etc/modules

This is my /etc/modules


#w1-sunxi
#w1-gpio
#w1-therm
#gc2035
#vfe_v4l2
#sunxi-cir
#v4l2loopback

you may see /dev/video0, but when you reboot, it lose again

I add my scrip to /etc/rc.local

this is my /etc/rc.local


sunxi-pio -m "PG11<1><0><1><1>"
modprobe gc2035
modprobe vfe_v4l2
sleep 5
modprobe v4l2loopback devices=2
/root/vidcopy/vidcopy -w 640 -h 480 -r 30 -i /dev/video0 -o /dev/video1 -f UYVY
sleep 5
/root/vidcopy/vidcopy -w 640 -h 480 -r 30 -i /dev/video1 -o /dev/video2 -f UYVY
exit 0

Thanks my friend: "虚耗"

It's not helped for me. Armbian 5.31 don't want to make camera active.

Why you work with PG11 pin? Maybe here is the difference beetween OPi PC and OPi One? It's likely PE11 in OPi One.

Anyway, /dev/video0 is not created.

 

Share this post


Link to post
Share on other sites

Anyone, please, help me to activate camera. It's not power up at all. What address line needs to make HIGH to turn it on??

I was add to rc.local:

sunxi-pio -m "PD14<1><default><default><1>"
sunxi-pio -m "PE14<1><default><default><1>"
sunxi-pio -m "PE15<1><default><default><0>"
sunxi-pio -m "PA17<1><default><default><1>"
sunxi-pio -m "PG11<1><0><1><1>"
modprobe gc2035
modprobe vfe_v4l2

But still have not /dev/video0, and have:

[    5.358154] [CSI_ERR][GC2035]sensor_read err at sensor_detect!
[    5.358170] [CSI_ERR][GC2035]chip found is not an target chip.
Camera connected right. Seller said it works under Armbian 5.20. What is the different in initialization??

Is anyone have script.bin of Armbian 5.20 for OPi One? I can't find old images. The older only 5.25.

And who can say what means <drive level> at sunxi-pio command? Is it different voltage levels (1.5,1.8,2.8,3.3)?

Thanks!

 

Share this post


Link to post
Share on other sites

AFAIK drive level refers to the current that a gpio configured as output can supply, unfortunately I don't remember where I read it and cannot find the documentation right now.

Share this post


Link to post
Share on other sites

I think it is driver problem, but I can misstake.

The thing is,  if I turn on lines below in rc.local, when driver starts it's turns off - no power, reset is low.

sunxi-pio -m "PG11<1><0><1><1>" #AVDD,DOVDD,DVDD
sunxi-pio -m "PE15<1><0><1><0>" #Power_Down
sunxi-pio -m "PE14<1><0><1><1>" #reset

 

Please, can anybody give me some advice to fix it?

Share this post


Link to post
Share on other sites
On 05.11.2017 at 5:04 PM, olivluca said:

AFAIK drive level refers to the current that a gpio configured as output can supply, unfortunately I don't remember where I read it and cannot find the documentation right now.

Thanks olivluca! But as I understand all service signals ok.

Two questions:

1. Can I see camera on a i2c bus when do i2cdetect - y 0/1?

2. What address on twi is right? I have =120 in my script.bin, but tryed to change on = 0x78. Or it is the same?

Thanks!

 

Share this post


Link to post
Share on other sites

Ok guys, I found the answer!

1. DO NOT touch /etc/modules. Leave it like that:

#w1-sunxi
#w1-gpio
#w1-therm
#gc2035
#vfe_v4l2
2.  rc.local:

modprobe gc2035 hres=0
modprobe vfe_v4l2

sunxi-pio -m "PG11<1><0><1><1>" #DOVDD
sunxi-pio -m "PE15<1><0><1><0>" #Power_Down
sunxi-pio -m "PE14<1><0><1><1>" #reset

 

And it works!

$fswebcam -r 1600x1200 -p YUV420P /home/dimak/qwe.jpg

I got image.

Thanks for all!!!

Dmitriy Voitenko likes this

Share this post


Link to post
Share on other sites
On 08.11.2017 at 12:17 PM, Dmitriy Voitenko said:

I try this method.

But /dev/video0 ... 

No such file or directory.

Armbian 5.31 LTS 3.3.113

After reconect fpc cable and reboot camera work.

Thank your.

Reboot is necessarily!

rc.local applyes parametrs at boot.

Share this post


Link to post
Share on other sites

Following this thread I got an Orange Pi Zero Plus 2 H3 with Armbian 5.35 jessie working.

 

My rc.local file looks like:

 

sunxi-pio -m "PA8<1><0><1><1>" #DOVDD
sunxi-pio -m "PE15<1><0><1><0>" #Power_Down
sunxi-pio -m "PE14<1><0><1><1>" #reset
  
modprobe gc2035
modprobe vfe_v4l2
sleep 5
modprobe v4l2loopback

 

Share this post


Link to post
Share on other sites

following the thread i've tried to find the way to make it work on opiLite. Armbian 5.35, no chance to get 5.20. I tried different GPIO's settings with no success.  Anybody succeed with this setup? Any knowlege on  pins?

Share this post


Link to post
Share on other sites
On 4.11.2017 at 12:43 PM, Dimak said:
  On 1.9.2017 at 5:36 PM, garlic said:

I had solved this problem by my friend.

Run this script


sunxi-pio -m "PG11<1><0><1><1>"
modprobe gc2035
modprobe vfe_v4l2

The most import is that don't load gc2035 & vfe_v4l2 before. So you had better remove it in /etc/modules

This is my /etc/modules


#w1-sunxi
#w1-gpio
#w1-therm
#gc2035
#vfe_v4l2
#sunxi-cir
#v4l2loopback

you may see /dev/video0, but when you reboot, it lose again

I add my scrip to /etc/rc.local

this is my /etc/rc.local


sunxi-pio -m "PG11<1><0><1><1>"
modprobe gc2035
modprobe vfe_v4l2
sleep 5
modprobe v4l2loopback devices=2
/root/vidcopy/vidcopy -w 640 -h 480 -r 30 -i /dev/video0 -o /dev/video1 -f UYVY
sleep 5
/root/vidcopy/vidcopy -w 640 -h 480 -r 30 -i /dev/video1 -o /dev/video2 -f UYVY
exit 0

Thanks my friend: "虚耗"

did you tried this one? according to schematics there shouldn't be a difference between OPi One and OPi PC Plus

Share this post


Link to post
Share on other sites

Thanks for the reply. im using OPI Lite as i've mentioned before. i've tried the scripts you point to, but i didnt menage to  

modprobe v4l2loopback devices=2

i cannot install the module. I stuck on make and make and install part of importing. But i thought v4l2loopback just forwards the dev/video0 signal to dev/video1 virtual path, but after running your script i still cannot find dev/Video0 device.

Share this post


Link to post
Share on other sites
3 hours ago, Konstantinos Brokalakis said:

I've tried all the proposed solutions from this topic

sure?

gc2035_motion.jpg.08ae1999edc98d798e177fa91dd5d56c.jpgOPi PC+ just weeks ago... 

Share this post


Link to post
Share on other sites

Thank you!!

 

20 hours ago, chwe said:

sure?

gc2035_motion.jpg.08ae1999edc98d798e177fa91dd5d56c.jpgOPi PC+ just weeks ago... 

 

I didn't connect the camera properly! :)

I had the my OPi One away in the basement connected on the network and today that I visited it again I realized what was happening.

Thanks for indicating the exact message from @informer15 that made it work, and made me realize that it should work!

Here is the output from my camera!

OPi One, Armbian 5.36, Kernel 3.4.113

thanks.png

Share this post


Link to post
Share on other sites

Hint: check the orientation of your cable!

 

Hi guys, I also came here after purchasing a cheap orangepione + camera, had the same error dmesg but all the GPIO magic did not work for me. Then I checked the camera connection and the cable end at the camera board was flipped - it came pre-assembled and I assumed it was right, but it wasn't. Google with image search and verify your cable connection. My cable had blue markers, they are facing up now (before it was flipped at the camera side). 

 

hope it helps.

 

 

 

 

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

10 10

  • Support the project

    We need your help to stay focused on the project.

    Choose the amount and currency you would like to donate in below.