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.

  • TI Thinks Resolved

TMS320VC5509A: Errata questions

Part Number: TMS320VC5509A

  • What CPU_XXX bugs are still in the 5509a and 5510a silicon dies?

  • Can we get more info on CPU_120 to CPU_127?

Thanks,

Catalog Processors

  • Hi Rogerio,
    I have asked a team member to take a look and respond.

    Lali
  • Hi Rogerio
    Can you further clarify the background and reason for this request.
    Looking through internally, to pull something like this will take time and effort.

    The last known document that was trying to capture the CPU bugs for c55x family is the following
    www.ti.com/.../spru652g.pdf (this goes to CPU_119)

    This has not been rev'd since 2005 and does not capture the status for 120 to 127 for the requested devices.
    The devices are very old and we have limited resources to pull this.

    I would like a better business justification for this request.

    Regards
    Mukul
  • Hi  David Johansson86 (4455186)

    I have tried to dig through various bug tracking systems and archives, and unfortunately there are no known owners for these devices from a design/development standpoint , so the data I have pulled is based on what I can cobble together based on what I see in the archives

    To the best of my knowledge here following is the story on the addition CPU bugs for the devices you are interested in

      5507 5509A  5510a
    CPU Revision  v2.2 v2.2 v2.11
    CPU_120      
    CPU_121      
    CPU_122 x x  
    CPU_123 x x x
    CPU_124      
    CPU_125 x x x
    CPU_126 x x x
    CPU_127 x x x
    CPU_128 x x x

    x implies bug is present/applicable. 

    I will be out next week, and once I am back I will try to see if I can verify this further with someone with additional background on this.

    Any questions on CCS/compiler workarounds etc for these devices will likely need to be addressed by folks in the CCS forum team.

    Regards

    Mukul 

  • In reply to Mukul Bhatnagar:

    Unlocking thread
  • In reply to Jim Carrillo:

    Hi David
    I spend some time digging this further, and the update i have provided in the previous post reflects what I was able to find in the archives.
    There is no further action planned on this and the information above is good to go to see if this helps closes this out with your customer.

    Regards
    Mukul
  • In reply to Mukul Bhatnagar:

    Hi Mukul and David,

    Is there some documentation on what cpu_124 to cpu_128 mean? I have checked the following sources with no luck:

    CCS release notes:

    'readme 3.2.2.txt'
    'readme 3.2.3.txt'
    'readme 3.3.3.txt'
    'readme 3.3.4.txt'
    'readme 3.3.5.txt'
    'readme 3.3.6.txt'

    spru652g.pdf
    sprz006e.pdf
    sprz008o.pdf
    sprz200f.pdf
    sprz217c.pdf

    And also 

    Best regards, and thanks in advance

  • In reply to Santiago Palomino:

    Hi Santiago
    As far as i know there is no public documentation on these CPU erratas. The SPRU652G has not been updated since 2005.

    Regards
    Mukul
  • In reply to Mukul Bhatnagar:

    Is it possible for my company to get information under NDA? I am the person who initiated this conversation with David last Summer.
  • In reply to Santiago Palomino:

    Hi Santiago
    This is somewhat non trivial and I will need to discuss internally. It will also take us several weeks in my opinion as the bug reports are in an internal bug repo and not in document format that can be shared.

    I will keep you posted if there is anything I can offer to help on this. As you can imagine this is almost 15+ year old data.

    On a positive note, it appears that CPU_125 and 126 will not be relevant to customers.
    So the list of ones that maybe relevant for you is smaller.

    Regards
    Mukul

  • In reply to Mukul Bhatnagar:

    Hi,

    I have taken a look into some of the documents, I am sending our replies to David Johanssen and Anders Dunkars. I hope they can forward them to you.

    Best regards,

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.