• Content Count

  • Joined

  • Last visited

About bmentink

  • Rank
    Frequent Visitor

Recent Profile Visitors

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

  1. @JColvin You are still focusing too much on the cables. The only statement that really needs to be addressed, and is probably an understatement is: >Also, it is my understanding that the Cmod A7 (for reasons unknown to me) appears to also be more susceptible to this I agree, you do have a USB design issue, I suggest you give all existing users of this product a discount voucher for your new improved USB re-designed Cmod-A7 and like I have said before, if you did not hide that part of the circuit, which is crazy, us engineers/customers could help you out with that design .... for free. Cheers, B.
  2. @zygot This USB issue is also discussed at the end of this thread: Digilent have been very quick to blame the cables ... but like you, I have used my "faulty" cables on a number of other vendor boards without issue. Looks like Digilent have some re-design to do regarding the high speed USB area of the board. Let's hope version II is better .. There is even a similar issue on the Xilinx forum that could be this fault: @Bianca Your signature is very apt for this issue: Love it ..
  3. @JColvin > 9k and 300k iterations Not sure what that means: You did 300k programs on the one cable? Testing should be trying a number of cables, because doing multiple tests on the same cable is pointless. (After all, the definition of madness is to repeat the same thing expecting a different result) > I imagine this does not come up frequently during single use cases as much as one would think from a poorly constructed cable. For me, and at least one other on this forum, it errors out every time on a cable and we tried a bunch of cables. .... and I mean a bunch. I tried 7 different cables and they all did not program, it was only when I used a real short 6" cable that it worked. The other person refered to in a previous post had the same issue. I don't think you can deflect the problem onto just cables .. they all can't be bad, that's just not logical, especially given the fact that they work just fine doing high speed programming on other boards. I would suggest you have a USB impedance matching / track layout issue on the board. If the design was "open" us engineers could peer review it for you free of charge, but we can't. My 2c.
  4. @JColvin Noted: Many thanks. Although it does seem strange that those same "faulty" cables work perfectly fine on other development boards like Lattice ICE40 boards, and Papillio Duo/Pro boards of which I have many and none have this issue.. Cheers, Bernie
  5. bmentink

    Cmod-A7 power budget

    @jpeyron Thanks Jon, It begs the question though: Why on earth have you got a proprietary circuit in this day and age of open reference designs? There are multiple boards out there with published FTDI22xx based USB->JTAG interfaces .... I fail to see what benefit it is to you, or users by hiding that circuit ... maybe I am missing something .... The fact is, if the programming circuit is open or closed, it makes no difference to my decision to include this board as a module in my designs .... (Actually I am more likely to use it if I understand the board ..... competely) If I want to make my own Artix-7 based design ..... there are plenty of reference designs out there .. Anyway my 2c .... end of rant ...
  6. bmentink

    Cmod-A7 power budget

    @jpeyron Cool, thanks .. EDIT: That dropped it to 80mA from 130mA .. still can't figure out why so much greater than the Spartan-6 PapillioPro board .. PS: I eluded to this in my other thread, but will there be a complete schematic anytime soon? It would be good to see how the FTDI chip is wired ..
  7. @D@n I don't think that is the issue ... a powered hub or different port made no difference. Also I have the same issue on another PC. Also, I measured the 5V current while it was performing the erase/programming stage and it goes right down to 5ma, then back up to 130mA run current on reset which is no where near the USB 500mA allocation. A program after the 1st boot up of the PC always works ... subsequent ones don't .... if it was a power issue I would expect variable results on the 1st program as well .. I have tried multiple cables. Cheers, EDIT: I see another poster is having similar USB issues here: Like me, the poster had problems programming the board after the initial one time. Maybe there is a USB issue with the board? @jpeyron Any more feedback from the hardware engineer on this issue. UPDATE: I tried a USB cable just 6" long and that seems to work ok. Anything longer and I have issues. For me it is only a problem for Flashing, if I program the FPGA direct, that works fine will all cables. I would suggest that either the USB hardware on this board is marginal .... .. or there is some issue with the flashing code ..
  8. @jpeyron Ok, I used your files and it flashed the led.bin file ........ once ... the next time it error'd out with: It seems the HW server crashes after programing the device, it will only program again if I reboot the machine ... I also see the USB device fails enumeration after the one program .... which also maybe the issue .. I get in dmesg: I have to move the device onto another usb hub to get a good enumeration ... or reboot. EDIT: SUCCESS: After a reboot, my bin file also programs .... once ... I wonder if the hw server is crashing and tying up the USB port so it cannot program a second time .. oh, well at least I know the script works ... also, sometimes the programming just locks up, never returns, have to kill -9 the hw server process .. Many thanks for your help Jon
  9. bmentink

    Cmod-A7 power budget

    Hi Guys, Is there a way to measure the Artix-7 current directly on the board, or alternatively a way to disable the FT2232HQ device as it draws 100mA by itself. At the moment with 130mA drawn from 5V total board comsumption, that would place the Artix-7 + mem chip + osc + reg at 30mA which seems quite high. (My Papillio-pro board with a Spartan-6 was 80mA@5V (70mA used by a lower power FT2232, so that made it 10mA for the Spartan-6 etc... the Artix-7 is mean't to be 50% less power than the Spartan-6) ... they are both clocked at 80Mhz .. Weird ..
  10. @jpeyron Thanks, but as mentioned in a previous post, I had already used the SPIx4 interface option. I have posted on the xilinx forum as well, will update this post if I have any luck. I also said I was using @malexander's script .... it is his script that is not working! PS: I don't want to use the GUI intially because it plasteres files all over my nicely formated project tree .. I will just program the FPGA for now and will wait to program the flash until there is some support to do that. It just means I can't easily test my product as it is battery powered.
  11. @Natsu I disagree somewhat. Digilent should be able to support their boards, they made them , not Xilinx, and they should provide a howto for non-gui development on their boards, or at the very least provide differences from the xilinx boards so I can make changes to the xilinx scripts .... if I can find them. After all, the schematics are not even complete for the cmod-a7 board .... so am I supposed to guess the connections? >Digilent isn't obligated to support non-GUI usage of Vivado. Why not? By your argument they don't have to support GUI usage on Vivado either then. If Digilent want to support those of us that might want to do small/large production runs of a product that uses the cmod-a7 board, then we need to have non-GUI tools setup to program the board in production .... can't do that with a GUI. (I am making the assumption Digilent is interested in more than just single item purchases ..) If we have to go chase up the tools/scripts necessary to do that all over the net, that is not a good end user experience ..... I still don't have everything setup ..... after how many days?
  12. @jpeyron Hi any joy on this from your co-workers? Cheers, B.
  13. That did not work, I get: The ball is yours ...
  14. @jpeyron Hmm, thought the Flash was a 4-bit wide Micron so not sure why the BPI example .... are you saying I should use bpix4 ?? Maybe someone at Digilent would know what -interface setting I should use .. for their hardware ... (I don't know if you work there or not? ) I went of this document, that states to use SPIx4 ...
  15. @jpeyron Thanks Jon, Now I get the following error: