Forum Discussion

Altera_Forum's avatar
Altera_Forum
Icon for Honored Contributor rankHonored Contributor
15 years ago

Quartus Programmer "FACTORY" mode command

Hi All:

We have a new board that just came in with a Cyclone III LS device: EP3CLS150F484.

This is the first LS design we've done. We are having a cpu program the device though using the Fast Passive Parallel (FPP) method.

The configuration appears to complete successfully, but the design does not appear to function (To the point I can not even turn on an LED).

I've already found that we had to turn off bitfile compression in FPP mode.

However the question is: When I try to program the bitfile through JTAG, I'm getting the error message : Expected JTAG ID code 0x027030DD for device 1, but found JTAG ID code 0x00000000.

I've searched here and on the Altera Website, and they are basically saying the design security has the device locked and and need to send the "FACTORY" command to program the device through JTAG.

I get this response regardless if I've previously programmed the device at powerup or not. Which doesn't seem correct. (Should be unlocked at POR unless). However JTAG seems to identify the device correctly, and the JTAG tests work in the Quartus II programmer..

Is there a way to make the Quartus II programmer send the FACTORY command? I don't see any switches to make this happen in the GUI.

The SOF file was built using Quartus II 9.1 sp1, But I've tried both the 9.1 sp1 programmer, and the 10.1 sp1 programmer with the same results.

Thanks..

Pete

1 Reply

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    15 years ago

    Ok.. We were about to get it to work..

    The FPP configuration issue was we missed the following statement in the configuration doc:

    "Two DCLK falling edges are required after CONF_DONE goes high to begin the

    initialization of the device."

    This means the the device never entered user mode, so we were stuck in limbo.

    As far as programming with the JTAG cable, once the configuration completed successfully, I could then re-program the device with no issues. This sounds opposite of what I expected. But I don't have any security setup for this guy yet.. The only thing I can think of is the CPU is perhaps hold nCONFIG or nSTATUS in the wrong state, and it's blocking JTAG.. ?? Don't know..

    But we are running for now..

    Pete