A tourist walked into a pet shop and was looking at the animals on display. While he was there, another customer walked in and said to the shopkeeper: “I’ll have a C-monkey please”.
The shopkeeper nodded, went over to a cage at the side of the shop, and took out a monkey. He fit a collar and leash and handed it to the customer, saying “That’ll be $5000”.
The customer paid and walked out with his monkey.
Startled, the tourist went over to the shopkeeper and said: “That was a very expensive monkey, most of them are only a few hundred dollars. Why did it cost so much?”
Finally, the new Sumo robot is assembled, and up and moving :-):
When I create a new Processor Expert project for a board I already have the components configured, then an easy way to transfer components from one project to another is to copy-paste the components. In the ‘source’ project I select the components I want to use, choose Copy (or CTRL+C shortcut on Windows):
Unlike CodeWarrior, the Kinetis Design Studio (at least in V1.1.1) does not offer a choice between C and C++ projects. That makes sense with the GNU ARM Eclipse plugins, other than the CodeWarrior gcc integration, there is no need for setting up a special tool chain for C++ (see “Compiling C Files with GNU ARM G++“). While this is great, things are not perfect yet, so I’m providing in this post the information needed to properly setup a C++ project with Kinetis Design Studio V1.1.1.
Sometimes I think that a problem should be solvable in a few minutes, and then it turns out that it lingers around for months. Very, very frustrating! Such a thing is getting the USB 4.1.1 stack running on the FRDM-K64F board. I have that board since April 2014, and it took me 7 months to get the FSL USB stack running on it :-(.
I’m a believer that engineers not only need to act in a professional and ethical way, but they have to have some sense of humor too. For that reason I have the tradition to tell the class (almost) every semester week a joke or fun story with an engineering background :-). And to make it stick, at the exams there is always one bonus questions about these engineering jokes. Some of the jokes or fun stories came from my daughters, some from my former students, and some I have found myself. I have asked to share the fun story from this week, so here we go….
When I started the McuOnEclipse project back in 2012, I did not expect that it would create that much of attention :-). So far I’m sharing the project files on GitHub (see “McuOnEclipse goes Git“). GitHub is excellent for sharing sources, but not a good way to share release (binary) files. It is somewhat ok for small/few files, and initially that worked well for the few Processor Expert files (see “Processor Expert Component *.PEupd Files on GitHub“). However, with the amount of components and binary releases, the GitHub repository gets bloated. So I’m performing some maintenance work, and so I’m moving binary releases to a new McuOnEclipse SourceForge site.
The weekend plan is to cruise through the alps, sitting on top of two-cylinder boxer engine. And it begins with a beautiful starting fire….
Happy Firing 🙂