Tech Papers
Application Portability for 32-Bit Microcontrollers--Reality or Myth?
Microchip Technology
Erlendur KristjanssonApplication Note
December 2010
Comment
someEmbeddedGuy
Seemed to be a very lightweight editorial not really a "Paper"... I am ...
emmsys
I'm not surprised that this technical paper is from Microchip given that they ...
In November of 2008, ARM announced the availability of the Cortex Microcontroller Software Interface Standard (CMSIS). They claim that this will reduce the cost of designing software when creating projects for new devices or migrating existing software between Cortex-M based microcontrollers from different silicon vendors. This sounds very good, but is it valid? This paper investigates these claims to determine just how valid they are. This paper also looks at the components of a typical microcontroller and then see just what can or cannot be gained by adding an abstraction layer on top of the typical peripheral firmware libraries.
Rate this Content
|
|
|
|
|
Navigate to related information
charly5139
1/19/2011 10:03 AM EST
Yes, it's a myth...
Sign in to Reply
emmsys
1/26/2011 10:07 AM EST
I'm not surprised that this technical paper is from Microchip given that they decided to go with a Mips core for the PIC32 while almost everyone else went with a Cortex-M3. I doubt this paper would exist if the PIC32 was Arm based.
Sign in to Reply
someEmbeddedGuy
3/1/2011 3:26 PM EST
Seemed to be a very lightweight editorial not really a "Paper"... I am currently working with four different Cortex M3 processors from two vendors.
While the peripherals are a little different for each, I use the same compiler/debugger tool chain from IAR all of them. Because of that, my job is greatly simplified. (Tool familiarity, firmware build machine setup, tool cost savings, code generation is consistent as well as a host of other benefits.) Creating an abstraction layer for the unique peripheral differences is not that big of a project. In addition, portable code is do-able and not very difficult to write.
Sign in to Reply