Looking for a MCU with “accurate” ADC

[splin]

[edit] Funny that you did not even try to use search to find where sentence I mention "packet should be small (20 to 32 PINs)" comes from 

No-one should need to search a page to find all the requirements of someone asking for help, they should be in the first post.  If they change, or additional requirements need to be added then the first post should be amended.  It prevents exactly this kind of thing.

No no no!!!!!!

Let me repeat that -

No no no!!!

When posts get substantially edited the whole thread can collapse into total confusion. The whole history is lost and it becomes impossible to know what subsequent responses were responding to because the time relationship between all the posts in a thread are lost.

Some clearly documented minor edits, such as typos, are ok. It might be acceptable to mark part of a post specifically as containing information that may be kept up to date (such as the multimeter specs table) but that still risks some posters viewing, and possibly acting upon one version of the data and others seeing a later, different version with lots of potential for confusion.

Updating a post is great for viewers who encounter the post for the first time after the last update but is terrible for those who revisit or follow a thread, potentially (if they care enough), requiring them to reread the whole thread every time they come back to it.

[technix]

When posts get substantially edited the whole thread can collapse into total confusion. The whole history is lost and it becomes impossible to know what subsequent responses were responding to because the time relationship between all the posts in a thread are lost.

Some clearly documented minor edits, such as typos, are ok. It might be acceptable to mark part of a post specifically as containing information that may be kept up to date (such as the multimeter specs table) but that still risks some posters viewing, and possibly acting upon one version of the data and others seeing a later, different version with lots of potential for confusion.

Updating a post is great for viewers who encounter the post for the first time after the last update but is terrible for those who revisit or follow a thread, potentially (if they care enough), requiring them to reread the whole thread every time they come back to it.

If only the forum software can support a revision history feature for the posts...

[splin]

When posts get substantially edited the whole thread can collapse into total confusion. The whole history is lost and it becomes impossible to know what subsequent responses were responding to because the time relationship between all the posts in a thread are lost.

Some clearly documented minor edits, such as typos, are ok. It might be acceptable to mark part of a post specifically as containing information that may be kept up to date (such as the multimeter specs table) but that still risks some posters viewing, and possibly acting upon one version of the data and others seeing a later, different version with lots of potential for confusion.

Updating a post is great for viewers who encounter the post for the first time after the last update but is terrible for those who revisit or follow a thread, potentially (if they care enough), requiring them to reread the whole thread every time they come back to it.

If only the forum software can support a revision history feature for the posts...

If only. That could be a really useful feature for the forum administrators in the event of a legal case whereby they have to reconstruct the exact time of events that occurred in a discussion leading to a criminal episode.

Fortunately the forum software doesn't support 'a revision history feature for the posts' - through the UI - because it is so much simpler and more obvious, for those who aren't members of the 'revisionist illuminati', to work out what is going on by reading the thread.

[technix]

When posts get substantially edited the whole thread can collapse into total confusion. The whole history is lost and it becomes impossible to know what subsequent responses were responding to because the time relationship between all the posts in a thread are lost.

Some clearly documented minor edits, such as typos, are ok. It might be acceptable to mark part of a post specifically as containing information that may be kept up to date (such as the multimeter specs table) but that still risks some posters viewing, and possibly acting upon one version of the data and others seeing a later, different version with lots of potential for confusion.

Updating a post is great for viewers who encounter the post for the first time after the last update but is terrible for those who revisit or follow a thread, potentially (if they care enough), requiring them to reread the whole thread every time they come back to it.

If only the forum software can support a revision history feature for the posts...

If only. That could be a really useful feature for the forum administrators in the event of a legal case whereby they have to reconstruct the exact time of events that occurred in a discussion leading to a criminal episode.

Fortunately the forum software doesn't support 'a revision history feature for the posts' - through the UI - because it is so much simpler and more obvious, for those who aren't members of the 'revisionist illuminati', to work out what is going on by reading the thread.

If I recalled it right, Github’s discussion is constructed as a giant Git repo with each post and edit being a commit in it. This does allow viewing the full history of all posts using the Git blame feature.

[PCB.Wiz]

You are almost there with uncalibrated, lowest cost internal references on most MCUs, but as you have found out, not quite.

EFM8BB has ± 1.8% vref in full -40^o +85(or 125)^oC temperature and full Vcc range starting from $0.30

That sounds like a very good fit. SiLabs have good Analog performance.