PCA9306: PCA9306

Esteban Magana

Prodigy 10 points

Part Number: PCA9306

Hi,

We received PCN 20211019000.1 which affects two of the PN (PCA9306DCTR & PCA9306DCTT ) that we currently buy from TI.

We have the following questions

Are the thermal changes a result of a process change? Are they intentionally making these changes and if so, why?
Seems like the MIN/MAX value change was a type in the original version of the specification, but let me know if that is not the case
Is the following stating a package change or is this part # change only? is this package used in the affected PN?

over 3 years ago

0 Eric Schott1 over 3 years ago

TI__Guru 53555 points

Hi Esteban,

An I2C expert has been assigned to this thread and will respond to you today.

Regards,
Eric Schott

0 BOBBY over 3 years ago

TI__Guru 73331 points

Esteban Magana said:
Are the thermal changes a result of a process change? Are they intentionally making these changes and if so, why?

Yes, the thermal changes are a result of a different process technology. We did this to update the older processes with new ones due to FAB changes.

Esteban Magana said:
Seems like the MIN/MAX value change was a type in the original version of the specification, but let me know if that is not the case

The only MIN/MAX values change was in the ViK spec which was technically spec'd wrong. We fixed that in this datasheet to align with all of our other I2C datasheets.

The MAX values for several AC characteristics have changed (increased), if you're using this device for I2C then these changes won't affect your system. If you need more specific information about this, I can send you a powerpoint of the changes. (Again, for I2C applications this data isn't useful)

Esteban Magana said:
Is the following stating a package change or is this part # change only? is this package used in the affected PN?

That looks like a change unrelated to the PCN you mentioned. I believe based on the April 2019 date, the package for the DQE device changed..... I'm guessing the package height was modified resulting from a VSSON to an X2SON.

-Bobby