Thanks for that Riccardo. I really enjoyed reading your review. I too like the way you made the comparrison to Arduino. I usually like to ask a question of a review. I can't find an aspect in your review that may have been missed
Thanks again
Thank you for the compliments I hope that TIpiccolo kit would arrive
to do another special review!!! ;P
Best regards
Riccardo
Thank you for the compliments I hope that TIpiccolo kit would arrive
to do another special review!!! ;P
Best regards
Riccardo
Good review thanks!
I watched the mbed webinar a few weeks back, and so was aware that it was really for proof of concept and rapid prototyping, rather than building beta products or debugging.
If you get a chance, maybe you could write another review, sometime, detailing the development process - and the quantity/quality of libraries etc that are available, and how easy do you think it would be to go from mbed to production? Would it require a total re-work, or can you take the code with you from concept to reality?
Good review!
The only advantage that pops into my mind is about always up to date libraries. As you don't need to download them, your source code will be based on the latest libraries available but is it really worth it? I mean the down side is that you have to be connected to the net all the time as Glenn said. I sometimes enjoy working on my code at a cafe or during my train ride to my lab where I won't have internet connection mostly (or at least a free one). Oh and another advantage that I can think of: As compiler is web based, you can use it with Windows and Linux without any problems, am I right?
If you want to use mbed for production I think you need to switch to pure C libraries coming from NXP
this is for 2 reasons:
- better control of the bug of the libraries
- possible optimization of the code
Some other aspects bring me to think to avoid the mbed fo production project:
- programming procedure is not so suitable...you need pc, usb, etc...nowdays the best way is for sure the
use of a bootloader to flash the microcontroller remotly...
- the debugging almost impossibile doesn't allow an easy devolopment of the code...especially when you need
to manage multitask code like FSM or RTOS...sometime the emulation is essential!!! Otherise the is some trick
to debug all register throught serial port with some deamons that you can include as a mini OS but it's needed
a lot of time to develop them...
What bugs have you found in the core mbed libraries, Richard? I have found none so far. I found a minor bug in one of the cookbook examples, but that's not surprising.
no i didn't want to say that mbed library contains some bugs
I wanted to say just that i you want to use somenthing in a production
chain, you need to be sure at 100% of your basic libraries...
In my opinion I'd prefer to use this 3 opensource altenative for an ARM architecture:
Good hardware bur programming in .NET sdk should be dangerous because you loose any connection with the real hw
http://www.bugblat.com/products/cor.html
http://leaflabs.com/devices/maple/
Both architecture based on STM32 arm cortex m3...
I think it would be in NXPs best interest to make this a Production ready module, otherwise interest will drop in it quickly.
Profesionals won't need to use it and hobbiest won't want to use it.
Thanks for explaining, Riccardo, and for the links to the other systems.
It looks as if the ARM is entering the hobbyist mainstream.