--- Quote Start ---
I did not noticed If programming was successful, I found out after programming that the device did not configure ( via epcs64 and quartus 9.0).
But my problem is now that the normal boundary scan test passed before programming the device , did some ddr ram test with boundary sacn ,all ok.
Then I came to the conclusion that I was using the wrong programming file and used Quartus 9.0 to erase the epcs64 .
After this erase : I can not use the EP2S60 anymore, not with the USB blaster , not with the standard boaundary scan tools . I looks like the TAP controller is not working any more.
I thought it was board dependend but when I tried this on the second board with a EP2S60 : the same problem after the erase . TAP is not working !!
Am I the first with this problem ?
Tnx Hans
--- Quote End ---
Hi,
what kind of programming HW do you use (USB-Blaster?) ?
What happend when you choose "Auto detect" in the programmer ?
What HW is selected ?
Kind regards
GPK
Honored Contributor
