3 ms·
I've most definitely run into issues with others in that list, and my reports to the companies never generated an errata. One fun one was that when accessing t
by xobs 3y ago
I've most definitely run into issues with others in that list, and my reports to the companies never generated an errata.
One fun one was that when accessing the External Memory Interface module (think: parallel ROM) and switching from Bank 1 to Bank 0, the HDMI controller would get reset, but only when configured for two banks of 32 MB.
If I did one bank of 64 MB and just used the extra pin as CS, it worked just fine.
There are lots of similar quirks in every chip.
- ChuckNorris89 3y agoFrom my time in the semi industry, when reporting issues for the erata, it depends who you are. Are you some hobbyist or small company who sent your issue report to some generic company email address? Then your report most likely neve reached anyone on the team working on that chip, but probably reached some clueless jobsworth who didn't know what to do with it because large semi companies are highly siloed and there's no centralized management for such things, so you need direct contact with the team responsible for that chip. If you're large customer, you then have direct email addresses of support engineers, application engineers and the engineers who worked on the chip itself, and so your reports will definitely taken seriously. There's also another issue. There's public datasheets and eratas which are often not updated or fully transparent, and then there's confidential datasheets and eratas, which are updated and issued under NDA to industrial customers on a need to know basis. As a hobbyist you rarely get all the truthful info. It's not ideal, but the semi industry mostly focuses on large customers who buy in large volumes of product, not on hobbyists and tinkerers.
- tails4e 3y agoSounds like an open source/wiki for errata could be useful, at least then reports like yours could be published of the vendors do not