Thorsten Posted December 6, 2016 Report Share Posted December 6, 2016 Hello, I have tried to connect my XILINX Platform Cable USB to the Papilio Duo. To avoid interfere of the FTDI Chip and the programmer I changed the PORTA of the FTDI to optically isolated mode as described here: https://www.youtube.com/watch?v=JqMJ_AdK1sw. The device ID can be read out as shown there, but programming is not possible with the impact tool o Xilinx. The papilio loader works, when the platform cable is disconnected. In the end of the video the FTDI chip is resetted by erasing the EPROM completely with FT_PROG. I have several questions: - since the programming is not possible from impact using Platform Cable and, in my case, programming is also not possible with playtag (http://forum.gadgetfactory.net/index.php?/topic/1896-papilio-board-support-in-xilinx-tools-like-impactchipscope-etc/) from inside impact, what are possible adjustments to program from impact and to use chipscope? I consider removing FTDI Chip completely using hot air soldering and using Platform Cable solely. - The video shows resetting the FTDI completely by erasing the EPROM. This erases the complete intital configuration. I lost my backup file. Can you please provide the initial configuration file for FTDIs FT_PROG to be able to use Papilio Loader again? Can you please make a hint in the video that a save backup of the fie is necessary? Why is erasing the eprom an option? In my case the board is not programmable anymore. A short - but complete and correct – introduction on how to use the papilio duo board successfully from within ISE Webbench in combination with impact and chipscope would be a great help. I guess for some more people than me. Thank you very much. Quote Link to comment Share on other sites More sharing options...
mkarlsson Posted December 6, 2016 Report Share Posted December 6, 2016 Hi Thorsten, The video you are referring to was done 2012, well before the Papilio Duo board was introduced and is only applicable to the Papilio One boards. Papilio One uses a different FTDI chip than Papilio Duo (FT2232D vs. FT2232H) and the instructions in the video only works for FT2232D. Also, the Papilio One boards are shipped with a blank EEPROM so the instruction at the end of the video to restore the board to the way it was shipped by erasing the EEPROM is correct, but only for Papilio One. If you want to use the Xilinx cable then the FTDI pins used for JTAG must not interfere with the Xilinx cable. In normal UART mode (i.e. when the EEPROM is blank or Port A is configured as UART in the EEPROM) then those pins are used for TXD. RXD, RTS and CTS and will mess up the Xilinx cable signals. The solution is the reprogram the FTDI EEPROM to a mode where the signals are not driven by the FTDI chip. For the FT2232D chip, one way to do that is to program Port A to Opto Isolate mode. However, on FT2232H this mode does not exists for Port A, only for Port B. An alternative is to program Port A to 245 FIFO mode instead, this works for both FT2232D and FT2232H. Hope this helps, Magnus Quote Link to comment Share on other sites More sharing options...
Jack Gassett Posted December 6, 2016 Report Share Posted December 6, 2016 Magnus, I just tried to bring up impact and connect to the DUO using the Digilent plugin and it looks like it no longer works with ISE 14.7. Can you confirm that you are seeing the same thing? They must have made changes to the plugin to prevent non Digilent boards from working... If the Digilent plugin still worked or could be made to work again that would be the best solution to using Impact and Chipscope with the Papilio DUO. Jack. Quote Link to comment Share on other sites More sharing options...
Jack Gassett Posted December 6, 2016 Report Share Posted December 6, 2016 Thorsten, Please let us know if what Magnus suggested, setting to 245 FIFO mode works for you. Like he says, you just need some mode that sets the JTAG lines to High-Z and prevents them from conflicting with the Xilinx programmer. If you make changes to the FT eeprom and need to restore the Papilio DUO to factory configuration then please download and run the test plan as described here: http://www.gadgetfactory.net/opmanuals/index.php?n=Main.PapilioDUO At this point I cannot really make a tutorial because we need to discover what is the best method for using Xilinx tools is now. There was no need up to now for a tutorial for the Papilio DUO because the Digilent plugin allowed you to just plug the Papilio DUO USB cable in and use it without any hassle with the Xilinx tools. But it looks like they recently changed the way the Digilent tool detects a compatible board which means we have to figure out a new way of doing things. I didn't realize it was an issue until you just brought it up... Jack. Quote Link to comment Share on other sites More sharing options...
mkarlsson Posted December 7, 2016 Report Share Posted December 7, 2016 1 hour ago, Jack Gassett said: Magnus, I just tried to bring up impact and connect to the DUO using the Digilent plugin and it looks like it no longer works with ISE 14.7. Can you confirm that you are seeing the same thing? They must have made changes to the plugin to prevent non Digilent boards from working... If the Digilent plugin still worked or could be made to work again that would be the best solution to using Impact and Chipscope with the Papilio DUO. Jack. Well, they wanted to plug that possibility so if you install Vivado then they also update the Digilent plugin You can however revert to the ISE version by going to (assuming 64-bit Windows) C:\Xilinx\14.7\ISE_DS\common\bin\nt64\digilent and run install_digilent.exe It will prompt if you want to "downgrade" the plugin. 1 Quote Link to comment Share on other sites More sharing options...
Jack Gassett Posted December 7, 2016 Report Share Posted December 7, 2016 Ahh, excellent, that indeed worked for me here. I ran the install_digilent.exe and now I'm back in business. When I plug my Papilio DUO into the USB port it is detected under Impact as an officially supported board. Thorsten, this is going to be the easiest way to accomplish what you want. Please download the test plans from here and run the Papilio_DUO_Verification/Run_GadgetBox_Testplan.bat which will restore your eeprom settings. Then run install_digilent.exe like Magnus says and you should be in business. Please let us know if it works for you. Thanks Magnus, as always your help is greatly appreciated. Jack. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.