> -----Original Message----- > From: [email protected] [mailto:openocd- > [email protected]] On Behalf Of Øyvind Harboe > Sent: maandag 1 maart 2010 10:18 > To: Xiaofan Chen > Cc: [email protected] > Subject: Re: [Openocd-development] [PATCH] Add support for > Buspirateinterface > > > But the official PIC32 GCC compiler comes with proprietory > > C libraries from Microchip (together with MIPS). > > I tried to build some test code and immediately ran into this, > which quelled my enthusiasm for doing any further OpenOCD > work.
There is a simple workaround to get a proper free toolchain with a very small C library: Just download the MIPS GCC compiler from www.codesourcery.com and get the mini C library from MSPGCC (http://mspgcc.sourceforge.net/). The MSP library can be compiled for ARM by removing the MSP430 specific asm files. I'm sure it can also be compiled for MIPS without much problems. The only thing missing is a stub to keep interrupt vectors and some startup code. > > Personally I think Microchip is wrong to choose the MIPS core. > > It was cheaper they thought & faster? > > They may be regretting this decision already and the > marketing department may be tearing their hairs out trying to a) > fix the problem b) present a happy face outwards c) trying > to figure out how to spin stuff now so they don't look like complete ... > when they finally do come to their sense and license ARM. :-) MIPS ain't that bad. The main problem with MIPS is the 'one delay' slot when programming in assembler. This is going to turn down a lot of people that are used to program PIC8 processors in assembly and want to move on to a 32 bit platform. Furthermore I have a feeling MIPS is not further developed like the ARM Cortex series (low power M0, microcontroller M3 and high end A8/A9). And there is the PIC32 packaging problem. NXP is going to launch their Cortex M0/M3 devices in 32 pin QFN packages real soon. ARM power in a PIC footprint :-) I wonder how Microchip is going to keep up with that except for lowering their prices. Nico Coesel _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
