VS Arduino - Print Page

VS Arduino
Visual Micro >> Project Guidance >> Build/burn AVR bootloader with VS/VM ? https://www.visualmicro.com/forums/YaBB.pl?num=1418320641 Message started by stevech on Dec 11^th, 2014 at 5:57pm

Title: Build/burn AVR bootloader with VS/VM ?
Post by stevech on Dec 11^th, 2014 at 5:57pm

I have a wireless-capable bootloader that I wrote.
Currently, I have to use a Windows command window to run compile via ye ole makefile. Then I go into VS/VM to run the Atmel JTAGICE software to burn the .hex for the bootloader to boards.

Anyone know how to get VS/VM to use the makefile to do the build?

Better yet would be to setup a project in VS/VM that would also compile per project settings so I could eliminate the antique makefile. There are 3 build target chip-types, all AVR.

The makefile method works but it's so 1980's.

TIA
steve

Title: Re: Build/burn AVR bootloader with VS/VM ?
Post by Visual Micro on Dec 12^th, 2014 at 11:47am

Why can't you just use a native atmel studio project? What benefit is VM in this scenario?

Thanks

Title: Re: Build/burn AVR bootloader with VS/VM ?
Post by stevech on Dec 13^th, 2014 at 6:39am

er, I dunno!

I've not tried to do a bootloader compile using AStudio either!
I was thinking of how to get project properties in VS/VM arranged to do a boot compile (origin in flash) and not use a makefile.

One hangup is that apparently, STILL, the mega1284p requires its own core files. I would have thought that by now, #ifdef's in the standard core files would accommodate that years old part, for both bootloader and main.

Title: Re: Build/burn AVR bootloader with VS/VM ?
Post by Visual Micro on Dec 13^th, 2014 at 12:47pm

Maybe I haven't understood correctly.

You can burn any bootloader as long as it is in the correct location

You can use any arduino compatible core as long as it is in the correct location

Visual Micro supports the arduino 3rd party build process + teensy build + some extra stuff on top of that.

It's probably worth investigating how to create your own boards.txt, platform.txt and programmer.txt which are all part of the 3rd party build processes.

Take a look at arduinoide/hardware/arduino/sam/ or arduinoide/hardware/arduino/avr

Thanks