jaypdx

Members
  • Content Count

    6
  • Joined

  • Last visited

About jaypdx

  • Rank
    Newbie

Recent Profile Visitors

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

  1. So I downloaded the FTDI uninstaller from https://www.ftdichip.com/Support/Utilities.htm#CDMUninstaller. I run it against the Arty (VID=0403, PID=6010) and uninstalled all the drivers. Then I rebooted and installed the latest FTDI drivers using https://www.ftdichip.com/Drivers/CDM/CDM21228_Setup.zip. I plug in the Arty and get correct-looking entries in the device manager: one COM port + USB Serial Converter A+B. I can connect to the board from the Vivado Hardware Manager but still cannot open the COM port in putty/teraterm. I'm going to email FTDI directly about this, but in the meantime I'm willing to try the EEPROM reprogramming if you can provide instructions on how to do that. Thanks, Jay
  2. I have two Arty S7 boards that are acting very strange. When I plug them in they show up in the device manager as a COM port (one board shows up as two COM ports for some reason), and I can open each board in the Vivado Hardware Manager, but more than half the time I can't open the COM port (using Putty, hyperterm, etc.). I've tried multiple computers, plugging directly into the computer USB port, various cables, etc., but I can't find a pattern or a reliable way to get them both working all the time. It's quite frustrating. Is this any sort of know issue with the Win10 driver or the FT2232 programming? I've seen another thread that talks about reprogramming the FTDI part - is that something I should try? I was corresponding with a Digilent engineer about this but he stopped responding... can anyone help? Thanks!
  3. I think my board got fried somehow too. It's an Arty-S7. It had been working great for a couple of months. Windows Device Manager still recognizes it with two ports but I can't connect to the second port (which is the UART port). I've tried it on two computers and neither will connect. Other Arty boards work fine, so it seems the FTDI on this board somehow got damaged. Not sure how it happened - I haven't done FT_PROG or anything - but if there's a way to fix it that would be great. Can you please PM me with instructions?
  4. You guys should put in some protection to fix that on future board revs. Also I can't find any warnings about this in the on-line reference manual.
  5. If I push the SRST or POR buttons I can re-program the FPGA and then reload the code via the SDK/debugger and everything works. I'd just like to understand why the VDMA won't initialize properly following a soft-boot by the debugger.... it seems like the _ChannelInit () and _ChannelReset() should be enough to get the peripheral working properly - I wouldn't have expected a full bitstream re-load to be necessary. Probably there's something that's not being fully re-initialized by the Xilinx SDK code. I tried reversing the order of _ChannelInit() and _ChannelReset() but I still get the error on a soft-boot. A couple of other things... I notice that the board stays powered if I remove the USB connection but leave HDMI Out connected (when my external monitor is powered on). HDMI is only spec'd up to 50mA so the Arty shouldn't be running off that. Also, I needed to modify the frame-buffer declaration in display_demo.c to avoid an occasional alignment-related error: u8 frameBuf[DISPLAY_NUM_FRAMES][DEMO_MAX_FRAME] __attribute__((aligned(16))); // need to specify alignment or we sometimes get "Unaligned address 0: 12050c without DRE" error during DMA config - Jay
  6. I'm having a problem with the Arty Z7 HDMI Out demo (https://reference.digilentinc.com/learn/programmable-logic/tutorials/arty-z7-hdmi-demo/start). I can build, start and run the demo and it works just fine after a power-cycle, but if I then re-load and re-start the SDK code (via the debugger) without re-loading the FPGA bitstream I get the following error and there is no output from the HDMI port: Read channel reset failed 11000 VDMA Configuration Initialization failed 1 (error is happening in XAxiVdma_CfgInitialize(), right after XAxiVdma_ChannelInit(RdChannel); and XAxiVdma_ChannelReset(RdChannel); If I re-load the bitstream before re-launching the code things work fine, but it doesn't seem like I should have to reload the bitstream every time. Any idea what's going on? I'm using Vivado 2018.3 and version 6.3 (rev 6) of the VDMA IP.