How do I go about picking an architecture ? My first thoughts suggested Cortex M3 but the more I look into it the less sure I am.
Obviously I don't to go to the trouble of learning a new technology only to find that I've made a bad processor choice (ie nearly end of line). I've spent many hours looking at many websites and have yet to find any high-level stuff on choosing my first ARM device.
If there's one thing wrong with ARM its the almost infinite number of devices
I'm an embedded developer wanting to undertake my first ARM project, so I'm completely new to the ARM architecture. I want a low power device with serial, USB and some ADC channels.
if you are just trying to learn about the chips, it is a lot easier: the idiosyncrasy among the various ARM chips, even across vendors, is much less than for other chips, like PIC. that is especially true if you stay with a high-level language, like C.
however, if you start to use OEM libraries in your code, the program will become very platform dependent and far less portable, unless you rewrite the library functions for another chip - which is doable but can be burdensome.
if you are picking a chip for a particular design, I would prototype it on a dev board, figuring out how much resources you need and upon completion, pick the device that matches the current and future needs for that project.
It is always very dangerous to make use of manufacturer-specific libraries.
For commercial use, you should have full access to the source code, and a license that allows you to run the code on _any_ processor, even if different manufacturer or non-ARM architecture.
I'm not too fond of the libraries some manufacturers supplies with the intention to make it easy to move between different chips from them. It might sound good, but the main reason for the manufacturer-supplied libraries is to make it hard for you as customer to move to a different manufacturer. Having millions invested in a product and find that you can't move to a different manufacturer to save $2/device, or to get a working chip after the original chip stops being produced can be very interesting...
"I don't know exactly how long you have been in this business, but I have a wild guess...! No offese, of course."
I think I started with the mcs-48 family in the mid/late 1980s. then 8031/32 after that.
is your wild guess reasonably close?
"I think I started with the mcs-48 family in the mid/late 1980s. then 8031/32 after that."
So you were behind the curve, but playing it safe.
No.
Tapeer.
you must learn and stop being quick to jump with yo're conclusions.
i think you sometimes rate a book with what is in the next room.
Always yo're freind.
Zeusti.
lobotomized.
i am sad to hear of yo're condition.
please ask if yo need more support.
Zeusti
(you can read the abi during yo're recovery)
i am sad for u. do u know u r repeating ur self?
ur recovery has not started yet?
(knows you do not need to push r0 and r1)
i enjoy so much all the philisofical discusions with u. but i am busy and must work now.
plz. u lie down and relaxxxxx.
(job one, write good delay rootine)
I don't bother to read you messages anymore. I will only stop after you openly admit that you went through the lobotomy procedure, like this: "My name is zupeesti and I am lobotomized. Excuse my bad manners" (you can add typos were you like).
tamir, you sound like you have an anger mgmt issue.
calm down, please.
NO WAY, YOU @#!$#$%$@^#$%$#%$@%@%$@
:-)
"My verdict on their code was not positive. "
there are always bad OEM libraries, as there will always be bad programmers, or bad people.
But such facts don't mean all OEM libraries are bad, or all programmers are bad, or all people are bad.
if you don't believe me, take a look at Luminary's Stellaris and let me know if you think you can do better consistently.
"But such facts don't mean all OEM libraries are bad, or all programmers are bad, or all people are bad."
No one has made such a claim.
The question is just how much you are willing to trust the library supplier if you don't have access to the source code to verify the code quality and to incorporate fixes. Incorporating a bad library in a product can be lethal for a company, so the question is how much trust you have in the library supplier.
View all questions in Keil forum