skaat27

Members
  • Content Count

    11
  • Joined

  • Last visited

  1. skaat27

    RGB to DVI TMDS

    I figured out. I am missing the tmds.xml and tmds_rtl.xml under the if folder in the repo. Forgot to copy that. Thanks
  2. skaat27

    RGB to DVI TMDS

    @jpeyron I receive this error. If i expand the TMDS, i am able to make external with individual pins.
  3. skaat27

    RGB to DVI TMDS

    Hi, I am using the Digilent RGB to DVI IP to output to HDMI, i am using vivado 2016.2 and i havent been able to make the TMDS pin external. When i right click on the IP and choose make external it doesnt do anything. Any suggestions? I know that the IP documentation suggests vivado 2016.4 as tested, but if i use that then i have to use an YOCTO based petalinux which is another headache. I prefer to keep my petalinux dev environment simple. Edit 1 : i see this warning in the TCL console No interface ports matched 'get_bd_intf_ports TMDS' Regards, Karthik
  4. @jpeyron Hey, I am past that issue. Now when i try to boot via JTAG it says memory read error. when i try with SD card the kernel boot gets stuck at anufacturer ID: 3 OEM: 5344 Name: AALCD Tran Speed: 50000000 Rd Block Len: 512 SD version 3.0 High Capacity: Yes Capacity: 29.7 GiB Bus Width: 4-bit Erase Group Size: 512 Bytes reading image.ub 9028612 bytes read in 772 ms (11.2 MiB/s) ## Loading kernel from FIT Image at 10000000 ... Using 'conf@1' configuration Verifying Hash Integrity ... OK Trying 'kernel@0' kernel subimage Description: Linux Kernel Type: Kernel Image Compression: uncompressed Data Start: 0x100000d4 Data Size: 3828608 Bytes = 3.7 MiB Architecture: ARM OS: Linux Load Address: 0x00008000 Entry Point: 0x00008000 Hash algo: sha1 Hash value: 4bcad4b704b89428eb11f11e914aa200c6929ea7 Verifying Hash Integrity ... sha1+ OK ## Loading ramdisk from FIT Image at 10000000 ... Using 'conf@1' configuration Trying 'ramdisk@0' ramdisk subimage Description: ramdisk Type: RAMDisk Image Compression: uncompressed Data Start: 0x103aa678 Data Size: 5183900 Bytes = 4.9 MiB Architecture: ARM OS: Linux Load Address: unavailable Entry Point: unavailable Hash algo: sha1 Hash value: cf98121f7415ac2eb8023d0d0b330834fe3cd785 Verifying Hash Integrity ... sha1+ OK ## Loading fdt from FIT Image at 10000000 ... Using 'conf@1' configuration Trying 'fdt@0' fdt subimage Description: Flattened Device Tree blob Type: Flat Device Tree Compression: uncompressed Data Start: 0x103a6d48 Data Size: 14462 Bytes = 14.1 KiB Architecture: ARM Hash algo: sha1 Hash value: 25510021f3481108cde4be1925ff8aceadda1edd Verifying Hash Integrity ... sha1+ OK Booting using the fdt blob at 0x103a6d48 Loading Kernel Image ... OK Loading Ramdisk to 07b0e000, end 07fff99c ... OK Loading Device Tree to 07b07000, end 07b0d87d ... OK Starting kernel ... Uncompressing Linux... done, booting the kernel. [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.6.0-xilinx (skaat27@localhost.localdomain) (gcc v ersion 5.2.1 20151005 (Linaro GCC 5.2-2015.11-2) ) #1 SMP PREEMPT Fri Sep 15 11: 13:00 PDT 2017 [ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instructio n cache [ 0.000000] Machine model: peta2016.4 [ 0.000000] bootconsole [earlycon0] enabled [ 0.000000] cma: Reserved 16 MiB at 0x1f000000 [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] percpu: Embedded 12 pages/cpu @debcc000 s19776 r8192 d21184 u4915 2 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pag es: 130048 [ 0.000000] Kernel command line: console=ttyPS0,115200 earlyprintk [ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes) [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) [ 0.000000] Memory: 489456K/524288K available (5286K kernel code, 230K rwdata , 1848K rodata, 1024K init, 222K bss, 18448K reserved, 16384K cma-reserved, 0K h ighmem) [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB) [ 0.000000] vmalloc : 0xe0800000 - 0xff800000 ( 496 MB) [ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB) [ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) [ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB) [ 0.000000] .text : 0xc0008000 - 0xc07f793c (8127 kB) [ 0.000000] .init : 0xc0800000 - 0xc0900000 (1024 kB) [ 0.000000] .data : 0xc0900000 - 0xc0939ba0 ( 231 kB) [ 0.000000] .bss : 0xc0939ba0 - 0xc09713a4 ( 223 kB) [ 0.000000] Preemptible hierarchical RCU implementation. [ 0.000000] Build-time adjustment of leaf fanout to 32. [ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2. [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2 [ 0.000000] NR_IRQS:16 nr_irqs:16 16 [ 0.000000] efuse mapped to e0800000 [ 0.000000] slcr mapped to e0802000 [ 0.000000] L2C: platform modifies aux control register: 0x72360000 -> 0x7276 0000 [ 0.000000] L2C: DT/platform modifies aux control register: 0x72360000 -> 0x7 2760000 [ 0.000000] L2C-310 erratum 769419 enabled [ 0.000000] L2C-310 enabling early BRESP for Cortex-A9 [ 0.000000] L2C-310 full line of zeros enabled for Cortex-A9 [ 0.000000] L2C-310 ID prefetch enabled, offset 1 lines [ 0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled [ 0.000000] L2C-310 cache controller enabled, 8 ways, 512 kB [ 0.000000] L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001 [ 0.000000] zynq_clock_init: clkc starts at e0802100 [ 0.000000] Zynq clock init [ 0.000010] sched_clock: 64 bits at 325MHz, resolution 3ns, wraps every 43980 46511103ns [ 0.007907] clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycle s: 0x4af477f6aa, max_idle_ns: 440795207830 ns [ 0.018985] Switching to timer-based delay loop, resolution 3ns [ 0.025014] clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, ma x_idle_ns: 551318127 ns [ 0.034124] timer #0 at e080a000, irq=17 [ 0.038406] Console: colour dummy device 80x30 [ 0.042755] Calibrating delay loop (skipped), value calculated using timer fr equency.. 650.00 BogoMIPS (lpj=3250000) [ 0.053300] pid_max: default: 32768 minimum: 301 [ 0.058102] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.064649] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.072379] CPU: Testing write buffer coherency: ok [ 0.077332] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.082954] Setting up static identity map for 0x100000 - 0x100058 [ 0.188585] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 [ 0.188687] Brought up 2 CPUs [ 0.197273] SMP: Total of 2 processors activated (1300.00 BogoMIPS). [ 0.203689] CPU: All CPU(s) started in SVC mode. [ 0.209286] devtmpfs: initialized [ 0.215061] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 [ 0.222969] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, ma x_idle_ns: 19112604462750000 ns [ 0.233680] pinctrl core: initialized pinctrl subsystem [ 0.240071] NET: Registered protocol family 16 [ 0.246323] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.278221] cpuidle: using governor menu [ 0.289495] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers. [ 0.297387] hw-breakpoint: maximum watchpoint size is 4 bytes. [ 0.303452] zynq-ocm f800c000.ocmc: ZYNQ OCM pool: 256 KiB @ 0xe0880000 [ 0.310280] zynq-pinctrl 700.pinctrl: zynq pinctrl initialized After this it wouldnt continue. Do know how to proceed in both the cases??
  5. I have an arty z7 FPGA an am working on a petalinux project. I am able to config and build my project. But when i boot it it says bitstream is not compatible with the target. What does that mean? any suggestions? I exported the HDF from vivado and in project settings the target device is same as the one i am using.
  6. Hi, I am trying to rebuild the arty z7 petalinux BSP as per the instructions given by them here https://github.com/Digilent/petalinux-bsps/wiki/Quick-Start-Guide-for-Arty-Z7. But when I try the command $ petalinux-boot --jtag --prebuilt 3, I get an error saying [skaat27@localhost Digilent-Arty-Z7-Linux-BD-v2016.2]$ petalinux-boot --jtag --prebuilt 3 ERROR: No subsystem configuration file can be find in the project. sh: lsb_release: command not found webtalk failed:Invalid tool in the statistics file:petalinux-yocto! webtalk failed:Failed to get PetaLinux usage statistics! Anybody knows what the issue is? Karthik
  7. skaat27

    Arty Z7 HDMI IN issue

    @jpeyron I actually installed 2016.4 and Boooooom!!!! it worked. Anyways thanks for the idea, Ill try it out on 2017 and 2016.2. Also is it not real time relay? I mean i have the hdmi_in connected to my laptop and out to a monitor and i do not see the mouse moving. Or is it slow?
  8. skaat27

    Arty Z7 HDMI IN issue

    I use the 2016.2 version. Although the project was built using 2016.4. The HDMI_OUT project was also built using 201.4, but I was able to make it work on 2016.2
  9. skaat27

    Arty Z7 HDMI IN issue

    @jpeyron Okay. So I linked the proper repo. Even after that I am getting the place design error. Something to do with IOBUF???(Thats what I read in other forums).
  10. skaat27

    Arty Z7 HDMI IN issue

    @jpeyron Thanks for getting back. Apparently the vivado library folder was empty. So initially what i did was, i copied the repo from the hdmi_out project folder thinking that they use the same ips anyway (the ip status passed too). Now I have downloaded the repo for the hdmi_in and have linked it. Running the design now. Lets see if it works. Thanks a lot.
  11. skaat27

    Arty Z7 HDMI IN issue

    Hello Guys, I just received my Arty Z7 board and I was trying out the HDMI_IN design. I exactly followed the given instructions and I get this place_design error in vivado and "The Hardware Project referenced by this BSP (hdmi_in_bsp) was not found in this workspace." in sdk. I tried out the HDMI_OUT and it was working perfectly fine. I have attached the screenshots. Kindly help me out here. Note: I have seen similar questions on this forum, but none of those solutions helped me. So starting a new thread. TIA Regards, Karthik