theUltimateSource

Members
  • Content Count

    90
  • Joined

  • Last visited

Posts posted by theUltimateSource

  1. hello, I am interested in the following reference design:

    https://reference.digilentinc.com/learn/programmable-logic/tutorials/nexys-4-vga-test-pattern-with-mouse-overlay/start

    The design currently does not provide any sources:

    image.png.bc1c492f55ff7e970f9a476b064a264a.png

    Is this project abandoned? I believe it had not been updated since 2015. Is there a later version available (this one, perhaps, or on github?) I am interested in the USB host with mouse, which I intend to implement on the Zybo/Zybo-Z7. Do you provide the sources for this project?

    Is there a project you can recommend, There is also the BIST for the Zybo-Z7, maybe it contains relevant references?

    thank you

  2. I was concerned about compatibility issues. Since you are not using the correct board unexpected things can happen. Zybo and Zybo Z7-10 are very close to each other but there are differences. If you receive HDMI input signal on your monitor you are good.

    All monitor manufacturers, as well as the zybo, is following a standard for video signals. They have to to allow compatibility among all devices on the market. Sometimes though you can face problems because one of the device is not 100% compliant. 

    1. Digilent provides example projects in bare metal, use their HDMI output project to confirm operation. If your problem persists it is a LOT easier to deal with without linux
    2. you are providing a signal on HDMI. If you can, check the settings on the HDMI monitor and verify indicated resolution and framerate, preferable for both HDMI and VGA on the same device
    3. check your monitor's user manual, it provides information about which video formats are supported
    4. check your converter, is it an active or passive converter, is it HDMI->VGA or VGA->HDMI (it DOES matter!)
  3. 57 minutes ago, tekson said:

    i did everything as per the tutorial

    these instructions are for another board, the Zybo. It won't work on the Zybo-Z7 as they are not 100% compatible. On Step 4,

    Go to this link and select the last link. (it should be 533.4M size)

    the link is dead so which sources did you use? You'll need to make changes for the device tree, pin assignment. 

    See here for more information. 

  4. hello, 

    I just run the PCAM demo project and noticed the white balance is off. I can see the AWBs working but the image has a green cast. Has someone experienced similar results or can this be improved changing my lightening environment? 

     

    What would be the best approach to improve AWB? Does the sensor provide a calibration mechanism? I think I could load different colour matix'es to the sensor for different lighting scenarios. Is this a good solution?

    Alternatively I can implement my own algorithm and configure it with manual white balance. 

     

    What other factors could be involved in this behaviour, other than colour temperature? Judging from the colour (green) maybe gain/awb are not accounting for the bayer filter entirely? 

     

    thank you

  5. hello deppenkaiser,

    not sure what you are asking for... dtsi files are ALWAYS INCLUDED by a dts file. you can modify either one. You don't need to use dtsi files if you don't like to but you CAN decide to make your dts file generic and make your changes in dtsi's only.

     

    So, no they are not always generic unless you decide to do so. check your dts to see what files it depends on but generally dts and dtsi is all you need.

     

    You should also make use of generic drivers so you don't have a gazillion drivers for a gazillion devices. in this case you refer to all properties of such driver and only need to add the differences like device addresses.

  6. you can follow the tutorials in UG871, then add a new solution in HLS with the correct device (xc7z020clg400-1). I believe most of the labs can be completed even without any hardware. 

  7. 44 minutes ago, Newport_j said:

    I really wanted it on Linux, Ubuntu. I know Ubuntu Linux much better. ....

    So I have decided to install it on a bootable external hard drive. It will bypass my Windows 10 completely. My only concern is that I heard that there are some programs which when installed on anything but the c drive simply will not function. Is Vivado one of these? I also would install the Digilent board file sub directory. I have a Digilent Zybo-Z7-20 and I want to use it.

    I know that there way ways to fool an Linux operating system into believing what is not a c drive is actually a c drive.

    uh, my head is spinning. You'r mixing windows / linux a couple of times. I understood that you

    • have win10 OS installed on your native HDD/SSD, etc
    • want to install Vivado on Linux
    • want to install Vivado on an external hard drive

    In this case, why not install a linux distribution on your external hard drive as 2ndary boot OS instead of windows? I successfully run Vivado that way (ubuntu). Also, I have several Vivado versions installed on my external drive 2014.x - 2017.y with the Windows installer. Works like charm. The icons are placed in your start menu but you can't launch it before your drive is connected. 

    so install it on any drive letters you want in windows, or install it on a supported linux distro. 

    P.S: I have this configuration for quite a while now and never had any issues but never checked what would happen if your drive is mounted on a different partition (say, D:\ today, F:\ tomorrow). I'd expect it not to work but can't tell because never checked, never happend (yet). 

    P.P.S: Your virtual machine could also boot from a virtual C:\ drive located on your external hard drive. Also something I've done in the past. Anyway, have it your way :)

  8. one thing that catched my eye now is that I was indeed able to boot into root shell on Qemu. You can even see it on the terminal output I posted earlier, the 3rd line from the bottom sais:

    14 hours ago, theUltimateSource said:

    So that's a success, I guess.

    i2c timeout notice continues to show up even after boot and I could not make it shut up. That aside, it works.

    While booting from SD card this timeout never occurs.

    Anyway, I'll leave it by that.

    thank you

  9. hello,

    I builded the BSP for the Zybo. https://github.com/Digilent/Petalinux-Zybo/releases/download/v2017.2-1/Petalinux-Zybo-2017.2-1.bsp

    after building the kernel with default configuration I booted into qemu.

    However, boot never ends:

    Checking sstate mirror object availability: 100% |###############| Time: 0:02:39
    NOTE: Executing SetScene Tasks
    NOTE: Executing RunQueue Tasks
    NOTE: Tasks Summary: Attempted 2647 tasks of which 2620 didn't need to be rerun and all succeeded.
    INFO: Copying Images from deploy to images
    INFO: Creating images/linux directory
    [INFO] successfully built project

    [email protected]:~/Documents/lab2/Zybo$ ls
    build  components  config.project  images  pre-built  project-spec
    [email protected]:~/Documents/lab2/Zybo$ cd images/linux/
    [email protected]:~/Documents/lab2/Zybo/images/linux$ ls -la
    total 325260
    drwxrwxr-x 2 m m      4096 Fev  7 02:21 .
    drwxrwxr-x 3 m m      4096 Fev  7 02:21 ..
    -rw-r--r-- 1 m m  47909308 Fev  7 02:21 image.ub
    -rw-r--r-- 1 m m 129693184 Fev  7 02:21 rootfs.cpio
    -rw-r--r-- 1 m m  44075199 Fev  7 02:21 rootfs.cpio.gz
    -rw-r--r-- 1 m m  44149453 Fev  7 02:21 rootfs.tar.gz
    -rw-r--r-- 1 m m     24564 Fev  7 02:11 system.dtb
    -rw-r--r-- 1 m m   2188536 Fev  7 02:21 System.map.linux
    -rw-r--r-- 1 m m   2083850 Fev  7 02:02 system_wrapper.bit
    -rw-r--r-- 1 m m    420900 Fev  7 02:11 u-boot.bin
    -rw-r--r-- 1 m m   3246072 Fev  7 02:11 u-boot.elf
    -rw-r--r-- 1 m m  11467632 Fev  7 02:21 vmlinux
    -rw-r--r-- 1 m m  47595256 Fev  7 02:21 zImage
    -rw-r--r-- 1 m m    184884 Fev  7 02:09 zynq_fsbl.elf
    [email protected]:~/Documents/lab2/Zybo/images/linux$ cd .. cd..
    [email protected]:~/Documents/lab2/Zybo/images$ cd ..

    [email protected]:~/Documents/lab2/Zybo$ petalinux-boot --qemu --kernel
    INFO: The image provided is a zImage
    INFO: Set QEMU tftp to /home/m/Documents/lab2/Zybo/images/linux
    INFO: TCP PORT is free
    INFO: Starting arm QEMU
    INFO:  qemu-system-aarch64 -M arm-generic-fdt-plnx -machine linux=on   -serial /dev/null -serial mon:stdio -display none -kernel /home/m/Documents/lab2/Zybo/build/qemu_image.elf -gdb tcp::9000 -dtb /home/m/Documents/lab2/Zybo/images/linux/system.dtb  -net nic,vlan=1 -net user,vlan=1,tftp=/home/m/Documents/lab2/Zybo/images/linux -net nic -device loader,addr=0xf8000008,data=0xDF0D,data-len=4 -device loader,addr=0xf8000140,data=0x00500801,data-len=4 -device loader,addr=0xf800012c,data=0x1ed044d,data-len=4 -device loader,addr=0xf8000108,data=0x0001e008,data-len=4    
    The 'arm-generic-fdt-plnx' machine has been deprecated. Please use 'arm-generic-fdt-7series' instead.
    Warning: vlan 0 is not connected to host network
    Uncompressing Linux... done, booting the kernel.
    Booting Linux on physical CPU 0x0
    Linux version 4.9.0-xilinx-v2017.2 ([email protected]) (gcc version 6.2.1 20161016 (Linaro GCC 6.2-2016.11) ) #3 SMP PREEMPT Wed Feb 7 02:21:42 WET 2018
    CPU: ARMv7 Processor [410fc090] revision 0 (ARMv7), cr=10c5387d
    CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
    OF: fdt:Machine model: Zynq Zybo Development Board
    bootconsole [earlycon0] enabled
    cma: Reserved 64 MiB at 0x1c000000
    Memory policy: Data cache writealloc
    percpu: Embedded 14 pages/cpu @dbbad000 s25932 r8192 d23220 u57344
    Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
    Kernel command line: console=ttyPS0,115200 earlyprintk uio_pdrv_genirq.of_id=generic-uio
    PID hash table entries: 2048 (order: 1, 8192 bytes)
    Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
    Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
    Memory: 401172K/524288K available (6144K kernel code, 209K rwdata, 1488K rodata, 44032K init, 231K bss, 57580K reserved, 65536K cma-reserved, 0K highmem)
    Virtual kernel memory layout:
        vector  : 0xffff0000 - 0xffff1000   (   4 kB)
        fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
        vmalloc : 0xe0800000 - 0xff800000   ( 496 MB)
        lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)
        pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
        modules : 0xbf000000 - 0xbfe00000   (  14 MB)
          .text : 0xc0008000 - 0xc0700000   (7136 kB)
          .init : 0xc0900000 - 0xc3400000   (44032 kB)
          .data : 0xc3400000 - 0xc34344c0   ( 210 kB)
           .bss : 0xc34344c0 - 0xc346e258   ( 232 kB)
    Preemptible hierarchical RCU implementation.
        Build-time adjustment of leaf fanout to 32.
        RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
    RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
    NR_IRQS:16 nr_irqs:16 16
    efuse mapped to e0800000
    slcr mapped to e0802000
    L2C: platform modifies aux control register: 0x00000000 -> 0x30400000
    L2C: DT/platform modifies aux control register: 0x00000000 -> 0x30400000
    L2C-310 errata 588369 769419 enabled
    L2C-310 full line of zeros enabled for Cortex-A9
    L2C-310 cache controller enabled, 8 ways, 64 kB
    L2C-310: CACHE_ID 0x00000000, AUX_CTRL 0x00000000
    zynq_clock_init: clkc starts at e0802100
    Zynq clock init
    global-timer: non support for this cpu version.
    Failed to initialize '/amba/[email protected]': -38clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 551318127 ns
    sched_clock: 16 bits at 52kHz, resolution 18904ns, wraps every 619458570ns
    timer #0 at e080a000, irq=16
    Console: colour dummy device 80x30
    Calibrating delay loop... 2066.02 BogoMIPS (lpj=10330112)
    pid_max: default: 32768 minimum: 301
    Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
    Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
    CPU: Testing write buffer coherency: ok
    CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
    Setting up static identity map for 0x100000 - 0x100058
    CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
    Brought up 2 CPUs
    SMP: Total of 2 processors activated (4171.36 BogoMIPS).
    CPU: WARNING: CPU(s) started in wrong/inconsistent modes (primary CPU mode 0x13)
    CPU: This may indicate a broken bootloader or firmware.
    devtmpfs: initialized
    VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 0
    clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
    pinctrl core: initialized pinctrl subsystem
    NET: Registered protocol family 16
    DMA: preallocated 256 KiB pool for atomic coherent allocations
    cpuidle: using governor menu
    hw-breakpoint: debug architecture 0x4 unsupported.
    zynq-ocm f800c000.ocmc: can't request region for resource [mem 0x0000000c-0x0003ffff]
    zynq-ocm: probe of f800c000.ocmc failed with error -16
    zynq-pinctrl 700.pinctrl: zynq pinctrl initialized
    vgaarb: loaded
    SCSI subsystem initialized
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    media: Linux media interface: v0.10
    Linux video capture interface: v2.00
    pps_core: LinuxPPS API ver. 1 registered
    pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <[email protected]>
    PTP clock support registered
    EDAC MC: Ver: 3.0.0
    FPGA manager framework
    fpga-region fpga-full: FPGA Region probed
    Advanced Linux Sound Architecture Driver Initialized.
    clocksource: Switched to clocksource ttc_clocksource
    NET: Registered protocol family 2
    TCP established hash table entries: 4096 (order: 2, 16384 bytes)
    TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
    TCP: Hash tables configured (established 4096 bind 4096)
    UDP hash table entries: 256 (order: 1, 8192 bytes)
    UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
    NET: Registered protocol family 1
    RPC: Registered named UNIX socket transport module.
    RPC: Registered udp transport module.
    RPC: Registered tcp transport module.
    RPC: Registered tcp NFSv4.1 backchannel transport module.
    hw perfevents: enabled with armv7_cortex_a9 PMU driver, 1 counters available
    futex hash table entries: 512 (order: 3, 32768 bytes)
    workingset: timestamp_bits=30 max_order=17 bucket_order=0
    jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
    io scheduler noop registered
    io scheduler deadline registered
    io scheduler cfq registered (default)
    dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
    dma-pl330 f8003000.dmac:     DBUFF-256x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
    xilinx-vdma 43000000.dma: Xilinx AXI VDMA Engine Driver Probed!!
    e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 26, base_baud = 1488095) is a xuartps
    console [ttyPS0] enabled
    console [ttyPS0] enabled
    bootconsole [earlycon0] disabled
    bootconsole [earlycon0] disabled
    xdevcfg f8007000.devcfg: ioremap 0xf8007000 to e0869000
    [drm] Initialized
    [drm] load() is defered & will be called again
    brd: module loaded
    loop: module loaded
    m25p80 spi0.0: m25p80 (1024 Kbytes)
    4 ofpart partitions found on MTD device spi0.0
    Creating 4 MTD partitions on "spi0.0":
    0x000000000000-0x000000500000 : "boot"
    mtd: partition "boot" extends beyond the end of device "spi0.0" -- size truncated to 0x100000
    0x000000500000-0x000000520000 : "bootenv"
    mtd: partition "bootenv" is out of reach -- disabled
    0x000000520000-0x000000fa0000 : "kernel"
    mtd: partition "kernel" is out of reach -- disabled
    0x000000fa0000-0x000000100000 : "spare"
    mtd: partition "spare" is out of reach -- disabled
    libphy: Fixed MDIO Bus: probed
    CAN device driver interface
    libphy: MACB_mii_bus: probed
    macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 28 (52:54:00:12:34:56)
    Marvell 88E1149R e000b000.etherne:01: attached PHY driver [Marvell 88E1149R] (mii_bus:phy_addr=e000b000.etherne:01, irq=-1)
    e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
    e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
    ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    ehci-pci: EHCI PCI platform driver
    usbcore: registered new interface driver usb-storage
    e0002000.usb supply vbus not found, using dummy regulator
    ULPI transceiver vendor/product ID 0x0000/0x0000
    ULPI integrity check: failed!ci_hdrc ci_hdrc.0: unable to init phy: -19
    mousedev: PS/2 mouse device common for all mice
    i2c /dev entries driver
    cdns-i2c e0004000.i2c: 400 kHz mmio e0004000 irq 22
    cdns-i2c e0004000.i2c: timeout waiting on completion
    cdns-i2c e0005000.i2c: 400 kHz mmio e0005000 irq 23
    uvcvideo: Unable to create debugfs directory
    usbcore: registered new interface driver uvcvideo
    USB Video Class driver (1.1.1)
    EDAC MC: ECC not enabled
    Xilinx Zynq CpuIdle Driver started
    sdhci: Secure Digital Host Controller Interface driver
    sdhci: Copyright(c) Pierre Ossman
    sdhci-pltfm: SDHCI platform and OF driver helper
    mmc0: SDHCI controller on e0100000.sdhci [e0100000.sdhci] using DMA
    ledtrig-cpu: registered to indicate activity on CPUs
    usbcore: registered new interface driver usbhid
    usbhid: USB HID core driver
    NET: Registered protocol family 10
    sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
    NET: Registered protocol family 17
    can: controller area network core (rev 20120528 abi 9)
    NET: Registered protocol family 29
    can: raw protocol (rev 20120528)
    can: broadcast manager protocol (rev 20161123 t)
    can: netlink gateway (rev 20130117) max_hops=1
    zynq_pm_remap_ocm: OCM pool is not available
    zynq_pm_suspend_init: Unable to map OCM.
    Registering SWP/SWPB emulation handler
    [drm] No max horizontal width in DT, using default 1920
    [drm] No max vertical height in DT, using default 1080
    OF: graph: no port node found in /amba_pl/xilinx_drm
    [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
    [drm] No driver support for vblank timestamp query.
    cdns-i2c e0005000.i2c: timeout waiting on completion
    cdns-i2c e0005000.i2c: timeout waiting on completion
    cdns-i2c e0005000.i2c: timeout waiting on completion
    cdns-i2c e0005000.i2c: timeout waiting on completion
    cdns-i2c e0005000.i2c: timeout waiting on completion
    cdns-i2c e0005000.i2c: timeout waiting on completion
    cdns-i2c e0005000.i2c: timeout waiting on completion
    cdns-i2c e0005000.i2c: timeout waiting on completion
    cdns-i2c e0005000.i2c: timeout waiting on completion
    cdns-i2c e0005000.i2c: timeout waiting on completion

    xilinx-drm amba_pl:xilinx_drm: No connectors reported connected with modes
    [drm] Cannot find any crtc or sizes - going 1024x768
    Console: switching to colour frame buffer device 128x48
    xilinx-drm amba_pl:xilinx_drm: fb0:  frame buffer device
    [drm] Initialized xilinx_drm 1.0.0 20130509 on minor 0
    cdns-i2c e0005000.i2c: timeout waiting on completion
    cdns-i2c e0004000.i2c: timeout waiting on completion
    ssm2602 0-001a: Failed to issue reset: -110
    ssm2602 0-001a: ASoC: failed to probe component -110
    asoc-simple-card amba_pl:sound: ASoC: failed to instantiate card -110
    asoc-simple-card: probe of amba_pl:sound failed with error -110
    hctosys: unable to open rtc device (rtc0)
    of_cfs_init
    of_cfs_init: OK
    ALSA device list:
      No soundcards found.
    Warning: unable to open an initial console.
    Freeing unused kernel memory: 44032K (c0900000 - c3400000)
    cdns-i2c e0005000.i2c: timeout waiting on completion
    cdns-i2c e0005000.i2c: timeout waiting on completion
    cdns-i2c e0005000.i2c: timeout waiting on completion
    cdns-i2c e0005000.i2c: timeout waiting on completion
    cdns-i2c e0005000.i2c: timeout waiting on completion

    udevd[771]: starting version 3.2
    random: udevd: uninitialized urandom read (16 bytes read)
    random: udevd: uninitialized urandom read (16 bytes read)
    random: udevd: uninitialized urandom read (16 bytes read)
    udevd[772]: starting eudev-3.2
    cdns-i2c e0005000.i2c: timeout waiting on completion
    cdns-i2c e0005000.i2c: timeout waiting on completion
    hrtimer: interrupt took 1197345786 ns
    cdns-i2c e0005000.i2c: timeout waiting on completion
    random: udevd: uninitialized urandom read (16 bytes read)
    cdns-i2c e0005000.i2c: timeout waiting on completion
    cdns-i2c e0005000.i2c: timeout waiting on completion
    cdns-i2c e0005000.i2c: timeout waiting on completion
    cdns-i2c e0005000.i2c: timeout waiting on completion
    cdns-i2c e0005000.i2c: timeout waiting on completion
    cdns-i2c e0005000.i2c: timeout waiting on completion
    cdns-i2c e0005000.i2c: timeout waiting on completion
    cdns-i2c e0005000.i2c: timeout waiting on completion
    cdns-i2c e0005000.i2c: timeout waiting on completion
    cdns-i2c e0005000.i2c: timeout waiting on completion
    cdns-i2c e0005000.i2c: timeout waiting on completion

    random: dd: uninitialized urandom read (512 bytes read)
    IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
    cdns-i2c e0005000.i2c: timeout waiting on completion
    macb e000b000.ethernet eth0: link up (100/Full)
    IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    cdns-i2c e0005000.i2c: timeout waiting on completion
    cdns-i2c e0005000.i2c: timeout waiting on completion
    cdns-i2c e0005000.i2c: timeout waiting on completion
    cdns-i2c e0005000.i2c: timeout waiting on completion

    random: dropbearkey: uninitialized urandom read (32 bytes read)
    random: dropbearkey: uninitialized urandom read (32 bytes read)
    random: dropbearkey: uninitialized urandom read (32 bytes read)
    random: dropbear: uninitialized urandom read (32 bytes read)
    random: tcf-agent: uninitialized urandom read (16 bytes read)

    cdns-i2c e0005000.i2c: timeout waiting on completion
    cdns-i2c e0005000.i2c: timeout waiting on completion
    [email protected]:~# cdns-i2c e0005000.i2c: timeout waiting on completion
    cdns-i2c e0005000.i2c: timeout waiting on completion
    cdns-i2c e0005000.i2c: timeout waiting on completion

     

     

    The last line is repeated in an endless loop.

     

    I think there must be some problem with the I2C driver.

  10. hello @jpeyron,

    I am doing some tutorials on petalinux today. Since Zybo-Z720 version is not released yet, I wonder if I should use the Zybo BSP instead. Where are the differences as of today? I have both boards so using the Zybo version should save me some trouble?

    thank you