• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 1076 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.

AM5728_RevA.xml in CCS 6.1.1 causes errors when used in target configuration file due to multiple CPUs named ICECrusherCS_0

Chester Gillon
Guru 92251 points
Other Parts Discussed in Thread: AM5728

When used CCS 6.1.1.00022 with Sitara device support 1.2.5 to create a target configuration file for an AM5728_RevA the following errors were reported for the target configuration file:

Description	Resource	Path	Location	Type
More than one cpu is named ICECrusherCS_0	AM5728_RevA.ccxml	/am5728_hello/targetConfigs	Blackhawk USB560-M Emulator, 20-pin JTAG Cable\ICECrusherCS_0	Problem
More than one cpu is named ICECrusherCS_0	AM5728_RevA.ccxml	/am5728_hello/targetConfigs	Blackhawk USB560-M Emulator, 20-pin JTAG Cable\ICECrusherCS_0	Problem
More than one cpu is named ICECrusherCS_0	AM5728_RevA.ccxml	/am5728_hello/targetConfigs	Blackhawk USB560-M Emulator, 20-pin JTAG Cable\ICECrusherCS_0	Problem

The error appears to be caused by the ccsv6/ccs_base/common/targetdb/devices/AM5728_RevA.xml containing four CPUs named ICECrusherCS_0, as components of the IPUs.

Note that this is not currently causing me a problem, but just noticed the error when investigating something else.

  • 0
    TI__Guru**** 171094 points
    Chester,

    This is a bug that slipped through CCSv6.1.1. The AM572x configurations for Si Rev 1.x fail when created via the Project wizard, but not directly from the target configuration editor. This is reported in bug number SDSCM00052300 and proper device configurations for AM572x Si Rev 2.0 will be made available in CCSv6.1.2 (to be released in the next few days or weeks).

    To workaround this problem, open the target configuration in the target configuration editor, go to the tab Advanced and rename the ICECrusher _CSn of IPU1_C1, IPU2_C0 and IPU2_C1 to sequential numbers starting from 1.

    I apologize for the inconvenience,
    Rafael
  • 0 in reply to desouza
    Guru 92251 points

    desouza said:
    To workaround this problem, open the target configuration in the target configuration editor, go to the tab Advanced and rename the ICECrusher _CSn of IPU1_C1, IPU2_C0 and IPU2_C1 to sequential numbers starting from 1.

    Thanks for the workaround, confirm that it works.

    After doing that realize that the contents of the .ccxml file can override the contents which come from the device .xml files.