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.
"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 @#!$#$%$@^#$%$#%$@%@%$@
:-)
"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.
just a little foot note: you do know that this only applies to THUMB mode, don't you? otherwise, the following would not have appeared in the ATPCS (ARM-Thumb Procedure Call Standard) document, surely you agree?
maybe you have skipped this while browsing your documentation:
infocenter.arm.com/.../DUI0056.pdf
see page 24, paragraph 2.2.1
quote:
The following register usage applies in all variants of the ATPCS except where otherwise stated. To comply with the ATPCS you must follow these rules: Use registers r0-r3 to pass parameter values into routines, and to pass result values out. You can refer to r0-r3 as a1-a4 to make this usage apparent. See Parameter passing on page 2-9. Between subroutine calls you can use r0-r3 for any purpose. A called routine does not have to restore r0-r3 before returning. A calling routine must preserve the contents of r0-r3 if it needs them again....
however, if you can find a similar quote for ARM mode, in which I have written my code - you are right (but I doubt you will).
I forgot to highlight the following:
"A called routine does not have to restore r0-r3 before returning". but this is only true when complying with ATPCS. it is certainly not true (as far as I know) when running in ARM mode.