An Executable Binary File is a file (.tpc type) which contains your project in compiled form, along with any resource files. It is uploaded to the target, where it is actually executed by the TiOS Virtual Machine.

Making a Binary

If this is not the first time you're building this project, the build process will skip any files which were unmodified since the last time the project was built. This optimizes build speed.

To force the build of all files, even those which were not modified since the last time, select Project > Rebuild All.

On build, the Output pane will display any errors. You can double-click on the line describing an error to jump directly to the problematic line in your code.

Uploading a Binary

Before uploading, TIDE checks if the project has been changed since it was last built. If so, it builds the project again and attempts to upload the new build.

Also, the current project hosted on the target will be checked. If it is the same (same project and same build number) as the project you are trying to upload, uploading will not occur. Thus, trying to upload a project twice without making any change in the project will not result in a second upload. Also, before uploading, the firmware version is checked and if it is incompatible with the firmware version specified in the platform file, the upload is aborted with an error message.

Running a Binary

For a debug version (the default version type), uploading the binary does not automatically start its execution on the target. Once uploaded, it just sits there, waiting to be executed.

This action optionally builds and uploads your application, if needed. If a new upload was just performed, it also reboots the target before running it. This ensures that target starts running the newly uploaded program from a 'fresh' state.