• Locked Locked
  • Replies 10 replies
  • Subscribers 29 subscribers
  • Views 475 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.

PCM2904: Successor model to PCM2904

Conor
Guru 10680 points
Part Number: PCM2904

Hi, 

There is an item "2.3 Exceeding Max-Packet Size" in the PCM2904 Errata guide.

In the workaround for this item, there is a statement that a revision of the IC with the bug fixed in 2008 is scheduled to be released.

Q1. Is it correct to understand that the bug has been fixed in the currently released IC?

Q2. Please let me know if there is a successor model to PCM2904.

Thanks,

Conor

  • TI__Mastermind 40115 points

    Hi Conor,

    PCM2904C is the successor model. The bug has been fixed in current silicon.

    Best regards,
    Jeff McPherson

  • in reply to Jeff McPherson
    Guru 10680 points

    Hi Jeff,

    It seems that PCM2904C is not currently released by TI. PCM2904D is probably the successor model of PCM2904C, but am I correct in my understanding that this errata has also been resolved in PCM2904D? I would like to check just in case, as a problem similar to the above errata has occurred with PCM2904D.

    Thanks,

    Conor

  • in reply to Conor
    TI__Mastermind 40115 points

    Hi Conor,

    Sorry, I got the parts confused. You're right there is no PCM2904C. However the bug would've been fixed in a silicon revision without releasing a new part. Let me check with our design team on this bug.

    However the PCM2904D doesn't exist, so I'm confused on what part you're seeing an issue with?

    Thanks,
    Jeff McPherson

  • in reply to Jeff McPherson
    Guru 10680 points

    Hi Jeff,

    Please let me know if the above bug has been resolved in the currently released PCM2904. Also, the package number printed on the PCM2904DBR that is currently experiencing a problem is "6AM057M". Since the revision is not specified on the package, please also check whether the bug has been resolved in the product with this printed number.

    Thanks,

    Conor

  • in reply to Conor
    TI__Mastermind 40115 points

    Hi Conor,

    I've passed the package information to the design team and I'll let you know what they come back with.

    Best regards,
    Jeff McPherson

  • in reply to Jeff McPherson
    Guru 10680 points

    Hi Jeff,

    Thank you. We look forward to hearing from our design team.

    Thanks,

    Conor

  • in reply to Conor
    TI__Mastermind 40115 points

    Hi Conor,

    Our team is looking into it but since it's such an old device it may take a few days. I'll leave the thread open but I'll give an update when we have something we can share.

    Best regards,
    Jeff McPherson

  • in reply to Jeff McPherson
    Guru 10680 points

    Hi Jeff,

    It would be very helpful if you could check it as soon as possible.

    Thanks,

    Conor

  • in reply to Jeff McPherson
    Guru 10680 points

    Hi Jeff,

    We checked internally and it appears that no PCN changes have been issued as a result of the REVISION change. Is there anything to update?

    Thanks,

    Conor

  • in reply to Conor
    TI__Mastermind 40115 points

    Hi Conor,

    Internal records aren't 100% conclusive on this because again the device is quite old, but it appears like there wasn't a revision released to address this bug.