• State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 22 subscribers
  • Views 3278 views
  • Users 0 members are here
Options
Related
How was your experience today?
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

i need to learn ARM programming

Robert Stanton

Hi,

Where should I begin, and what shall I do to learn programming ARM processors?

I have got a Discovery development board (STM32F0308),
and I am looking into learning this family of processors STM32F030.

Can anybody give me some advice?

I am pretty good at programming PIC microcontrollers in C, so I won't start from zero knowledge,......or should I forget everything and start afresh?

Thanks.

Parents
  • 0 in reply to Westonsupermare Pier

    Look for some reference code - preferably C and not assembler - and read it at the same time as you read the datasheet/user manual for the specific processor, to get a feel for how the program interacts with the peripherials.

    Then spend time reading through the processor documentation, so you get a feel for all the features supported by the processor.

    I'd leave it as a later stage, when you are already comfortable with writing and debugging C code with reading up on any assembler instructions. The Cortex family of chips are designed to allow even the startup file to just use C code, and there is no reason to switch to assembler unless you really do need to squeeze the last performance out of a chip because of cost.

    Just realize that not all reference code is written by good software developers, so it may not be as easy to read as it should have been. And it may not follow any recommendable coding styles. But the main goal with reference code is to complement the manuals, helping you find out what parts of the manuals that are relevant for different tasks.

Reply
  • 0 in reply to Westonsupermare Pier

    Look for some reference code - preferably C and not assembler - and read it at the same time as you read the datasheet/user manual for the specific processor, to get a feel for how the program interacts with the peripherials.

    Then spend time reading through the processor documentation, so you get a feel for all the features supported by the processor.

    I'd leave it as a later stage, when you are already comfortable with writing and debugging C code with reading up on any assembler instructions. The Cortex family of chips are designed to allow even the startup file to just use C code, and there is no reason to switch to assembler unless you really do need to squeeze the last performance out of a chip because of cost.

    Just realize that not all reference code is written by good software developers, so it may not be as easy to read as it should have been. And it may not follow any recommendable coding styles. But the main goal with reference code is to complement the manuals, helping you find out what parts of the manuals that are relevant for different tasks.

Children
No data