*.s37 (similar to a binary file but contains the target memory location to flash to - an application image or a bootloader image, but not both) *.gbl (Gecko Bootloader file, specialized firmware file for use with the Gecko bootloader) *.bin (binary image file, can be flashed to any address) *.axf (image that can be read on a Microsoft Windows device) The GNU ARM® compiler for a 32-bit device using the Zigbee EmberZNet SDK generates: *.omf (contains additional debug information) For example, the Keil® 8051 compiler for an 8-bit device generates: The binaries generated depend on both the SDK and the target device. Right-click a binary for a context menu from which you can debug, flash, and perform other functions. The binaries are physically located in a directory named for the compiler used to generate them, and are also shown as a 'binaries' group in project explorer. The result of the build is a compiled application known as a firmware image or binary. Be sure that generation and indexing complete before building the application image. Speed varies depending on your system, number of projects, and other factors. Progress is shown in the lower right of the Simplicity IDE perspective. Project files must be generated before you can build the project.įor 32-bit device development using AppBuilder, click Generate in the Simplicity IDE.įiles are automatically generated if the project uses Project Configurator. Projects are built with the toolchain defined when the project was created, and using the active configuration. Simplicity Studio® 5 (SSv5) offers two convenient ways to compile or 'build' projects:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |