Tim@Visual Micro wrote on Sep 14
th, 2014 at 11:16pm:
Hi both,
There is an
Sp2 version of the current release with a fix for this issue. It wasn't how things were meant to be so I hope you find this release works properly.
Awesome, thanks. I'll try it out soon.
Quote:1)
If you can please switch on "Tools>Visual Micro>Upload using programmer" and select the "tools>Visual Micro>Programmers>Atmel Studio - ATMEL ICE (ISP)". When you click the green or blue tool bar arrows does the upload happen correctly via your ICE?
I have the
SAM-ICE, not the
ATMEL ICE, so it only has the 20 pin connector which I have made a custom cable to the 10 pin on the
Tilda board.
The board doesn't programme via this device (it doesn't come up as an option to do so in atmelstudio/visualmicro), it does typically programme successfully via the virtual COM port (I haven't tested with the service pack, but it was where I had to remove the "arduino:" before it would flash).
Quote:This can be avoided by creating an empty sam project (in a folder with the same name) and then manually adding a .ino text file (with the same name). Visual Micro will then start working with the project that you have created.
The reason for this, with sam boards, is that I haven't figured out the best way to switch the project type when selecting different boards such as Avr/Sam

In Visual Studio we only need one project type but then we don't get non-arduino programmers (atmel).
Ah, I see that workaround, but that's a bit awkward I guess. That's why I suggested trusting the path in the hardware folder for the definition of the board you're flashing, enumerating that as to which folder it's in (sam or avr) looks to be a reliable enough way until the folder tree is changed for whatever reason in the future.
Else I guess we're relying on hoping a suggestion being made to arduino to define it in the boards.txt?