Live data from Hacker News

New Texas Instruments 5532 chips are not the 5532s we’ve used for decades

groupdiy.com

41–50 of 59 posts

Re: New Texas Instruments 5532 chips are not the 5532s we’ve used for decades

#41
Dave Jones didn't spare words [1] on how insane it was to have a jellybean component changing specs so significantly, particularly the input voltage from 22V to 18V, the removal of offset trim, and more.

[1] https://www.youtube.com/watch?v=22ZmmZ67SMY

Re: New Texas Instruments 5532 chips are not the 5532s we’ve used for decades

#42

An amusing aside: Look at the list of "applications." Netbooks? Multichannel video transcoders? Scalable platforms? I've seen this in other TI datasheets. One old general purpose 74HC series logic chip included "E Meters" in its applications. My hunch is that whoever was assigned to add these "applications" to each data sheet was having some harmless fun. Another note is that I'm a low profile customer of Digi-Key an…

Funnily enough, E-Meters are known to be made with fairly high quality components.

https://hackaday.com/2018/07/19/whats-inside-a-scientology-e...

I guess if you have tons of cash rolling in, you might as well commit to it.

Re: New Texas Instruments 5532 chips are not the 5532s we’ve used for decades

#43
post #32

Earlier quoted context omitted.

... How do the "paper-pusher regulators" feel about getting a completely different part unannounced? I would guess unhappy, tbh. Like based on the thread it's not trivial changes.

Kind of like keeping a certain plane model number the same, and claiming that re-training isn't needed even when it clearly is

An iPhone 17 is very different to an iPhone 3G, but we can pretend to ignore the fact one had its first flight in 1968 and the other in 2016.

Re: New Texas Instruments 5532 chips are not the 5532s we’ve used for decades

#45
post #15
post #7

Earlier quoted context omitted.

It annoys me too but part numbers are not a spec but more of a strong hint. The attitude of the industry is that it’s up to you to read data sheets carefully and test. Even for a 2N2222 or whatever.

Keeping in mind, though, that this is a jellybean part. You're supposed to be able to order "a" 5532 without specifying the supplier, because many vendors produce "a" 5532, and they're all the same. Different vendors' 5532s are supposed to be able to be treated as the same SKU — literally dumped into co-mingled stock in warehouses — with no ill consequence! (And yes, until TI's recent move, that was true of the 5532.…

Dave Jones also did some videos on the LMV321 used in his uCurrent Gold project. The AS5X variant caused issues while others worked fine.

Looking now, a document source suggests the AS5X variant in the parts list... but it's explained in the video around 19:30

https://www.youtube.com/watch?v=1VlKoR0ldIE

Re: New Texas Instruments 5532 chips are not the 5532s we’ve used for decades

#47

This is the electronics equivalent of Python3's breaking changes to string handling. It's pure evil, and will have 2nd order effects for decades.

How were they python 3 changes pure evil? I think it was a good thing for the language in the long run, and the earlier you do it, the better.

In the long run, python projects just became an unmaintainable mess, and now lots of devs moved on or use python less. At least in my experience.

Re: New Texas Instruments 5532 chips are not the 5532s we’ve used for decades

#48
post #27

Earlier quoted context omitted.

Kind of. I want all 7400s to be four NAND gates, regardless of how they are implemented. As long as the results are correct, you might as well put a little ARM controller pretending to be four NAND gates. For analog parts, I agree any change to the data sheet should receive at least a different suffix letter.

I disagree. At a certain moment you start to rely on behavior, knowingly or unknowingly. These kind of changes might surface bugs that you never had. https://xkcd.com/1172/

If you relied on behavior not in the spec this is on you.

Re: New Texas Instruments 5532 chips are not the 5532s we’ve used for decades

#49
post #27

Earlier quoted context omitted.

Kind of. I want all 7400s to be four NAND gates, regardless of how they are implemented. As long as the results are correct, you might as well put a little ARM controller pretending to be four NAND gates. For analog parts, I agree any change to the data sheet should receive at least a different suffix letter.

I disagree. At a certain moment you start to rely on behavior, knowingly or unknowingly. These kind of changes might surface bugs that you never had. https://xkcd.com/1172/

I don’t care for bugs that never manifest themselves under intended uses.

Re: New Texas Instruments 5532 chips are not the 5532s we’ve used for decades

#50

Earlier quoted context omitted.

I disagree. At a certain moment you start to rely on behavior, knowingly or unknowingly. These kind of changes might surface bugs that you never had. https://xkcd.com/1172/

If you relied on behavior not in the spec this is on you.

In these cases of the TI parts, some of their most important specifications, like maximum supply voltage, noise and slew rate, have been changed, and not by a few percent, but by even a factor close to 2.

For so great changes, it is really not acceptable to use the same part number, especially when the part numbers have been in widespread use for many decades, so most users who are familiar to them will not bother to check again their latest specifications, where they could notice that they are no longer what they knew.

Post reply on HN