With email and Internet news announcements seemingly every day about new MCUs and how they will make your life easier, there has been a subtle change in the background research designers perform when starting a new project. Designers used to ask, “How do I find out about what solutions are available?” Now they tend to ask, “How do I find out how usable these products are?”
Evaluation (eval) kits are one answer. But those, too, have changed. In the "old days", when there were not so many new product offerings, vendors were willing to give you small eval kits without expecting you to immediately place a purchase order for 10,000 pieces. Nowadays, you have to qualify as being ready to buy to get a small eval kit on loan for a month or two. I was lucky that I had the chance to learn about embedded control from the freebies I got 20 years ago. Otherwise I may never have gotten into the business at all.
Even though the freebies are now hard to come by, in their place most vendors offer a plethora of inexpensive eval kits. Many of these kits come with more or less limited development tools (more on that in a later blog) and are so low-priced that I have purchased some myself with my own money, when I really wanted to evaluate a part but did not have an immediate business need. I used my own money because it was just simpler than filling out a lot of company paperwork. My threshold is somewhere between $10 and $50, more likely the former. What you are willing to do with your own money for work may be different.
But there are so many eval kits now available you have another choice to make. Once you have selected a product or a product family to evaluate because it appears to be able to meet your needs, you need to select the eval kit you will purchase. What are the features that will drive your selection?
Some kits are specialized, and intended to let you evaluate specific advanced device features. If your need is to evaluate specific features, and there is an eval kit targeting those features, you are in luck.
Other kits are quite general. These typically are pretty much bare-bones designs with most of the chip’s pins available on connectors or solder pads. Such generalized boards are usually my favorites and have met my needs nicely. Good examples can be found in the Silabs ToolStick family, although many vendors offer similar kits. Let me explain why I like them.
Most Toolsticks are about $10. To program them, you need a USB adapter (Toolstick Base Adapter) that is under $20. The base adapter plugs into the USB connector on your PC and has a socket that mates with a card edge connector found on all Toolsticks. Once you have programmed the Toolstick it can operate without using the base adapter, so you can keep the adapter for use in the next project.
Many Toolsticks contain just the core MCU and simply bring the key I/O pins to connection points on the PCB. Some Toolsticks also have a few additional parts, like a couple of LEDs, a potentiometer, or pads for capacitive touch sensing, to make the sample software examples more interesting. Some have interface chips to implement simple networking features.
Simple software examples available from Silabs demonstrate each peripheral, so it is very easy to understand how each peripheral works and how to configure it. You can combine the examples to build a more complex project, as well. The examples come in individualized versions for each of the chips, and are available both in C and in assembly so that you can be sure that you will always be able to run the examples.
Silabs also has a configuring tool that greatly facilitates the sometimes difficult task of setting up peripherals. Unfortunately, the sample programs do not use the configuring tool, which makes it difficult to go from a sample program to creating an equivalent setup in the configuring tool, but this is a relatively minor gripe.
I find that not only are the Toolsticks neat and inexpensive, they are the best way to evaluate chips that come in leadless packages. Their low price also makes them useful for one-off setups, like creating test jigs or building demos.
Low price, minimal additional hardware, easy I/O access, and plenty of support for learning about MCU peripherals is what makes the Toolstick my favorite evaluation kit. What are your favorite eval kit features and why? Comments invited!
NHegde 4/11/2012 3:01:21 PM User Rank System supervisor
Re: MSP430 Lauchpad
The MSP430G2553 series seems to have some problem and I didnt receive the PDIP packaged ones I had requested, as its telling that TI has backordered these products! Dont know exactly..
NHegde 4/11/2012 2:29:03 PM User Rank System supervisor
Re: Free eval kit, if you're lucky
Unsure of other tools, but we use IAR licence hooked to USB dongle and we move the licence around office in different machines/persons based on need., So it just works out for us, may not be for all., And there are also server licencing available to many tools I guess!
pmwrightjr 4/11/2012 12:42:40 PM User Rank Bit twiddler
Roman Black's Shift1-LCD kit
Although it is not a development kit, per se, one of my most productive finds was Roman Black's Shift1-LCD kit. The stated purpose of the kit is to just run an LCD display by clocking the bits into a shift register using a timing algorithm but it includes provisions for an 8-pin PIC that can host all sorts of applications. I have used it for a temperature alarm and a Morse Code trainer using a 12F683 PIC.
Because the display functions are essentially handled by the hardware, you can focus on the application and I've been able to do far more with an 8-pin PIC than I would have thought.
Over the past few years, I have had the chance to experiment with many evaluation boards and kits including the Ti MSP430, the Freescale Tower system, a couple of different ARM implementations but the most useful of all in terms of actually producing products that worked was the Shift1-LCD kit. Obviously, there are a limited number of I/O pins on an 8-pin PIC but when you can do the display with one line and there is an internal A/D, there is a lot you can do. There are also a handful of applications that work "out of the box" so you can start with working code and tweak it as needed and that fits well in my development style.
Didier_Juges 4/11/2012 12:26:39 PM User Rank Blogger
Re: Free eval kit, if you're lucky
Rich, I am just not much of a lottery player... I will get a kit from Silabs at some point soon, but at the moment the only kits available are a little rich for my own wallet, and I do not have yet a good justification for buying one on company money, but that is coming, so expect a blog from me when that happens :)
At the moment, I have been grinding my teeth on the Cortex-M3 with a small Eagle50E board from Micromint (http://www.micromint.com/index.php/SBC/eagle-50.html). It is supported by open source tools (gcc, gdb, codeBlock IDE) and TI's free tools (flash loader and Stellaris libraries). I also played with the demo version of the IAR development tools, and if not for the $5,000 or so price tag, I otherwise like it very much.
I want to point out again that while it is not hard to justify spending $5,000 on a development job for work, because the right tools can certainly save that much money over a project or two, the problem is that the commercial tools are tied to one machine, one person, one location and therefore would restrict my flexibility. I would rather not get there in the first place and it is worth to me, and the company to spend the time to learn the free tools and not have that restriction.
I just installed the Altera Quartus software on my work laptop, and the 2.5GB install completed, after a while, and without a single request for NIC ethernet address or other such thing. I like that.
previous version of Launchpad (MSP-EXP430G2 Rev. 1.4) has MSP430G2231 and 2211, but Rev. 1.5 has more powerful MSP430G2553 with Universal Serial Communication Interface (USCI): Enhanced UART Supporting Auto Baudrate Detection (LIN) IrDA Encoder and Decoder Synchronous SPI I2C
Microp 4/11/2012 4:09:30 AM User Rank Program Manager
Eval kits
"Nowadays, you have to qualify as being ready to buy to get a small eval kit on loan for a month or two"
Didler, you are right. Quiet sometimes back, vendors used to visit companies with evaluations kits and they allow us to use it for up to 6 months. But now a day, they had short cut this time frame for 15-45 days and from day one onwards they start tracking of the status also. But once if we had placed the order, they never mind to take back the eval kit also.
duanebenson 4/11/2012 3:05:01 AM User Rank Blogger
Re: LPCXpresso/ mbed
Didier - The mbed has a really full set of libraries along with the online compiler. As far as I can tell, they take care of anything set up or register related. The libraries are very easy to use (at least the ones that I've used). For example, here's one of their sample PWM programs:
// Sweep the motor speed from full-speed reverse (-1.0) to full speed forwards (1.0)
#include "mbed.h"#include "Motor.h"Motor m(p23, p6, p5); // pwm, fwd, revint main() {
for (float s= -1.0; s < 1.0 ; s += 0.01) {
m.speed(s);
wait(0.02);
}
}
Here's another example for running an R/C servo:
#include "mbed.h"
PwmOut servo(p21);
int main() {
servo.period(0.020); // servo requires a 20ms period
while (1) {
for(float offset=0.0; offset<0.001; offset+=0.0001) {
servo.pulsewidth(0.001 + offset); // servo position determined by a pulsewidth between 1-2ms
wait(0.25);
}
}
}
The compiler and libraries are also the best documented that I've run across in the MCU world and the documentation is easier to find than anything else I've run across. More importantly, everything there is written specifically for the mbed. A lot of the other tool chains I dabble in have pieces of documentation scattered here and there and much of it is more generic rather than targeted at a specific piece of hardware.
I haven't bypassed the libraries and written closer to the hardware but my understanding is that you can do that. You can also export code to a number of other toolchains.
I'd call it a good platform for rapid prototyping and a superb educational platform.
The MSP430G2553 is compatible with the TI Launchpad and has a "Universal Serial Communication Interface" that will support serial communications Didier. And of course you can always bit-bang a serial comm port without much difficulty in any of the MSP430 parts, even the lowly MSP430G2211 14-pin DIP that came with your Launchpads. This is handy for exploiting the back-channel serial support the Launchpad provides via its USB connection. (The eval. board's example code includes a 2400 baud comm. module that can easily (and reliably) run at 9600 baud with the G2211.)
NHegde 4/10/2012 9:50:43 PM User Rank System supervisor
Re: MSP430 Lauchpad
There was also a discussion on UART in this forum, but seriously I never felt the need of that in any of my work, may be because when I bought my laptop (after which I started working on embedded systems) 8 years back, which didnt have any RS232 interface on it and I have always used the debugger/jtag for debugging my applications., Having said that, I have to admit that I have seen many applications where in UART was really a great interface.,
Didier_Juges 4/10/2012 8:48:42 PM User Rank Blogger
Re: Eval kit software
Rich, I think the key to get me hooked to a kit is simple software that works (and that I can use as a starting point for a real, more complicated project), as opposed to complicated software that may be doing something very impressive, but that is too complicated to be used as a starting point, and may be difficult to get going or even to evaluate.
I found that I learn faster and more effectively by combining simple programs rather than trying to understand a large, complicated application.
Another thing, some vendors do not give schematics with their eval kits. I find that totally uninspired. I found that to be the case more frequently with FPGA kits than microcontroller kits, but I have seen it just too many times. I can read specs until I am blue in the face, looking at a schematic of something that works is just something else, like the proverbial picture worth a thousand words.
With his applications straining the bounds of 8-bit processors, Didier is considering an RTOS but is unsure if it's worth the MCU resources it consumes.
To save this item to your list of favorite Microcontroller Central content so you can find it later in your Profile page, click the "Save It" button next to the item.
If you found this interesting or useful, please use the links to the services below to share it with other readers. You will need a free account with each service to share an item via that service.