mikemcg

Members
  • Content Count

    7
  • Joined

  • Last visited

Everything posted by mikemcg

  1. Hi Jon, So I just installed libusb, diligent-adept-runtime and diligent-adept-utilities to use the djtgcfg enum command Found 1 device(s) Device: Zybo Product Name: Digilent Zybo User Name: Zybo Serial Number: 210279575077 I then went back to Vivado 2016.1 and it programmed fine so my issue seems to be solved. Looks like I should have installed the above earlier..... I'd like to mark this as answered and closed. Cheers Mike.
  2. Hi JColvin. Thanks - Much appreciated. Mike
  3. Hi dakefeng and D@n and thanks for the response. Good to know that there is nothing special about the cable, I'll stop worrying about that. I will try installing 2015.4 but I'm pretty sure that I did have it working with 2014.4 when I was using it back in 2014. Other than that I'm doing exactly as you suggested. JP5 is set for JTAG mode, I'm only trying to program via the SDK. I always plug the Zybo board in before I launch Vivado to make sure the board is there before the app loads and does any port checking. dmesg gives me the following usb 1-1: new high speed USB device using ehci_hcd and address 5 usb 1-1: configuration #1 chosen from 1 choice ftdi_sio 1-1:1.0: FTDI USB Serial Device converter detected drivers/usb/serial/ftdi_sio.c: Detected FT2232C usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB0 ftdi_sio 1-1:1.1: FTDI USB Serial Device converter detected drivers/usb/serial/ftdi_sio.c: Detected FT2232C usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB1 Maybe I've misunderstood how the dual jtag and serial port works with the zybo board. I thought that it presented two ports /dev/ttyusb0 and /dev/ttyusb1 with usb0 used for the JTAG and usb1 used for the serial communications. I wonder if I did something bad when I used the board in 2014 and corrupted the JTAG loader? Does anyone know if there is any kind of image available for the SD card that would allow me to flash the board back to factory defaults. As I mentioned the board will boot u-boot from the QSPI and provide messages on /dev/ttyUSB1 so I belive the serial port is working. I'm just struggling to get the JTAG port working. Thanks Mike.
  4. I'm trying to program my Zybo board. I have tried using Vivado 2014.4 under Centos 5.9 and Vivado Webpack 2016.2 on Ubuntu 14.04.2. I am using the Zybo walwart for power and both linux's are VM's(VMWARE Fusion) running on OS X El Capitan With Jumper J5 assigned to JTAG when the board is connected to linux both /dev/ttyUSB0 and /dev/ttyUSB1 show up when the board is connected via the USB micro A/B cable. When I use the SDK to program the FPGA it shows the following error message Program FPGA failed. Reason: Connection to board failed. I was using this board about a year ago and was able to load linux into the board at that time. Currently if I boot from the QSPI I see messages being sent to /dev/ttyUSB1, Currently I no longer have the USB cable that was supplied by digilent (so I'm not sure if there is anything special about the cable) so I have tried two different cables with the same results. Any suggestions on how I can program the Zybo board? Thanks Mike.
  5. Hi Sam, Thanks so much, that really helped. I was able to build it from scratch and boot into Ubuntu. I can get back to my own design.... BTW I'm not using VGA so the HDMI is fine for me. Anyway, much appreciated, Mike
  6. Thanks Josh. I tried that and it boots linaro very nicely (although I could only get it to work with HDMI and not VGA). My problem is that it's using pre-canned boot.bin, uImage and devicetree.dtb . For my project I'm designing AXI peripherals that will be resident in the FPGA so I need to generate my own kernel loaders etc. So far I have been able to get the filesystem contained in the ramImage loaded after following the tutorials but I have not been able to get the filesystem to load from the ext4 partition on the sdcard. I think I need to change more than the devicetree.dts bootargs above to pull this off but I haven't figured out (after more than 10 days of learning linux booting) what else I need to change over the zybo_base_system setups. For now I'd settle for just bringing up the reference design and just building/modifying the boot.bin, uImage and devicetree.dts files. I have been able to build all of them just I can't get the system to load from the ext4 partition. Any help on that would be appreciated. Best Mike.
  7. I'm a newbie to embedded development. I've worked through the linux hands on tutorial and have been successful at bringing up linux on the ramdisk as per the tutorial. What I really want is a ubuntu desktop working on the Zybo board. I have loaded the Linaro filesystem onto the sd card (as per the zed board examples) but still the Zybo insists on trying to load from a ramdisk. I have changed the chosen bootargs in the devicetree to bootargs = "console=ttyPS0,115200 root=/dev/mmcblk0p2 rw earlyprintk rootfstype=ext4 rootwait devtmpfs.mount=1" Is there something else I need to do in say the config file or uboot.elf to get it to use the filesystem from the ext4 partition rather than the ramfile? In using Vivado 2014.4 and SDK 2014.4. Thanks Mike.