--- Quote Start ---
hey so new issue for you
--- Quote End ---
Oh yippee ... :)
--- Quote Start ---
turns out that altera gave me the wrong .pof file
--- Quote End ---
Oops ... another X for closed-source.
--- Quote Start ---
i now have the right .pof and am able to program my byte blaster and get it recognized by the quartus programmer. yet when I try to use it to connect to another board, I hit auto detect and get the error “unable to scan device chain. On-board programming hardware is disabled. Any ideas?
--- Quote End ---
I don't have any USB-Blaster II hardware, so I'll relay what I have done with a USB-Blaster to debug things.
1. Start the Quartus JTAG debugger tool (Tools->JTAG Chain Debugger)
2. Select the "JTAG Chain Debugging" tab
3. Shift a 32-bit data instruction with a value of 0.
When the JTAG TAP goes through reset, it loads the IDCODE into the data register. The above procedure reads it out.
You can now probe the JTAG TCK and TMS signals to see if they toggle. You can probe the TDO signal to see if it toggles. If you change the value to 0x55555555, then you can probe the TDI signal to see if it toggles.
Try that to start with ...
Cheers,
Dave
Honored Contributor
