You should find a new menu item in the next release called "vMicro>Compiler>Always Export Binary". Check the menu and the file is copied into the project folder after each build.

Download link in the next release post

fyi: The build output is also available under the folder specified in project property pages > Final build output folder". Normally that is solutionLocation/Release or solutionLocation/Debug. In the case of the pi it appears the .hex is renamed to "project.variant.bin" and copied to the project folder. This info enables an older build to be uploaded if required.

Sorry I wasn't clear. The update is already available with the link I provided.

Oh I see. Yes I can add a board.txt property to enable you to set the path

The binary file name is specified in the platform.txt of whatever board you are using. So .hex is what 

If you switch on vmicro>compiler>verbose and then build you should see the export command in the output

For the Pi that I have installed it produced a .bin which is actually the .hex from the build folder.

# Export Binary: tch1.ino.hex to file:///C:\Users\tl\Documents\Arduino\TestSketch1\TestSketch1.ino.bplus.bin

1)
What do you see

2)
How does the arduino ide handle this?

Thanks for the info.

Normally for IP devices we use the facility first introduced for the Arduino Yun which uses SSH to upload. However it's not very nice

1)
Because you have a mapped drive it makes life easy. We can have a new property in the project to allow the path to be set that the export will use. It seems that might then be better to have the export happen when upload is clicked or when use manually clicks export because the copy might be slow?

2)
Alternatively we could create the export in the output folder such as Project\Debug. Actually the output folder can already be configured by you in the Visual Studio Project Property Pages. It's a standard visual studio project property called Final Output Folder. This solution would place all .o, .hex, .elf etc in the specified final output folder which might or might not be what is required. If this is a good solution it would negate the need for 1)

3)
I have a Pi Zero and am trying to make a simple setup guide for users. The toolchain and Arduino build is no problem. Loading Jessie onto the SD is no problem but how do I configure the IP address in the simplest possible way?

Thanks

Great thanks.

For 2), although it won't have the project.devicetype.bin right now but you can put a file in the folder and try it. If it works I can change the export to be in that folder instead of the project folder or both.

To find 2) right click the project in solution explore and choose "Properties"

RIGHT CLICK PROJECT NAME > PROPERTIES

No, that suggests permissions issue. Try running VS as administrator to prove this out.

It fails silently if it can't copy the files because most arduino users don't understand or need this process.

The .hex is the .bin. The .bin is the .hex renamed by the export. We just need to know the copy works then I can make the export put the bin in the output folder instead of the project folder. It currently exports to the project folder because that is what arduino does.

Okay great thanks. Does the copy work now in admin mode? The .hex will be there won't have device variant name in the name.

ok will have a go next day or so

It's best to do that from the Rpi desktop. You can do the LAN and WAN by using the GUI on the desktop. Pretty much the same as you would set a fixed ip for windows.

SO you only have to connect the screen once when you set up the Pi. After that you can configure it to not use the desktop. You run a command on a terminal "sudo rasp-config" and set all the hardware and software stuff. You can select there if you want to boot to CLI or desktop.

I use a program called Angry IP Scanner to find the Rpi IP and the use MobaXterm to log onto the Pi.


If you want to go by the command line then:

Edit the file /etc/dhcpcd.conf as follows:

    Type sudo nano /etc/dhcpcd.conf at the command prompt.

    Scroll to the bottom of the script, and add the following lines:

    interface eth0

    static ip_address=192.168.0.2/24
    static routers=192.168.0.1
    static domain_name_servers=192.168.0.1

    interface wlan0

    static ip_address=192.168.0.2/24
    static routers=192.168.0.1
    static domain_name_servers=192.168.0.1

    Save the file with ctrl + o and then exit nano with ctrl + x.

Your Raspberry Pi will now boot up with the IP address 192.168.0.2 every time;
we didn't use 192.168.0.1 as this is reserved for the router.
You can of course use any address you like, but in the configuration above the range must be between
192.168.0.2 and 192.168.0.255. 

The zero does not have an Ethernet or wireless function so I use a USB to Ethernet adapter to connect with it.