Command-Line Tools
From Curuxa
This is the list of command-line programs and scripts available in the Curuxa installers.
compile-mbp8
Compiles a source file written in C-language which is intended to run on a MBP8.
Usage
$> compile-mbp8 MyProgram.c
This generates a .hex file which can be burnt into the microcontroller.
compile-mbp14
Compiles a source file written in C-language which is intended to run on a MBP14.
Usage
$> compile-mbp14 MyProgram.c
This generates a .hex file which can be burnt into the microcontroller.
compile-mbp18
Compiles a source file written in C-language which is intended to run on a MBP18.
Usage
$> compile-mbp18 MyProgram.c
This generates a .hex file which can be burnt into the microcontroller.
compile-mbp40
Compiles a source file written in C-language which is intended to run on a MBP40.
Usage
$> compile-mbp40 MyProgram.c
This generates a .hex file which can be burnt into the microcontroller.
burnpic
Burns/writes a .hex file into a microcontroller using a PICkit 2.
Usage
- Compile your program
- Plug your PICkit 2 to your computer using a USB cable
- Connect your Main Board to the PICkit 2
- Execute:
$> burnpic MyProgram.hex
Now the microcontroller in your Main Board has your program written into it. As soon as you power on the circuit it will begin running.
runpic
Powers up your Main Board and all modules plugged to it at 5 volts. The program previously written to the microcontroller will begin running.
Usage
$> runpic
stoppic
Powers down your Main Board and all modules plugged to it. If the microcontroller was running it will stop.
Usage
$> stoppic
detectpic
Retrieves the exact model of PIC microcontroller plugged to your PICkit 2.
Usage
$> detectpic
Possible returned values
- PICkit 2 not plugged to your computer
$> detectpic
No PICkit 2 found- Main Board not connected to your PICkit 2
$> detectpic Auto-Detect: No known part found
- Everything is fine. Main Board plugged to PICkit 2, plugged to your computer
$> detectpic PIC16Fxxx
|
|