Skip to main content
Topic: Bus Pirate v4.0 FreePCB build. (or how MPLABX fails) (Read 2042 times) previous topic - next topic

Bus Pirate v4.0 FreePCB build. (or how MPLABX fails)

Well, my BusPirate v3 from sparkfun finally died (and the connector was backwards anyway).  By died I mean that the clock line fails self test and never switches high.

Whatever happened, I took this as a sign that I should build up the BPv4 board that I got from a twitter drawing a few months back.

So I ordered the extra parts I needed from Mouser, combined it with the eBay reels that I already had, and built up the board.


I used the cheap Abracon crystal that has a 4-land package.  It just barely fits the "Seeed SMD crystal" footprint.  (see the linked image).

Overall, I'd have to give major kudos to whoever did the layout (Ian?) for great spacing and large pads that make hand soldering a breeze.

I then tried to get code loaded on.  I'm running a pure linux box, and have MPLABX v1.00a installed.  I grabbed the SVN, opened up the Bus Pirate bootloader for BPv4, changed the project to use my PicKit3, fixed the error of trying to include <p24fxxxx.h> instead of <p24Fxxxx.h> (silly case insensitive windows guys).  But then I get

Code: [Select]
 /opt/microchip/mplabc30/v3.30c/bin/bin/pic30-elf-bin2hex: dist/default/production/firmware-v1.production.elf is not a valid object file.
make[2]: *** [dist/default/production/firmware-v1.production.hex] Error 255

After searching around, it seems that this is a known problem with no real workaround.

So, my question for all of you: is there any way for me to get a bootloader on here without having to find a Windows box with MPLAB v8?

Re: Bus Pirate v4.0 FreePCB build. (or how MPLABX fails)

Reply #2
Did you try creating a new project using MPLABX's "Create from existing MPLAB 8" thingee? I at least got the firmware to build.
I am running 64 bit windows7 though but it should still work.

Re: Bus Pirate v4.0 FreePCB build. (or how MPLABX fails)

Reply #3
I just used MPLABX to flash the pre-built packages.  Apparently there's still something in the linker script that chokes on the libraries on the svn right now.