Programming PIC Micro Controllers in BASIC
Programming PIC Micro Controllers in BASIC
Table of Contents
● Preface
● Chapter 1: The Basics
● Chapter 2: Elements of BASIC Language
● Chapter 3: Operators
● Chapter 4: Control Structures
● Chapter 5: Built-in and Library Routines
● Chapter 6: Examples with PIC Integrated Peripherals
● Chapter 7: Examples with Displaying Data
● Chapter 8: Examples with Memory and Storage Media
● Chapter 9: Communications Examples (under construction)
● Appendix A: mikroBasic IDE
Preface
In order to simplify things and crash some prejudices, I will allow myself to give you
some advice before reading this book. You should start reading it from the chapter that
interests you the most, in any order you find suitable. As the time goes by, read the
parts you may need at that exact moment. If something starts functioning without you
knowing exactly how, it shouldn’t bother you too much. Anyway, it is better that your
program works than that it doesn’t. Always stick to the practical side of life. Better to
finish the application on time, make it reliable and, of course, get paid for it as well as
possible.
In other words, it doesn’t matter if the exact manner in which the electrons move
within the PN junctions escapes your knowledge. You are not supposed to know the
whole history of electronics in order to assure the income for you or your family. Do
not expect that you will find everything you need in a single book, though. The
information are dispersed literally everywhere around us, so it is necessary to collect
them diligently and sort them out carefully. If you do so, the success is inevitable.
With all my hopes of having done something worthy investing your time in.
Yours,
Nebojsa Matic
mikroElektronika Recommends
EasyPIC 2
Development system for PIC MCUs
mikroBasic
Advanced BASIC compiler for PIC
“PIC Microcontrollers”
On-line book, 3rd edition
To Reader’s Knowledge
The book was prepared with due care and attention, however the publisher does not
accept any responsibility neither for the exactness of the information published
therein, nor for any consequences of its application.
PIC, PIC, PICmicro, and MPLAB are registered and protected trademarks of the Microchip
Technology Inc. USA. Microchip logo and name are the registered tokens of the Microchip
Technology. mikroBasic is a registered trade mark of mikroElektronika. All other tokens
mentioned in the book are the property of the companies to which they belong.
mikroElektronika © 1998 - 2004. All rights reserved. If you have any questions, please
contact our office.
● Introduction
● 1.1 Why BASIC?
● 1.2 Choosing the right PIC for the task
● 1.3 A word about code writing
● 1.4 Writing and compiling your program
● 1.5 Loading program to microcontroller
● 1.6 Running the program
● 1.7 Troubleshooting
Introduction
Simplicity and ease which higher programming languages bring in, as well as broad
application of microcontrollers today, were reasons to incite some companies to adjust and
upgrade BASIC programming language to better suit needs of microcontroller
programming. What did we thereby get? First of all, developing applications is faster and
easier with all the predefined routines which BASIC brings in, whose programming in
assembly would take the largest amount of time. This allows programmer to concentrate on
solving the important tasks without wasting his time on, say, code for printing on LCD
display.
To avoid any confusion in the further text, we need to clarify several terms we will be using
frequently throughout the book:
Programming language is a set of commands and rules according to which we write the
program. There are various programming languages such as BASIC, C, Pascal, etc. There is
plenty of resources on BASIC programming language out there, so we will focus our
Compiler is a program run on computer and its task is to translate the original BASIC code
into language of zeros and ones that can be fed to microcontroller. The process of translation
of BASIC program into executive HEX code is shown in the figure below. The program
written in BASIC and saved as file program.pbas is converted by compiler into
assembly code (program.asm). The generated assembly code is further translated into
executive HEX code which can be written to microcontroller memory.
Programmer is a device which we use to transfer our HEX files from computer to
microcontroller memory.
BASIC is still considered by many PC users to be the easiest programming language to use.
Nowadays, this reputation is being shifted to the world of microcontrollers. BASIC allows
faster and much easier development of applications for PIC compared to the Microchip’s
assembly language MPASM. When writing the code for MCUs, programmers frequently
deal with the same issues, such as serial communication, printing on LCD display,
generating PWM signals, etc. For the purpose of facilitating programming, BASIC provides
a number of built-in and library routines intended for solving these problems.
As far as the execution and program size are in question, MPASM has a small advantage in
respect with BASIC. This is why there is an option of combining BASIC and assembly code
— assembly is commonly used for parts of program in which execution time is critical or
same commands are executed great number of times. Modern microcontrollers, such as PIC,
execute instructions in a single cycle. If microcontroller clock is 4MHz, then one assembly
instruction requires 250ns x 4 = 1us. As each BASIC command is technically a sequence of
assembly instructions, the exact time necessary for its execution can be calculated by simply
summing up the execution times of constituent assembly instructions.
Currently, the best choice for application development using BASIC are: the famous
PIC16F84, PIC16F87x, PIC16F62x, PIC18Fxxx. These controllers have program memory
built on FLASH technology which provides fast erasing and reprogramming, thus allowing
fast debugging. By a single mouse click in the programming software, microcontroller
program can be instantly erased and then reloaded without removing chip from device. Also,
program loaded in FLASH memory can be stored after the power is off. Beside FLASH
memory, microcontrollers of PIC16F87x and PIC16F84 series also contain 64-256 bytes of
internal EEPROM memory, which can be used for storing program data and other
parameters when power is off. BASIC features built-in EEPROM_Read and
EEPROM_Write instructions that can be used for loading and saving data to EEPROM.
Older PIC microcontroller families (12C67x, 14C000, 16C55x, 16C6xx, 16C7xx, and
16C92x) have program memory built on EPROM/ROM technology, so they can either be
programmed only once (OTP version with ROM memory) or have a glass window (JW
version with EPROM memory) which allows erasing by few minutes exposure to UV light.
OTP versions are usually cheaper and are a natural choice for manufacturing large series of
products.
In order to have complete information about specific microcontroller in the application, you
should get the appropriate Data Sheet or Microchip CD-ROM.
The program examples worked out throughout the book are mostly to be run on
the microcontrollers PIC16F84 or PIC6F877, but with minor adjustments, can
be run on any other PIC microcontroller.
Technically, any text editor that can save program file as pure ASCII text (without special
symbols for formatting) can be used for writing your BASIC code. Still, there is no need to
do it “by hand” — there are specialized environments that take care of the code syntax, free
the memory and provide all the necessary tools for writing a program.
mikroBasic IDE includes highly adaptable Code Editor, fashioned to satisfy needs of both
novice users and experienced programmers. Syntax Highlighting, Code Templates, Code &
Parameter Assistant, Auto Correct for common typos, and other features provide
comfortable environment for writing a program.
If you had no previous experience with advanced IDEs, you may wonder what Code and
Parameter Assistants do. These are utilities which facilitate the code writing. For example, if
you type first few letter of a word in Code Editor and then press CTRL+SPACE, all valid
identifiers matching the letters you typed will be prompted to you in a floating panel. Now
you can keep typing to narrow the choice, or you can select one from the list using keyboard
arrows and Enter.
In combination with comprehensive help, integrated tools, extensive libraries, and Code
Explorer which allows you to easily monitor program items, all the necessary tools are at
hand.
The first step is to write our code. Every source file is saved in a single text file with
extension .pbas. Here is an example of one simple BASIC program, blink.pbas.
program LED_Blink
main:
end.
When the program is completed and saved as .pbas file, it can be compiled by clicking on
Compile Icon (or just hit CTRL+F9) in mikroBasic IDE. The compiling procedure takes
place in two consecutive steps:
1. Compiler will convert .pbas file to assembly code and save it as blink.asm file.
2. Then, compiler automatically calls assembly, which converts .asm file into
executable HEX code ready for feeding to microcontroller.
You cannot actually make the difference between the two steps, as the process is completely
automated and indivisible. In case of syntax error in program code, program will not be
compiled and HEX file will not be generated. Errors need to be corrected in the original .
pbas file and then the source file may be compiled again. The best approach is to write and
test small, logical parts of the program to make debugging easier.
MCL file (mikro compile library) is created for each module you have included in the
project. In the process of compiling, .mcl files will be linked together to output asm, lst and
hex files. If you want to distribute your module without disclosing the source code, you can
send your compiled library (file extension .mcl). User will be able to use your library as if
he had the source code. Although the compiler is able to determine which routines are
implemented in the library, it is a common practice to provide routine prototypes in a
separate text file.
HEX file is the one you need to program the microcontroller. Commonly, generated HEX
will be standard 8-bit Merged Intel HEX format, accepted by the vast majority of the
programming software. The programming device (programmer) with accessory software
installed on PC is in charge of writing the physical contents of HEX file into the internal
memory of a microcontroller. The contents of a file blink.hex is given below:
:100000000428FF3FFF3FFF3F031383168601FF30A5
:10001000831286000630F000FF30F100FF30F2005E
:10002000F00B13281A28F10B16281928F20B1628A2
:10003000132810281A30F000FF30F100F00B2128AF
:100040002428F10B21281E284230F000F00B26282E
:1000500086010630F000FF30F100FF30F200F00BB7
:1000600032283928F10B35283828F20B3528322868
:100070002F281A30F000FF30F100F00B4028432801
:10008000F10B40283D284230F000F00B45280428B1
:100090004828FF3FFF3FFF3FFF3FFF3FFF3FFF3F3E
:02400E007A3FF7
:00000001FF
Beside loading a program code into programming memory, programmer also configures the
target microcontroller, including the type of oscillator, protection of memory against
reading, watchdog timer, etc. The following figure shows the connection between PC,
programming device and the MCU.
Note that the programming software should be used only for the communication with the
programming device — it is not suitable for code writing.
Oscillator can be 4MHz crystal and either two 22pF capacitors or the ceramic resonator of
the same frequency (ceramic resonator already contains the mentioned capacitors, but unlike
oscillator has three termination instead of only two). The rate at which the microcontroller
operates, i.e. the speed at which the program runs, depends heavily on the oscillator
frequency. During the application development, the easiest thing to do is to use the internal
reset circuit — MCLR pin is connected to +5V through a 10K resistor. Below is the scheme
of a rectifier with LM7805 circuit which gives the output of stable +5V, and the minimal
configuration relevant for the operation of a PIC microcontroller.
After the supply is brought to the circuit previously shown, PIC microcontroller should look
animated, and the LED diode should blink once every second. If the signal is completely
missing (LED diode does not blink), then check if +5V is present at all the relevant pins of
PIC.
1.7 Troubleshooting
● Check whether the MCLR pin is connected to +5V, over reset circuit, or simply with
10K resistor. If the pin remains disconnected, its level will be “floating” and it may
work sometimes, but it usually won’t. Chip has power-on-reset circuit, so the
appropriate external pull-up resistor on MCLR pin should be sufficient.
● Check whether the connection with the resonator is stable. For most PIC
microcontrollers to begin with 4MHz resonator is well enough.
● Check the supply. PIC microcontroller consumes very little energy but the supply
needs to be well filtrated. At the rectifier output, the current is direct but pulsating,
and as such is not suitable for the supply of microcontroller. To avoid the pulsating,
the electrolytic capacitor of high capacitance (e.g. 470 mF) is placed at the rectifier
output.
● If PIC microcontroller supervises devices that pull a lot of energy, they may provoke
enough malfunctioning on the supply lines to cause the microcontroller start behaving
somewhat strangely. Even seven-segmented LED display may well induce tension
drops (the worst scenario is when all the digits are 8, when LED display needs the
most power), if the source itself is not capable to procure enough current (e.g. 9V
battery).
● Some PIC microcontrollers feature multi-functional I/O pins, for example
PIC16C62x family (PIC16C620, 621 and 622). Controllers of this family are
provided with analog comparators on port A. After putting those chips to work, port
A is set to analog mode, which brings about the unexpected behavior of the pin
functions on the port. Upon reset, any PIC with analog inputs will show itself in
analog mode (if the same pins are used as digital lines they need to be set to digital
mode). One possible source of troubles is that the fourth pin of port A exhibits
singular behavior when it is used as output, because the pin has open collectors output
instead of usual bipolar state. This implies that clearing this pin will nevertheless set
it to low level, while setting the pin will let it float somewhere in between, instead of
setting it to high level. To make the pin behave as expected, the pull-up resistor was
placed between RA4 and 5V. Its magnitude is between 4.7K and 10K, depending on
the current necessary for the input. In this way, the pin functions as any other input
pin (all pins are output after reset).
More problems are to be expected if you plan to be seriously working with PIC. Sometimes
the thing seems like it is going to work, but it just won’t, regardless of the effort. Just
remember that there is always more than one way to solve the problem, and that a different
approach may bring solution.
PIC, PIC, PICmicro, and MPLAB are registered and protected trademarks of the Microchip
Technology Inc. USA. Microchip logo and name are the registered tokens of the Microchip
Technology. mikroBasic is a registered trade mark of mikroElektronika. All other tokens mentioned
in the book are the property of the companies to which they belong.
mikroElektronika © 1998 - 2004. All rights reserved. If you have any questions, please contact our
office.
● Introduction
● 2.1 Identifiers
● 2.2 Operators
● 2.3 Expressions
● 2.4 Instructions
● 2.5 Data Types
● 2.6 Constants
● 2.7 Variables
● 2.8 Symbols
● 2.9 Directives
● 2.10 Comments
● 2.11 Labels
● 2.12 Procedures and Functions
● 2.13 Modules
Introduction
This chapter deals with the elements of BASIC language and the ways to use them efficiently. Learning how to
program is not complicated, but it requires skill and experience to write code that is efficient, legible, and easy to
handle. First of all, program is supposed to be comprehensible, so that the programmer himself, or somebody else
working on the application, could make necessary corrections and improvements. We have provided a code sample
written in a clear and manifest way to give you an idea how programs could be written:
'******************************************************************************
' microcontroller : P16F877A
'
' Project: Led_blinking
' This project is designed to work with PIC 16F877A;
' with minor adjustments, it should work with any other PIC MCU.
'
' The code demonstrates blinking of diodes connected to PORTB.
' Diodes go on and off each second.
'******************************************************************************
program LED_Blinking
Through clever use of comments, symbols, labels and other elements supported by BASIC, program can be rendered
considerably clearer and more understandable, offering programmer a great deal of help.
Also, it is advisable to divide larger programs into separate logical entities (such as routines and modules, see below)
which can be addressed when needed. This also increases reusability of code.
Names of routines and labels indicating a program segment should make some obvious sense. For example, program
segment that swaps values of 2 variables, could be named "Swap", etc.
2.1 Identifiers
Identifiers are names used for referencing the stored values, such as variables and constants. Every program, module,
procedure, and function must be identified (hence the term) by an identifier.
Valid identifier:
1. Must begin with a letter of English alphabet or possibly the underscore (_)
2. Consists of alphanumeric characters and the underscore (_)
3. May not contain special characters:
~ ! @ # $ % ^ & * ( ) + ` - = { } [ ] : " ; ' < > ? , . / | \
4. Can be written in mixed case as BASIC is case insensitive; e.g. First, FIRST, and fIrST are an
equivalent identifier.
Elements ignored by the compiler include spaces, new lines, and tabs. All these elements are collectively known as
the “white space”. White space serves only to make the code more legible – it does not affect the actual compiling.
Several identifiers are reserved in BASIC, meaning that you cannot use them as your own identifiers (e.g. words
function, byte, if, etc). For more information, please refer to the list of reserved words. Also, BASIC has a
number of predefined identifiers which are listed in Chapter 4: Instructions.
2.2 Operators
BASIC language possesses set of operators which is used to assign values, compare values, and perform other
operations. The objects manipulated for that purpose are called operands (which themselves can be variables,
constants, or other elements).
Operators in BASIC must have at least two operands, with an exception of two unary operators. They serve to create
expressions and instructions that in effect compose the program.
1. Arithmetic Operators
2. Boolean Operators
3. Logical (Bitwise) Operators
4. Relation Operators (Comparison Operators)
2.3 Expressions
Expression is a construction that returns a value. BASIC syntax restricts you to single line expressions, where
carriage return character marks the end of the expression. The simplest expressions are variables and constants,
while more complex can be constructed from simpler ones using operators, function calls, indexes, and typecasts.
Here is one simple expression:
You need to pay attention that the sum must be within the range of variable A in order to avoid the overflow and
therefore the evident computational error. If the result of the expression amounts to 428, and the variable A is of
byte type (having range between 0 and 255), the result accordingly obtained will be 172, which is obviously wrong.
2.4 Instructions
Each instruction determines an action to be performed. As a rule, instructions are being executed in an exact order in
which they are written in the program. However, the order of their execution can be changed by means of jump,
routine call, or an interrupt.
if Time = 60 then
Instruction if..then contains the conducting expression Time = 60 composed of two operands, variable
Time, constant 60 and the comparison operator (=). Generally, instructions may be divided into conditional
instructions (decision making), loops (repeating blocks), jumps, and specific built-in instructions (e.g. for
accessing the peripherals of microcontroller). Instruction set is explained in detail in Chapter 4: Instructions.
Type determines the allowed range of values for variable, and which operations may be performed on it. It also
determines the amount of memory used for one instance of that variable.
Array, which represent an indexed collection of elements of the same type, often called the base type. Base type can
be any simple type.
String represents a sequence of characters. It is an array that holds characters and the first element of string holds
the number of characters (max number is 255).
Sign is important attribute of data types, and affects the way variable is treated by the compiler.
byte 0 .. 255
word 0 .. 65535
2.6 Constants
Constant is data whose value cannot be changed during the runtime. Every constant is declared under unique name
which must be a valid identifier. It is a good practice to write constant names in uppercase.
If you frequently use the same fixed value throughout the program, you should declare it a constant (for example,
maximum number allowed is 1000). This is a good practice since the value can be changed simply by modifying the
declaration, instead of going trough the entire program and adjusting each instance manually. As simple as this:
Constants can be declared in decimal, hex, or binary form. Decimal constants are written without any prefix.
Hexadecimal constants begin with a sign $, while binary begin with %.
It is important to understand why constants should be used and how this affects the MCU. Using a constant in a
program consumes no RAM memory. This is very important due to the limited RAM space (PIC16F877 has 368
locations/bytes).
2.7 Variables
Variable is data whose value can be changed during the runtime. Each variable is declared under unique name which
has to be a valid identifier. This name is used for accessing the memory location occupied by the variable. Variable
can be seen as a container for data and because it is typed, it instructs the compiler how to interpret the data it holds.
In BASIC, variable needs to be declared before it can be used. Specifying a data type for each variable is mandatory.
Variable is declared like this:
where identifier is any valid identifier and type can be any given data type.
For example:
Individual bits of byte variables (including SFR registers such as PORTA, etc) can be accessed by means of dot,
both on left and right side of the expression. For example:
2.8 Symbols
Symbol makes possible to replace a certain expression with a single identifier alias. Use of symbols can increase
readability of code.
BASIC syntax restricts you to single line expressions, allowing shortcuts for constants, simple statements, function
calls, etc. Scope of symbol identifier is a whole source file in which it is declared.
For example:
end if
PORT.1 = 0
DELAY1S
...
Note that using a symbol in a program technically consumes no RAM memory – compiler simply replaces each
instance of a symbol with the appropriate code from the declaration.
2.9 Directives
Directives are words of special significance for BASIC, but unlike other reserved words, appear only in contexts
where user-defined identifiers cannot occur. You cannot define an identifier that looks exactly like a directive.
Directive Meaning
Absolute specify exact location of variable in RAM
Org specify exact location of routine in ROM
Absolute specifies the starting address in RAM for variable (if variable is multi-byte, higher bytes are stored at
consecutive locations).
Org specifies the starting address of routine in ROM. For PIC16 family, routine must fit in one page – otherwise,
compiler will report an error. Directive org is appended to the declaration of routine:
2.10 Comments
Comments are text that is added to the code for purpose of description or clarification, and are completely ignored
by the compiler.
It is a good practice to comment your code, so that you or anybody else can later reuse it. On the other hand, it is
often useful to comment out a troublesome part of the code, so it could be repaired or modified later. Comments
should give purposeful information on what the program is doing. Comment such as Set Pin0 simply explains the
syntax but fails to state the purpose of instruction. Something like Turn Relay on might prove to be much more
useful.
Specialized editors feature syntax highlighting – it is easy to distinguish comments from code due to different color,
and comments are usually italicized.
2.11 Labels
Labels represent the most direct way of controlling the program flow. When you mark a certain program line with
label, you can jump to that line by means of instructions goto and gosub. It is convenient to think of labels as
bookmarks of sort. Note that the label main must be declared in every BASIC program because it marks the
beginning of the main module.
Label name needs to be a valid identifier. You cannot declare two labels with same name within the same routine.
The scope of label (label visibility) is tied to the routine where it is declared. This ensures that goto cannot be used
for jumping between routines.
Goto is an unconditional jump statement. It jumps to the specified label and the program execution continues
normally from that point on.
Gosub is a jump statement similar to goto, except it is tied to a matching word return. Upon jumping to a
specified label, previous address is saved on the stack. Program will continue executing normally from the label,
until it reaches return statement – this will exit the subroutine and return to the first program line following the
caller gosub instruction.
program test
main:
my_loop:
goto my_loop
end.
Note: Although it might seem like a good idea to beginners to program by means of jumps and labels, you should
try not to depend on it. This way of thinking strays from the procedural programming and can teach you bad
programming habits. It is far better to use procedures and functions where applicable, making the code structure
more legible and easier to maintain.
Procedures and functions, referred to as routines, are self-contained statement blocks that can be called from
different locations in a program. Function is a routine that returns a value upon execution. Procedure is a routine that
does not return a value.
Once routines have been defined, you can call them any number of times. Procedure is called upon to perform a
certain task, while function is called to compute a certain value.
where procedureName is any valid identifier, statements is a sequence of statements that are executed upon the
calling the procedure, and (parameterList), and localDeclarations are optional declaration of variables and/or
constants.
par1 and par2 are passed to the procedure by the value, but variables marked by keyword byref are passed by the
address.
passes tA and tB by the value: creates par1 = tA; and par2 = tB; then manipulates par1 and par2 so that tA and tB
remain unchanged;
passes tC and tD by the address: whatever changes are made upon vp1 and vp2 are also made upon tC and tD.
Function declaration is similar to procedure declaration, except it has a specified return type and a return value.
Function declaration has the form:
where functionName is any valid identifier, returnType is any simple type, statements is a sequence of statements to
be executed upon calling the function, and (parameterList), and localDeclarations are optional declaration of
variables and/or constants.
In BASIC, we use the keyword Result to assign return value of a function. For example:
As functions return values, function calls are technically expressions. For example, if you have defined a function
called Calc, which collects two integer arguments and returns an integer, then the function call Calc(24, 47) is
an integer expression. If I and J are integer variables, then I + Calc(J, 8) is also an integer expression.
2.13 Modules
Large programs can be divided into modules which allow easier maintenance of code. Each module is an actual file,
which can be compiled separately; compiled modules are linked to create an application. Note that each source file
must end with keyword end followed by a dot.
In mikroBasic IDE, all source code including the main program is stored in .pbas files. Each project consists of a
single project file, and one or more module files. To build a project, compiler needs either a source file or a compiled
file for each module.
Every BASIC application has one main module file and any number of additional module files. All source files have
same extension (pbas). Main file is identified by keyword program at the beginning, while other files have
keyword module instead. If you want to include a module, add the keyword include followed by a quoted name
of the file.
For example:
program test_project
include "math2.pbas"
dim tA as word
dim tB as word
main:
tA = sqrt(tb)
end.
Keyword include instructs the compiler which file to compile. The example above includes module math2.
pbas in the program file. Obviously, routine sqrt used in the example is declared in module math2.pbas.
If you want to distribute your module without disclosing the source code, you can send your compiled library (file
extension .mcl). User will be able to use your library as if he had the source code. Although the compiler is able to
determine which routines are implemented in the library, it is a common practice to provide routine prototypes in a
separate text file.
Note that there is no “body” section in the module – module files serve to declare functions, procedures, constants
and global variables.
PIC, PIC, PICmicro, and MPLAB are registered and protected trademarks of the Microchip Technology Inc. USA. Microchip
logo and name are the registered tokens of the Microchip Technology. mikroBasic is a registered trade mark of
mikroElektronika. All other tokens mentioned in the book are the property of the companies to which they belong.
mikroElektronika © 1998 - 2004. All rights reserved. If you have any questions, please contact our office.
Chapter 3: Operators
● Introduction
● 3.1 Arithmetic Operators
● 3.2 Boolean Operators
● 3.3 Logical (Bitwise) Operators
● 3.4 Relation Operators (Comparison Operators)
Introduction
In complex expressions, operators with higher precedence are evaluated before the
operators with lower precedence; operators of equal precedence are evaluated
according to their position in the expression starting from the left.
Operator Priority
not first (highest)
*, div, mod, and, <<, >> second
+, -, or, xor third
=, <>, <, >, <=, >= fourth (lowest)
A div B is the value of A divided by B rounded down to the nearest integer. The
mod operator returns the remainder obtained by dividing its operands. In other words,
X mod Y = X - (X div Y) * Y.
If 0 (zero) is used explicitly as the second operand (i.e. X div 0), compiler will
report an error and will not generate code. But in case of implicit division by zero : X
div Y , where Y is 0 (zero), result will be the maximum value for the appropriate
type (for example, if X and Y are words, the result will be $FFFF).
If number is converted from less complex to more complex data type, upper bytes are
filled with zeros. If number is converted from more complex to less complex data
type, data is simply truncated (upper bytes are lost).
If number is converted from less complex to more complex data type, upper bytes are
filled with ones if sign bit equals 1 (number is negative). Upper bytes are filled with
zeros if sign bit equals 0 (number is positive). If number is converted from more
complex to less complex data type, data is simply truncated (upper bytes are lost).
a = 3
b = -a
' assign value -3 to b
Boolean operators are not true operators, because there is no boolean data type defined
in BASIC. These operators conform to standard Boolean logic. They cannot be used
with any data type, but only to build complex conditional expression.
Operator Operation
not negation
and conjunction
or disjunction
For example:
<< : shift left the operand for a number of bit places specified in the right operand
>> : shift right the operand for a number of bit places specified in the right operand
(must be positive and less then 255).
For example, if you need to extract the higher byte, you can do it like this:
main:
TRISA = word(temp >> 8)
end.
Relation operators (Comparison operators) are commonly used in conditional and loop
statements for controlling the program flow. Overview of relation operators in BASIC:
PIC, PIC, PICmicro, and MPLAB are registered and protected trademarks of the Microchip
Technology Inc. USA. Microchip logo and name are the registered tokens of the Microchip
Technology. mikroBasic is a registered trade mark of mikroElektronika. All other tokens
mentioned in the book are the property of the companies to which they belong.
mikroElektronika © 1998 - 2004. All rights reserved. If you have any questions, please
contact our office.
● Introduction
● 4.2 Loops
● 4.2.1 FOR Statement
● 4.2.2 DO..LOOP Statement
● 4.2.3 WHILE Statement
Introduction
Statements define algorithmic actions within a program. Simple statements - like assignments and
procedure calls - can be combined to form loops, conditional statements, and other structured
statements.
Simple statement does not contain any other statements. Simple statements include assignments, and
calls to procedures and functions.
Structured statements are constructed from other statements. Use a structured statement when you
want to execute other statements sequentially, conditionally, or repeatedly.
Conditional statements are used for change the flow of the program execution upon meeting a certain
condition. The BASIC instruction of branching in BASIC language is the IF instruction, with several
variations that provide the necessary flexibility.
Description Instruction selects one of two possible program paths. Instruction IF..THEN is the
fundamental instruction of program branching in PIC BASIC and it can be used in
several ways to allow flexibility necessary for realization of decision making logic.
Example The simplest form of the instruction is shown in the figure below. Our example
tests the button connected to RB0 - when the button is pressed, program jumps to
the label "Add" where value of variable "w" is increased. If the button is not
pressed, program jumps back to the label "Main".
dim j as byte
Main:
if PORTB.0 = 0 then
goto Add
end if
goto Main
Add: j = j + 1
end.
More complex form of instruction is program branching with the ELSE clause:
dim j as byte
Main:
if PORTB.0 = 0 then
j = j + 1
else
j = j - 1
endif
goto Main
end.
Description Select Case statement is used for selecting one of several available branches in the
program course. It consists of a selector variable as a switch condition, and a list
of possible values. These values can be constants, numerals, or expressions.
Eventually, there can be an else statement which is executed if none of the labels
corresponds to the value of the selector.
As soon as the Select Case statement is executed, at most one of the statements
statements_1 .. statements_n will be executed. The Value which matches the
Selector determines the statements to be executed.
If none of the Value items matches the Selector, then the statements_else in the
else clause (if there is one) are executed.
...
Description Goto statement jumps to the specified label unconditionally, and the program
execution continues normally from that point on.
Avoid using GOTO too often, because over-labeled programs tend to be less
intelligible.
main:
goto myLabel
myLabel:
end.
4.2 Loops
Loop statements allow repeating one or more instructions for a number of times. The conducting
expression determines the number of iterations loop will go through.
Description For statement requires you to specify the number of iterations you want the loop to go
through.
Every statement between for and next will be executed once per iteration.
Example Here is a simple example of a FOR loop used for emitting hex code on PORTB for 7-
segment display with common cathode. Nine digits should be printed with one second
delay.
for i = 1 to 9
portb = i
delay_ms(1000)
next i
Syntax do
statement_1
...
statement_N
loop until expression
Description Expression returns a True or False value. The do..loop statement executes
statement_1; ...; statement_N continually, checking the expression after each
iteration. Eventually, when expression returns True, the do..loop statement
terminates.
The sequence is executed at least once because the check takes place in the end.
Example I = 0
do
I = I + 1 ' execute these 2 statements
PORTB = I ' until i equals 10 (ten)
loop until I = 10
Description Expression is tested first. If it returns True, all the following statements enclosed
by while and wend will be executed (or only one statement, alternatively). It
will keep on executing statements until the expression returns False.
...
while I > 0
I = I div 3
PORTA = I
wend
Syntax asm
statementList
end asm
Description Sometimes it can be useful to write part of the program in assembly. ASM
statement can be used to embed PIC assembly instructions into BASIC code.
Note that you cannot use numerals as absolute addresses for SFR or GPR variables
in assembly instructions. You may use symbolic names instead (listing will
display these names as well as addresses).
Be careful when embedding assembly code - BASIC will not check if assembly
instruction changed memory locations already used by BASIC variables.
Example asm
movlw 67
movwf TMR0
end asm
PIC, PIC, PICmicro, and MPLAB are registered and protected trademarks of the Microchip Technology Inc.
USA. Microchip logo and name are the registered tokens of the Microchip Technology. mikroBasic is a
registered trade mark of mikroElektronika. All other tokens mentioned in the book are the property of the
companies to which they belong.
mikroElektronika © 1998 - 2004. All rights reserved. If you have any questions, please contact our office.
● 5.2.11.8 GLCD_Clear_Dot
● 5.2.4 CANSPI Library ● 5.2.20 Software UART Library
● 5.2.11.9 GLCD_Set_Dot
● 5.2.4.1 CANSPISetOperationMode ● 5.2.20.1 Soft_UART_Init
● 5.2.11.10 GLCD_Circle
● 5.2.4.2 CANSPIGetOperationMode ● 5.2.20.2 Soft_UART_Read
● 5.2.11.11 GLCD_Line
● 5.2.4.3 CANSPIInitialize ● 5.2.20.3 Soft_UART_Write
● 5.2.11.12 GLCD_Invert
● 5.2.4.4 CANSPISetBaudRate
● 5.2.11.13 GLCD_Goto_XY ● 5.2.21 Sound Library
● 5.2.4.5 CANSPISetMask
● 5.2.11.14 GLCD_Put_Char ● 5.2.21.1 Sound_Init
● 5.2.4.6 CANSPISetFilter
● 5.2.11.15 GLCD_Clear_Screen ● 5.2.21.2 Sound_Play
● 5.2.4.7 CANSPIWrite
● 5.2.11.16 GLCD_Put_Text
● 5.2.4.8 CANSPIRead
● 5.2.11.17 GLCD_Rectangle ● 5.2.22 Trigonometry Library
● 5.2.4.9 CANSPI Library Constants
● 5.2.11.18 GLCD_Set_Font ● 5.2.22.1 SinE3
● 5.2.22.2 CosE3
● 5.2.5 Compact Flash Library
● 5.2.12 Manchester Code
● 5.2.5.1 CF_Init_Port
Library ● 5.2.23 Utilities
● 5.2.5.2 CF_Detect
● 5.2.12.1 Man_Receive_Init ● 5.2.23.1 Button
● 5.2.5.3 CF_Write_Init
● 5.2.12.2 Man_Receive_Config
● 5.2.5.4 CF_Write_Byte
● 5.2.12.3 Man_Receive
● 5.2.5.5 CF_Write_Word
● 5.2.12.4 Man_Send_Init
● 5.2.5.6 CF_Read_Init
● 5.2.12.5 Man_Send_Config
● 5.2.5.7 CF_Read_Byte
● 5.2.12.6 Man_Send
● 5.2.5.8 CF_Read_Word
● 5.2.5.9 CF_File_Write_Init
● 5.2.5.10 CF_File_Write_Byte
● 5.2.5.11 CF_File_Write_Complete
Introduction
BASIC was designed with focus on simplicity of use. Great number of built-in and library routines are included to help you
develop your applications quickly and easily.
BASIC incorporates a set of built-in functions and procedures. They are provided to make writing programs faster and easier. You
can call built-in functions and procedures in any part of the program.
Prototype sub procedure SetBit(dim byref Reg as byte, dim Bit as byte)
Description Sets <Bit> of register <Reg>. Any SFR (Special Function Register) or variable of byte type can pass as valid
variable parameter, but constants should be in range [0..7].
Prototype sub procedure ClearBit(dim byref Reg as byte, dim Bit as byte)
Description Clears <Bit> of register <Reg>. Any SFR (Special Function Register) or variable of byte type can pass as valid
variable parameter, but constants should be in range [0..7].
Prototype sub function TestBit(dim byref Reg as byte, dim Bit as byte) as byte
Description Tests <Bit> of register <Reg>. If set, returns 1, otherwise 0. Any SFR (Special Function Register) or variable of
byte type can pass as valid variable parameter, but constants should be in range [0..7].
Example TestBit(PORTA,2)
' returns 1 if PORTA bit RA2 is 1, returns 0 otherwise
Description Returns byte 0 of <Par>, assuming that word/integer comprises bytes 1 and 0, and longint comprises bytes 3, 2,
1, and 0.
Description Returns byte 1 of <Par>, assuming that word/integer comprises bytes 1 and 0, and longint comprises bytes 3, 2,
1, and 0.
Description Returns byte 2 of <Par>, assuming that longint comprises bytes 3, 2, 1, and 0.
Example Higher(Aaaa) ' returns byte next to the highest byte of variable Aaaa
Description Returns byte 3 of <Par>, assuming that longint comprises bytes 3, 2, 1, and 0.
A comprehensive collection of functions and procedures is provided for simplifying the initialization and use of PIC MCU and its
hardware modules. Routines currently includes libraries for ADC, I2C, USART, SPI, PWM, driver for LCD, drivers for internal
and external CAN modules, flexible 485 protocol, numeric formatting routines…
Numeric formatting routines convert byte, short, word, and integer to string. You can get text representation of numerical value by
passing it to one of the routines listed below.
http://www.mikroelektronika.co.yu/english/product/books/picbasicbook/05.htm (9 sur 112)05/11/2004 02:20:52
Programming PIC Microcontrollers in BASIC - mikroElektronika
Prototype sub procedure ByteToStr(dim input as byte, dim byref txt as char[6])
Description Parameter <input> represents numerical value of byte type that should be converted to string; parameter <txt>
is passed by the address and contains the result of conversion.
Prototype sub procedure WordToStr(dim input as word, dim byref txt as char[6])
Description Parameter <input> represents numerical value of word type that should be converted to string; parameter <txt>
is passed by the address and contains the result of conversion.
Prototype sub procedure ShortToStr(dim input as short, dim byref txt as char[6])
Description Parameter <input> represents numerical value of short type that should be converted to string; parameter <txt>
is passed by the address and contains the result of conversion.
Prototype sub procedure IntToStr(dim input as integer, dim byref txt as char[6])
Description Parameter <input> represents numerical value of integer type that should be converted to string; parameter
<txt> is passed by the address and contains the result of conversion.
Description Function converts 8-bit BCD numeral to its decimal equivalent and returns the result as byte.
Description Function converts 8-bit decimal numeral to BCD and returns the result as byte.
Description Function converts 16-bit BCD numeral to its decimal equivalent and returns the result as byte.
Description Function converts 16-bit decimal numeral to BCD and returns the result as word.
ADC (Analog to Digital Converter) module is available with a number of PIC MCU models. Library function ADC_Read is
included to provide you comfortable work with the module. The function is currently unsupported by the following PIC MCU
models: P18F2331, P18F2431, P18F4331, and P18F4431.
Description Routine initializes ADC module to work with RC clock. Clock determines the time period necessary for
performing AD conversion (min 12TAD). RC sources typically have Tad 4uS. Parameter <Channel>
determines which channel will be sampled. Refer to the device data sheet for information on device channels.
Example res = ADC_Read(2) ' reads channel 2 and stores value in variable res
ADC HW connection
The Controller Area Network module (CAN) is serial interface, used for communicating with other peripherals or microcontrollers.
CAN module is available with a number of PIC MCU models. BASIC includes a set of library routines to provide you comfortable
work with the module. More details about CAN can be found in appropriate literature and on mikroElektronika Web site.
Description The procedure copies <Mode> to CANSTAT and sets CAN to requested mode.
If Wait is true, this is a blocking call. It won't return until requested mode is set. If Wait is false, this is a non-
blocking call. It does not verify if CAN module is switched to requested mode or not. Caller must use
CANGetOperationMode() to verify correct operation mode before performing mode specific operation.
Example CANGetOperationMode
Prototype sub procedure CANInitialize(dim SJW as byte, dim BRP as byte, dim PHSEG1
as byte, dim PHSEG2 as byte, dim PROPSEG as byte, dim CAN_CONFIG_FLAGS as
byte)
Description The procedure initializes CAN module. CAN must be in Configuration mode or else these values will be
ignored.
Parameters:
SJW value as defined in 18XXX8 datasheet (must be between 1 thru 4)
BRP value as defined in 18XXX8 datasheet (must be between 1 thru 64)
PHSEG1 value as defined in 18XXX8 datasheet (must be between 1 thru 8)
PHSEG2 value as defined in 18XXX8 datasheet (must be between 1 thru 8)
PROPSEG value as defined in 18XXX8 datasheet (must be between 1 thru 8)
CAN_CONFIG_FLAGS value is formed from constants (see below)
Output:
http://www.mikroelektronika.co.yu/english/product/books/picbasicbook/05.htm (17 sur 112)05/11/2004 02:20:52
Programming PIC Microcontrollers in BASIC - mikroElektronika
CAN bit rate is set. All masks registers are set to '0' to allow all messages.
Filter registers are set according to flag value:
Side Effects:
All pending transmissions are aborted.
CANInitialize(1, 1, 3, 3, 1, aa)
Prototype sub procedure CANSetBaudRate(dim SJW as byte, dim BRP as byte, dim PHSEG1
as byte, dim PHSEG2 as byte, dim PROPSEG as byte, dim CAN_CONFIG_FLAGS as
byte)
Description The procedure sets CAN Baud Rate. CAN must be in Configuration mode or else these values will be ignored.
Parameters:
SJW value as defined in 18XXX8 datasheet (must be between 1 thru 4)
BRP value as defined in 18XXX8 datasheet (must be between 1 thru 64)
PHSEG1 value as defined in 18XXX8 datasheet (must be between 1 thru 8)
PHSEG2 value as defined in 18XXX8 datasheet (must be between 1 thru 8)
PROPSEG value as defined in 18XXX8 datasheet (must be between 1 thru 8)
CAN_CONFIG_FLAGS - Value formed from constants (see section below)
Output:
Given values are bit adjusted to fit in 18XXX8 and BRGCONx registers and copied. CAN bit rate is set as per
given values.
Description The procedure sets the CAN message mask. CAN must be in Configuration mode. If not, all values will be
ignored.
Parameters:
CAN_MASK - One of predefined constant value
val - Actual mask register value
CAN_CONFIG_FLAGS - Type of message to filter, either CAN_CONFIG_XTD_MSG or
CAN_CONFIG_STD_MSG
Output:
Given value is bit adjusted to appropriate buffer mask registers.
Prototype sub procedure CANSetFilter(dim CAN_FILTER as byte, dim val as longint, dim
CAN_CONFIG_FLAGS as byte)
Description The procedure sets the CAN message filter. CAN must be in Configuration mode. If not, all values will be
ignored.
Parameters:
CAN_FILTER - One of predefined constant values
val - Actual filter register value.
CAN_CONFIG_FLAGS - Type of message to filter, either CAN_CONFIG_XTD_MSG or
CAN_CONFIG_STD_MSG
Output:
Given value is bit adjusted to appropriate buffer filter registers
Prototype sub function CANWrite(dim id as longint, dim byref Data : as byte[8], dim
DataLen as byte, dim CAN_TX_MSG_FLAGS as byte) as byte
Description If at least one empty transmit buffer is found, given message is queued for the transmission. If none found,
FALSE value is returned. CAN must be in Normal mode.
Parameters:
id - CAN message identifier. Only 11 or 29 bits may be used depending on message type (standard or extended)
Data - array of bytes up to 8 bytes in length
DataLen - Data length from 1 thru 8
CAN_TX_MSG_FLAGS - Value formed from constants (see section below)
Prototype sub function CANRead(dim byref id as longint, dim byref Data as byte[8],
dim byref DataLen as byte, dim byref CAN_RX_MSG_FLAGS as byte) as byte
Description If at least one full receive buffer is found, the function extracts and returns the message as byte. If none found,
FALSE value is returned. CAN must be in mode in which receiving is possible.
Parameters:
id - CAN message identifier
Data - array of bytes up to 8 bytes in length
DataLen - Data length from 1 thru 8
CAN_TX_MSG_FLAGS - Value formed from constants (see below)
You need to be familiar with constants that are provided for use with the CAN module. All of the following constants are
predefined in CAN library.
CAN_OP_MODE
These constant values define CAN module operation mode. CANSetOperationMode() routine requires this code. These values
must be used by itself, i.e. they cannot be ANDed to form multiple values.
CAN_TX_MSG_FLAGS
These constant values define flags related to transmission of a CAN message. There could be more than one this flag ANDed
together to form multiple flags.
CAN_RX_MSG_FLAGS
These constant values define flags related to reception of a CAN message. There could be more than one this flag ANDed together
to form multiple flags. If a particular bit is set; corresponding meaning is TRUE or else it will be FALSE.
e.g.
CAN_MASK
These constant values define mask codes. Routine CANSetMask()requires this code as one of its arguments. These enumerations
must be used by itself i.e. it cannot be ANDed to form multiple values.
const CAN_MASK_B1 = 0
const CAN_MASK_B2 = 1
CAN_FILTER
These constant values define filter codes. Routine CANSetFilter() requires this code as one of its arguments. These enumerations
must be used by itself, i.e. it cannot be ANDed to form multiple values.
const CAN_FILTER_B1_F1 = 0
const CAN_FILTER_B1_F2 = 1
const CAN_FILTER_B2_F1 = 2
const CAN_FILTER_B2_F2 = 3
const CAN_FILTER_B2_F3 = 4
const CAN_FILTER_B2_F4 = 5
CAN_CONFIG_FLAGS
These constant values define flags related to configuring CAN module. Routines CANInitialize() and CANSetBaudRate() use
these codes. One or more these values may be ANDed to form multiple flags
The Controller Area Network module (CAN) is serial interface, used for communicating with other peripherals or microcontrollers.
CAN module is available with a number of PIC MCU models. MCP2515 or MCP2510 are modules that enable any chip with SPI
interface to communicate over CAN bus. BASIC includes a set of library routines to provide you comfortable work with the
module. More details about CAN can be found in appropriate literature and on mikroElektronika Web site.
Note: CANSPI routines are supported by any PIC MCU model that has SPI interface on PORTC. Also, CS pin of MCP2510 or
MCP2515 must be connected to RC0 pin.
Description The procedure copies <mode> to CANSTAT and sets CAN to requested mode.
If Wait is true, this is a blocking call. It won't return until requested mode is set. If Wait is false, this is a non-
blocking call. It does not verify if CAN module is switched to requested mode or not. Caller must use
CANGetOperationMode() to verify correct operation mode before performing mode specific operation.
Example CANGetOperationMode
Prototype sub procedure CANSPIInitialize(dim SJW as byte, dim BRP as byte, dim
PHSEG1 as byte, dim PHSEG2 as byte, dim PROPSEG as byte, dim
CAN_CONFIG_FLAGS as byte)
Description The procedure initializes CAN module. CAN must be in Configuration mode or else these values will be
ignored.
Parameters:
SJW value as defined in 18XXX8 datasheet (must be between 1 thru 4)
BRP value as defined in 18XXX8 datasheet (must be between 1 thru 64)
PHSEG1 value as defined in 18XXX8 datasheet (must be between 1 thru 8)
PHSEG2 value as defined in 18XXX8 datasheet (must be between 1 thru 8)
PROPSEG value as defined in 18XXX8 datasheet (must be between 1 thru 8)
CAN_CONFIG_FLAGS value is formed from constants (see below)
Output:
CAN bit rate is set. All masks registers are set to '0' to allow all messages.
Filter registers are set according to flag value:
http://www.mikroelektronika.co.yu/english/product/books/picbasicbook/05.htm (30 sur 112)05/11/2004 02:20:52
Programming PIC Microcontrollers in BASIC - mikroElektronika
Side Effects:
All pending transmissions are aborted.
CANInitialize(1, 1, 3, 3, 1, aa)
Prototype sub procedure CANSPISetBaudRate(dim SJW as byte, dim BRP as byte, dim
PHSEG1 as byte, dim PHSEG2 as byte, dim PROPSEG as byte, dim
CAN_CONFIG_FLAGS as byte)
Description The procedure sets CAN Baud Rate. CAN must be in Configuration mode or else these values will be ignored.
Parameters:
SJW value as defined in 18XXX8 datasheet (must be between 1 thru 4)
BRP value as defined in 18XXX8 datasheet (must be between 1 thru 64)
PHSEG1 value as defined in 18XXX8 datasheet (must be between 1 thru 8)
PHSEG2 value as defined in 18XXX8 datasheet (must be between 1 thru 8)
PROPSEG value as defined in 18XXX8 datasheet (must be between 1 thru 8)
CAN_CONFIG_FLAGS - Value formed from constants (see section below)
Output:
Given values are bit adjusted to fit in 18XXX8 and BRGCONx registers and copied. CAN bit rate is set as per
given values.
Description The procedure sets the CAN message mask. CAN must be in Configuration mode. If not, all values will be
ignored.
Parameters:
CAN_MASK - One of predefined constant value
val - Actual mask register value
CAN_CONFIG_FLAGS - Type of message to filter, either CAN_CONFIG_XTD_MSG or
CAN_CONFIG_STD_MSG
Output:
Given value is bit adjusted to appropriate buffer mask registers.
Description The procedure sets the CAN message filter. CAN must be in Configuration mode. If not, all values will be
ignored.
Parameters:
CAN_FILTER - One of predefined constant values
val - Actual filter register value.
CAN_CONFIG_FLAGS - Type of message to filter, either CAN_CONFIG_XTD_MSG or
CAN_CONFIG_STD_MSG
Output:
Given value is bit adjusted to appropriate buffer filter registers
Description If at least one empty transmit buffer is found, given message is queued for the transmission. If none found,
FALSE value is returned. CAN must be in Normal mode.
Parameters:
id - CAN message identifier. Only 11 or 29 bits may be used depending on message type (standard or extended)
Data - array of as bytes up to 8 as bytes in length
DataLen - Data length from 1 thru 8
CAN_TX_MSG_FLAGS - Value formed from constants (see section below)
Prototype sub function CANSPIRead(dim byref id as longint, dim byref Data as byte
[8], dim byref DataLen as byte, dim byref CAN_RX_MSG_FLAGS as byte) as byte
Description If at least one full receive buffer is found, the function extracts and returns the message as byte. If none found,
FALSE value is returned. CAN must be in mode in which receiving is possible.
Parameters:
id - CAN message identifier
Data - array of bytes up to 8 bytes in length
DataLen - Data length from 1 thru 8
CAN_TX_MSG_FLAGS - Value formed from constants (see below)
You need to be familiar with constants that are provided for use with the CAN module. All of the following constants are
predefined in CANSPI library.
CAN_OP_MODE
These constant values define CAN module operation mode. CANSetOperationMode() routine requires this code. These values
must be used by itself, i.e. they cannot be ANDed to form multiple values.
CAN_TX_MSG_FLAGS
These constant values define flags related to transmission of a CAN message. There could be more than one this flag ANDed
together to form multiple flags.
CAN_RX_MSG_FLAGS
These constant values define flags related to reception of a CAN message. There could be more than one this flag ANDed together
to form multiple flags. If a particular bit is set; corresponding meaning is TRUE or else it will be FALSE.
e.g.
CAN_MASK
These constant values define mask codes. Routine CANSetMask()requires this code as one of its arguments. These enumerations
must be used by itself i.e. it cannot be ANDed to form multiple values.
const CAN_MASK_B1 = 0
const CAN_MASK_B2 = 1
CAN_FILTER
These constant values define filter codes. Routine CANSetFilter() requires this code as one of its arguments. These enumerations
must be used by itself, i.e. it cannot be ANDed to form multiple values.
const CAN_FILTER_B1_F1 = 0
const CAN_FILTER_B1_F2 = 1
const CAN_FILTER_B2_F1 = 2
const CAN_FILTER_B2_F2 = 3
const CAN_FILTER_B2_F3 = 4
const CAN_FILTER_B2_F4 = 5
CAN_CONFIG_FLAGS
These constant values define flags related to configuring CAN module. Routines CANInitialize() and CANSetBaudRate() use
these codes. One or more these values may be ANDed to form multiple flags
Example of interfacing CAN transceiver MCP2551, and MCP2510 with MCU and bus
Compact Flash Library provides routines for accessing data on Compact Flash card (abbrev. CF further in text). CF cards are
widely used memory elements, commonly found in digital cameras. Great capacity (8MB ~ 2GB, and more) and excellent access
time of typically few microseconds make them very attractive for microcontroller applications.
In CF card, data is divided into sectors, one sector usually comprising 512 bytes (few older models have sectors of 256B). Read
and write operations are not performed directly, but successively through 512B buffer. Following routines can be used for CF with
FAT16 and FAT32 file system.
Before write operation, make sure you don’t overwrite boot or FAT sector as it could make your card on PC or digital cam
unreadable. Drive mapping tools, such as Winhex, can be of a great assistance.
Prototype sub procedure CF_INIT_PORT(dim byref CtrlPort as byte, dim byref DataPort
as byte)
Example CF_Init_Port(PORTB, PORTD) ' Control port is PORTB, Data port is PORTD
Description The function checks if Compact Flash card is present. Returns true if present, otherwise returns false.
<CtrlPort> must be initialized (call CF_INIT_PORT first).
Example do
nop
loop until CF_Detect(PORTB) = true ' wait until CF card is inserted
Prototype sub procedure CF_WRITE_INIT(dim byref CtrlPort as byte, dim byref DataPort as
byte, dim Adr as longint, dim SectCnt as byte)
Description The procedure initializes CF card for writing. Ports need to be initialized.
Parameters:
CtrlPort - control port,
DataPort - data port,
k - specifies sector address from where data will be written,
SectCnt - parameter is total number of sectors prepared for write.
Example CF_Write_Init(PORTB, PORTD, 590, 1) ' Initialize write at sector address 590
' of 1 sector (512 bytes)
Prototype sub procedure CF_WRITE_BYTE(dim byref CtrlPort as byte, dim byref DataPort as
byte, dim BData as byte)
Description The procedure writes 1 byte to Compact Flash. The procedure has effect only if CF card is initialized for writing.
Parameters:
CtrlPort - control port,
DataPort - data port,
dat - data byte written to CF
Example CF_Write_Init(PORTB, PORTD, 590, 1) ' Initialize write at sector address 590
' of 1 sector (512 bytes)
Prototype sub procedure CF_WRITE_WORD(dim byref CtrlPort as byte, dim byref DataPort
as byte, dim WData as word)
Description The procedure writes 1 word to Compact Flash. The procedure has effect only if CF card is initialized for
writing.
Parameters:
CtrlPort - control port,
DataPort - data port,
Wdata - data word written to CF
Prototype sub procedure CF_READ_INIT(dim byref CtrlPort as byte, dim byref DataPort as
byte, dim Adr as longint, dim SectCnt as byte)
Description Parameters:
CtrlPort - control port,
DataPort - data port,
Adr - specifies sector address from where data will be read,
SectCnt - total number of sectors prepared for read operations.
Prototype sub function CF_READ_BYTE(dim byref CtrlPort as byte, dim byref DataPort
as byte) as byte
Description Function reads 1 byte from Compact Flash. Ports need to be initialized, and CF must be initialized for reading.
Parameters:
CtrlPort - control port,
DataPort - data port
Example PORTC = CF_Read_Byte(PORTB, PORTD) ' read byte and display on PORTC
Prototype sub function CF_READ_WORD(dim byref CtrlPort as byte, dim byref DataPort
as byte) as word
Description Function reads 1 word from Compact Flash. Ports need to be initialized, and CF must be initialized for reading.
Parameters:
CtrlPort - control port,
DataPort - data port
Example PORTC = CF_Read_Word(PORTB, PORTD) ' read word and display on PORTC
5.2.5.9 CF_File_Write_Init – Initializes CF card for file writing operation (FAT16 only, PIC18
only)
Description This procedure initializes CF card for file writing operation (FAT16 only, PIC18 only).
Parameters:
CtrlPort - control port,
DataPort - data port
5.2.5.10 CF_File_Write_Byte – Adds one byte to file (FAT16 only, PIC18 only)
Description This procedure adds one byte (Bdata) to file (FAT16 only, PIC18 only).
Parameters:
CtrlPort - control port,
DataPort - data port,
Bdata - data byte to be written.
5.2.5.11 CF_File_Write_Complete – Closes file and makes it readable (FAT16 only, PIC18
only)
http://www.mikroelektronika.co.yu/english/product/books/picbasicbook/05.htm (49 sur 112)05/11/2004 02:20:52
Programming PIC Microcontrollers in BASIC - mikroElektronika
Description Upon all data has be written to file, use this procedure to close the file and make it readable by Windows
(FAT16 only, PIC18 only).
Parameters:
CtrlPort - control port,
DataPort - data port,
Filename (must be in uppercase and must have exactly 8 characters).
EEPROM data memory is available with a number of PIC MCU models. Set of library procedures and functions is listed below to
http://www.mikroelektronika.co.yu/english/product/books/picbasicbook/05.htm (51 sur 112)05/11/2004 02:20:52
Programming PIC Microcontrollers in BASIC - mikroElektronika
Notes:
Be aware that all interrupts will be disabled during execution of EEPROM_Write routine (GIE bit of INTCON register will be
cleared). Routine will set this bit on exit.
Ensure minimum 20ms delay between successive use of routines EEPROM_Write and EEPROM_Read. Although EEPROM will
write the correct value, EEPROM_Read might return undefined result.
Description Function reads byte from <Address>. <Address> is of byte type, which means it can address only 256
locations. For PIC18 MCU models with more EEPROM data locations, it is programmer's responsibility to set
SFR EEADRH register appropriately.
Ensure minimum 20ms delay between successive use of routines EEPROM_Write and EEPROM_Read.
Although EEPROM will write the correct value, EEPROM_Read might return undefined result.
Example TRISB = 0
Delay_ms(30)
for i = 0 to 20
PORTB = EEPROM_Read(i)
for j = 0 to 200
Delay_us(500)
next j
next i
Description Function writes byte to <Address>. <Address> is of byte type, which means it can address only 256 locations.
For PIC18 MCU models with more EEPROM data locations, it is programmer's responsibility to set SFR
EEADRH register appropriately.
All interrupts will be disabled during execution of EEPROM_Write routine (GIE bit of INTCON register will be
cleared). Routine will set this bit on exit
Ensure minimum 20ms delay between successive use of routines EEPROM_Write and EEPROM_Read.
Although EEPROM will write the correct value, EEPROM_Read might return undefined result.
Example for i = 0 to 20
EEPROM_Write(i, i + 6)
next i
Prototype sub function Flash_Read(dim Address as longint) as byte ' for PIC18
sub function Flash_Read(dim Address as word) as word ' for PIC16
Example for i = 0 to 63
toRead = Flash_Read($0D00 + i)
' read 64 consecutive locations starting from 0x0D00
next i
Prototype sub procedure Flash_Write(dim Address as longint, dim byref Data as byte
[64]) ' for PIC18
sub procedure Flash_Write(dim Address as word, dim Data as word) ' for
PIC16
Description Procedure writes chunk of data to Flash memory (for PIC18, data needs to exactly 64 bytes in size). Keep in
mind that this function erases target memory before writing <Data> to it. This means that if write was
unsuccessful, your previous data will be lost.
I2C interface is serial interface used for communicating with peripheral or other microcontroller devices. Routines below are
intended for PIC MCUs with MSSP module. By using these, you can configure and use PIC MCU as master in I2C communication.
Description Initializes I2C module. Parameter <Clock> is a desired I2C clock (refer to device data sheet for correct values in
respect with Fosc).
Example I2C_Init(100000)
Description Determines if I2C bus is free and issues START condition; if there is no error, function returns 0.
Example I2C_Start
Example I2C_Repeated_Start
Description Receives 1 byte from slave and sends not acknowledge signal if <Ack> is 0; otherwise, it sends acknowledge.
Description After you have issued a start or repeated start you can send <Data> byte via I2C bus. The function returns 0 if
there are no errors.
Example I2C_Stop
BASIC provides a set of library procedures and functions for communicating with commonly used 4-bit interface LCD (with
Hitachi HD44780 controller). Be sure to designate port with LCD as output, before using any of the following library procedures
or functions.
Description Initializes LCD at <Port> with default pin settings (see the figure below).
Example LCD_Init(PORTB)
' Initializes LCD on PORTB (check pin settings in the figure below)
Prototype sub procedure LCD_Config(dim byref Port as byte, const RS, const EN, const
WR, const D7, const D6, const D5, const D4)
Description Initializes LCD at <Port> with pin settings you specify: parameters <RS>, <EN>, <WR>, <D7> .. <D4> need
to be a combination of values 0..7 (e.g. 3,6,0,7,2,1,4).
Example LCD_Config(PORTD, 1, 2, 0, 3, 5, 4, 6)
' Initializes LCD on PORTD with our custom pin settings
Prototype sub procedure LCD_Chr(dim Row as byte, dim Column as byte, dim Character
as byte)
Example LCD_Chr_CP("k")
' Prints character "k" at current cursor position
Prototype sub procedure LCD_Out(dim Row as byte, dim Column as byte, dim byref Text
as char[255])
Description Prints <Text> (string variable) at specified <Row> and <Column> on LCD. Both string variables and string
constants can be passed.
Description Prints <Text> (string variable) at current cursor position. Both string variables and string constants can be
passed.
LCD_First_Row
' Moves cursor to 1st row
LCD_Second_Row
' Moves cursor to 2nd row
LCD_Third_Row
' Moves cursor to 3rd row
LCD_Fourth_Row
' Moves cursor to 4th row
LCD_Clear
http://www.mikroelektronika.co.yu/english/product/books/picbasicbook/05.htm (62 sur 112)05/11/2004 02:20:53
Programming PIC Microcontrollers in BASIC - mikroElektronika
LCD_Return_Home
' Returns cursor to home position,
' returns a shifted display to original position.
' Display data RAM is unaffected.
LCD_Cursor_Off
' Turn off cursor
LCD_Underline_On
' Underline cursor on
LCD_Blink_Cursor_On
' Blink cursor on
LCD_Move_Cursor_Left
' Move cursor left without changing display data RAM
LCD_Move_Cursor_Right
' Move cursor right without changing display data RAM
LCD_Turn_On
' Turn LCD display on
LCD_Turn_Off
http://www.mikroelektronika.co.yu/english/product/books/picbasicbook/05.htm (63 sur 112)05/11/2004 02:20:53
Programming PIC Microcontrollers in BASIC - mikroElektronika
LCD_Shift_Left
' Shift display left without changing display data RAM
LCD_Shift_Right
' Shift display right without changing display data RAM
LCD HW connection
LCD HW connection
BASIC provides a set of library procedures and functions for communicating with commonly used 8-bit interface LCD (with
Hitachi HD44780 controller). Be sure to designate Control and Data ports with LCD as output, before using any of the following
library procedures or functions.
Prototype sub procedure LCD8_Init(dim byref Port_Ctrl as byte, dim byref Port_Data
as byte)
Description Initializes LCD at <Port_Ctrl> and <Port_Data> with default pin settings (see the figure below).
Prototype sub procedure LCD8_Config(dim byref Port_Ctrl as byte, dim byref Port_Data
as byte, const RS, const EN, const WR, const D7, const D6, const D5, const
D4, const D3, const D2, const D1, const D0)
Description Initializes LCD at <Port_Ctrl> and <Port_Data> with pin settings you specify: parameters <RS>, <EN>,
<WR> need to be in range 0..7; parameters <D7>..<D0> need to be a combination of values 0..7 (e.g.
3,6,5,0,7,2,1,4).
Prototype sub procedure LCD8_Chr(dim Row as byte, dim Column as byte, dim Character
as byte)
Example LCD8_Chr_CP("k")
' Prints character "k" at current cursor position
Prototype sub procedure LCD8_Out(dim Row as byte, dim Column as byte, dim byref Text
as char[255])
Description Prints <Text> (string variable) at specified <Row> and <Column> on LCD. Both string variables and string
constants can be passed.
Description Prints <Text> (string variable) at current cursor position. Both string variables and string constants can be
passed.
Example LCD8_Out_CP("Test")
' Prints "Test" at current cursor position
LCD_First_Row
' Moves cursor to 1st row
LCD_Second_Row
' Moves cursor to 2nd row
LCD_Third_Row
' Moves cursor to 3rd row
LCD_Fourth_Row
' Moves cursor to 4th row
LCD_Clear
' Clears display
LCD_Return_Home
' Returns cursor to home position,
' returns a shifted display to original position.
' Display data RAM is unaffected.
LCD_Cursor_Off
' Turn off cursor
LCD_Underline_On
' Underline cursor on
LCD_Blink_Cursor_On
' Blink cursor on
LCD_Move_Cursor_Left
' Move cursor left without changing display data RAM
LCD_Move_Cursor_Right
' Move cursor right without changing display data RAM
LCD_Turn_On
' Turn LCD display on
LCD_Turn_Off
' Turn LCD display off
LCD_Shift_Left
' Shift display left without changing display data RAM
LCD_Shift_Right
' Shift display right without changing display data RAM
LCD HW connection
LCD HW connection
mikroPascal provides a set of library procedures and functions for drawing and writing on Graphical LCD. Also it is possible to
http://www.mikroelektronika.co.yu/english/product/books/picbasicbook/05.htm (71 sur 112)05/11/2004 02:20:53
Programming PIC Microcontrollers in BASIC - mikroElektronika
convert bitmap (use menu option Tools > BMP2LCD) to constant array and display it on GLCD. These routines works with
commonly used GLCD 128x64, and work only with the PIC18 family.
Prototype sub procedure GLCD_Config(dim byref Ctrl_Port as byte, dim byref Data_Port
as byte, dim Reset as byte, dim Enable as byte,dim RS as byte, dim RW as
byte, dim CS1 as byte, dim CS2 as byte)
Description Initializes GLCD at <Ctrl_Port> and <Data_Port> with custom pin settings.
Description Initializes LCD at <Ctrl_Port> and <Data_Port>. With default pin settings Reset=7, Enable=1, RS=3, RW=5,
CS1=2, CS2=0.
Example GLCD_Put_Ins(DISPLAY_ON)
Example GLCD_Put_Data(temperature)
Description Sends data to GLCD at specified <side> (<side> can take constant value LEFT or RIGHT) .
Example GLCD_Put_Data2(temperature, 1)
Example GLCD_Select_Side(1)
Example GLCD_Data_Read
Description Draws a circle on the GLCD, centered at <CenterX, CenterY> with <Radius>.
Description Procedure inverts display (changes dot state on/off) in the specified area, X pixels wide starting from 0 position,
8 pixels high. Parameter Xaxis spans 0..127, parameter Yaxis spans 0..7 (8 text lines).
Example GLCD_Invert(60, 6)
Description Sets cursor to dot (x,y). Procedure is used in combination with GLCD_Put_Data, GLCD_Put_Data2, and
GLCD_Put_Char.
Example GLCD_Goto_XY(60, 6)
Example GLCD_Put_Char(k)
Example GLCD_Clear_Screen
Prototype sub procedure GLCD_Put_Text(dim x_pos as word, dim y_pos as word, dim
byref text as char[25], dim invert as byte)
Description Draws a rectangle on the GLCD. (x1,y1) sets the upper left corner, (x2,y2) sets the lower right corner.
Description Sets font for GLCD. Parameter <font_index> spans from 1 to 4, and determines which font will be used:
1: 5x8 dots
2: 5x7
3: 3x6
4: 8x8
Example GLCD_Set_Font(2)
mikroBasic provides a set of library procedures and functions for handling Manchester coded signal. Manchester code is a code in
which data and clock signals are combined to form a single self-synchronizing data stream; each encoded bit contains a transition
at the midpoint of a bit period, the direction of transition determines whether the bit is a 0 or a 1; second half is the true bit value
and the first half is the complement of the true bit value (as shown in the figure below).
Note: Manchester receive routines are blocking calls (Man_Receive_Config, Man_Receive_Init, Man_Receive).
This means that PIC will wait until the task is performed (e.g. byte is received, synchronization achieved, etc).
Note: Routines for receiving are limited to a baud rate scope from 340 ~ 560 bps.
Description Procedure works same as Man_Receive_Config, but with default pin setting (pin 6).
Example Man_Receive_Init(PORTD)
Prototype sub procedure Man_Receive_Config(dim byref Port as byte, dim RXpin as byte)
Description This procedure needs to be called in order to receive signal by procedure Man_Receive. You need to specify
the <Port> and <RXpin> of input signal. In case of multiple errors on reception, you should call
Man_Receive_Init once again to enable synchronization.
Example Man_Receive_Config(PORTD, 5)
Description Function extracts one byte from signal. If format does not match the expected, <Error> flag will be set True.
Description Procedure works same as Man_Send_Config, but with default pin setting (pin 0).
Example Man_Send_Init(PORTB)
Prototype sub procedure Man_Send_Config(dim byref Port as byte, dim TXpin as byte)
Description Procedure needs to be called in order to send signals via procedure Man_Send. Procedure specifies <Port> and
<TXpin> for outgoing signal (const baud rate).
Example Man_Send_Config(PORTB, 4)
CCP (Capture/ Compare/ PWM) module is available with a number of PIC MCU models. Set of library procedures and functions is
listed below to provide comfortable work with PWM (Pulse Width Modulation).
Note that these routines support module on PORTC pin RC2, and won't work with modules on other ports. Also, BASIC doesn't
support enhanced PWM modules.
Description Initializes PWM module with (duty ratio) 0%. <PWM_Freq> is a desired PWM frequency (refer to device data
sheet for correct values in respect with Fosc).
Description Routine changes duty ratio. <New_Duty> takes values from 0 to 255, where 0 is 0% duty ratio, 127 is 50% duty
ratio, and 255 is 100% duty ratio. Other values for specific duty ratio can be calculated as (Percent*255)/100.
Example PWM_Start
Example PWM_Stop
PWM demonstration
RS485 is a multipoint communication which allows multiple devices to be connected to a single signal cable. BASIC provides a set
of library routines to provide you comfortable work with RS485 system using Master/Slave architecture.
Master and Slave devices interchange packets of information, each of these packets containing synchronization bytes, CRC byte,
address byte, and the data. In Master/Slave architecture, Slave can never initiate communication. Each Slave has its unique address
and receives only the packets containing that particular address. It is programmer's responsibility to ensure that only one device
transmits data via 485 bus at a time.
RS485 routines require USART module on port C. Pins of USART need to be attached to RS485 interface transceiver, such as
LTC485 or similar. Pins of transceiver (Receiver Output Enable and Driver Outputs Enable) should be connected to port C, pin 2
(see the figure at end of the chapter).
Note: Address 50 is a common address for all Slave devices: packets containing address 50 will be received by all Slaves. The only
exceptions are Slaves with addresses 150 and 169, which require their particular address to be specified in the packet.
Example RS485Master_Init
Description Master receives any message sent by Slaves. As messages are multi-byte, this procedure must be called for each
byte received (see the example at the end of the chapter). Upon receiving a message, buffer is filled with the
following values:
Procedure automatically sets data[4] and data[5] upon every received message. These flags need to be cleared
repeatedly from the program.
Note: MCU must be initialized as Master in 485 communication to assign an address to MCU
Example RS485Master_Read(dat)
Description Routine sends number of bytes (1 < datalen <= 3) from buffer via 485, to slave specified by <address>.
MCU must be initialized as Master in 485 communication. It is programmer's responsibility to ensure (by
protocol) that only one device sends data via 485 bus at a time.
Example RS485Master_Write(dat, 1)
<address> can take any value between 0 and 255, except 50, which is common address for all slaves.
Description Only messages that appropriately address Slaves will be received. As messages are multi-byte, this procedure
must be called for each byte received (see the example at the end of the chapter). Upon receiving a message,
buffer is filled with the following values:
Procedure automatically sets data[4] and data[5] upon every received message. These flags need to be cleared
repeatedly from the program.
Example RS485Slave_Read(dat)
Description Sends number of bytes (1 < datalen <= 3) from buffer via 485 to Master.
MCU must be initialized as Slave in 485 communication. It is programmer's responsibility to ensure (by
protocol) that only one device sends data via 485 bus at a time.
Example RS485Slave_Write(dat, 1)
SPI (Serial Peripheral Interface) module is available with a number of PIC MCU models. You can easily communicate with other
devices via SPI - A/D converters, D/A converters, MAX7219, LTC1290 etc. You need PIC MCU with hardware integrated SPI
(for example, PIC16F877). Then, simply use the following functions and procedures.
● Master mode,
● clock Fosc/4,
● clock idle state low,
● data transmitted on low to high edge,
● input data sampled at the middle of interval.
Example SPI_Init
Description For advanced settings, configure and initialize SPI using the procedure SPI_Init_Advanced.
Description Routine provides clock by sending <Buffer> and reads the received data at the end of the period.
Description Routine writes <Data> to SSPBUF and immediately starts the transmission.
Example SPI_Write(7)
USART (Universal Synchronous Asynchronous Receiver Transmitter) hardware module is available with a number of PIC MCU
models. You can easily communicate with other devices via RS232 protocol (for example with PC, see the figure at the end of this
chapter - RS232 HW connection). You need a PIC MCU with hardware integrated USART (for example, PIC16F877). Then,
simply use the functions and procedures described below.
Note: Some PIC micros that have two USART modules, such as P18F8520, require you to specify the module you want to use.
Simply append the number 1 or 2 to procedure or function name, e.g. USART_Write2(Dat).
Description Initializes PIC MCU USART hardware and establishes communication at specified <Baud_Rate>.
Refer to the device data sheet for baud rates allowed for specific Fosc. If you specify the unsupported baud rate,
compiler will report an error.
Example USART_Init(2400)
Example USART_Data_Ready
Example USART_Read
Example USART_Write(dat)
RS232 HW connection
1-wire library provides routines for communicating via 1-wire bus, for example with DS1820 digital thermometer. Note that
oscillator frequency Fosc needs to be at least 4MHz in order to use the routines with Dallas digital thermometers.
Prototype sub function OW_Reset(dim byref PORT as byte, dim Pin as byte) as byte
Description Issues 1-wire reset signal for DS1820. Parameters <PORT> and <Pin> specify the location of DS1820; return
value of the function is 0 if DS1820 is present, and 1 otherwise.
Example OW_Reset(PORTA, 5)
Prototype sub function OW_Read(dim byref PORT as byte, Pin as byte) as byte
Prototype sub procedure OW_Write(dim byref PORT as byte, dim Pin as byte, dim par as
byte)
BASIC provides routines which implement software I2C. These routines are hardware independent and can be used with any
MCU. Software I2C enables you to use MCU as Master in I2C communication. Multi-master mode is not supported.
Prototype sub procedure Soft_I2C_Config(dim byref Port as byte, const SDA,const SCL)
Parameter <Port> specifies port of MCU on which SDA and SCL pins will be located;
parameters <SCL> and <SDA> need to be in range 0..7 and cannot point at the same pin;
Example Soft_I2C_Config(PORTD, 3, 4)
Example Soft_I2C_Start
Description After you have issued a start signal you can send <Data> byte via I2C bus. The function returns 0 if there are no
errors.
Example Soft_I2C_Write($A3)
Description Receives 1 byte from slave and sends not acknowledge signal if <Ack> is 0; otherwise, it sends acknowledge.
Example Soft_I2C_Stop
BASIC provides routines which implement software SPI. These routines are hardware independent and can be used with any
MCU. You can easily communicate with other devices via SPI - A/D converters, D/A converters, MAX7219, LTC1290 etc.
Simply use the following functions and procedures.
Prototype sub procedure Soft_SPI_Config(dim byref Port as byte, const SDI, const
SD0, const SCK)
Description Routine configures and initializes software SPI with the following defaults:
SDI pin, SDO pin, and SCK pin are specified by the appropriate parameters.
Example Soft_SPI_Config(PORTB, 1, 2, 3)
' SDI pin is RB1, SDO pin is RB2, and SCK pin is RB3.
Description Routine provides clock by sending <Buffer> and reads the received data at the end of the period.
Example Soft_SPI_Read(dat)
Description Routine writes <Data> to SSPBUF and immediately starts the transmission.
Example Soft_SPI_Write(dat)
BASIC provides routines which implement software UART. These routines are hardware independent and can be used with any
MCU. You can easily communicate with other devices via RS232 protocol . Simply use the functions and procedures described
below.
Prototype sub procedure Soft_UART_Init(dim byref Port as byte, const RX, const TX,
const Baud_Rate)
Description Initializes PIC MCU UART at specified pins establishes communication at <Baud_Rate>.
If you specify the unsupported baud rate, compiler will report an error.
Description Function returns a received byte. Parameter <Msg_received> will take true if transfer was succesful.
Soft_UART_Read is a non-blocking function call, so you should test <Msg_received> manually (check the
example below).
Example Soft_UART_Write(Received_byte)
BASIC provides a sound library which allows you to use sound signalization in your applications.
Description Procedure Sound_Init initializes sound engine and prepares it for output at specified <Port> and <Pin>.
Parameter <Pin> needs to be within range 0..7.
Description Procedure Sound_Play plays the sound at the specified port pin. <Period_div_10> is a sound period given in
MCU cycles divided by ten, and generated sound lasts for a specified number of periods (<Num_of_Periods>).
For example, if you want to play sound of 1KHz: T = 1/f = 1ms = 1000 cycles @ 4MHz<.
code>. This gives us our first parameter: 1000/10 = 100. Then, we could
play 150 periods like this: Sound_Play(100, 150).
Example ...
while true
adcValue = ADC_Read(2) ' Get lower byte from ADC
Sound_Play(adcValue, 200) ' Play the sound
wend
BASIC provides a trigonometry library for applications which involve angle calculations. Trigonometric routines take an angle (in
degrees) as parameter of type word and return sine and cosine multiplied by 1000 and rounded up (as integer).
Description Function takes a word-type number which represents angle in degrees and returns the sine of <Angle> as
integer, multiplied by 1000 (1E3) and rounded up to nearest integer: result = round_up(sin(Angle)
*1000). Thus, the range of the return values for these functions is from -1000 to 1000.
Note that parameter <Angle> cannot be negative. Function is implemented as lookup table, and the maximum
error obtained is ±1.
angle = 45
result = sinE3(angle) ' result is 707
Description Function takes a word-type number which represents angle in degrees and returns the cosine of <Angle> as
integer, multiplied by 1000 (1E3) and rounded up to nearest integer: result = round_up(cos(Angle)
*1000). Thus, the range of the return values for these functions is from -1000 to 1000.
Note that parameter <Angle> cannot be negative. Function is implemented as lookup table, and the maximum
error obtained is ±1.
angle = 90
result = cosE3(angle) ' result is 0
5.2.23 Utilities
BASIC provides a utility set of procedures and functions for faster development of your applications.
Prototype sub function Button(dim byref PORT as byte, dim Pin as byte, dim Time as
byte, dim Astate as byte) as byte
Description Function eliminates the influence of contact flickering due to the pressing of a button (debouncing).
Parameters <PORT> and <Pin> specify the location of the button; parameter <Time> represents the minimum
time interval that pin must be in active state in order to return one; parameter <Astate> can be only zero or one,
and it specifies if button is active on logical zero or logical one.
PIC, PIC, PICmicro, and MPLAB are registered and protected trademarks of the Microchip Technology Inc. USA. Microchip logo and name
are the registered tokens of the Microchip Technology. mikroBasic is a registered trade mark of mikroElektronika. All other tokens mentioned
in the book are the property of the companies to which they belong.
mikroElektronika © 1998 - 2004. All rights reserved. If you have any questions, please contact our office.
● Introduction
● 6.1 Interrupt Mechanism
● 6.2 Internal AD Converter
● 6.3 TMR0 Timer
● 6.4 TMR1 Timer
● 6.5 PWM Module
● 6.6 Hardware UART module (RS-232 Communication)
Introduction
It is commonly said that microcontroller is an “entire computer on a single chip”, which implies that it has more to offer
than a single CPU (microprocessor). This additional functionality is actually located in microcontroller’s subsystems, also
called the “integrated peripherals”. These (sub)devices basically have two major roles: they expand the possibilities of the
MCU making it more versatile, and they take off the burden for some repetitive and “dumber” tasks (mainly
communication) from the CPU.
Every microcontroller is supplied with at least a couple of integrated peripherals – commonly, these include timers,
interrupt mechanisms and AD converters. More powerful microcontrollers can command a larger number of more diverse
peripherals. In this chapter, we will cover some common systems and the ways to utilize them from BASIC programming
language.
Interrupts are mechanisms which enable instant response to events such as counter overflow, pin change, data received,
etc. In normal mode, microcontroller executes the main program as long as there are no occurrences that would cause an
interrupt. Upon interrupt, microcontroller stops the execution of main program and commences the special part of the
program which will analyze and handle the interrupt. This part of program is known as the interrupt (service) routine.
In BASIC, interrupt service routine is defined by procedure with reserved name interrupt. Whatever code is stored in
that procedure, it will be executed upon interrupt.
First, we need to determine which event caused the interrupt, as PIC microcontroller calls the same interrupt routine
regardless of the trigger. After that comes the interrupt handling, which is executing the appropriate code for the trigger
event.
In the main loop, program keeps LED_run diode on and LED_int diode off. Pressing the button T causes the interrupt –
microcontroller stops executing the main program and starts the interrupt procedure.
program testinterrupt
end if
end if
end if
end if
end sub
main:
end.
Now, what happens when we push the button? Our interrupt routine first analyzes the interrupt by checking flag bits with
couple of if..then instructions, because there are several possible interrupt causes. In our case, an external interrupt
took place (pin RB0/INT state changes) and therefore bit INTF in INTCON register is set. Microcontroller will change
LED states, and provide a half second delay for us to actually see the change. Then it will clear INTF bit in order to
enable interrupts again, and return to executing the main program.
In situations where microcontroller must respond to events unrelated to the main program, it is very useful to have an
interrupt service routine. Perhaps, one of the best examples is multiplexing the seven-segment display – if multiplexing
code is tied to timer interrupt, main program will be much less burdened because display refreshes in the background.
A number of microcontrollers have built in Analog to Digital Converter (ADC). Commonly, these AD converters have 8-
bit or 10-bit resolution allowing them voltage sensitivity of 19.5mV or 4.8mV, respectively (assuming that default 5V
voltage is used).
The simplest AD conversion program would use 8-bit resolution and 5V of microcontroller power as referent voltage
(value which the value "read" from the microcontroller pin is compared to). In the following example we measure voltage
on RA0 pin which is connected to the potentiometer (see the figure below).
Potentiometer gives 0V in one terminal position and 5V in the other – since we use 8-bit conversion, our digitalized
voltage can have 256 steps. The following program reads voltage on RA0 pin and displays it on port B diodes. If not one
diode is on, result is zero and if all of diodes are on, result is 255.
program ADC_8
main:
eloop:
ADCON0.2 = 1 ' Conversion starts
wait:
First, we need to properly initialize registers ADCON1 and ADCON0. After that, we set ADCON0.2 bit which initializes
the conversion and then check ADCON0.2 to determine if conversion is over. If over, the result is stored into ADRESH
and ADRESL where from it can be copied.
Former example could also be carried out via ADC_Read instruction. Our following example uses 10-bit resolution:
program ADC_10
main:
TRISA = %11111111 ' PORTA is input
As one port is insufficient, we can use LCD for displaying all 10 bits of result. Connection scheme is below and the
appropriate program follows. For more information on LCD routines, check Chapter 5.2: Library Routines.
program ADC_on_LCD
main:
eloop:
TMR0 timer is an 8-bit special function register with working range of 256. Assuming that 4MHz oscillator is used,
TMR0 can measure 0-255 microseconds range (at 4MHz, TMR0 increments by one microsecond). This period can be
increased if prescaler is used. Prescaler divides clock in a certain ratio (prescaler settings are made in OPTION_REG
register).
Our following program example shows how to generate 1 second using TMR0 timer. For visual purposes, program
toggles LEDs on PORTB every second.
Before the main program, TMR0 should have interrupt enabled (bit 2) and GIE bit (bit 7) in INTCON register should be
set. This will enable global interrupts.
program Timer0_1sec
main:
a = 0
b = 1
OPTION_REG = $84 ' Assign prescaler to TMR0
TRISB = 0 ' PORTB as output
PORTB = $FF ' Initialize PORTB
cnt = 0 ' Initialize cnt
TMR0 = 96
INTCON = $A0 ' Enable TMRO interrupt
' If cnt is 200, then toggle PORTB LEDs and reset cnt
do
if cnt = 200 then
PORTB = not(PORTB)
cnt = 0
end if
loop until 0 = 1
end.
Prescaler is set to 32, so that internal clock is divided by 32 and TMR0 increments every 31 microseconds. If TMR0 is
initialized at 96, overflow occurs in (256-96)*31 us = 5 ms. We increase cnt every time interrupt takes place, effectively
measuring time according to the value of this variable. When cnt reaches 200, time will total 200*5 ms = 1 second.
TMR1 timer is a 16-bit special function register with working range of 65536. Assuming that 4MHz oscillator is used,
TMR1 can measure 0-65535 microseconds range (at 4MHz, TMR1 increments by one microsecond). This period can be
increased if prescaler is used. Prescaler divides clock in a certain ratio (prescaler settings are made in T1CON register).
Before the main program, TMR1 should be enabled by setting the zero bit in T1CON register. First bit of the register
defines the internal clock for TMR1 – we set it to zero. Other important registers for working with TMR1 are PIR1 and
PIE1. The first contains overflow flag (zero bit) and the other is used to enable TMR1 interrupt (zero bit). With TMR1
interrupt enabled and its flag cleared, we only need to enable global interrupts and peripheral interrupts in the INTCON
register (bits 7 and 6, respectively).
Our following program example shows how to generate 10 seconds using TMR1 timer. For visual purposes, program
toggles LEDs on PORTB every 10 seconds.
program Timer1_10sec
main:
TRISB = 0
T1CON = 1
PIR1.TMR1IF = 0 ' Clear TMR1IF
PIE1 = 1 ' Enable interrupts
PORTB = $F0
cnt = 0 ' Initialize cnt
INTCON = $C0
' If cnt is 152, then toggle PORTB LEDs and reset cnt
do
if cnt = 152 then
PORTB = not(PORTB)
cnt = 0
end if
loop until 0 = 1
end.
Prescaler is set to 00 so there is no dividing the internal clock and overflow occurs every 65.536 ms. We increase cnt
every time interrupt takes place, effectively measuring time according to the value of this variable. When cnt reaches 152,
time will total 152*65.536 ms = 9.96 seconds.
Microcontrollers of PIC16F87X series have one or two built-in PWM outputs (40-pin casing allows 2, 28-pin casing
allows 1). PWM outputs are located on RC1 and RC2 pins (40-pin MCUs), or on RC2 pin (28-pin MCUs). Refer to PWM
library (Chapter 5.2: Library Routines) for more information.
The following example uses PWM library for getting various light intensities on LED connected to RC2 pin. Variable
which represents the ratio of on to off signals is continually increased in the loop, taking values from 0 to 255. This results
in continual intensifying of light on LED diode. After value of 255 has been reached, process begins anew.
program PWM_LED_Test
dim j as byte
main:
end.
The easiest way to transfer data between microcontroller and some other device, e.g. PC or other microcontroller, is the
RS-232 communication (also referred to as EIA RS-232C or V.24). RS232 is a standard for serial binary data interchange
between a DTE (Data terminal equipment) and a DCE (Data communication equipment), commonly used in personal
computer serial ports. It is a serial asynchronous 2-line (Tx for transmitting and Rx for receiving) communication with
effective range of 10 meters.
Microcontroller can establish communication with serial RS-232 line via hardware UART (Universal Asynchronous
Receiver Transmitter) which is an integral part of PIC16F87X microcontrollers. UART contains special buffer registers
for receiving and transmitting data as well as a Baud Rate generator for setting the transfer rate.
This example shows data transfer between the microcontroller and PC connected by RS-232 line interface MAX232
which has role of adjusting signal levels on the microcontroller side (it converts RS-232 voltage levels +/- 10V to TTL
levels 0-5V and vice versa).
Our following program example illustrates use of hardware serial communication. Data received from PC is stored into
variable dat and sent back to PC as confirmation of successful transfer. Thus, it is easy to check if communication works
properly. Transfer format is 8N1 and transfer rate is 2400 baud.
program USART_Echo
main:
end.
In order to establish the communication, PC must have a communication software installed. One such communication
terminal is part of mikroBasic IDE. It can be accessed by clicking Tools > Terminal from the drop-down menu. Terminal
allows you to monitor transfer and to set all the necessary transfer settings. First of all, we need to set the transfer rate to
2400 to match the microcontroller's rate. Then, select the appropriate communication port by clicking one of the 4
available (check where you plugged the serial cable).
After making these adjustments, clicking Connect starts the communication. Type your message and click Send Message
– message will be sent to the microcontroller and back, where it will be displayed on the screen.
Note that serial communication can also be software based on any of 2 microcontroller pins – for more information, check
the Chapter 9: Communications.
PIC, PIC, PICmicro, and MPLAB are registered and protected trademarks of the Microchip Technology Inc. USA. Microchip logo
and name are the registered tokens of the Microchip Technology. mikroBasic is a registered trade mark of mikroElektronika. All
other tokens mentioned in the book are the property of the companies to which they belong.
mikroElektronika © 1998 - 2004. All rights reserved. If you have any questions, please contact our office.
● Introduction
● 7.1 LED Diode
● 7.2 Seven-Segment Display
● 7.3 LCD Display, 4-bit and 8-bit Interface
● 7.4 Graphical LCD
● 7.5 Sound Signalization
Introduction
Microcontrollers deal very well with 0’s and 1’s, but humans do not. We need indicator lights, numbers, letters, charts,
beepers… In order to comprehend the information presented quicker and better, we need that information to be displayed
to us in many different ways. In practice, human - machine communication can require substantial (machine) resources,
so it is sometimes better to dedicate an entire microcontroller to that task. This device is then called the Human -
Machine Interface or simply HMI. The second microcontroller is then required to get the human wishes from HMI, “do
the job” and put the results back to HMI, so that operator can see it.
Clearly, the most important form of communication between the microcontroller system and a man is the visual
communication. In this chapter we will discuss various ways of displaying data, from the simplest to more elaborate
ones. You’ll see how to use LED diodes, Seven-Segment Displays, character- and graphic LCDs. We will also consider
using BASIC for sound signalization necessary in certain applications.
Just remember: the more profound communication you wish to be, the more MCU resources it’ll take.
One of the most frequently used components in electronics is surely the LED diode (LED stands for Light Emitting
Diode). Some of common LED diode features include: size, shape, color, working voltage (Diode voltage) Ud and
electric current Id. LED diode can be round, rectangular or triangular in shape, although manufacturers of these
components can produce any shape needed for specific purposes. Size i.e. diameter of round LED diodes ranges from 3
to 12 mm, with 3 - 5 mm sizes most commonly used. Common colors include red, yellow, green, orange, blue, etc.
Working voltage is 1.7V for red, 2.1V for green and 2.3 for orange color. This voltage can be higher depending on the
manufacturer. Normal current Id through diode is 10 mA, while maximal current reaches 25 mA. High current
consumption can present problem to devices with battery power supply, so in that case low current LED diode (Id ~ 1-2
mA) should be used. For LED diode to emit light with maximum capacity, it is necessary to connect it properly or it
might get damaged.
The positive pole is connected to anode, while ground is connected to cathode. For matter of differentiating the two,
cathode is marked by mark on casing and shorter pin. Diode will emit light only if current flows from anode to cathode;
in the other case there will be no current. Resistor is added serial to LED diode, limiting the maximal current through
diode and protecting it from damage. Resistor value can be calculated from the equation on the picture above, where Ur
represents voltage on resistor. For +5V power supply and 10 mA current resistor used should have value of 330•.
LED diode can be connected to microcontroller in two ways. One way is to have microcontroller "turning on" LED
diode with logical one and the other way is with logical zero. The first way is not so frequent (which doesn't mean it
doesn't have applications) because it requires the microcontroller to be diode current source. The second way works with
higher current LED diodes.
program LED_Blinking
main:
TRISB = 0 ' PORTB is output
PORTB = %11111111 ' Turn ON diodes on PORTB
Delay_ms(1000) ' Wait for 1 second
PORTB = %00000000 ' Turn OFF diodes on PORTB
Delay_ms(1000) ' Wait for 1 second
goto main ' Endless loop
end.
Seven-segment digits represent more advanced form of visual communication. The name comes from the seven diodes
(there is an eighth diode for a dot) arranged to form decimal digits from 0 to 9. Appearance of a seven-segment digit is
given on a picture below.
As seven-segment digits have better temperature tolerance and visibility than LCD displays, they are very common in
industrial applications. Their use satisfies all criteria including the financial one. They are commonly used for displaying
value read from sensors, etc.
One of the ways to connect seven-segment display to the microcontroller is given in the figure below. System is
connected to use seven-segment digits with common cathode. This means that segments emit light when logical one is
brought to them, and that output of all segments must be a transistor connected to common cathode, as shown on the
picture. If transistor is in conducting mode any segment with logical one will emit light, and if not no segment will emit
light, regardless of its pin state.
Bases of transistors T1 and T2 are connected to pin0 and pin1 of PORTA. Setting those pins turns on the transistor,
allowing every segment from "a" to "h", with logical one on it, to emit light. If zero is on transistor base, none of the
segments will emit light, regardless of the pin state.
Using the previous scheme, we could display a sequence of nine digits like this:
program seven_seg_onedigit
dim i as byte
main:
do
for i = 0 to 9
PORTB = mask(i)
Delay_ms(1000)
next i
loop until false ' Endless loop
end.
Purpose of the program is to display numbers 0 to 9 on the ones digit, with 1 second delay. In order to display a number,
its mask must be sent to PORTB. For example, if we need to display "1", segments b and c must be set to 1 and the rest
must be zero. If (according to the scheme above) segments b and c are connected to the first and the second pin of
PORTB, values 0000 and 0110 should be set to PORTB. Thus, mask for number "1" is value 0000 0110 or 06
hexadecimal. The following table contains corresponding mask values for numbers 0-9:
Digit Seg. h Seg. g Seg. f Seg. e Seg. d Seg. c Seg. b Seg. a HEX
0 0 0 1 1 1 1 1 1 $3F
1 0 0 0 0 0 1 1 0 $06
2 0 1 0 1 1 0 1 1 $5B
3 0 1 0 0 1 1 1 1 $4F
4 0 1 1 0 0 1 1 0 $66
5 0 1 1 0 1 1 0 1 $6D
6 0 1 1 1 1 1 0 1 $7D
7 0 0 0 0 0 1 1 1 $07
8 0 1 1 1 1 1 1 1 $7F
9 0 1 1 0 1 1 1 1 $6F
You are not, however, limited to displaying digits. You can use 7seg Display Decoder, a built-in tool of mikroBasic, to
get hex code of any other viable combination of segments you would like to display.
But what do we do when we need to display more than one digit on two or more displays? We have to put a mask on one
digit quickly enough and activate its transistor, then put the second mask and activate the second transistor (of course, if
one of the transistors is in conducting mode, the other should not work because both digits will display the same value).
The process is known as “multiplexing”: digits are displayed in a way that human eye gets impression of simultaneous
display of both digits – actually only one display emits at any given moment.
Now, let’s say we need to display number 38. First, the number should be separated into tens and ones (in this case,
digits 3 and 8) and their masks sent to PORTB. The rest of the program is very similar to the last example, except for
having one transition caused by displaying one digit after another:
program seven_seg_twodigits
dim v as byte
dim por1 as byte
dim por2 as byte
main:
end.
The multiplexing problem is solved for now, but your program probably doesn’t have a sole purpose of printing constant
values on 7seg display. It is usually just a subroutine for displaying certain information. However, this approach to
printing data on display has proven sto be very convenient for more complicated programs. You can also move part of
the program for refreshing the digits (handling the masks) to the interrupt routine.
The following example increases variable i from 0 to 99 and prints it on displays. After reaching 99, counter begins anew.
program seven_seg_counting
dim i as byte
dim j as byte
dim v as byte
dim por1 as byte
end sub
if v = 0 then
PORTB = por2 ' Prepare mask for digit
PORTA = 1 ' Turn on 1st, turn off 2nd 7seg
v = 1
else
PORTB = por1 ' Prepare mask for digit
PORTA = 2 ' Turn on 2nd, turn off 1st 7seg
v = 0
end if
TMR0 = 0
INTCON = $20
end sub
main:
OPTION_REG = $80
por2 = $3F
j = 0
TMR0 = 0
INTCON = $A0 ' Disable PEIE, INTE, RBIE, T0IE
TRISA = 0
TRISB = 0
PORTB = 0
PORTA = 0
do
for i = 0 to 99 ' Count from 0 to 99
Delay_ms(1000)
next i
loop until false
end.
In the course of the main program, programmer doesn’t need to worry of refreshing the display. Just call the subroutine
mask every time display needs to change.
One of the best solutions for devices that require visualizing the data is the “smart” Liquid Crystal Display (LCD). This
type of display consists of 7x5 dot segments arranged in rows. One row can consist of 8, 16, 20, or 40 segments, and
LCD display can have 1, 2, or 4 rows.
LCD connects to microcontroller via 4-bit or 8-bit bus (4 or 8 lines). R/W signal is on the ground, because
communication is one-way (toward LCD). Some displays have built-in backlight that can be turned on with RD1 pin via
PNP transistor BC557.
Our following example prints text on LCD via 4-bit interface. Assumed pin configuration is default.
program LCD_default_test
main:
end.
Our second example prints text on LCD via 8-bit interface, with custom pin configuration.
program LCD8_test
main:
TRISB = 0 ' PORTB is output
TRISD = 0 ' PORTD is output
' Initialize LCD at PORTB and PORTD with custom pin settings
LCD8_Config(PORTB,PORTD,2,3,0,7,6,5,4,3,2,1,0)
Most commonly used Graphical LCD (GLCD) has screen resolution of 128x64 pixels. This allows creating more
elaborate visual messages than usual LCD can provide, involving drawings and bitmaps.
The following figure shows GLCD HW connection by default initialization (using GLCD_LCD_Init routine); if you
need different pin settings, refer to GLCD_LCD_Config.
BASIC offers a comprehensive library for GLCD – refer to Chapter 5: Built-in and Library Routines for more
information. Our following example demonstrates the possibilities of GLCD and the mentioned library. Note that the
library works with PIC18 only.
program GLCD_test
' For PIC18
main:
PORTC = 0
PORTB = 0
PORTD = 0
TRISC = 0
TRISD = 0
TRISB = 0
while true
GLCD_Clear_Screen
Delay_Ms(4000)
Delay_Ms(4000)
GLCD_Clear_Screen
GLCD_Line(0,63, 50, 0)
Delay_Ms(5000)
Some applications require sound signalization in addition to visual or instead of it. It is commonly used to alert or
announce the termination of some long, time-consuming process. The information presented by such means is fairly
simple, but relieves the user from having to constantly look into displays and dials.
BASIC’s Sound library facilitates generating sound signals and output on specified port. We will present a simple
demonstration using piezzo speaker connected to microcontroller’s port.
program Sound
' The following three tones are calculated for 4MHz crystal
sub procedure Tone1
Sound_Play(200, 200) ' Period = 2ms <=> 500Hz, Duration = 200 periods
end sub
Tone1
Tone2
Tone3
Tone3
Tone1
Tone2
Tone3
Tone3
Tone1
Tone2
Tone3
Tone1
Tone2
Tone3
Tone3
Tone1
Tone2
Tone3
Tone3
Tone3
Tone2
Tone1
end sub
main:
TRISB = $F0
while true
if Button(PORTB,7,1,1) then ' RB7 plays Tone1
Tone1
end if
while TestBit(PORTB,7) = 1 ' Wait for button to be released
nop
wend
wend
wend
end.
PIC, PIC, PICmicro, and MPLAB are registered and protected trademarks of the Microchip Technology Inc. USA. Microchip logo
and name are the registered tokens of the Microchip Technology. mikroBasic is a registered trade mark of mikroElektronika. All
other tokens mentioned in the book are the property of the companies to which they belong.
mikroElektronika © 1998 - 2004. All rights reserved. If you have any questions, please contact our office.
● Introduction
● 8.1 EEPROM Memory
● 8.2 Flash Memory
● 8.3 Compact Flash
Introduction
There is no program on this world that doesn’t interact with memory in some way. First, during its
execution, it retains the operational data from, uses or alters it, and puts it back into the program
memory. Second, it is often necessary to store and handle large amount of data that can be obtained
from various sources, whether it is the car engine temperature acquisition data or some bitmap image
to be displayed on the GLCD. In this chapter we will focus on the latter problem, i.e. we’ll go through
the techniques of manipulating data on the so-called memory storage devices and systems.
Data used by microcontroller is stored in the RAM memory as long as there is a power supply present.
If we need to keep the data for later use, it has to be stored in a permanent memory. An EEPROM
(E²PROM), or Electrically-Erasable Programmable Read-Only Memory is a non-volatile storage chip,
commonly used with PIC microcontrollers for this purpose. An EEPROM can be programmed and
erased multiple times electrically – it may be erased and reprogrammed only a certain number of
times, ranging from 100,000 to 1,000,000, but it can be read an unlimited number of times.
Some PIC microcontrollers have internal EEPROM allowing you to store information without any
BASIC has a library for working with internal EEPROM which makes writing and reading data very
easy. Library function EEPROM_Read reads data from a specified address, while library procedure
EEPROM_Write writes data to the specified address.
Note: Be aware that all interrupts will be disabled during execution of EEPROM_Write routine (GIE
bit of INTCON register will be cleared). Routine will set this bit on exit. Ensure minimum 20ms delay
between successive use of routines EEPROM_Write and EEPROM_Read. Although EEPROM will
write the correct value, EEPROM_Read might return undefined result.
In our following example, we will write a sequence of numbers to successive locations in EEPROM.
Afterwards, we’ll read these and output to PORTB to verify the process.
program EEPROM_test
dim i as byte
dim j as byte
main:
TRISB = 0
for i = 0 to 20
EEPROM_Write(i, i + 6)
next i
Delay_ms(30)
for i = 0 to 20
PORTB = EEPROM_Read(i)
for j = 0 to 200
Delay_us(500)
next j
next i
end.
Occasionally, our needs will exceed the capacity of PIC’s internal EEPROM. When we need to store a
larger amount of data obtained by PIC, we have an option of using external serial EEPROM. Serial
means that EEPROM uses one of the serial protocols (I2C, SPI, microwire) for communication with
microcontroller. In our example, we will work with EEPROM from 24Cxx family which uses two
lines and I2C protocol for communication with MCU.
Serial EEPROM connects to microcontroller via SCL and SDA lines. SCL line is a clock for
synchronizing the transfer via SDA line, with frequency going up to 1MHz.
I2C communication allows connecting multiple devices on a single line. Therefore, bits A1 and A0
have an option of assigning addresses to certain I2C devices by connecting the pins A1 and A0 to the
ground and +5V (one I2C line could be EEPROM on address $A2 and, say, real time clock PCF8583
on address $A0). R/W bit of address byte selects the operation of reading or writing data to memory.
More detailed data on I2C communication can be found in the technical documentation of any I2C
device.
Our following program sends data to EEPROM at address 2. To verify transfer, we’ll read data via
I2C from EEPROM and send its value to PORTD. For more information on I2C Library consult
Chapter 5: Built-in and Library Routines.
program EEPROM_test
main:
I2C_init(100000) ' Initialize full master mode
TRISD = 0 ' PORTD is output
PORTD = $ff ' Initialize PORTD
I2C_Start ' Issue I2C start signal
I2C_Wr($a2) ' Send byte via I2C(command to 24cO2)
EE_adr = 2
I2C_Wr(EE_adr) ' Send byte(address of EEPROM)
EE_data = $aa
I2C_Wr(EE_data) ' Send data(data that will be written)
I2C_Stop ' Issue I2C stop signal
end.
Flash memory is a form of EEPROM that allows multiple memory locations to be erased or written in
one programming operation. Normal EEPROM only allows one location at a time to be erased or
written, meaning that Flash can operate at higher effective speeds when the systems using it read and
write to different locations at the same time.
Flash memory stores information on a silicon chip in a way that does not need power to maintain the
information in the chip. This means that if you turn off the power to the chip, the information is
retained without consuming any power. In addition, Flash offers fast read access times and solid-state
shock resistance. These characteristics make it very popular for microcontroller applications and for
applications such as storage on battery-powered devices like cell phones.
Many modern PIC microcontrollers utilize Flash memory, usually in addition to normal EEPROM
storage chip. Therefore, BASIC provides a library for direct accessing and working with MCU’s
Flash. Note: Routines differ for PIC16 and PIC18 families, please refer to Chapter 5: Built-in and
Library Routines.
program flash_pic18_test
main:
TRISB = 0 ' PORTB is output
for i = 0 to 63 ' initialize array
toWrite[i] = i
next i
Flash_Write($0D00, toWrite) ' write contents of the
array to the address 0x0D00
' verify write
PORTB = 0 ' turn off PORTB
toRead = FLASH_ERROR ' initialize error state
for i = 0 to 63
toRead = Flash_Read($0D00+i) ' read 64 consecutive
locations starting from 0x0D00
if toRead <> toWrite[i] then ' stop on first error
program flash_pic16_test
main:
TRISB = 0 ' PORTB is output
for i = 0 to 63
Compact Flash (CF) was originally a type of data storage device, used in portable electronic devices.
As a storage device, it typically uses Flash memory in a standardized enclosure. At present, the
physical format is used in handheld and laptop computers, digital cameras, and a wide variety of other
devices, including desktop computers. Great capacity (8MB ~ 8GB, and more) and excellent access
time of typically few microseconds make them very attractive for microcontroller applications.
Flash memory devices are non-volatile and solid state, and thus are more robust than disk drives,
consuming only about 5% of the power required by small disk drives. They operate at 3.3 volts or 5
volts, and can be swapped from system to system. CF cards are able to cope with extremely rapid
changes in temperature – industrial versions of flash memory cards can operate at a range of -45°C to
+85°C.
BASIC includes a library for accessing and handling data on Compact Flash card. In CF card, data is
divided into sectors, one sector usually comprising 512 bytes (few older models have sectors of 256B).
Read and write operations are not performed directly, but successively through 512B buffer. These
routines are intented for use with CF that have FAT16 and FAT32 file system. Note: routines for file
handling (CF_File_Write_Init, CF_File_Write_Byte,
CF_File_Write_Complete) can only be used with FAT16 file system, and only with PIC18
family!
File accessing routines can write file. File names must be exactly 8 characters long and written in
uppercase. User must ensure different names for each file, as CF routines will not check for possible
match. Before write operation, make sure you don't overwrite boot or FAT sector as it could make
your card on PC or digital cam unreadable. Drive mapping tools, such as Winhex, can be of a great
assistance.
Here’s an example for using Compact Flash card from BASIC. A set of files is written on CF card.
This can be checked later by plugging the CF card on a PC or a digital camera. Observe the way the
file is being written:
program CompactFlash_File
' for PIC18
dim i1 as word
dim index as byte
dim fname as char[9]
dim ext as char[4]
main:
ext = "txt" ' File extensions will be
"txt"
index = 0 ' Index of file to be
written
http://www.mikroelektronika.co.yu/english/product/books/picbasicbook/08.htm (9 sur 12)05/11/2004 02:28:30
Programming PIC Microcontrollers in BASIC - mikroElektronika
end.
If you do not wish to use your CF card in PCs and digicams but ruther as a simple storage device for
your PIC MCU only, you can then ignore the entire FAT system and store data directly to CF memory
sectors:
program cf_test
dim i as word
main:
TRISC = 0 ' PORTC is output
CF_Init_Port(PORTB,PORTD) ' Initialize ports
do
nop
loop until CF_Detect(PORTB) = true ' Wait until CF
card is inserted
Delay_ms(500)
CF_Write_Init(PORTB, PORTD, 590, 1) ' Initialize write
at sector address 590
' of 1 sector
(512 bytes)
for i = 0 to 511 ' Write 512 bytes
to sector (590)
CF_Write_Byte(PORTB, PORTD, i + 11)
next i
PORTC = $FF
Delay_ms(1000)
CF_Read_Init(PORTB, PORTD, 590, 1) ' Initialize write
at sector address 590
' of 1 sector
(512 bytes)
for i = 0 to 511 ' Read 512 bytes
from sector (590)
PORTC = CF_Read_Byte(PORTB, PORTD) ' and display
it on PORTC
Delay_ms(1000)
next i
end.
PIC, PIC, PICmicro, and MPLAB are registered and protected trademarks of the Microchip Technology Inc.
USA. Microchip logo and name are the registered tokens of the Microchip Technology. mikroBasic is a
registered trade mark of mikroElektronika. All other tokens mentioned in the book are the property of the
companies to which they belong.
mikroElektronika © 1998 - 2004. All rights reserved. If you have any questions, please contact our office.