• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 54 subscribers
  • Views 888 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Bug: CCS TMS320VC5501/5502/5503/5507/5509 register module xml file missing

Gaurav Singh
Prodigy 190 points
Other Parts Discussed in Thread: TMS320VC5502

CSS need few XML file to get the register details in registerview . these xml file are in
C:\ti\ccsv6\ccs_base\common\targetdb\Modules\XXXX

There are xml file for all type of processor there but not for TMS320VC5501/5502/5503/5507/5509

  • 0
    TI__Guru**** 161500 points
    Gaurav,

    Unfortunately there are no plans to add the detailed register information for these devices.

    Regards,
    John
  • 0 in reply to JohnS
    Prodigy 190 points
    so these devices are not recomended for new design.

    i have already made a hardware around one one of processors,
    are these devices still supported or not?
  • 0 in reply to Gaurav Singh
    TI__Guru* 82575 points
    Hi Gaurav
    The 5501/02/09 family is still supported and maintained. We have not put a "not recommended for new design" on these - however these are very old devices (almost ~12+ year old) - so if there are gaps in the offerings - there are no plans to address these gaps or do any new development at this time.

    The 5505/5515/5535/5545 and 5517 family are the newest c55x devices we have and you will see us have more latest/greatest support around these device families.
  • 0 in reply to Mukul Bhatnagar
    Prodigy 190 points
    i tried a little but could not able to find any message on the TMS320VC5502 Page where it says that it is not recomended to new design.
    can you please find me any reference .
  • 0 in reply to Gaurav Singh
    TI__Guru* 82575 points
    Gaurav
    In post i mentioned we have *not* put a "NRND" on this device. Customers are still using it - but majority of the development seems to be on legacy designs still in production.


    We continue to evaluate if a specific device family needs a collateral refresh , based on business opportunities etc.

    If you are starting a new development - you will encounter some roadblocks as we are not refreshing/creating any new collateral for this at this point.

    Hope this clarifies.

    Regards
    Mukul
  • 0 in reply to Mukul Bhatnagar
    Prodigy 190 points
    okey so they are still *not* on "NRND" but still they are actually "NRND" because new tools won't support them or cutomer need to write support files.

    this is fair enough