Copyright © mikroElektronika, December 2011. All rights reserved.
1. Introduction to mikroBasic PRO for ARM
01 mikroBasic PRO for ARM® organizes applications into projects consisting of a single project file (file with the .mbpar
extension) and one or more source files (files with the .c extension). The mikroBasic PRO for ARM® compiler allows you to manage several projects at a time. Source files can be compiled only if they are part of the project.
02
06
07
03
A project file contains:
• Project name and optional description;
• Target device in use;
• Device clock;
• List of the project source files;
• Binary files (*.emcl); and
• Other files.
04
05
In this reference guide, we will create a new project, write code, compile it and test the results. The purpose of this project is to make microcontroller PORTA LEDs blink, which will be easy to test.
01 Main Toolbar
02 Code Explorer
03 Project Settings
Page 2
04 Messages
05 Code Editor
06 Image Preview
08
07 Project Manger
08 Library Manager
Page 3
Page 2
2. Hardware Connection
VCORE
Let’s make a simple “Hello world” example for the selected microcontroller. First thing embedded programmers usually write is a simple LED blinking program. So, let’s do that in a few simple lines of
Basic code.
VCORE
AVCC
LED blinking is just turning ON and OFF LEDs that are connected to desired PORT pins. In order to see the example in action, it is necessary to connect the target microcontroller according to schematics shown on Figure 2-1 . In the project we are about to write, we will use only PORTA , so you should connect the LEDs to PORTA only.
E9
10uF
10
8
9
6
7
4
5
11
12
13
14
15
1
2
3
22
23
24
25
16
17
18
19
20
21
PG1
PG0
VDD
GND
PC7
PC6
PC5
PC4
PE7
PE6
VDDA
GNDA
PE5
PE4
LDO
VDD
GND
PD0
PD1
PD2
PD3
PJ0
PH7
XTALPPHY
XTALNPHY
LM3S9B95
U1
PE1
PE0
USB0BIAS
PB2/I2C0SCL
USB0DP
USB0DM
GND
VDD
PB1/USB0VBUS
PB0/USB0ID
PB3/I2C0SDA
RST
PH5
PH6
PF1
PF2
PF3
MDIO
GND
VDD
PJ7
PJ6
PJ5
PJ4
NC
63
62
61
60
59
68
67
66
65
64
75
74
73
72
71
70
69
54
53
52
51
58
57
56
55
VCC-3.3
R61
9K1 LD0
LED
R1
4K7
LD4
LED
R5
4K7
VCC3
VCC3
R2
4K7
LD1
LED
R6
4K7
LD5
LED
Figure 2-1:
Hardware connection schematics
R3
4K7
LD2
LED
R7
4K7
LD6
LED
R4
4K7
LD3
LED
R8
4K7
LD7
LED
Prior to creating a new project, it is necessary to do the following:
Step 1: Install the compiler
Install the mikroBasic PRO for ARM® compiler from the Product DVD or download it from the MikroElektronika website: http://www.mikroe.com/eng/products/view/753/mikrobasic-pro-for-arm/
Step 2: Start up the compiler
Double click on the compiler icon in the Start menu, or on your desktop to Start up the mikroBasic PRO for ARM® compiler. The mikroBasic
PRO for ARM® IDE (Integrated Development Environment) will appear on the screen. Now you are ready to start creating a new project.
Page 3
3. Creating a New Project
The process of creating a new project is very simple. Select the New Project option from the Project menu as shown below. The New
Project Wizard window appears. It can also be opened by clicking the New Project icon from the Project toolbar .
The New Project Wizard ( Figure 3-1 ) will guide you through the process of creating a new project. The introductory window of this application contains a list of actions to be performed when creating a new project.
01 Click Next .
01
Figure 3-1: Introductory window of the New Project Wizard
Page 4 Page 5
Page 4
Step 1 - Project Settings
First thing we have to do is to specify the general project information. This is done by selecting the target microcontroller, it’s operating clock frequency, and of course
- naming our project. This is an important step, because compiler will adjust the internal settings based on this information.
Default configuration is already suggested to us at the begining. We will not change the microcontroller, and we will leave the default
LM3S9B95 as the choice for this project.
Figure 3-2: You can specify project name, path, device and clock in the first step
Page 5
Step 1 - Project Settings
If you do not want to use the suggested path for storing your new project, you can change the destination folder . In order to do that, follow a simple procedure:
01 Click the Browse button of the Project
Settings window to open the Browse for Folder dialog.
02 Select the desired folder to be the destination path for storing your new project files.
03 Click the OK button to confirm your selection and apply the new path.
02
01
03
Figure 3-3: Change the destination folder using Browse For Folder dialog
Page 6 Page 7
Page 6
Step 1 - Project Settings
Once we have selected the destination project folder, let’s do the rest of the project settings:
01
01 Enter the name of your project. Since we are going to blink some LEDs, it’s appropriate to call the project
“LedBlinking”
02 For this demonstration, we will use the default 16MHz clock . Clock speed depends on your target hardware, and whether you are using PLL or not. But however you configure your hardware, make sure to specify the exact clock
( Fosc ) that the microcontroller is operating at.
03 Click the OK button to proceed.
02
03
Figure 3-4: Enter project name and change device clock speed if necessary
Page 7
Step 2 - Add files
This step allows you to include additional files that you need in your project: some headers or source files that you already wrote, and that you might need in further development.
Since we are building a simple application, we won’t be adding any files at this moment.
01
Click Next .
01
Figure 3-5: Add existing headers, sources or other files if necessary
Page 8 Page 9
Page 8
Step 3 - Include Libraries
Following step allows you to quickly set whether you want to include all libraries in your project, or not. Even if all libraries are included, they will not consume any memory unless they are explicitely used from within your code. The main advantage of including all libraries is that you will have over 500 functions available for use in your code right away, and visible from Code Assistant
[CTRL+Space] . We will leave this in default configuration:
01 Make sure to leave “Include All” selected.
02
Click Next.
01
02
Figure 3-6: Include all libraries in the project, which is a default configuration.
Page 9
Step 4 - Finishing
After all configuration is done, final step allows you to do just a bit more.
01 There is a check-box called “Open Edit
Project window to set Configuration bits” at the final step. Edit Project is a specialized window which allows you to do all the necessary oscillator and PLL settings. We made sure that everything is described in plain English, so you will be able to do the settings without having to open the datasheet. Anyway, since we are only building a simple application, we will leave it at default configuration (internal 16MHz oscillator with PLL disabled). Therefore, leave the checkbox unchecked.
02 Click Finish .
01
02
Figure 3-7: Choose whether to open Edit Project window after dialog closes.
Page 10 Page 11
Page 10
Blank new project created
New project is finally created. A new source file called “LedBlinking.mbas” is created and it contains the main: function, which will hold the program. You may notice that project is configured according to the settings done in the New Project Wizard .
Figure 3-8: New blank project is created with your configuration
Page 11
4. Code Example
Time has come to do some coding. mikroBasic
PRO for ARM® has the unique libraries that enable you to do complicated tasks in a single line of code. Built-in GPIO library enables you to set configure each PORT and enable pins that you need, without worrying about complex procedure that this operation requires. To demonstrate this, we will write our first line of code:
‘ Set PORTA as digital output
GPIO_Digital_Output(
@GPIO_PORTA,
_GPIO_PINMASK_ALL)
Once we have enabled PORTA to act as digital output, we can now initialize PORTA with logic zeros on every PORT pin:
‘ Set PORTA initial value to 0
GPIO_PORTA_DATA = 0
Finally, in a while() loop we will toggle the
PORTA value, and put a 1000 ms delay, so the blinking is not too fast.
LedBlinking.mbas - source code
13
14
15
16
9
10
11
12
7
8
5
6
3
4
1
2
17
18
19
20
21
22
program LedBlinking
‘ Declarations section main:
‘ Main program
‘ Set PORTA as digital output
GPIO_Digital_Output(@GPIO_PORTA,
_GPIO_PINMASK_ALL)
‘ Set PORTA initial value to zero
GPIO_PORTA_DATA = 0 while TRUE
‘ Toggle PORTA
GPIO_PORTA_DATA = NOT GPIO_PORTA_DATA
‘ Delay 1000 ms
Delay_ms(1000) wend end.
Figure 4-1: Complete source code of the PORTA LED blinking
Page 12 Page 13
Page 12
Figure 4-2: This is how the code looks written in compiler code editor window
Page 13
5. Building the Source
When we are done writing our first
LedBlinking code, we can now build the project and create a .HEX file which can be loaded into our target microcontroller, so we can test the program on real hardware. “Building” includes compilation, linking and optimization which is all done automatically. Build your code by clicking on the icon in the main toolbar, or simply go to Build menu and click Build [CTRL+F9] . Message window will report the details of the building process ( Figure 5-2 ). Compiler automatically creates necessary output files. LedBlinking.hex
( Figure 5-1 ) is among them.
Figure 5-1: Listing of project files after building is done
Figure 5-2: After the successful compilation and linking, the message window should look something like this
Page 14 Page 15
Page 14
6. Changing Project Settings
If you need to change the target microcontroller or clock speed, you don’t have to go through the new project wizard all over again. This can be done quickly in the Edit Project window. You can open it using Project->Edit Project [CTRL+SHIFT+E] menu option.
02
01
01
To change your MCU, just select the desired microcontroller from the dropdown list.
02
03
02
To change your oscillator settings enter the oscillator value and adjust oscillator configuration registers using drop-down boxes.
03
03 Several most commonly used oscillator settings can be loaded using the provided oscillator “schemes”.
Load the desired scheme by clicking the Load Scheme button.
04
Select whether to build a Debug
HEX , which is necessary for hardware debugging, or a final Release HEX .
Figure 6-1: Edit Project Window
Page 15
If you want to learn more about our products, please visit our website at www.mikroe.com. If you are experiencing some problems with any of our products or just need additional information, please place your ticket at www.mikroe.com/esupport If you have any questions, comments or business proposals, do not hesitate to contact us at [email protected]
Designed by
MikroElektronika,
December 2011.
