After all of the amazing things I'd seen in µC/Probe's own GUI, my knee-jerk reaction was to wonder what Excel brought to the party. The thing is that you can use all of the math functions that Excel is really good at to enhance the capabilities of µC/Probe, such as scaling the raw values coming out of an analog-to-digital converter (ADC) and presenting them in real-world engineering units. Also, although it sounds trivial, your ability to select fonts and colors and suchlike in Excel can make things so much easier to work with.
There are three flavors ("editions") of µC/Probe as follows:
Educational/Evaluation Edition: This is free, but it has limited functionality and times out after running for one minute.
Basic Edition: This costs $25/month, $250/year, or $450 for a perpetual license. It contains most of the features of the Professional Edition, except that is doesn't support Excel, scripting, uC/Trace triggers, and Terminal Windows.
Professional Edition: This costs $50/month, $500/year, or $900 for a perpetual license. This is the full-up, all-singing all-dancing version that will make you squeal with delight.
You can discover a lot more about all of this -- including a bunch of videos -- on Micriµm's website. The bottom line is that I, for one, am very impressed. What tools and techniques to you currently use to analyze and debug your embedded system? Do you think µC/Probe would be of interest? If you do download the Evaluation Edition and play with it, I'd love to hear what you think about it.
Yes the tool seems to be very useful for software engineers who spend hours altogether finding the bug. SOmething like this will save them lot of time. Imagine the times when you got to work on a code written and by someone else and there is no documentation explaining the code.
@MB - resizing - I still have XP (yeah, I know, I'm a luddite :-) and you can resize in that with the Image \ Stretch and Skew. You just stretch by the same amount vertically and horizontally. Otherwise you get some very weird effects.....
For cropping I prefer MS Office picture manager - it's very easy, also for adjusting colour / brightness / contrast.
illustrious - adjective 1. well known, respected, and admired for past achievements.
@David - I'm glad I am in such illustrious company.
From 2088 to 2011, I was the EDN Design Ideas editor (three of the longest years of my life). One prolific contributor in Eastern Europe would hand draw his schematics and scan them. It drove me crazy because they were hard to edit. I asked him about getting some kind of schematic drawing program, but no way. Finally I asked if you could use PowerPoint and the did. So, I make up a library of circuit symbols in PowerPoint and sent it to him. After that, his scematics were easier to read and consistent. He probably still uses it. Michael Dunn should thank me for that.
At that time, EDN was still in print and until 2010, we had someoen who did a beautiful job drawing schematics for the magazine. She you take anyting and turn it into EDN's style. We lost her when EDN was sold to Canon but she came back part time for a while under UBM.
@MeasurementBlues - "As for me, I still do most of my graphics with Windows Paint. "
I thought I was the only one still using it! I'm glad I am in such illustrious company. MS Paint is, for most things, so easy to use. It's horses for courses, for example MS Paint cannot (as far as I know, correct me if I am wrong) do graduated fills, but for most diagrams it can do pretty well anything you need. I have a file of schematic symbols and have it open so I can copy and paste when I am doing schematics - for a small schematic it is very quick. MS Paint is also great for putting (eg) a quick red circle on a photo to indicate the bit you're describing, or to annotate photos with text. Simple it may be, but it's a great little program and I wouldn't be without it.
LOL, I actually have a deerstalker! [For those who aren't familiar with the term, it's the type of hat worn by Sherlock Holmes.] If I have a particularly nasty problem that requires detective work, putting on the deerstalker puts me in the right frame of mind. OTOH, some problems require exploration. For those, I have a pith helmet.
What a great rule. I need to make a bronze plaque and put that above my workbench. So many times I dive into debugging without really thinking of the data I need to really figure things out. probably need to get a deerstalker hat to wear while debugging too come to think of it...
I like printf(). As long as you have a fast compiler+linker and a fast way to download a new image to your prototype hardware, printf() can be very effective. For one thing, you can customize printfs to the specific problem at hand -- you are not limited to what the debug vendor has imagined that you might need. The printfs tell you what the program is doing and the program "practically debugs itself" :-)
You can use conditional compilation to "comment them out", so that when [sic] the bug comes back three revisions later, just enable your printfs and "Bob's your uncle".
Here's the rule I've heard (and try to apply): All time spent writing debug and diagnostic code pays for itself -- it's never wasted.
David Patterson, known for his pioneering research that led to RAID, clusters and more, is part of a team at UC Berkeley that recently made its RISC-V processor architecture an open source hardware offering. We talk with Patterson and one of his colleagues behind the effort about the opportunities they see, what new kinds of designs they hope to enable and what it means for today’s commercial processor giants such as Intel, ARM and Imagination Technologies.