AVR Embedded C Tutorial
For novices: yet another Embedded C Programming Tutorial based on 8-bit AVR micro-controllers, using Microchip/Atmel Studio (not Arduino IDE).
Here is a self-study tutorial intended as a first course in embedded micro-controller programming using a sub-set of the C language called “C-less” (C language essentials). “C-less” was conceived to provide enough of C to develop “real-world” applications, while avoiding unnecessary complex constructs which novices might find overwhelming.
The software development environment (PC application) used in this tutorial is Microchip/Atmel Studio IDE. This is a free download from Microchip's website. Don't be intimidated by Atmel Studio. Although it is a far more professional IDE than Arduino, it is not much more difficult to learn.
Coding examples and exercises are targeted towards Atmel 8-bit AVR micro-controller devices, specifically the ATmega328P, as fitted on the author’s “AVR-BED / Nano" and Microchip "AVR X-mini" boards. Arduino Uno and Nano boards are also supported. Appendix A of the tutorial describes various options for a suitable hardware platform.
Many of the program examples in this tutorial use a pre-built function library to facilitate access to peripheral devices such as displays, timers, push-buttons, analogue inputs, UARTs, etc. This approach avoids the need for a detailed understanding of peripheral driver code in the early stages of learning when the focus is on C language syntax.
Prerequisite Knowledge & Skills:
The course assumes a rudimentary knowledge of Boolean logic and binary arithmetic. Practical skills in digital electronic circuits and systems incorporating micro-controllers, peripheral devices, etc, will be beneficial to learning embedded programming.
The software development environment (PC application) used in this tutorial is Microchip/Atmel Studio IDE. This is a free download from Microchip's website. Don't be intimidated by Atmel Studio. Although it is a far more professional IDE than Arduino, it is not much more difficult to learn.
Coding examples and exercises are targeted towards Atmel 8-bit AVR micro-controller devices, specifically the ATmega328P, as fitted on the author’s “AVR-BED / Nano" and Microchip "AVR X-mini" boards. Arduino Uno and Nano boards are also supported. Appendix A of the tutorial describes various options for a suitable hardware platform.
Many of the program examples in this tutorial use a pre-built function library to facilitate access to peripheral devices such as displays, timers, push-buttons, analogue inputs, UARTs, etc. This approach avoids the need for a detailed understanding of peripheral driver code in the early stages of learning when the focus is on C language syntax.
Prerequisite Knowledge & Skills:
The course assumes a rudimentary knowledge of Boolean logic and binary arithmetic. Practical skills in digital electronic circuits and systems incorporating micro-controllers, peripheral devices, etc, will be beneficial to learning embedded programming.
Diskussion (3 Kommentare)
pbaak vor 2 Jahren
Referring to an earlier discussion:
There is no obligation for any nomenclature in this area. Having said so, let's have a look at Kernighan and Ritchie, being the initiators of C. In their book "The C programming Language" 2nd edition, Ansi C, p.26, it is stated that we "generally use parameter to indicate variables in the parenthesized list of a function". However, it is also stated that "formal argument and actual argument are sometimes used for the same distinction". This widely opens the door for confusion. Better they should have firmly declared the nomenclature in C.
An argument is a means ("-mentum") of claiming or stating ("arguere") something that one can bring into a dispute or conversation. "Argument" therefore seems the right word when calling a function.
A parameter is always formal; it describes what will happen if the associated function is called. At first, it has not even a retrievable value and is thus beside ("para") any value ("metron"). Only when the value of an argument has been copied into a parameter, it becomes a (local) variabele. "Parameter" therefore seems the right word when defining or declaring a function.
In years I have seen used "actual parameter" and "formal argument"; I even heard a teacher swapping the use of argument and parameter altogether. This of course leads to confusion when explaining issues as giving variables and pointers and arrays at the same time to functions. The students, even those who understood things before, did no longer understand things afterwards.
There is no obligation for any nomenclature in this area. Having said so, let's have a look at Kernighan and Ritchie, being the initiators of C. In their book "The C programming Language" 2nd edition, Ansi C, p.26, it is stated that we "generally use parameter to indicate variables in the parenthesized list of a function". However, it is also stated that "formal argument and actual argument are sometimes used for the same distinction". This widely opens the door for confusion. Better they should have firmly declared the nomenclature in C.
An argument is a means ("-mentum") of claiming or stating ("arguere") something that one can bring into a dispute or conversation. "Argument" therefore seems the right word when calling a function.
A parameter is always formal; it describes what will happen if the associated function is called. At first, it has not even a retrievable value and is thus beside ("para") any value ("metron"). Only when the value of an argument has been copied into a parameter, it becomes a (local) variabele. "Parameter" therefore seems the right word when defining or declaring a function.
In years I have seen used "actual parameter" and "formal argument"; I even heard a teacher swapping the use of argument and parameter altogether. This of course leads to confusion when explaining issues as giving variables and pointers and arrays at the same time to functions. The students, even those who understood things before, did no longer understand things afterwards.
Antworten
M J Bauer vor 2 Jahren
Thank you for clarifying the distinction between the terms "argument" and "parameter". To most programmers, this is of academic interest only, I guess, and so most will continue to favour either one term or the other, or to use the terms interchangeably. We could also get into a discussion to distinguish between the terms "declaration" and "definition". You can find my personal email address in the tutorial and in the C-less manual. I am curious to know your background.
Antworten
Mehr anzeigen
1 Kommentar(e)
pbaak vor 2 Jahren
An argument is not the same as a parameter, contrary to stated in C less reference p. 7.
Antworten
M J Bauer vor 2 Jahren
Hello, pbaak. Thanks for your interest in my "C-less Reference Manual". You may be right... there could well be some technical difference between the terms "argument" and "parameter" as applied to function arguments. However, the manual does not state that "an argument is the same as a parameter". It states that an argument is "also known as a parameter", which may or may not be correct usage of the term. I am curious to know how you differentiate between these two terms, when used in this context. Cheers - Mike
Antworten
Mehr anzeigen
1 Kommentar(e)
Updates vom Autor
M J Bauer vor 2 Jahren
Their course is targeted toward beginners "without much experience in electronics and programming languages". The attraction of Arduino is that it hides the complexity of microcontroller on-chip peripherals and the program code necessary to drive them. While this is wonderful at the beginner level, there is no "upgrade path" to a more in-depth understanding.
My AVR tutorial is also aimed at beginners, initially using a code library to simplify the handling of peripherals. However, the tutorial gradually introduces more of the inner workings of the ATmega328 MCU peripherals and the library functions which drive them. After working through the tutorial, a student should have a solid foundation on which to advance to a higher level.
So why not "man up" and give Arduino the flick? Learn to use a professional IDE (Microchip Studio IDE for AVR and SAM Devices) and understand how to drive MCU peripherals (timers, etc) from reading the datasheet!
Note 1: Training platforms used in the tutorial can be assembled for much lower expense than the Elektor-Arduino training board. You will also have the satisfaction of building it yourself. (The option based on Microchip's AVR "X-mini" board involves a minimal amount of soldering.)
Note 2: Training platforms based on the Arduino Nano or Microchip AVR "X-mini" board do not require any additional programming tool to install program code into the MCU. (See PDF doc in 'Project Elements / Other".)