398
edits
Changes
PIC
,Undo revision 2983 by [[Special:Contributions/imported>Pew|imported>Pew]] ([[User talk:imported>Pew|talk]])
'''PIC''' microcontrollers are a relatively popular line of [[w:Reduced_instruction_set_computing|RISC]] line microcontrollers from [[w:Microchip_Technology|MicrochipTechnology]]. Different toolchains are required to build code between the 8-bit, 16-bit, and 32-bit data size lines. They are used in [[gp:ECE 2504 Introduction to Computer Engineering|ECE 2504 Introduction to Computer Engineering]] and [[gp:ECE 4534 Embedded System Design|ECE 4534 Embedded System Design]]. ==Toolchains=====8-Bit===The [[freeware]] [http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en536656 MCC18 toolchain] from Microchip provides libraries and will compile and link for the 8-bit data word chips such as PIC18 devices. MCC18 can be run on Linux using wine. [http://sdcc.sourceforge.net/index.php sdcc] is a [[software libre]] toolchain that supports a [http://sdcc.sourceforge.net/doc/sdccman.html/node122.html number of PIC18 devices]. ===16-Bit===To build a nonfree toolchain for Linux, use the instructions at [http://www.electricrock.co.nz/blog/microchip-c30/]. To build a completely [[software libre]] toolchain for the PIC24 or dsPIC, follow the steps below.<pre>sudo apt-get install build-essential tofrodosmkdir ~/prj/pic30cd ~/prj/pic30wget http://ww1.microchip.com/downloads/en/DeviceDoc/mplabalc30v3_31.tar.gzwget http://ww1.microchip.com/downloads/en/DeviceDoc/mplabc30v3_31.tar.gzwget http://www.electricrock.co.nz/c30/pic30-binutils-v01.tar.bz2wget http://www.electricrock.co.nz/c30/pic30-gcc-v01.tar.bz2tar xf mplabalc30v3_31.tar.gztar xf mplabc30v3_31.tar.gzfind . -type f -exec fromdos {} \;# We don't need to "fix" the search path by adding -nonfree directoriestar xf pic30-binutils-v01.tar.bz2 --exclude=search-path-fix.difftar xf pic30-gcc-v01.tar.bz2 --exclude=search-path-fix.difffor p in pic30-binutils-v01/patches/*; do patch -p0 < $p; donefor p in pic30-gcc-v01/patches/*; do patch -p0 < $p; donecd acmeCFLAGS=-DMCHP_VERSION=v3.31-Debian ./configure --prefix="${HOME}/prj/pic30/build" --target=pic30-coffmakecd ..cd gcc-4.0.2/gcc-4.0.2CFLAGS=-DMCHP_VERSION=v3.31-Debian ./configure --prefix="${HOME}/prj/pic30/build" --target=pic30-coff --enable-languages=cmakecd ../..</pre> ===32-Bit=== ==Programmers==See the [[PICKit 2]] article for programming your hex file natively using <code>pk2cmd</code>. ==Integrated Development Environments==MPLAB is the freeware IDE written by Microchip. Only Windows versions of older versions were made available, although those could be run with wine and with a [[Windows virtual machine]]. The newer MPLAB X is cross-platform [[freeware]]. [http://piklab.sourceforge.net/ Piklab] is a [[software libre]] IDE for PIC microcontrollers.
==Compiling Code==
MPLAB is the IDE recommended by the ECE department. It can be run inside a Virtual Machine, programming using USB passthrough. It can also be installed under wine and the compiler used from the commandline. [http://sdcc.sourceforge.net/index.php sdcc] is a GPL C compiler with some support for PIC devices. Some GNU utilities (namely the assembler and linker, but not compiler) have been modified to support Microchip's microprocessors as part of the [http://gputils.sourceforge.net/ gputils project]. [http://piklab.sourceforge.net/ Piklab] is an IDE with support for both open source toolchains.
MPLABX, the current version of MPLAB, runs natively under Linux.
===Using Wine to Run the Toolchain===
RM = rm
Proj1.cof : main.o messages.o interruptsinterSecure Shellrupts.o user_interrupts.o my_uart.o uart_thread.o timer1_thread.o timer0_thread.o my_i2c.o
$(LD) /p18F2680 /l"C:\MCC18\lib" "main.o" "messages.o" "interrupts.o" "user_interrupts.o" "my_uart.o" "uart_thread.o" "timer1_thread.o" "timer0_thread.o" "my_i2c.o" /u_CRUNTIME /u_EXTENDEDMODE /z__MPLAB_BUILD=1 /m"Proj1.map" /w /o"Proj1.cof"
==Programming==
See the [[PICKit 2]] article for programming your hex file natively using <code>pk2cmd</code>. The PICKit 3 has superceded the PICKit 2 but is lacking certain features. ==Debugging Hardware==Reading printf-style debugging messages over UART with the [[PICKit 2]] is possible from a Windows virtual machine with USB passthrough.
==Debugging=I2C===here's a variety of useful hardware available for debugging I2C:Reading printf* The [http://www.totalphase.com/products/aardvark-style debugging messages i2cspi/ Aardvark I2C/SPI Host Adapter] is capable of acting as either an I2C master or slave and reading and writing data over UART with USB. There is an [https://aur.archlinux.org/packages/aardvark-gui/ AUR package] for the Aardvark GUI for 32-bit machines. VTLUUG [https://vtluug.org/files/aardvark/ mirrors] other Aardvark files since they are no longer available on the PICKit 2 is possible from vendor's website. The Aardvark also works well in a Windows virtual machine VM with USB passthrough.* A [[Raspberry Pi]] has two onboard I2C buses and should be able to act as a master or slave. Performance and reliability may be suboptimal.* A [[Bus Pirate]] can act as an I2C master or slave and is suitable for human-speed interaction.
===UART===
UART can easily be debugged using an RS232 and a level shifter in the [https://en.wikipedia.org/wiki/MAX232 MAX232] family. For computers without hardware serial ports, USB to serial adapters have near-universal Linux support. For a simpler hardware setup, it may be desirable to use a Bus Pirate or Raspberry Pi as they both support 3v3 CMOS-level UART.
==External Links==
* [http://hackaday.com/2010/11/03/how-to-program-pics-using-linux/ How-to Program PICs using Linux - Hackaday] (see article and comments)
* [http://gun.io/open/43/libre-pic30-toolchain-bitbake-recipe Bounty on a libre pic30 toolchain BitBake recipe]
[[Category:Hardware]]
[[Category:Howtos]]
[[Category:Software]]
[[Category:Scripts]]