TARGET Embedded Mipsel

From Free Pascal wiki
Jump to: navigation, search

The mipsel-embedded target was created to target the pic32mx microcontroller chips produced by Microchip.

There exist several lines of chips:

Those are the most maker-friendly chips in the lineup, they come in the form of DIL-28 and SOIC-28, even the TQFP-44 packages are relatively easy to solder. Max. CPU speed is 50MHz
High Pin Count devices starting with TQFP-48 packages and max. CPU speed of 80-100MHz
High Pin Count devices starting with QFN-64 packages and max. CPU speed 200MHz uses "MIPS 14K" Architecture which on top of faster processing offers additional features such as eight register sets, enhanced ability for signal processing (e.g. by four 64 Bit accumulators and SIMD instructions) enhanced hardware support for Interrupts.


  • support is only available in svn trunk version
  • the complete lineup of existing controllers is supported, testing is done with pic32mx150, pic32mx460 and pic32mx795 chips on a MacOSX-Host


Get latest FPC from svn:

svn co fpc

Get pic32-embedded tools from this page:

you will find precompiled binaries for macosx, linux and windows in the directory 'compiler':

( compilers/pic32-tools-chipKIT-cxx-master-{Platform} )

Important: Make sure that you grab the old version from 20130228, the newer versions create a compiler assertion.

You only need the binaries of pic32-ar(.exe), pic32-as(.exe), pic32-ld(.exe), pic32-strip(.exe), pic32-objdump(.exe) and pic32-objcopy(.exe). Put these utils in a directory included in your path.

To build binutils from sources check out

cd binutils
./configure --target=pic32mx-elf --prefix=/usr/local --program-prefix=pic32- --disable-werror

Build FPC for mipsel-embedded (OABI):

cd fpc
make clean buildbase installbase CROSSINSTALL=1 OS_TARGET=embedded CPU_TARGET=mipsel SUBARCH=pic32mx BINUTILSPREFIX=pic32-

This builds only the compiler and the RTL instead of the whole FPC. Because of the limited capabilities of the embedded systems supposed to be used, building all packages is not useful. However, one must be careful to avoid overwriting an existing arm compiler on the system. If this is the case, INSTALL_PREFIX should be used to install into a different directory and switch between those.

SUBARCH is required and should match your binutils, currently there are two different versions of binutils:
pic32mx: chipkit port with some pic32 specific patches, has the same output arch as xc32, so linking with xc32-libs should be possible
mips32r2: plain vanilla binutils, linking with xc32-libs does not work

The Microchips official version of binutils that is delivered with the xc32 compiler does not work correctly at the moment.

All testing was done with the chipkit version, besides the possibility of linking with xc32 generated code one advantage is that binaries are available for all major platforms.

For Debugging you will also need to build pic32-gdb from sources:

cd gdb
./configure --target=mipsel-elf32 --prefix=/usr/local --program-prefix=pic32- --disable-werror

Compiling a simple example

program hello;
  i : integer;
while true do
  for i := 0 to 40000 do
  for i := 0 to 40000 do

to build the program use the following commands (on Linux & MacOSX)

DEBUG="-gw2 -godwarfsets -godwarfmethodclassprefix"
/usr/local/lib/fpc/2.7.1/ppcrossmipsel -Cp$SUBARCH -Wp$CPU -XP$BINUTILS -MObjFPC -d$CPU -Tembedded -Pmipsel -O2 -Scghi -Ch1024 -Cs1024 $DEBUG -vewnhix -l -FD/usr/local/bin -a hello.pas

Flashing and Debugging

Some history: The pic32 target has been in development for nearly a year now, the main reason for this long development was that there was simply no easy way to reliably flash the chip. But this has changed now, a very simple solution is available from, their Version 9.0 of the J-Link hardware now supports flashing and debugging of all pic32mx chips.

the openocd project also has support for flashing pic32mx chips but I had mixed results with flashing; debugging on the other side works just fine.

So my recommendation here is that you invest €50 and buy a J-Link Edu debug probe. It also works great for ARM based controllers so you only need one tool for debugging both platforms. You must make sure that the hardware revision of the probe is at least V9, older versions do not support pic32mx.

The only thing you need in addition to the probe is an adapter to connect the J-Link to the pic32, a schematic can be found on the segger homepage:

Debugging is now straightforward:

Start the gdb-server:

JLinkGDBServer -device PIC32MX795F512H -if 2-wire-JTAG-PIC32 -speed auto

and connect to it with gdb:

pic32-gdb hello.elf --tui --eval-command="target extended :2331" --eval-command="monitor reset halt" --eval-command="set mem inaccessible-by-default off" --eval-command="load" --eval-command="layout asm" --eval-command="layout regs"  --eval-command="set remotetimeout 3000"

See also