This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How do you choose an ARM family

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.

Parents
  • "I have never once said that manufacturers likes to give out their libraries with full source and carte blanche licenses. But I have claimed that the main reason for such libraries is to bind you harder to their products."

    Now I use my MCU vendors brain:
    Creating the libraries often involves many man years of coding, so why giving it away to be used by competitors. Why would you not want to try binding customers to your chips if at all possible. That is viable business practice as long as you help your own customers.

    Switching brain to MCU user:
    It sucks to be stuck with one vendor, particularly using ARM where it would be rather easy to switch from A to N to S or T. So if I find a real open source I will probably go for that one.

    Impair, an attempt:
    If you find what you are looking for with one vendor and the chips do what they should and the price is right, don't argue, go for it and get work done.

    Cheers, Robert
    For the original poster there is a site that gathers articles related to Cortex-M
    mcu-related.com/.../35-cortex-m3

Reply
  • "I have never once said that manufacturers likes to give out their libraries with full source and carte blanche licenses. But I have claimed that the main reason for such libraries is to bind you harder to their products."

    Now I use my MCU vendors brain:
    Creating the libraries often involves many man years of coding, so why giving it away to be used by competitors. Why would you not want to try binding customers to your chips if at all possible. That is viable business practice as long as you help your own customers.

    Switching brain to MCU user:
    It sucks to be stuck with one vendor, particularly using ARM where it would be rather easy to switch from A to N to S or T. So if I find a real open source I will probably go for that one.

    Impair, an attempt:
    If you find what you are looking for with one vendor and the chips do what they should and the price is right, don't argue, go for it and get work done.

    Cheers, Robert
    For the original poster there is a site that gathers articles related to Cortex-M
    mcu-related.com/.../35-cortex-m3

Children
No data