This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Tool/software: Code Composer Studio
I have been working on the EVB to develop my c code.
Now I designed a new PCB with similar schematic (but no EEPROM for FT2232) and trying to download the firmware into PCB. Before that, I firstly configured FT2232D, channel A as JTAG for code download, channelB as COM port for data transfer when program is running.
I use Labview to realize the function below
FT_Open(0, &ftHandle) // 0 for channel A I guess FT_SetBitmode (ftHandle, 0xff, 0x2) // set IOs to output; set MPSSE mode FT_Close(ftHandle)
I got the correct return value. Now I am trying to download firmware in CCS, but failed with Error connecting to the target
I think I have successfully set the FT2232 with channel A as JTAG port and channelB as COM port. I am using the same CCS project code for this PCB as for controlSTICK EVB. I did the CCS downloading right after finishing setup FT2232 without power off or any other operation.
I am not sure if there is any step missing? Is the config process correct for FT2232, are values set in the above functions correct? Do I need to do any changes to the CCS project? Please help
Thanks,
Ning
Hi Ning,
Have you made any progress since your post?
===
Why did you remove the FT2232's EEPROM? The EEPROM gets read at FT2232 bootup to determine the VID/PID (and therefore impacts which driver Windows may use for interfacing). This information would then get lost once powered-down, if not do other things (I'm not an expert on this FT2232 chip when used in this way).
When you try to connect via CCS, what FTDI/XDS100 entries do you see in Device Manager?
Thank you,
Brett