If I run Particle: Cloud Compile it will return a bin file. I can then use Particle: Cloud Flash to flash the bin file. Am I correct in thinking that the bin file can only be used to flash through the cloud? The bin file cannot be used to local flash?
Particle: Compile application (local) - When this is run I see that a target folder is created which contains the compiled? files of the application and also creates a cpp file based off of the ino file. I’m guessing that the cpp file is created because the ino file isn’t actually used by the controller, the cpp file is instead? When a local flash is done, it is actually using the files in the target folder?
When it comes to local compile and flash options there is application, application & DeviceOS, and application for debug, question is when to use which? I would assume that application for debug would be if one were using a ST-Link or such for debugging whereby the code is compiled in a certain way to allow to allow interaction with the ST-Link. I’m assuming if I compile/flash application it’s doing just that, takes my application, compiles it, flashes to the controller, whatever version of the DeviceOS that is already on the controller isn’t affected? And then compile/flash application & DeviceOS will compile my application and DeviceOS version as called out in the particle.firmwareVersion setting and flash both to the controller?
To compile a project with the cloud takes less time than compiling it locally. When I compiled an empty project in the cloud it took 15 seconds, when I compiled the same project locally it took 50 seconds, does that sound right?