• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 56 subscribers
  • Views 803 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

C6457 Lyrtech EVM - need CCSv4 emulation driver

TommyG
Genius 13045 points
Other Parts Discussed in Thread: TMS320C6457

I am trying to migrate C6457 Lyrtech EVM project from CCS3.3 (which is the default from Lyrtech) to CCSv4.  I haven't been able to find emulation driver for the C6457 EVM in my CCSv4 installation.  I saw in another post that I should go to Lyrtech to get the new emulation driver.  I went through their Help Desk and got this response:

Thank you for contacting us.

there is not driver available for CCS 4.0. We do not support CCS 4.0. TI has decided to distribute CCS 4.0 with the EVM instead CCS 3.3 without discussed with us. So, you must contact TI for supporting this issue.

We can offer support only with CSS 3.3.

Since they are not going to support CCSv4, where do I go to get the driver?  The EVM uses embedded Blackhawk emulation.  I tried to use BH USB 510 driver that is available in CCSv4.1 which I setup like the CCS3.3 configuration, but it doesn't work.

Help!

  • 0
    TI__Guru**** 162305 points

    What error message do you get?  My understanding is that if you use the BH 510USB connection it will work if you have a full CCS license.

    CCSv4.1.x doesn't have the device file for C6457.  I see it in my CCSv4.2.1 install.  You may want to update to that.  You are not going to be able to connect to the device unless all the ICEPick settings are correct (that info is in the device file).

     

    John

  • 0 in reply to JohnS
    TI__Genius 13045 points

    John,

    I'll have to get you the error message when I get back to the office Friday.

    I used the BH USB 510 driver and copied all the settings from my CCS3.3 setup.  I am attaching my .ccxml file for you to look at.  Do you see anything wrong?

    I'll also try upgrading CCSv4 to latest version to see if results are any different.

    Thanks.

    C6457 Lyrtech EVM.ccxml
  • 0 in reply to TommyG
    TI__Guru**** 162305 points

    Tommy,

    The ICEPick settings look ok.  

    John

  • 0 in reply to JohnS
    TI__Genius 13045 points

    John,

    Attached is the error message I received when trying to connect to EVM after launching Target Configuration.  Also included shot of IDE Debug mode view in case that is useful.  Let me know if you see what I am doing wrong.

    Thanks.

    CCSv4 Error Msg.doc
  • 0 in reply to TommyG
    TI__Guru**** 171094 points

    Tom,

    Sorry for the delay;

    Blackhawk mentioned that some versions of the drivers were not pulling the correct device driver package, therefore causing CCS to fail with the ever-present OCS error.

    As per their recommendation, I then tested the board with the most up-to-date device driver release (4.2.0.9) and it connects perfectly with CCS when using the Blackhawk. USB510 connection (check picture below).

    However, CCSv4 lacks proper support for the TCI6484/C6457 devices, as well as for the board (which contains two devices in the same scan chain), therefore I created the package attached:

    • Close CCS
    • Unpack the zip file <TCI6484_C6457.zip> into the directory <CCS_INSTALL_DIR>\ccsv4\common\targetdb
      • It will unpack files in the directories boards, Modules and Devices.
      • It contains the TMS320C6457 and TMS320TCI6484 device configurations
      • It contains a EVMC6457 board configuration
    • Create a new target configuration file and select a BlackHawk USB510 and the EVMC6457. It already contains the two devices in the daisy-chain.
    • Manually add the corresponding GEL files for each core.

    Let me know if this helps, ok?

    Best regards,

    Rafael

     

     

    TCI6484_C6457.zip
  • 0 in reply to desouza
    Prodigy 10 points

    Hello,

    the patch works pretty well in CCS 4 and also seems to be included in CCS 5.1. Nevertheless there seems to be a bug in the cslr_dev.xml file. E.g. the offset for the DEVCFG register is set to 0x910 (see: <register id="DEVCFG" acronym="DEVCFG" offset="0x910" width="32" description="Device Configuration Register ">). On the other hand, in the file C6457.xml, which includes the cslr_dev.xml file (see: <instance href="..\Modules\TCI6484_C6457\cslr_dev.xml"         id="DEV"         xml="cslr_dev.xml"         xmlpath="..\Modules\TCI6484_C6457\" HW_version="TCI6484" description="SoC Level Registers"             requestor="TMS320C64XP" baseaddr="0x2880800" endaddr="0x2880bff" size="0x500"     accessnumbytes="4" permissions="p"/>), the base address is set to 0x2880800 (see above) and the end address is set to 0x2880bff. Adding the offset 0x910 found in cslr_dev.xml to the base address results in 0x2881110, which exeeds the end adress of 0x2880bff. According to SPRS582B Table 2-2 the address 0x2881110 falls into a reserved memory block.

    So where does this mistake come from? Looking into Table 3-2 in SPRS582B the register DEVCFG has the address 0x02880910. Therefore it can be assumed that the offsets in cslr_dev.xml are defined to a base address of 0x02880000 and not 0x02880800, as it is defined in C6457.xml. Therefore either of those two files should be fixed. Furthermore a similar problem exists in CCS 3.3 where one also cannot access the DEVCFG register.

    Matthias