I just made a spreadsheet of all the tinyAVR parts. All my pals love the MCU selector guide, but I have a lot of analog dinosaur buddies that prefer a spreadsheet to a web-based interface. You can sort the data and this spreadsheet has the filter box on the columns, so you can sort out things you care about and exclude the things you don’t. The spreadsheet fits on a 24-inch display, and you can print it out on a single B-sized sheet and use it as an infographic.
I started with an Excel dump of the selector guide after adding every single parameter to the search. I then took all the tinyAVR parts, and rearranged the columns, throwing out the irrelevant ones. I also combined the automotive parts with the basic parts. That added two columns for automotive temp and automotive Vcc range. Adding 2 columns to remove 13 rows seemed like a good deal. The part name links to the product page on our website.
I made a column for each package. That took a long time. Semiconductor companies think of a part as the silicon die, with the package being almost irrelevant. We systems folk know the package might be the most important thing. I tried to put the smaller packages on the left, with those big ol’ DIP (dual-inline plastic) parts on the right side. There is a second sheet in the spreadsheet that shows all the parts by number and there I put the package size, in mm. In both sheets, the package name links to the definition page on our website.
Besides the packages and package size, I also spent a long time getting pricing. My buddy Wayne Yamaguchi requested this, and he is absolutely right, price is the most important spec of any part, and I hate when it takes 5 clicks to find it. These prices are a bit sketchy. All I did was click on the “Buy” link and select a handful of parts from each family, and then looked at the Digi-Key price, in 1000s. I put in the highest and lowest of the few I selected, but this is by no means scientific or dispositive, as the lawyers would say. What I should do is put the price in the “Package” column, so you know what the package is and what price we charge, but many parts are in the same package but have two Vcc ranges, so there is no unique way to encode this and keep the spreadsheet on one printable page. Maybe I can blow out the second page to show every orderable part number and its price and specs. Always time to do it over, never time to do it right.
The major thing I want to add is the OrCAD 9.2 footprint name for the packages. I am afraid to do this now, since we have all been burned by narrow-DIP/wide-DIP and narrow -SOIC/wide-SOIC and what pin numbering to use on SOT parts, so that will have to wait for next time. If anyone has a proven definitive list of the OrCAD footprints, please let me know. paul.rako[yeah, the at sign]atmel.com
You can highlight all the parts and use the “Data>Sort” function to order them any way you want. I did it by Flash memory size and part name. You can also use the little filter boxes on each column to include or exclude, or even put in a logical range with equal or less than or all the other things. Its not exactly grep or regular expressions, but it can get the job done helping you to find the right part.
I am told this spreadsheet works OK in Open Office/Libre. My pal Dave asked that any columns that are filtered be lit up red, but that takes a macro, and the VB macro may not work in Open Office, we are checking for that. Meanwhile, check there are 36 part families or that the little filter box does not have 3 pixels different to show the filter is on.
Weasel weasel, CYA CYA, legal boilerplate—this is a hobby job, not an official Atmel document. If the selector guide had it wrong, it is wrong here too. I made my own mistakes too. And I already told you the pricing and the tiny1634 stuff was dicey. What I am hoping is that I can get some community support where you point out the errors, and tell me what to add. paul.rako[yeah, the at sign]atmel.com I also ask that you send this URL link to your pals, instead of just emailing the spreadsheet. That way the bosses will see you like this, and I can have the time to keep working on it.
It will be much better if you don’t use a proprietary office suite. Start with LibreOffice as you will help all the people, and not just some. Is not working properly in LibreOffice 4.x under win8.1 – not tested yet under Linux, where fonts may differ. Personally, I will consider this just a good start… until is done properly.