Esti.A

Members
  • Content Count

    16
  • Joined

  • Last visited

About Esti.A

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Esti.A

    OpenCV and Pcam5-c

    yes, but there is no change... It is a zybo 020-ZYNQ 7020 the only thing I get now is this:
  2. Esti.A

    OpenCV and Pcam5-c

    Hi @bogdan.deac, Yes, I have everything connected perfectly. What is interesting is that the hdmi signal is active, because a message appears: Kind regards Esti
  3. Esti.A

    OpenCV and Pcam5-c

    Hi @bogdan.deac, 1. Yes, I did follow the steps defined in the link 2. I didn't get any error while the project creation but I get the following when running the .elf file after mounting the mmcblk0p1 all the video initializing is performed correctly: And I also checked the raw test creation : And if I try to run again the app (Demo.elf) it starts running but I get the following message:
  4. Esti.A

    OpenCV and Pcam5-c

    The thing is that actually I am not able to watch any image in the monitor, and the port tty1 is still opened. I have tried to check the drivers but no image is displayed, and when initializing the stream it gets blocked in the process.
  5. Esti.A

    Open CV error

    Hi everyone, I got this error after building the SDx project satisfactorily and I do not understand what is going from in teh code to abort the program execution. Has anybody faced this? Kind regards Esti Hi everyone
  6. Hi everyone, I was trying to integrate two demos in a single SDx project, which means I was using the demo of live I/O using the PCam5-c with the bilateral filter. The objective was to use the images obtained from the camera, process them by the bilateral filter and the display (by hdmi) and save them in the sd_card. To do so, all the files were imported and linked in the project and it actually did achieve to synthesis teh FPGA. The error came out while creating the bitstream for the FPGA. Note the errors are the followings: The project is defined as shown: The error log is attached as vivado.log Hope ypu can help me to solve this issue. vivado.log
  7. Esti.A

    OpenCV and Pcam5-c

    Hi @bogdan.deac, I followed your instructions but I found a error message while booting from the sd card the reVision platform that says the following: U-Boot 2017.01 (Aug 05 2018 - 22:17:14 -0700) Model: Zynq Zybo Z7 Development Board Board: Xilinx Zynq I2C: ready DRAM: ECC disabled 1 GiB MMC: sdhci@e0100000: 0 (SD) Using default environment In: serial Out: serial Err: serial Net: ZYNQ GEM: e000b000, phyaddr 1, interface rgmii-id SF: Detected s25fl128s_64k with page size 256 Bytes, erase size 64 KiB, total 16 MiB Warning: ethernet@e000b000 using MAC address from ROM eth0: ethernet@e000b000 U-BOOT for Zybo Z7 ethernet@e000b000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Hit any key to stop autoboot: 0 Device: sdhci@e0100000 Manufacturer ID: 1d OEM: 4144 Name: SD Tran Speed: 50000000 Rd Block Len: 512 SD version 3.0 High Capacity: Yes Capacity: 58.9 GiB Bus Width: 4-bit Erase Group Size: 512 Bytes reading image.ub 3910868 bytes read in 340 ms (11 MiB/s) ## Loading kernel from FIT Image at 10000000 ... Using 'conf@2' configuration Verifying Hash Integrity ... OK Trying 'kernel@0' kernel subimage Description: Linux Kernel Type: Kernel Image Compression: uncompressed Data Start: 0x100000d4 Data Size: 3878632 Bytes = 3.7 MiB Architecture: ARM OS: Linux Load Address: 0x00008000 Entry Point: 0x00008000 Hash algo: sha1 Hash value: 4b23816e227252b7549419997f26b3edbd525a7e Verifying Hash Integrity ... sha1+ OK ## Loading fdt from FIT Image at 10000000 ... Using 'conf@2' configuration Trying 'fdt@0' fdt subimage Description: Flattened Device Tree blob Type: Flat Device Tree Compression: uncompressed Data Start: 0x103b30b0 Data Size: 30941 Bytes = 30.2 KiB Architecture: ARM Hash algo: sha1 Hash value: 6bda90ed3c9361add0bd7bb38aeb560c25288661 Verifying Hash Integrity ... sha1+ OK Booting using the fdt blob at 0x103b30b0 Loading Kernel Image ... OK Loading Device Tree to 07ff5000, end 07fff8dc ... OK Starting kernel ... Uncompressing Linux... done, booting the kernel. Booting Linux on physical CPU 0x0 Linux version 4.9.0-xilinx-v2017.4 (digilent@ubuntu) (gcc version 6.2.1 20161016 (Linaro GCC 6.2-2016.11)) #1 SMP PREEMPT Mon Jul 9 19:13:02 PDT 2018 CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache OF: fdt: Machine model: Zynq Zybo Z7 Development Board bootconsole [earlycon0] enabled OF: graph: no port node found in /amba_pl/xilinx_drm EXT4-fs (mmcblk0p2): couldn't mount as ext3 due to feature incompatibilities INIT: version 2.88 booting Starting udev udev: Not using udev cache because of changes detected in the following files: udev: /proc/version /proc/cmdline /proc/devices udev: lib/udev/rules.d/* etc/udev/rules.d/* udev: The udev cache will be regenerated. To identify the detected changes, udev: compare the cached sysconf at /etc/udev/cache.data udev: against the current sysconf at /dev/shm/udev.cache Populating dev cache ALSA: Restoring mixer settings... No state is present for card ZyboZ7SoundCard Found hardware: "Zybo-Z7-Sound-C" "" "" "" "" Hardware is initialized using a generic method /usr/share/alsa/init/default:26: value write error: Input/output error /usr/share/alsa/init/default:26: value write error: Input/output error /usr/share/alsa/init/default:263: value write error: Input/output error /usr/share/alsa/init/default:263: value write error: Input/output error /usr/share/alsa/init/default:265: value write error: Input/output error No state is present for card ZyboZ7SoundCard hwclock: can't open '/dev/misc/rtc': No such file or directory Tue Jul 10 02:14:48 UTC 2018 hwclock: can't open '/dev/misc/rtc': No such file or directory Starting internet superserver: inetd. INIT: Entering runlevel: 5 Configuring network interfaces... udhcpc (v1.24.1) started Sending discover... Sending discover... Sending discover... No lease, forking to background done. Starting system message bus: dbus. Starting Dropbear SSH server: dropbear. hwclock: can't open '/dev/misc/rtc': No such file or directory Starting syslogd/klogd: done Starting tcf-agent: OK as you can see it is not finding this device and I dont know if this causes not to display any image in the hdmi. I am using filter2d demo, as is suggested for PCAM-5c set-up.
  8. Esti.A

    OpenCV and Pcam5-c

    Hi @bogdan.deac, 1.The version I am using is 2017.4. 2. I cloned from git directly from the link. I resolved the problem by manually defining the location of the bd. loading it again and introducing every line in the TCL console.
  9. Esti.A

    OpenCV and Pcam5-c

    Thank you for your great answer @bogdan.deac . I previously have tried with this project but I get the same problem as with Vivado 2018.2 which is that I am not able to write teh dsa file because its not able to get the properties of the design. So I dont know what is not working in there but I get the same result for both projects. This one, has been directly ran and loaded without any changes on it.
  10. Esti.A

    OpenCV and Pcam5-c

    Hi @jpeyron, My question is how sdx is helping me to create a proyect managing all the libraries of Open CV, because as far as I know I could use OpenCv without xfopenCv whic is integrated in SDx. Another thing that is not clear is how should the set-up done to get a connection with teh actual PCam and OpenCV. Thanks Esti
  11. Esti.A

    OpenCV and Pcam5-c

    Hi @jpeyron, And consequently the SDx version should match with the petalinux version. So how I am supossed to build projects in other vivado versions? cause I am getting quite a lot of error to configure the petalinux project. Can this be due to the bsp file definition? As I have read, I have to create a hdf file and try to match it withe the created project, so what is not making sense? Thanks Esti
  12. Esti.A

    OpenCV and Pcam5-c

    Thank you @jpeyron for your quick answer. I see that I should install linux to work with these softwares as most of them are only suported by Linux. Another thing I dont understand is if I can use Vivado 2018.2 for the hardware design but a SDx 2017.4 for the same proyect or not. Thank you very much Esti
  13. Esti.A

    OpenCV and Pcam5-c

    Hi everyone, I am working in teh demo that was created by Digilent to get images from teh Pcam5-c that is connected by a MIPI CSI-2 interface to teh zybo z7-020 board. In this case, I was wondering if I decide to do the processing of the image (edge detection, enhancement of light,...) I would need to use SDx. I have seen that there are plenty of solutions in OpenCv but I dont know how the hardware proyect and the SDx project can be linked. Note, in this initial design I have teh initiallization od teh camara and platform in a C++ application file that I dont know how if I should export to sdx file and how does this interact with the platform. Anothr queation I have is that for interacting with the openCv set-up do I must use Linux ? Kind regards Esti
  14. I achieved everything to work properlly. Thanks @jpeyron. Kind regards Esti
  15. Does anyone know if these MIPI_D_PHY_RX_ 0 and MIPI_CSI_2_RX_0 could directly be reclaced by the MIPI_CSI_2_RX of the last version avaiable at digilent for vivado 2018.2 ?