Hello Stefan, It is entirely possible to create a single debuggable project that incorporates both the bootloader and application code so that the MSP430 executes the application upon startup instead of waiting to receive a new image from the SPI/BLE interface. However it should be understood that this can only be accomplished during the initial programming of the device using a JTAG interface or native BSL . The purpose of MSPBoot is to create a small, flexible main memory bootloader that a user can customize for their own purposes and demonstrate the relationship between bootloader and application code. Whenever field updates are required the user will need to interface with the bootloader to update the app through a custom firmware image, therefore the bootloader itself cannot be updated at this time. External shared variables should be kept in place or else any updates to the application will not be able to communicate through the shared channels incorporated into the MSPBoot firmware. Regards, Ryan
↧