Created Sun, 12 Aug 2012 06:14:52 +0000 by ricklon
Sun, 12 Aug 2012 06:14:52 +0000
Release Candidate 4 is here.
Updated compiler from 20120720. Updated PDE.jar build code. win-debug, and linux-debug targets added to build.xml
Other than that only minor changes.
If this one is good then we are going to release it officially. This will be the fully open source newlib based compiler.
Linux32 (Fixed Link to Linux Build) https://github.com/downloads/chipKIT32/chipKIT-builds/mpide-0023-linux32-20120811-test.tgz
Tue, 14 Aug 2012 05:01:14 +0000
Uh is is just me or is the link for the linux download a windows image?
Wed, 15 Aug 2012 03:58:43 +0000
You are correct. I just opened my Linux window and the file was sitting there ready to be uploaded. I was kinda tired. Oops.
Anyway, I just fixed the url. Should be good now.
Sun, 19 Aug 2012 05:03:14 +0000
I'm prepping RC4 to become the official release.
In the meantime builds will continue to be generated that include the latest changes and updates. These build will contain a build number, the current build is 0x01000303
Thu, 23 Aug 2012 01:00:53 +0000
I'm trying to compile RepRap 'Marlin' firmware. Github link - https://github.com/jcrocholl/Marlin/commits/Marlin_v1/
MPIDE errors that it does not recognize sub-directory paths within the avr tree for recipe/program #include(s). Specifically util/<filename>. The compile does not progress but, is likely not to find other sub-directories.
Could you correct this within MPIDE so that I may try Arduino Compatibility with a RepRap 3D printer?
The need is soon - I am building a 3D printer based on the chipKIT Max32 for show at Maker Faire Pittsburgh, September 22nd. I am building up the electronics - now. We need to have a fully printing machine and need the time to work out the hardware bugs. Please? Regards, Brian.
Thu, 23 Aug 2012 17:15:09 +0000
I had a quick look, the marlin firmware includes a whole bunch of avr specific headers that you will need to convert (or ignore)
#include <avr/pgmspace.h> #include <avr/eeprom.h> #include <avr/wdt.h> #include <avr/interrupt.h>
the SD stuff has defs for avr boards so you need to change that. sd2pinmap.h, some of the other SD files have atmega spi pin specific stuff.
Your going to have to get your hands dirty, its not just a recompile with mpide.
Thu, 23 Aug 2012 17:47:57 +0000
Thank you for the helpful and quick reply. I was under the thought that if MicroChip is marketing chipKIT as compatible with Arduino (AVR) then their version of the IDE (MPIDE) would have pin conversions and the avr pathways correct within the IDE. They do include all the libraries within the distribution. The paths programmed to recognize the locations from a program call. Yes? No?
The chipKIT runs the AVR examples with no issues.....
I'm just tired of bleeding edge touted as easy to implement and compatible with items. Then having to working out all the compile and coding inconsistencies to make the product work. I can just plug and compile my Arduino and keep on keeping on...
I shouldn't have to fix and build the tool chain to program my HW. Unless I am creating the new use. I was told - Compatible. Oh, Hum.... :(
Thu, 23 Aug 2012 19:53:36 +0000
compatible on the api high level is one thing, but compatible on the low level? Embedded stuff is inherently banging on the hardware, an avr is not a pic32, expecting all avr code to compile is a bad assumption.
do you blame microchip/digilent because Marlin is doing some low level AVR things and directly defining atmel avr pin numbers to specific things and wonder why the pic32 compiler cant compile some avr stuff?
do you understand that arduino boards are 5v and chipkit boards are 3.3v and not all pins are 5v tolerant? I assume (but am probably wrong) your using some kind of ramps1.4 shield? if the ramps board expects 5v on some pins it might not see 3.3v?
Thu, 23 Aug 2012 21:26:03 +0000
Gotcha - YEP - RAMPS. Board power not so vital - I've the peripherals powered. But, as you note that programming is important at the hardware level. Thanks for the discussion. I was afraid of that. Looks like I'll build the machine first. Get it to working then play with porting software to a different controller. maybe....
Thu, 06 Sep 2012 22:18:06 +0000
Just downloaded the above MPIDE 0023 Linux32 201 208 11 test.
When I try to compile the Blinbk example I get errors, see below
In file included from /home/kim/MP_IDE_023/mpide-0023-linux32-20111221/hardware/pic32/cores/pic32/WProgram.h:16:0, from Blink.cpp:8: /home/kim/MP_IDE_023/mpide-0023-linux32-20111221/hardware/pic32/cores/pic32/WCharacter.h: In function 'boolean isblank(int)': /home/kim/MP_IDE_023/mpide-0023-linux32-20111221/hardware/pic32/cores/pic32/WCharacter.h:45:29: error: new declaration 'boolean isblank(int)' /home/kim/Desktop/mpide-0023-linux32-20120811-test/hardware/pic32/compiler/pic32-tools/bin/../lib/gcc/pic32mx/4.5.1/../../../../pic32mx/include/ctype.h:24:5: error: ambiguates old declaration 'int isblank(int)'
Thu, 11 Oct 2012 13:15:09 +0000
Edit: I can see there is a newer thread about version releases so ignore this message. Question removed
Wed, 27 Nov 2013 22:20:49 +0000
any update to get Marlin to run on Chipkit?
Wed, 27 Nov 2013 23:13:49 +0000
What's Marlin? (sorry, I'm late to this thread)
Sun, 16 Feb 2014 03:32:11 +0000
If your following this thread and trying to get a RepRap to work with a chipKIT board you might take a look at demitasse:
It doesn't compile in the latest release but I did get it to compile under MPIDE version 20120903.
Sun, 16 Feb 2014 03:46:57 +0000
I was under the thought that if MicroChip is marketing chipKIT as compatible with Arduino (AVR) then their version of the IDE (MPIDE) would have pin conversions and the avr pathways correct within the IDE. ... I shouldn't have to fix and build the tool chain to program my HW. Unless I am creating the new use. I was told - Compatible. Oh, Hum.... :(
Try to run this code on an Arduino Due. I think you will probably find that that an Arduino Due is not compatible with an Arduino (AVR).
I agree that the compatibility claim was a marketing mistake, especially the early claims of 100% compatibility. It could have been handled better.
Its probably also a good idea to point out that MPIDE is not a Microchip product, but a community project that is developed and maintained by many individuals. Microchip and people that work there have been a great support in this effort.