Love the product. Efforts much appreciated.
One suggestion I have is support for the Microchip line of products possibly the Chipkit which I believe arleady supports AVRDude and GCC also their Microstick II.

Keep up the good work folsks.
Allan

Thanks

Actually I think the latest beta is quite a few steps closer to being able to achieve version 1 of this functionality.

I think the config you will need will include a core. In which case the system will attempt to include the arduino.h but you can make your own core folder and add an arduino.h that simply includes the header files you need

I'm pushed for time and will write more about the features of the latest beta but there are some documents that tell you what you need to know here. The SITL example is simply an example of a radically different tool chain and does not relate to this post

Custom Build Example (Advanced Users)

Cygwin Install Guide (SITL)


The support for other tool chains and cores will improve again during the next few weeks whe the arduino 1.5 compatible system is released. Older arduino systems will still be fully supported but the 1.5 build process is also very flexible. 

Visual Micro already supports a combination of arduino, teensy and its own build settings. The next release should support all of these + 1.5

I hope this helps, if not please remind me in a few weeks to re-look at this. If you take up the challenge feel free to ask questions along the way

You need 1305.01 or above from our codeplex downloads list to use these settings

Thanks

ps: Some of these features will not be available in the Atmel Studio version of Visual Micro unless the resulting compile has some relationship to Atmel hardware

Any more news anyone on ChipKit / MPIDE support? I really could do with this working and I will certainly buy the full version if this is feature is added. I find the Arduino hasn't enough grunt for my projects and a quick knock up of a 32MX440 board which worked first time is proving to be exactly what I want. Pity the MPIDE is rather rubbish and the JVM keeps crashing when using the Serial Monitor.

Please, please can you get this feature added????

BTW: The app looks awesome, if only it worked with MPIDE

Thanks, Dan

So no news then Tim?? Please can we have an update? I don't mind it being a 'No, we're not going to support chipkit'. Something other than no response at all would be much appreciated, even Andreas the guy designing the Parallella board (massive undertaking) has responded quicker than this, tsk tsk

Hi Tim, 

I didn't mean to offend, so if I did I apologize! It was more of a request for an update regardless of the outcome. Hearing that the support for ChipKit is about 80% done gives me great hope. 

I'll take a look myself and see if there's any way I can get Visual Micro to work with the chipkit build system. If there are any pointers you can give me to start me off, that'd be a great help. Of course anything I find out or if I can get it to work I'll post on here...

Thanks again for your hard work, it is most definitely appreciated

Thanks, Dan

Hi Tim,

That would be great, if I can help out I'd be glad to, but no promises

Thanks again and have an awesome Christmas!

Dan

There is a bit more to it than that because the Chipkit boards.txt format is very different to Arduino. The following is where we are up to in providing a visual micro custom app config for mpide. There is no support for this and to complete the definition you need a lot of knowledge but try it and let us know what builds if anything.

After you set this up visual micro will show a new app in the main list. In addition to Arduino 1.0.x and Arduino 1.5.x you will see Chipkit (MPIDE) which can be configured with a path that points to the location of an mpide.exe.

If you expand this zip into your "documents" folder you should end up with mydocuments\visual micro\micro platforms\mpide.

Visual Micro (MPIDE).zip

Then in "Tools>Options>Visual Micro>Application & Locations>My Visual Micro Configs" enter the Visual Micro folder path that you created. example "c:\users\[name]\documents\visual micro"

For this custom definition to be read by visual micro you need to have the plus pack/debugger activated. If your trial has ended then let me know and I will try to get you another trial key. Please don't buy a license on the basis that mpide will work! If you have already purchased a license for arduino debug then thanks!

If the ide is open during this config then click "tools>visual micro>reload tool chains" then configure your new app path.

Hi Tim,

Thanks for replying so quickly! I gave the above a good try and had to copy the contents of 
c:\arduino\hardware\pic32\compiler\pic32-tools 
to 
c:\arduino\hardware\tools\pic32
as it didn't exist. This is possibly due to the newer version I'm using although it still says May 2011, not so great versioning!!

Anyway after trying to compile it seems as though it's getting hung up on a missing file called syscalls_PIC32.c.o.

The MPIDE output is too long to post, so here is the line which is ok in MPIDE (note the missing : which seems to have been stripped when I copied the text!):

C \Arduino/hardware/pic32/compiler/pic32-tools/bin/pic32-g++  -Os  -Wl,--gc-sections  -mdebugger  -mprocessor=32MX440F256H  -o  C  C \Users\Daniel\AppData\Local\Temp\build3818776942718976953.tmp\TouchTest.cpp.o    C \Users\Daniel\AppData\Local\Temp\build3818776942718976953.tmp\core.a  -LC \Users\Daniel\AppData\Local\Temp\build3818776942718976953.tmp  -lm  -T  C \Arduino\hardware\pic32\cores\pic32/chipKIT-application-32MX440F256.ld  -TC \Arduino\hardware\pic32\cores\pic32/chipKIT-application-COMMON.ld

but fails under VM:
"c:\arduino/hardware/pic32/compiler/pic32-tools/bin/pic32-g++" -Os -Wl,--gc-sections -mdebugger -mprocessor=32MX440F256H "-Tc:\arduino\hardware\pic32\variants\Fubarino_SD/chipKIT-BL-mega.ld" _sd_seeed/TouchTest.map" -o /TouchTest.elf" ed" -lm -lgcc -mthumb -Wl,--cref -Wl,--check-sections -Wl,--gc-sections -Wl,--entry=Reset_Handler -Wl,--unresolved-symbols=report-all -Wl,--warn-common -Wl,--warn-section-align -Wl,--warn-unresolved-symbols -Wl,--start-group /syscalls_PIC32.c.o" \TouchTest.cpp.o" "c:\arduino\hardware\pic32\variants\Fubarino_SD/{build.variant_system_lib}" /core.a" -Wl,--end-group

Visual studio reports this:
pic32-g++* : : syscalls_PIC32.c.o: No such file or directory
pic32-g++* : : c:\arduino\hardware\pic32\variants\Fubarino_SD\{build.variant_system_lib}: No such file or directory
Error creating .elf

I still don't think it's that far off, especially seen as I get the error with or without the external touchscreen library. I tried both to be sure this wasn't an issue either by commenting out the library include and all references to it. This left 4 basic pin defines and a serial.begin(9600). Maybe it's something that's expected to be in the variants folder or maybe the syscalls file is generated internally, I just don't know.

I can zip everything up and either email it or send you a dropbox link, or I can test anything else you need?!

I'll probably do a little dance and power punch the air when I see it all working, I have faith in it working at some point and sorry about the formatting above

Have a cracking Christmas Tim!!

Hi, I downloaded the latest version as shown in the sticky on the chipkit forum, I've copied the link here so you can grab the exact version I was using: https://github.com/downloads/chipKIT32/chipKIT32-MAX/mpide-0023-windows-20120903...

I also tried reverting to the previous version which then wouldn't run, all I got was the loading splash screen which then disappeared a few moments later with no exception messages, nothing. After copying back the newer release everything that worked before suddenly worked again and mpide loaded correctly. I then closed that and tried the previous tests in visual studio which gave the same results. I just though I'd let you know that it seems there's no way to revert the mpide version without possibly hacking the registry which is always a bad thing!

Have fun, Dan

Update (2)

I installed the mpide from here. It looks like a July 2013 build, I think your build is Sept 2012 but sounds like they both work the same because we get the same compiler results.