mikrocontroller.net

Forum: FPGA, VHDL & Co. Cyclone 2 USB-Blaster Absturz


Autor: Stefan Helmert (Firma: dm2sh) (stefan_helmert)
Datum:

Bewertung
0 lesenswert
nicht lesenswert
Hallo,

mir ist ein dummes Missgeschick passiert:
Ich habe in Verilog ein Modul geschrieben und im ebenfalls in Verilog 
verfassten Top-Level-Modul instanziiert. Dabei hieß ein eingang des 
Moduls clk_50 und im Top-Level wollte ich diesen Eingang mit mit 
CLOCK_50 verbinden. Dummerweise hatte ich clk_50 geschrieben, was im 
Top-Level nicht existierte, sondern nur im instanziierten Modul, aber 
trotzdem keinen Fehler brachte! Wie der Name schon andeutet handelt es 
sich dabei um ein Taktsignal.

Nun habe ich aber das compilierte Design auf mein Altera DE1 gespielt. 
Die Folge war, der Quartus 2 Programmer stürzte ab:
Error: Can't access JTAG chain
Error: Can't configure device. Expected JTAG ID code 0x020B30DD for device 1, but found JTAG ID code 0x00000000.
Error: Operation failed
Info: Ended Programmer operation at Sat Oct 17 15:46:36 2009
Info: Started Programmer operation at Sat Oct 17 15:46:55 2009
Info: Started Programmer operation at Sat Oct 17 15:47:29 2009
Error: Device chain in use
Error: Operation failed
Info: Ended Programmer operation at Sat Oct 17 15:47:39 2009
Error: Can't access JTAG chain
Info: Operation canceled
Info: Ended Programmer operation at Sat Oct 17 15:47:43 2009
Info: Started Programmer operation at Sat Oct 17 15:48:02 2009
Info: Configuring device index 1
Info: Device 1 contains JTAG ID code 0x020B30DD
Error: Can't access JTAG chain
Error: Can't configure device. Expected JTAG ID code 0x020B30DD for device 1, but found JTAG ID code 0xFFFFFFFF.
Error: Operation failed
Info: Ended Programmer operation at Sat Oct 17 15:48:04 2009
Info: Started Programmer operation at Sat Oct 17 15:48:06 2009
Error: JTAG Server can't access selected programming hardware
Error: Operation failed
Info: Ended Programmer operation at Sat Oct 17 15:48:06 2009
Info: Started Programmer operation at Sat Oct 17 15:48:08 2009
Error: JTAG Server can't access selected programming hardware
Error: Operation failed
Info: Ended Programmer operation at Sat Oct 17 15:48:08 2009
Info: Started Programmer operation at Sat Oct 17 15:48:12 2009
Error: JTAG Server can't access selected programming hardware
Error: Operation failed
Info: Ended Programmer operation at Sat Oct 17 15:48:12 2009
Info: Started Programmer operation at Sat Oct 17 15:48:12 2009
Error: JTAG Server can't access selected programming hardware
Error: Operation failed
Info: Ended Programmer operation at Sat Oct 17 15:48:12 2009
Info: Started Programmer operation at Sat Oct 17 15:48:17 2009
Error: Can't access JTAG chain
Error: Operation failed
Info: Ended Programmer operation at Sat Oct 17 15:48:17 2009
Info: Started Programmer operation at Sat Oct 17 15:48:51 2009
Info: Configuring device index 1
Info: Device 1 contains JTAG ID code 0x020B30DD
Error: Can't access JTAG chain
Error: Can't configure device. Expected JTAG ID code 0x020B30DD for device 1, but found JTAG ID code 0xFFFFFFFF.
Error: Operation failed
Info: Ended Programmer operation at Sat Oct 17 15:48:53 2009
Info: Started Full Compilation at Sat Oct 17 15:49:02 2009 Westeuropäische Normalzeit
Info: Ended Full Compilation at Sat Oct 17 15:49:32 2009 Westeuropäische Normalzeit
Info: Started Programmer operation at Sat Oct 17 15:49:43 2009
Error: JTAG Server can't access selected programming hardware
Error: Operation failed
Info: Ended Programmer operation at Sat Oct 17 15:49:43 2009
Info: Started Programmer operation at Sat Oct 17 15:50:05 2009
Error: JTAG Server can't access selected programming hardware
Error: Operation failed
Info: Ended Programmer operation at Sat Oct 17 15:50:05 2009
Info: Started Programmer operation at Sat Oct 17 15:50:20 2009
Error: JTAG Server can't access selected programming hardware
Error: Configuration failed
Info: Ended Programmer operation at Sat Oct 17 15:50:20 2009
Info: Started Programmer operation at Sat Oct 17 15:50:24 2009
Error: JTAG Server can't access selected programming hardware
Error: Configuration failed
Info: Ended Programmer operation at Sat Oct 17 15:50:24 2009
Info: Started Programmer operation at Sat Oct 17 15:51:41 2009
Error: Device chain in Chain Description File does not match physical device chain -- expected 2 device(s) but found 1 device(s).
Error: Operation failed
Info: Ended Programmer operation at Sat Oct 17 15:51:42 2009
Info: Started Programmer operation at Sat Oct 17 15:51:50 2009
Info: Configuring device index 1
Info: Device 1 contains JTAG ID code 0x020B30DD
Error: Can't access JTAG chain
Error: Can't configure device. Expected JTAG ID code 0x020B30DD for device 1, but found JTAG ID code 0x00000000.
Info: Operation canceled
Info: Ended Programmer operation at Sat Oct 17 15:53:21 2009
Info: Started Programmer operation at Sat Oct 17 15:53:43 2009
Info: Configuring device index 1
Info: Device 1 contains JTAG ID code 0x020B30DD
Error: Can't access JTAG chain
Error: Can't configure device. Expected JTAG ID code 0x020B30DD for device 1, but found JTAG ID code 0x00000000.
Info: Operation canceled
Info: Ended Programmer operation at Sat Oct 17 15:54:51 2009
Info: Started Programmer operation at Sat Oct 17 15:55:24 2009
Error: Unable to reset device before configuration
Error: Configuration failed
Info: Ended Programmer operation at Sat Oct 17 15:55:24 2009
Info: Started Programmer operation at Sat Oct 17 15:55:29 2009
Error: Unable to reset device before configuration
Error: Configuration failed
Info: Ended Programmer operation at Sat Oct 17 15:55:30 2009
Info: Started Programmer operation at Sat Oct 17 15:55:31 2009
Error: Unable to reset device before configuration
Error: Configuration failed
Info: Ended Programmer operation at Sat Oct 17 15:55:32 2009
Info: Started Programmer operation at Sat Oct 17 15:55:38 2009
Info: Configuring device index 1
Info: Device 1 contains JTAG ID code 0x020B30DD
Error: Can't access JTAG chain
Error: Can't configure device. Expected JTAG ID code 0x020B30DD for device 1, but found JTAG ID code 0xFFFFFFFF.
Info: Operation canceled
Info: Ended Programmer operation at Sat Oct 17 15:55:56 2009
Info: Started Programmer operation at Sat Oct 17 15:56:07 2009
Info: Configuring device index 1
Info: Device 1 contains JTAG ID code 0x020B30DD
Error: Can't access JTAG chain

Durch mehrmaliges Abziehen und Wiederanstecken des USB-Kabels sowie 
Korrektur des Source-Codes ließ sich das ganze noch retten, aber der 
Cyclone 2 wurde dabei schon richtig warm!

Mich wundert nur, dass der Quartus 2 Verilog-Compiler den Fehler nicht 
bemerkt hat! Ist das euch auch schon mal passiert? Wieso hat das der 
Compiler durchgehen lassen?

Antwort schreiben

Die Angabe einer E-Mail-Adresse ist freiwillig. Wenn Sie automatisch per E-Mail über Antworten auf Ihren Beitrag informiert werden möchten, melden Sie sich bitte an.

Wichtige Regeln - erst lesen, dann posten!

  • Groß- und Kleinschreibung verwenden
  • Längeren Sourcecode nicht im Text einfügen, sondern als Dateianhang

Formatierung (mehr Informationen...)

  • [c]C-Code[/c]
  • [avrasm]AVR-Assembler-Code[/avrasm]
  • [vhdl]VHDL-Code[/vhdl]
  • [code]Code in anderen Sprachen, ASCII-Zeichnungen[/code]
  • [math]Formel in LaTeX-Syntax[/math]
  • [[Titel]] - Link zu Artikel
  • Verweis auf anderen Beitrag einfügen: Rechtsklick auf Beitragstitel,
    "Adresse kopieren", und in den Text einfügen




Bild automatisch verkleinern, falls nötig
Bitte das JPG-Format nur für Fotos und Scans verwenden!
Zeichnungen und Screenshots im PNG- oder
GIF-Format hochladen. Siehe Bildformate.
Hinweis: der ursprüngliche Beitrag ist mehr als 6 Monate alt.
Bitte hier nur auf die ursprüngliche Frage antworten,
für neue Fragen einen neuen Beitrag erstellen.

Mit dem Abschicken bestätigst du, die Nutzungsbedingungen anzuerkennen.