Hardware: logi-bone (R1.0, 2014.03.18), logi-cam (7670, R1.1,2014.03.31), BeagleboneBlack (A6)
Software: pre-built logi image (logibone_r1_ubuntu_v4.img), recent logi-apps (about 2 days ago, git clone -b logibone
https://github.com/fpga-logi/logi-apps.git)
After the following command and output,
ubuntu@arm:~/logi-apps/imgproc_app$ sudo ./make_demo.sh
What is your sensor version (7670, 7725, ...)7670
0+1 records in
0+1 records out
341536 bytes (342 kB) copied, 0.959428 s, 356 kB/s
DEMO NOW RUNNING ***************************************************************************
* Demo will now start :
* Open a browser and connect to
http://<your beaglebone ip address>:8080/stream.html
* Use switches on the logibone to switch between video processing modes (normal, gaussian, sobel, harris)
* full documentation on this app:
http://valentfx.com/wiki/index.php?title=LOGI_-_Image_Processing_-_Project* Press ctrl-c to end demo
END INSTRUCTIONS ***************************************************************************
MJPG Streamer Version.: 2.0
o: www-folder-path...: ./www/
o: HTTP TCP port.....: 8080
o: username:password.: disabled
o: commands..........: enabled
I tried
http://my_logi_bone_ip:8080/stream.html, I got the text (with color) of that web page, but the video area is blank, while the browser continuously refreshing the page. I tried Firefox and IE. Same result. As a test, I tried the Blink LED demo and it works.
I am new to this. Any help would be appreciated. Thanks.
Comments
Thanks for the replies. The len cover is off. I tried the entire length of len screw. Same result. The video area in my case is not black, it is blank (white, no color).
Only two LEDs on logi-bone are on (steady) --- the PWR LED near the JTAG and the DONE LED between the two PMOD connectors. My connection matches the logi-cam quick start guide photos. Maybe I did something wrong.
Thanks.
1. Yes, confirmed -- the LED0 and LED1 stay off, doing nothing.
2. After doing the following,
ubuntu@arm:~/logi-apps/imgproc_app$ ls
logibone_camera_R1_7670.bit make_demo.sh README.TXT
ubuntu@arm:~/logi-apps/imgproc_app$ sudo logi_loader logibone_camera_R1_7670.bit
[sudo] password for ubuntu:
0+1 records in
0+1 records out
341536 bytes (342 kB) copied, 0.977835 s, 349 kB/s
ubuntu@arm:~/logi-apps/imgproc_app$
when I tried the web page, it says it's unable to connect server at my_logi_bone_ip:8080. LED0 and LED1 stay off. By the way , I also checked the port 8080 with netstat -na, which indicates port 8080 is not listening. This is similar to using Ctrl+C to terminate the sudo ./make_demo.sh --- I think the FPGA is configured, but Ctrl+C might have stopped the web server/service on port 8080/tcp. (sorry I got sidetracked here a little).
3. I tested this again,
ubuntu@arm:~/logi-apps/blink_led_app$ sudo ./make_demo.sh
0+1 records in
0+1 records out
340703 bytes (341 kB) copied, 0.965638 s, 353 kB/s
Logipi leds should now be blinking !
The LED0 and LED1 are blinking.
Thanks.
LED1 in this application is connected to the camera vertical synchronization signal, so as @mjones stated it should blink at 30Hz. LED0 is connected to the reset signal so it should be off all the time. No VSYNC from the camera can mean that your camera is damaged, or that its not correctly plugged in in the adapter. Could you send a picture of your setup, with close-up of the camera module at support@valentfx.com (or embed in this forum page) ? In the mean time, can you make sure that the wishbone app is working correctly ?
Regards,
Jonathan Piat
(this conversation continued on support@valentfx.com)
today is built a new debian image (Jessie), did the test of running the img_proc application and it did not work on first try ... but worked on the second. If you experience the same problem, you can try the following. In the imgproc_app folder, delete the .done file (this is to avoid running the apt-get command every time the demo is run) and re-run the make_demo.sh script as sudo. If the led blink on the board (at 30hz, so you may just notify that led0 is dim), the hardware is good. The software though can failt to communicate with the board or fail to synchronize with the camera. To make sure that the communication with the logiboen is working, try the wishbone app (LED0 should be slowly fading). If the wishbone app fails, it can mean that the you did not initialize the logibone eeprom cape ID (see on valentfx/wiki).
If the software fails to synchronize with the camera (after trying multiple times), you can speed up the beaglebone-black CPU by issuing the following command :
sudo cpufreq-set --governor performance
This will force the CPU to run at 1Ghz and could help the software keep-up with the pixel flow.
Thank you, Jonathan, Mike and Ribbox for all your time, advice/tip and help.
sorry for the mistake in the wiki. Every new board need to have its eeprom configured and you may have to re-configure the eeprom as we release new images. Thanks for the feedback, the documentation was updated.
Regards,
Jonathan Piat
Did I miss a step or something?
Thanks for the help in advance
Only make_demo.sh and logibone_camera_R1_7670.bit
Did you saiy that you tried the demo with camera disconnected and the led0 would remain on ? The led should be blinking fast only with camera connected. Did you try to run the wishbone demo ? The wishbone demo will help make sure that the communication with the board is working fine. If the wishbone demo is not work in this means that the logibone was not detected properly.
Regards,
Jonathan piat
I m loading new image to the SD and will go through the process again
Hi Mike & Jonathan,
I will try to provide all the info to help you guys help me.
loaded a new image to the SD card : logibone_r1_ubuntu_v4.img
cd deploy
sudo ./init_eeprom.sh
sudo reboot
cd Logi_apps
cd imagproc_app
git pull
sudo logi_loader logilogibone_camera_R1_7670.bit
./make_demo.sh (LED1 always OFF/ runing make_demo.sh make LED0 blink once but go solid after that -stays ON)
no image in MJPG-Streamer
ls -la ( see .done and removed it using rm -f .done)
ran ./make_demo.sh
no images in Steamer
power down the beagle bone/logi
removed the camera board
power on the board
both LEDs (the one beside Done and LED0 are OFF)
removed the .done
ran ./make_demo.sh LED0 and the LED beside Done turn ON and stays ON. LED1 always OFF
***********************************
cd wishbone
sudo logi_loader logibone_wishbone_r1.bit
LED0 turned OFF. LED beside Done ON
sudo ./make_demo.sh (LED0 turn ON and start diming OFF untill OFF and turn ON ------ continuously. LED1 OFF)
I noticed in your last post, you did "cd Logi-apps". In my case "Logi-apps" came with the logi ubuntu image. To get the updated apps, I did "git clone -b logibone https://github.com/fpga-logi/logi-apps.git", then I have a "logi-apps" directory (note the lower case L). I then use the "logi-apps", not "Logi-apps".
I don't know if this applies to your case or not.
I am not an expert on this. Just want to share my experience, in case it is helpful.
Mike are u talking about the camera itself (OV7670) or the Camera - logi board ?
If we determine that it is the camera itself I can go ahead and buy a new one cause I have to start working on a project for a hackaton demo here at John Deere.
I tried what lze suggested ( Mike I know you mentioned that the changes only includes minor changes from upper case L to lower case l ) but I couldnt go to sleep without trying it. so after (git cone -b......) I endup with logi-apps and folowing the same steps as before I endup wthe the following output, it may not be relevent to my current problem:
after I entered 7670
0+1 records in
0+1 records out
0% [Connecting to ports.ubuntu.com]
.
.
.
Err http://ports.ubuntu.com saucy InRelease
Err http://ports.ubuntu.com saucy Release.gpg
could not resolve 'port.ubuntu.com'
Err http://ports.ubuntu.com saucy-updates Release.gpg
could not resolve 'port.ubuntu.com'
Readng package lists ... Done
W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/saucy/InRelease
W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/saucy-updates/InRelease
W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/saucy/InRelease.gpg could not resolve 'ports.ubuntu.com'
W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/saucy/InRelease could not resolve 'ports.ubuntu.com'
W: Some index files failed to download. They have been ignored, or old ones used instead
Reading packages lists ... Done
Building depenceny tree
Reading state information ... Done
gcc is already the newest version
libjpeg8-dev is already the newest version
make is already the newest version
v41-utils is already the newest version
0 ugrades, 0 newly intalled, 0 to remove and 28 not upgraded
In : failed to create symbolic link '/usr/include/linux/videodev.h':File exists
make:Nothing to be done for 'all'
DEMO NOW RUNNING*********************************************************************************8
.
.
.
.
.
o: commands.............:enabled
No harm in trying..... It looks like you may need to run "sudo apt-get update" to remove the previous errors. But, it does not look like they affect your problem.
Unless it is a connection problem, then it sounds like to me that it is probably the ov7670 camera module. There is not much that can go wrong with the logi-cam board. Jonathan will evaluate whether is any further code that you can try to run to debug.
In the mean time I have sent you message to verify your current shipping address to arrange getting you a new module.
Cheers,
Mike
I have attached another bit file to this post, can you try runing it just to see if you get the blinking led (it won't stream data to the CPU). Copy the bitfile to your beaglebone and then run sudo logi_loader <bitfilename> to load the provided bitfile. If the LED0 is blinking, this means that the camera module is fine. You can also delete the logi-apps repository from your filesystem and fetch it again :
git clone -b logibone https://github.com/fpga-logi/logi-apps.git
It appears that sometime the bitfile is corrupted and thus won't work as exepcted.
Regards,
Jonathan Piat