Forum Discussion

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

Issue FACTORY command

I'm using a Cyclone III LS 150 (780 pin), and programmed it using Active Serial. Now, I am altering the program stored in the Serial Device by programming through the JTAG port nad using the FPGA as the serial loader. However, I cannot reprogram the FPGA and Serial Device. Altera says I need to issue a FACTORY command via JTAG to solve this.

Can anyone give me instructions on how to do this via Quartus and the USB Blaster? Or is it even possible?

Thanks in advance

18 Replies

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

    Is it possible to issue JTAG commands via .tcl scripts?

    Or perhaps using the JTAG Chain Debugger?
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    14 years ago

    --- Quote Start ---

    Is it possible to issue JTAG commands via .tcl scripts?

    Or perhaps using the JTAG Chain Debugger?

    --- Quote End ---

    Use 'quartus_stp -s' from the command line, source the attached Tcl script, and then use jtag_open, and then read_idcode or read_usercode. If you have the IR value for FACTORY, you can create a new Tcl procedure to issue that command.

    Cheers,

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

    Thank you Dave! This could be just what I need.

    I followed your instructions, however, once I use jtag_open it says "The specified device is not found".
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    14 years ago

    The problem is, that all Quartus JTAG stack operations are starting with identifying the connected JTAG chain by an IDCODE read, which is apparently disabled with configured C III LS.

    In this situation, you can only access the device, if you know which devices are connected to the chain. That seems to be the reason why Altera suggests to use third party tools for the FACTORY command related operations.

    In my opinion, they designed this feature without much thinking. You can easily access the device, but not using Altera standard tools. The C III LS development board has a switch to disable the default configuration and unlock JTAG access, if I understand right.

    You still can use the USB Blaster with third party tools that support it or access JTAG through your own software.
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    14 years ago

    Ah, okay.

    Yes, this feature has been the source of much frustration.

    I wonder, if I can supply the IDCODE to the jtag_open command, perhaps that may let it work.
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    14 years ago

    Alright, it turns out I still had the JTAG Chain Debugger open, preventing it from accessing the JTAG Chain. That's why I got that error.

    So, jtag_open works now, and the read_idcode works (returns 0x000000, which is what I expect).

    I added this to the sourced .tcl file:

    proc send_factory {} {

    device_lock -timeout 10000

    # Shift-IR: = USERCODE = 281

    device_ir_shift -ir_value 281

    device_unlock

    return

    }

    281 is the hex value of FACTORY (10 1000 0001)

    However, this does not reset the FPGA it appears, the IDCODE is still all zero's and I am unable to reprogram.

    Perhaps I need to hold nCONFIG low...
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    14 years ago

    Okay, if anyone else has the issue in the future, you must hold nCONFIG low, issue the FACTORY command, and then release nCONFIG. once you close the jtag port, you can use Quartus to program as normal.

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

    Just F.Y.I

    If you are suing Cyclone III LS 150 devkit, the system controler(max2) will issue the factory_command right after power cycle.
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    14 years ago

    --- Quote Start ---

    Just F.Y.I

    If you are suing Cyclone III LS 150 devkit, the system controler(max2) will issue the factory_command right after power cycle.

    --- Quote End ---

    I wish it had been that easy! :)

    It was on a custom PCB, but at least I figured it out. With help!
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    14 years ago

    You must issue the FACTORY command before the device is configured as otherwise it will be ignored.

    This applies whether you are using Altera tools or third party tools.