3 ms·
This is an aside, but whenever choosing a microcontroller I always read the Errata. You'd be surprised that TI or Microchip or whoever ships silicon with blocks
by coupdejarnac 10y ago
This is an aside, but whenever choosing a microcontroller I always read the Errata. You'd be surprised that TI or Microchip or whoever ships silicon with blocks of functionality that just don't work.
If I were you in this situation, I'd get on the phone with Microchip's closest field engineer, and maybe they can point you in the right direction, especially if this is a known issue. Perhaps they can connect you with engineering support farther up the chain.
- retSava 10y agoHa, not only that it doesn't work, but also that the datasheet/TRM/FUG says it's there and working, while the errata says it does not work and there is no workaround. So I fully agree, reading the errata is essential and should always be done before starting any implementation since the way you imagined to solve the thing might be totally off due to some errata issue.