Skip to content

USAGE and README typo fixes #60

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

USAGE and README typo fixes #60

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# AVRA

*Assember for the Atmel AVR microcontroller family*
*Assembler for the Atmel AVR microcontroller family*

AVRA is an assembler for Atmel AVR microcontrollers, and it is almost
compatible with Atmel's own assembler, AVRASM32. AVRA is written in C99.
Expand All @@ -9,7 +9,7 @@ compatible with Atmel's own assembler, AVRASM32. AVRA is written in C99.

There are some differences between the original Atmel assembler AVRASM32 and
AVRA. Basically, AVRA is designed to replace AVRASM32 without special changes
in your current Atmel AVR Studio enviroment. Command line options have been
in your current Atmel AVR Studio environment. Command line options have been
adapted as far as possible. Jumping to fault-containing lines directly by
double-clicking on the error message in the output window does work as with
AVRASM32.
Expand Down Expand Up @@ -39,7 +39,7 @@ increase the ability to reuse code, e.g., build your own library.

#### Debugging support

AVRA creates a coff file everytime assembly is sucessful. This
AVRA creates a coff file every time assembly is successful. This
file allows AVR Studio or any coff compatible debugger to simulate
or emulate the program.

Expand Down
18 changes: 9 additions & 9 deletions USAGE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,10 @@ compiled version of the file in Intel HEX format at `mysource.S.hex`. You can
control the output filename with `-o`. See `--help` for more options (not all
options work).

## Warning Supression
## Warning Suppression

There is a possibility to supress certain warnings.
Currently only register reassignment warnings can be supressed:
There is a possibility to suppress certain warnings.
Currently only register reassignment warnings can be suppressed:

avra -W NoRegDef

Expand All @@ -34,7 +34,7 @@ Now `network` is set to the value 1. You can also define names without values:
Both versions are equivalent, as AVRA will implicitly define `network` to be 1
in the second case. (Although, if you really want `network` to be 1, you
should use the first version.) You may want to assemble a specific part of your
code depeding on a define or switch setting. You can test your defined word on
code depending on a define or switch setting. You can test your defined word on
existence (`.ifdef` and `.ifndef`) as well as on the value it represents. The
following code shows a way to prevent error messages due to testing undefined
constants:
Expand Down Expand Up @@ -69,7 +69,7 @@ particular value has not been previously set:

### Directives `.nolist` and `.list`

The ouput to the list file can be paused and resumed by the `.nolist` and
The output to the list file can be paused and resumed by the `.nolist` and
`.list` directives. After AVRA discovers a `.nolist` while assembling, it
stops output to the list file. After a `.list` directive is detected, AVRA
continues the normal list file output.
Expand Down Expand Up @@ -131,7 +131,7 @@ macro parameters. See the following examples.

### Automatic Type Conversion For Macros

Values representing more than 8 bits are usualy kept in a set of byte wide
Values representing more than 8 bits are usually kept in a set of byte wide
registers. To simplify 16 bit operations, words can be written as `r16:r17`. In
this example, `r16` contains the most significant byte and register `r17`
contains the least significant byte. In the same way, a 24 bit value stored
Expand Down Expand Up @@ -168,7 +168,7 @@ To simplify the examples below, we redefine some registers:
.def w = r20 ; working registers
.def v = r21

If we substract the 16 bit value `c:d` from `a:b`, we usually have to use the
If we subtract the 16 bit value `c:d` from `a:b`, we usually have to use the
following command sequence:

sub b,d
Expand Down Expand Up @@ -278,7 +278,7 @@ Another example of macro overloading follows.


; This writes 9999 into the memory at 'counter' using only the working
; register for transfering the values.
; register for transferring the values.

poke [counter,w:w,9999]

Expand Down Expand Up @@ -379,5 +379,5 @@ or `.dw` for data in the code or eeprom segments.

If you get an "internal assembler error" please contact the project maintainer
via the [GitHub issue tracker](https://github.com/Ro5bert/avra/issues). Be sure
to include a code example and a description of your working enviroment.
to include a code example and a description of your working environment.