Topic: ZTEX 1.15y: High speed FPGA configuration failed ... (Read 1023 times)
Does it look like you got any broken welds on the board? check near the FPGA itself.
Hi ALL,
I'm running ztex 1.15y cluster.
Sometimes the boards disappears.
To get it back I pressing r in console and the board redetected and restarted.
But sometimes I get the messages like
"
Warning: Error uploading bitstream: FPGA configuration failed: DONE pin does not go high, possible USB transfer errors (INIT_B_HIST=222; 0 bytes got lost): Retrying it ...
Warning: Error uploading bitstream: FPGA configuration failed: DONE pin does not go high, possible USB transfer errors (INIT_B_HIST=222; 0 bytes got lost): Retrying it ...
Warning: High speed FPGA configuration failed, trying low speed mode:Error uploading bitstream: FPGA configuration failed: DONE pin does not go high, possible USB transfer errors (INIT_B_HIST=222; 0 bytes got lost): Trying low speed mode
"
Then I go to another console and reprogram that particular board by its id.
These messages stop coming to console and the board get redetected successfully or I need to press r again to refresh.
Q: does anybody know the easier way to get rid of this trouble?
With best regards,
fossil
I'm running ztex 1.15y cluster.
Sometimes the boards disappears.
To get it back I pressing r
But sometimes I get the messages like
"
Warning: Error uploading bitstream: FPGA configuration failed: DONE pin does not go high, possible USB transfer errors (INIT_B_HIST=222; 0 bytes got lost): Retrying it ...
Warning: Error uploading bitstream: FPGA configuration failed: DONE pin does not go high, possible USB transfer errors (INIT_B_HIST=222; 0 bytes got lost): Retrying it ...
Warning: High speed FPGA configuration failed, trying low speed mode:Error uploading bitstream: FPGA configuration failed: DONE pin does not go high, possible USB transfer errors (INIT_B_HIST=222; 0 bytes got lost): Trying low speed mode
"
Then I go to another console and reprogram that particular board by its id.
These messages stop coming to console and the board get redetected successfully or I need to press r
Q: does anybody know the easier way to get rid of this trouble?
With best regards,
fossil
Jump to: