Update GR8NET FPGA offline: Can't recognize silicon ID for device 1

Por karloch

Prophet (2067)

Imagen del karloch

04-03-2018, 16:24

Does someone have updated the FPGA core of the GR8NET using a USB Blaster? I am having trouble achieving it. After following the procedure as stated in the manual:

(JTAG cable connected to GR8NET and USB Blaster that it is connected to the PC USB ports, MSX powered on)
9. Start Altera Programmer application (fig. 11c) -> OK
(1) set up ByteBlaster-II or USB-Blaster device and choose it; -> OK
(2) select Active Serial mode -> OK
(3) Click Add Device, and select EPCS16 from the list; -> OK
(4) Clock Erase checkbox (only) -> OK
(5) Clock Start to start erasing entire EPCS16 chip -> ERROR: Can't recognize silicon ID for device 1

  • OS: Windows 10 1709 x64
  • Quartus 13.1
  • USB Blaster driver version:

Things I tried so far:

  • Quartus version 11.1, 13.0 SP1
  • Different JTAG cables
  • Different USB cables
  • Different USB ports

The GR8NET itself is working fine beyond these update problems.

Login sesión o register para postear comentarios

Por karloch

Prophet (2067)

Imagen del karloch

04-03-2018, 17:40

Tried also with Quartus 13.1 from Ubuntu GNU/Linux with the very same error message, so it leads me to think it is not OS or driver related...

Por Avkooi

Expert (76)

Imagen del Avkooi

04-03-2018, 22:23

That's strange... I updated my GR8NET (normal and stereo) with exactly the same hard- and software. The only thing I can think of is the connection to the GR8NET board. I get the same error message in the Quartus programmer if I break the connection to the board. All steps before don't 'look' at the board apparently...

Good luck!

Por Eugeny_Brychkov

Paragon (1107)

Imagen del Eugeny_Brychkov

04-03-2018, 23:05

We had such case with ericb59 some time ago. Whatever we were trying at his table programmer was saying this nonsense. Tried different cables, different blasters, two GR8NETs. No way. Then he sent me boards with occasion, I inserted them into my machine, connected using my byteblaster-II, started programmer and programmed BOTH without any issues.

So my answer - I do not know what is a problem! Maybe the problem is in software or driver, but it is not confirmed. Maybe issue is in parallel port driver. I am wrong here, USB is used Sad

Por karloch

Prophet (2067)

Imagen del karloch

24-04-2018, 22:39

The issue is finally solved! The solution was to use a more reliable USB Blaster v2 that worked like a charm following the steps provided in the GR8NET user guide.

Just for reference, I used this one I order through eBay. A bit more expensive but way more reliable that the ones sold for ~8 EUR.