Search the Community

Hi, Is it possible to use the onboard FT2232 on the papilio-one to debug other chips? How would we keep the Spartan in reset? Using it to debug other chips would be a problem because we can't daisy chain the new chip with the onbard Spartan, right? Has anyone tried this?

Hi There I had purchased a Papilio Pro a while ago, but didn't get time to play around with it. But recently when I tried to program it with the Quick Start bit file, the programmer couldn't recognize it. Suspecting that the FDTI EEPROM might have corrupted or similar, I switched from Ubuntu to Windows and used the FTDIProg utility to read. It looked non-empty, so I erased it and programmed which I thought is the default configuration. It still didn't help To investigate further, I programmed the FDTI with opto isolators activated and soldered in the JTAG pins. However the impact was unable to recognize the device. Not sure whats going on. Any help will be appreciated. The following is the diagnostic outputs from the programmer : xx:~ (master)> pap-check-status Executing /opt/GadgetFactory/papilio-loader/bin//opt/GadgetFactory/papilio-loader/bin/pap-check-status.... Using built-in device listInvalid chain position 0, position must be less than 0 (but not less than 0). ############################################# Programmer status ############################################ Using built-in device listInvalid chain position 0, position must be less than 0 (but not less than 0). Response incompatible with mask xxxx01ISC_Done = 0ISC_Enabled = 0House Cleaning = 0DONE = 0 ############################################# FPGA Status ############################################ Using built-in device listInvalid chain position 0, position must be less than 0 (but not less than 0). STAT RegisterID_ERROR = 0 IDCODE not validated.DONE = 0 Input from the DONE pin.INIT = 0 Input from the INIT pin.MODE = 000b Input from the MODE pins (M2:M0).GHIGH_B = 0 0 = asserted.GWE = 0 0 = all FFs and Block RAMs are write-disabled.GTS_CFG = 0 0 = all I/Os are 3-stated.IN_ERROR = 0 Legacy input error.DCI_MATCH = 0 DCI is matched.DCM_LOCK = 0 DCMs are locked.CRC_ERROR = 0 CRC error.cycleTCK in TEST_LOGIC_RESET ====================================================================================================================================== With exactly the same setup my Papilio500 works without any problem.The diagnostics produces the following output: 2004 pilakkat@pilakkat-W500:~ (master)> pap-check-status Executing /opt/GadgetFactory/papilio-loader/bin//opt/GadgetFactory/papilio-loader/bin/pap-check-status.... Using built-in device listJTAG chainpos: 0 Device IDCODE = 0x41c22093 Desc: XC3S500E ############################################# Programmer status ############################################ Using built-in device listJTAG chainpos: 0 Device IDCODE = 0x41c22093 Desc: XC3S500E ISC_Done = 1ISC_Enabled = 0House Cleaning = 1DONE = 1 ############################################# FPGA Status ############################################ Using built-in device listJTAG chainpos: 0 Device IDCODE = 0x41c22093 Desc: XC3S500E STAT RegisterID_ERROR = 0 IDCODE not validated.DONE = 1 Input from the DONE pin.INIT = 1 Input from the INIT pin.MODE = 001b Input from the MODE pins (M2:M0).GHIGH_B = 1 0 = asserted.GWE = 1 0 = all FFs and Block RAMs are write-disabled.GTS_CFG = 1 0 = all I/Os are 3-stated.IN_ERROR = 0 Legacy input error.DCI_MATCH = 1 DCI is matched.DCM_LOCK = 1 DCMs are locked.CRC_ERROR = 0 CRC error. More over I am able to connect the XILINX Platform Cable II and use it with impact!!! Regardsskp

Hi guys! I'm just wondering if there's any way to use the programmer on the Papilio to program other devices via JTAG? If there's any, how? I'd probably like to program some Xilinx CPLD, like the XC95144XL with it... I guess it should be possible somehow... Thank you for your answers. Richard, the crazy one.

In addition to my Papilio 500k, I have a separate Altera Cyclone dev board. When the USB blaster cable is plugged into my computer, I can no longer upload to the Papilio. Seems that the Papilio uploader is trying to communicate with the wrong JTAG or FTDI device. How can I force the Papilio uploader to talk only to the Papilio? Or is there something I am not considering at all? I tried moving around USB cables to see if that helps, but to no avail. Thanks, Scott