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.
I have the same problem with BH USB 510 and TI XDS560. There are no any drivers for C6457.
Have You found drivers for c6457?
I have found Chip Support Package for c6457 in TI website but it is only for CCS 3.3. There is a C6457.xml file in CSP. I pluged it to my CCS4 but my emulator still not see processor.
Hi everyone,
The C6457 configuration files weren't ready in time to be included in CCS4.1.2, but check attached the preliminary version with complete peripheral descriptions. These files are yet untested in hardware, but some customers reported they are working fine. To install:
Close CCSv4 and unzip the contents of the attached ZIP file into C:\Program Files\Texas Instruments\ccsv4\common\targetdb. It will copy two xml files to the Devices directory and create a new subdirectory named \TCI6484_C6457 under Modules directory.
Delete the target cache files from the following places:
- file <targetdb.dat> typically located at C:\Program Files\Texas Instruments\ccsv4\common\targetdb
- file <targetdb.cache> typically located at C:\Program Files\Texas Instruments\ccsv4\DebugServer\bin\win32
- cache file located in the same directory as the target configuration file (.ccxml) - typically located in the project directory in the workspace
Additional details:
- If you are using the EVMC6457 from Lyrtech (http://www.lyrtech.com/Products/C6457%20evaluation%20module.php) and is connecting using the onboard emulator, you will have to get a CCSv4-compatible emulation device driver from them. The alternative is to have a compatible external emulator.
- From the information on their page it seems the devices in the EVM are physically connected in tandem if using the built-in emulator, therefore you will either have to add one more C6457 device when creating the target configuration (check the wiki page below for details) or configure SW5 properly (check the EVM6457 Technical Reference Guide below for details).
http://tiexpressdsp.com/index.php/Target_Configuration_-_Custom_Configurations
http://www.mylyrtech.com/docs/public/C6457%20EVM%20-%20Technical%20reference%20guide.pdf
Although the final release of these files will only be available in CCSv4.1.3, please feel free to give them a try and if you see any problems with it, ok?
Rafael
Hi Rafael,
Thank you for your help. I copied the files to the corresponding directories. And now, TCI6484 is on the target list. However, after the project is built, and tried to connect to the target, I got error message: Error initializing emulator. XDS510 USB has already identified the JTAG device. It seems to me that CCSv4 has some difficulty to connect to the emulator. Is there anything I need to do to solve the problem?
We are currently verifying our newly designed board based on c6457 using CCS v4.1.2 and SpectrumDigital XSD510 USB emulator.
Thanks.
More observation:
The complete error message after building the project:
Error connecting to the target:
Error 0x80000240/-1146
Fatal Error during: Initialization, OCS,
Invalid data was scanned by the emulation controller.
Verify the board setup to make sure the scan chain is properly
defined.
If the setup is correct, then RESET EMULATOR. This will disconnect each
target from the emulator. The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.
Anything error here? Thanks.
Using Rafael's attached file and the procedure, our c6457 environment is now working.
Thank you for the help.
Hi,
I'm facing the same problem and I tried to follow the steps. I ended up with the error logs that are already displayed on earlier messages. What did you do on your last step?
I'm using the Lyrtech C6457-EVM and a Blackhawk LAN/USB-Emulator which is connected via USB to the JTAG interface.
Does somebody have additional hints?
BR
Hi Rafael,
you've wrote that the bugfix would be available at CCSv4.1.3 but unfortunately we could not find the C6457 at the Target Configuration dialog. We have updated all available packages. Do you have any informations if the bugfix is really available at v4.1.3?
Thanks!