Author Topic: USB interface use by NIOS apps  (Read 828 times)

patk

  • Active Member
  • *
  • Posts: 3
USB interface use by NIOS apps
« on: March 27, 2018, 05:29:15 PM »
Can the USB interface be used by regular apps or is it locked down for only the JTAG/arrow interface? If I use a separate JTAG cable can I get around this?

JH

  • Hero Member
  • *****
  • Posts: 641
Re: USB interface use by NIOS apps
« Reply #1 on: March 28, 2018, 03:13:03 PM »

patk

  • Active Member
  • *
  • Posts: 3
Re: USB interface use by NIOS apps
« Reply #2 on: May 11, 2018, 06:18:53 PM »
I found out as I expected that the FTDI driver on Windows only lets one app access the USB interface at a time. It looks like you can use either the JTAG or the COM on the interface but not both. Does the separate Arrow USB programmer 2 get me past this road block?

JH

  • Hero Member
  • *****
  • Posts: 641
Re: USB interface use by NIOS apps
« Reply #3 on: May 15, 2018, 08:42:21 AM »
Hi,

why do you think it doesn't work on Windows?
I've tried out on my Win10 with CYC1000 and internal loopback from BDBUS0 to BDBUS1. See attachment picture.

br
John

patk

  • Active Member
  • *
  • Posts: 3
Re: USB interface use by NIOS apps
« Reply #4 on: May 15, 2018, 04:49:36 PM »
I finally figured out the second port on the FTDI driver. When the driver first installs with the Arrow blaster only the JTAG com port is turned on and shows in the device/serial ports. I found out that I had to manually open up the FTDI driver and enable a second VCP. This may have been obvious to someone familiar with the FTDI driver and the Arrow blaster, but new to me and its not easily found or documented.

I did get the second com port to work with the MAX1000.

JH

  • Hero Member
  • *****
  • Posts: 641
Re: USB interface use by NIOS apps
« Reply #5 on: May 17, 2018, 02:48:18 PM »
Hi,

thank you very much for this information.

I don't know why it works on my place, maybe this was set correctly during my Xilinx JTAG driver installation.  We use second FTDI port for uart also with our JTAG programmer for Xilinx devices.

I've forward this notes to the Arrow Programmer driver/setup files developer, so I hope they can solve this issue during the next update.

br
John