Low-Cost MCUs Cover Audio to Industrial

Hi Rich, great summary and I am a big fan of Microchip, but would it be possible to put in a link to a bigger version of the first (architecture) diagram - it is hardly readable, expecially for an old fella like myself :-)   Thanks

Here you go David. I also am a big fan of Microchip.

https://www.flickr.com/photos/microchiptechnology/15041258523/sizes/o/#utm_medium=Press-Release&utm_term=PIC32MX1-2-5-LasVegas_PR_11-3-14&utm_content=MCU32&utm_campaign=Block+Diagram

@AZskibum...many thanks, that is big enough to read and more...  :-)

Can someone tell us if this is better than PIC32MX7 series? Yes, the core frequency is more in PIC32MX7 but still what was the need for combining MX1/2/3 and MX5 seires when MX7 is anyway available? 

Sorry about that diagram. The software I use to create these posts automatically down-sizes my images. There is a way to append a larger version but I haven't figured it out yet. Will try to do better next time.

Thanks to AZskibum for the link to the larger version.

Better is a relative term, and will depend on the application's needs. You would have to do a side-by-side comparison to see the differences, and which is "better" will depend on the evaluation criteria.

@RichQ...Max would tell you...several of my blogs he has put links under the pics "Click here for a larger version".  I seem to remember he has to get the web guys to do it, but I'm not sure.

True, Max knows everything.

@RichQ: True, Max knows everything.

But he's incredibly modest and he doesn't like to boast (also he seems to have started talking about himself in the third person, which he finds to be a tad disconcerting)

Rich,

        We find manufacturers pack many more peripheral functions in micros than the available pins the package can support. Functions are multiplexed on common pins sometimes using some sort of cross point switch. This results in some functions being blocked when some other functions (pins) are used.It is not easily possible by looking at the data sheet to know which peripherals are exclusively available. I have so far not seen any manufacturer come out with a good matrix summary of what are going to be lost when some are used. Have you seen any such "Peripheral availability Matrix package wise" or peripheral Exclusivity Matrix" provided by any manufacturer so far? This matrix may have to be a three dimensional one as pins also enter as one dimension. What is the best way to represent this? 

It's a challenge, no question. I think most vendors offer some kind of pin selection guide. This one from Altera is a tool that helps. The image does just what you suggest, provides three dimensions (color code is the third). http://www.altera.com/literature/hb/qts/qts_qii52013.pdf

But it's going to take some fiddling to get the right assignments to the right pins and not blocking the perihperals you need, regardless of the tools.

The chips I discussed in this piece are supposed to allow any peripheral to connect to any digitial IO chip, the implication being without blocking. So that should make the problem you describe a bit less troublesome.

Rama

I have so far not seen any manufacturer come out with a good matrix summary of what are going to be lost when some are used. Have you seen any such "Peripheral availability Matrix package wise" or peripheral Exclusivity Matrix" provided by any manufacturer so far? This matrix may have to be a three dimensional one as pins also enter as one dimension. What is the best way to represent this? 

I did a design idea in EDN on this topic "Program "excelerates" microcomputer-I/O allocation". Unfortunately need to get to know your micro quite well to generate a worksheet like this, but at the end of it you will certainly be an expert- until the next time you choose to change processors! Rich will remember a blog I did on the subject on MCC, but that forum no longer exists- I will see if I can recycle it on MCU Designlines.

AD, if you're referring to Allocating MCU Resources Accurately , I have that archived and I will repost it here on the Industrial Control DesignLine.

Rich,Thanks for the input.

Antideluvian,Thanks for a very useful design idea. I am yet to read that fully, as unlike earlier, all the figures in the article pdf do not open in a 'contiguous article' fashion. I will save in a 'contiguous word' for convenience of reading. May be as HR softwares extract engineer's vital features from CVs, in future, manufacturers standardise datasheet organisation for a "CPU feature extractor tool" to yield "Designer's CPU data sheet".

Rama

Rich was quick off the mark and has re-posted my original blog  here: Allocating MCU Resources Accurately.

Rich

I have that archived and I will repost it here on the Industrial Control DesignLine.

That was impressive- located, edited and posted in less than an hour! Thanks!

Rama, glad to help. If you find a configuration/planning tool that works well, or create one of your own the way AD suggests, let us know.

AD, thanks. But don't be too impressed. I have the whold content of Microcontroller Central and of IoT World archived and it's in a form that is pretty easy to copy and paste without needing additional editing (it's been edited once). So it's mostly a matter of going through the motions.

If there are any other blogs anyone remembers from either site that seem like they would be a good fit here, just sing out. I'll get it ported over, although I may update it slightly if it needs it.

Rich

If there are any other blogs anyone remembers from either site that seem like they would be a good fit here, just sing out.

Actually I submitted one of them to Max for this month. Should be out Real Soon Now (does anyone remember Jerry Pournelle's articles in Byte?).