• Content Count

  • Joined

  • Last visited

About AdamZ

  • Rank

Recent Profile Visitors

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

  1. If anyone is having the same problem this is what I did to solve the problem: Set a static IP for the Ethernet ipv4 I incremented the packet identification for each sent packet; somehow the OS was not registering packets with the same ID Don't send 0000...00 data, as terminals see this as NULL and will not show as anything received
  2. Thanks for this, this is great stuff! I have a question, were you able to view the sent data through some other application other then wireshark? I am able to see all the packets through wireshark but am unable to view the packets through any other application or terminal.
  3. I haven't, thanks for your help I will look into it.
  4. Now that I have the JTAG working, yes the design (including sdk code) works fine when uploaded through SDK. However booting from USB still does not "activate" the SDK code. I also tried to combine the bit and elf files using "updatemem" in Vivado. I am doing this by associating the bootloop to microblaze in vivado, then merging the sdk generated elf file along with the memory mapping file and Vivado (hardware design) bit file.
  5. Problem solved. The USB eeprom reconfiguration did the trick. Previously I was not selecting the correct setting for the development board. MANY thanks for your invaluable help.
  6. Yes that does seem to be the problem. I am unable to test the JTAG interface as vivado/adept/sdk is not recognising the board. I had to resort to booting from a pendrive as a solution.
  7. I am trying to run a microblaze project on the Nexys video development board. However I am having cable driver issues and thus I am attempting to apply the design using a USB host (using a pendrive). I am able to apply a design with simple vivado hardware designs and that works fine. However I cannot get the sdk code for the microblaze to run. Currently I am using the download.bit file generated by the SDK. This bit file is generated using a bootloop. I am following this tutorial ( and so the design should not be the problem. My question is, should the design work if I use the download.bit file generated by SDK (by pressing program FPGA) or should I be using a different bit file to boot from a pendrive? Thanks.
  8. I am using USB driver version: I am Working with vivado 2015.4. I have also tried 2015.1 and 2016.1. The board does not show in adept. It shows no devices connected. Unchecking vcp made the com ports disappear. But vivado still gives the error and the board is still not seen in adept.
  9. It seems to be recognized fine. I have attached an image of the USB tree when board is plugged (left) and when unplugged (right). Thanks.
  10. I am trying to operate the Nexys Video development board using the vivado hardware manager on a windows 8 system. However I keep getting No hardware targets exist on the server error. Steps i have taken to remedy the situation include: Re-installed Vivado with included cable drivers Tried different versions of vivado Tried on a different PC Formatted PC and installed vivado Updated FTDI drivers Tried 3 different (new) USB cables Installed cable drivers manually The programming jumper is in the right position (jtag), the USB cable is plugged into the correct (prog) port and the board is powered. Can anyone suggest anything else I might try to fix the issue? Thanks.