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...
"most commercial TCP/IP stacks."
and you can eat BigMac with BK seasoning too, :).
while entertaining, your argument does sound irrelevant to our discussion here.
I did not find Andy's argument entertaining one bit (in the case). He is simply right.
I meant of course, "I did not find Andy's argument entertaining one bit (in this case). He is simply right."
tamir, have you managed to find Per's writing that suggests that his caution against the use of OEM libraries "is due to the impact such libraries can have on the performance, stability and in the end, SAFETY of systems. "?
Just don't want to put words in Per's mouth, you know.
I already explained to you where, and even provided a quote.
tamir, are you talking about this "quote"
"For commercial use, you should have full access to the source code..."
which part of that talked about "performance, stability and in the end SAFETY"?
are you suggesting that having, or not having, access to the source code will hurt "the performance, stability and in the end, SAFETY of systems".
if so, how?
if not, what exactly did you mean?
try to focus on the end of the quote. namely, the expression that start with a "s" (a blatant clue, surely you agree). if you need more, just say so. Ahh, whatever, I'll give you one more: the next character is "o". now it's a no-brainer.
tamir, thanks for that clue, not.
if you cannot answer the questions, please just admit to it and we will excuse you on your behalf.
thanks in advance.
I never like this, but it is a software release date and a reason to celebrate to let get it on!
I meant: "I'm never like this, but it is a software release date and a reason to celebrate to let get it on!"
Mr Tamir.
What are you on { about } ?
release P004 rocks...!
Per did use the word, "dangerous".
But I don't think he was talking (particularly) about hazards to persons or property - I think he was talking about business risks.
As in, "there is a danger [business risk] that not having the source code may leave your project/product high & dry"
I think.
"I think he was talking about business risks."
nice try. I would give you an F for effort.
tamir, don't give up. don't EVER give up, :).
I'm not. Actually, now that RTX related problems have been solved (I hope; will know more the coming days when the feedback from the client(s) arrives) there is a real possibility to making it to the original deadline. Say, Ashley, are you related to "Jack Sprat" [or maybe I should say: ARE you "Jack Sprat"? Sorry Per for resuming the kindergarten for a while; I'm actually enjoying myself. this was a good day - have I mentioned release P004 yet? :-) ] ho and Ashley you forgot to grade me!
View all questions in Keil forum