How can i compile and run one of the examples in C++ from the Ubuntu terminal?
The build instruction can be found here: github.com/.../
I thought I was wrong to take some steps but it isn't.
At this point the problem is of a completely different nature.
Using the command "dmesg" the camera is correctly identified.
Since I try to run the "first-frame" example script I get this series of errors:
After starting the example, if I reuse the "dmesg" command I get this:
I tried to start my script in python (it worked before these problems) and I get this:
I have the latest SD image for the Dragonboard downloaded, I am using Ubuntu 18.04 LTS.
Anyone have any suggestions?
P.s. I don't know if it is correct to continue on this topic or should I open a new one, in case I can do it without problems.
I noticed that the images are not visibile. The gallery can be found here:
Sorry for the delayed reply. This looks like and extension unit issue on this Ubuntu version. We'll try to reproduce the issue on our end.
You're using the latest SD card image which has Aditof SDK 1.5.0 installed. But at the same time you are using the latest master on your Ubuntu 18.04 LTS. On master we have added new code which requires changes to the SDK on the Dragonboard as well.
So, try to use the latest release instead (tag v1.5.0), on the Ubuntu.
ACozma DNechita, sorry for the delay but we are still with the same problem. we have tried to reinstall everything from 0 and the error persists, we have tried on different devices and different versions of Ubuntu (18.04 - 20.04) and nothing has changed so I don't think it depends on the Ubuntu version. We tried it on Windows and it seems to work there, but we need to run it on Linux devices. What could we do?
The problem seems to be related to the uvc driver that gets installed on your Ubuntu. Other people have been having similar issues with webcams - https://bugzilla.kernel.org/show_bug.cgi?id=111291
The solution seems to be installing the uvcdynctrl package. Can you please try that?
We tried installing the packages but we still have the same problems...
I don't know if it can be useful, but we noticed a difference in the devices between linaro and ubuntu (this both before and after installing the packages you suggested).When we activate the cam in linaro (where the system works) both media0 and media1 are present while in ubuntu only media0.
linaro@linaro-alip:/dev$ ls825000.etf mmcblk0p14 ptyp5 tty35 ttyp6826000.etr mmcblk0p15 ptyp6 tty36 ttyp7autofs mmcblk0p16 ptyp7 tty37 ttyp8block mmcblk0p17 ptyp8 tty38 ttyp9btrfs-control mmcblk0p18 ptyp9 tty39 ttypachar mmcblk0p19 ptypa tty4 ttypbconsole mmcblk0p2 ptypb tty40 ttypccpu_dma_latency mmcblk0p20 ptypc tty41 ttypdcuse mmcblk0p21 ptypd tty42 ttypedisk mmcblk0p22 ptype tty43 ttypfdri mmcblk0p23 ptypf tty44 urandomfb0 mmcblk0p24 random tty45 v4lfd mmcblk0p25 rfkill tty46 v4l-subdev0full mmcblk0p26 rpmsg_ctrl0 tty47 v4l-subdev1fuse mmcblk0p27 rpmsg_ctrl1 tty48 v4l-subdev10gpiochip0 mmcblk0p28 shm tty49 v4l-subdev2gpiochip1 mmcblk0p29 snd tty5 v4l-subdev3gpiochip2 mmcblk0p3 stderr tty50 v4l-subdev4gps_proxy_ch mmcblk0p4 stdin tty51 v4l-subdev5hugepages mmcblk0p5 stdout tty52 v4l-subdev6hwrng mmcblk0p6 tty tty53 v4l-subdev7i2c-0 mmcblk0p7 tty0 tty54 v4l-subdev8i2c-1 mmcblk0p8 tty1 tty55 v4l-subdev9i2c-3 mmcblk0p9 tty10 tty56 vcsinitctl mmcblk0rpmb tty11 tty57 vcs1input mmcblk1 tty12 tty58 vcs2kmem mmcblk1p1 tty13 tty59 vcs3kmsg mmcblk1p2 tty14 tty6 vcs4log mmcblk1p3 tty15 tty60 vcs5loop-control mmcblk1p4 tty16 tty61 vcs6loop0 mmcblk1p5 tty17 tty62 vcs7loop1 mmcblk1p6 tty18 tty63 vcsaloop2 mmcblk1p7 tty19 tty7 vcsa1loop3 mmcblk1p8 tty2 tty8 vcsa2loop4 mmcblk1p9 tty20 tty9 vcsa3loop5 mqueue tty21 tty96B0 vcsa4loop6 net tty22 tty96B1 vcsa5loop7 network_latency tty23 ttyGPS0 vcsa6media0 network_throughput tty24 ttyMSM0 vcsa7media1 null tty25 ttyMSM1 vfiomem port tty26 ttyS0 vga_arbitermemory_bandwidth ppp tty27 ttyS1 video0mmcblk0 psaux tty28 ttyS2 video1mmcblk0boot0 ptmx tty29 ttyS3 video2mmcblk0boot1 pts tty3 ttyp0 video3mmcblk0p1 ptyp0 tty30 ttyp1 video4mmcblk0p10 ptyp1 tty31 ttyp2 video5mmcblk0p11 ptyp2 tty32 ttyp3 video6mmcblk0p12 ptyp3 tty33 ttyp4 zerommcblk0p13 ptyp4 tty34 ttyp5
We have media0 and media1 in raspberry as well (and on raspberry, in local, it workes fine too).
Have you tried to build the Aditof SDK versio 1.5.0 on both target (camera board) and remote (PC with Ubuntu)? if so, can you post here the error messages that you receive on remote?
Sorry for delay answer. I have the SDK version 1.5.0 on the board, and i have installed the last version on my remote from this link: https://github.com/analogdevicesinc/aditof_sdk/tree/v1.5.0.
You can see the error that i receive here https://postimg.cc/gallery/GtDLGVG. Look at the pictures DMESG2, FirstFrame and PyScript.
I'm looking at picture DMESG2 and I can see that UVC control 4 (from extension unit 3) is being queried. This has been added after release v.1.5.0. Somehow you are using a newer version than 1.5.0.
when we bought the kit the version that was installed on the sd was v1.2.0 and everything worked fine, then I updated to the latest version and from that moment the issues appeared. If you please can send me a direct link to download the image with version 1.2.0 i think i can solve these problems and it could be a good occasion to catch the bug.I'm waiting for your answer.
We will provide a new image in a few days. This should solve the issues you are having.
We have added a new image. Could you please check it out?