Sorry for asking this here but I did it because there is no bootloader forum and I'm working with an MGM210P module I intend to use with ZigBee.
I've been reading UG266, UG103-06, and AN1084 since I need to incorporate the gecko bootloader into my product. I'm confused as to how an "Application Bootloader" is supposed to work.
The UG266 mentions in Section "3.2 Application Bootloader Operation" that the new image (app.gbl) is to be acquired by the application by any means necessary, put into the image storage slot, then rebooting into bootloader mode to let the bootloader take care of the rest.
I went ahead and created an "Internal Storage Bootloader (single image on 1MB device)" since I'm using an MGM210P module, which mentions in its description that it is:
Application Bootloader for all EFR32 and EFM32 devices with 1MB or larger flash, using the internal flash memory to store upgrade images received by the application in an application specific way, such as OTA, USB, Ethernet, etc.
So, according to this description, it is exactly what I need. I created the project and compiled it and it generates an executable BUT, things just got confusing because what am I supposed to do with this executable? If I flash it to the module it is going to override my application, isn't it? Or am I supposed to somehow "merge" my application executable with this bootloader executable and flash the combined executable into the module?
If this is true, how am I supposed to do this merge? And if the merge is done, how am I supposed to use the bootloader from my application?