I was able to use my USB Blaster in JTAG mode to program my A10 board. Once it was successfully Programmed and Verified, I cycled power to had the A10 load its configuration. It did not load, and now my USB Blaster sill not ever recognize a device is present. The Blaster does recognize other identical boards, but not this one. I have 5 out of 20 boards that wont load there program, the rest are working fine. On the boards that are not working, the CONF_DONE done Pin stays at a Zero instead going to 1.8V, and the nSTATUS pin sits at ~1V instead of 1.8V. What could be wrong. Are the A10's Dead?
Unfortunately no I cannot program with a SOF. After a board is programmed the first time, it is no longer recognized by the JTAG programmer. I have attached screen shots of the JTAG signals on both a good and bad board.
I ran some more tests here is a summary of my results:
(Is there a way to get FPGA to not try and boot from mem device, so I can check SOF/JIC sequencing)
It could be a coincidence… did my last group of board’s not have the problem as the middle set. The boards were randomly chosen out of the box. The first two on this da, I programmed direct with JIC and they are now hung.
Is it possible that something could be wrong with the memory devices on the boards that were?
Fundamentally it would be nice to know if a corrupted memory device could make the FPGA no longer recognizable to JTAG or any other reason that I can check.
Does programming an fpga the first time change how it powers up and could prevent the JTAG from recognizing the device.
My next steps are to have the A10's and / or the Memory devices replaced. Do you think just replacing the memory device first might work?
To clarify, my problems are not with a Intel Development Kit. I have two of my own custom board designs board A and board B. I built 20 of each of these boards.
I would like to know:
Any help you can provide would be appreciated