Hi Tom12345,

I faced the exactly same issue with my application. At the end I discovered that the issue is caused by wrong configuration of used serial port in the application. Please note that it is necessary to set property "RtsEnable" before opening the serial port.

Here is the related source of code for correct serial port configuration:

               _serialPort = new SerialPort(portName, 115200, Parity.None, 8, StopBits.One);
                _serialPort.Handshake = Handshake.None;
               _serialPort.RtsEnable = true;   // necessary when using the BlueGiga devkit
               _serialPort.Open();

I hope it will help.

Ivan Dousa

Hi Tom12345,

I faced the exactly same issue with my application. At the end I discovered that the issue is caused by wrong configuration of used serial port in the application. Please note that it is necessary to enable handshake and set property "RtsEnable" before opening the serial port.

Here is the related source of code for correct serial port configuration:

               _serialPort = new SerialPort(portName, 115200, Parity.None, 8, StopBits.One);
               _serialPort.Handshake = Handshake.RequestToSend;
               _serialPort.RtsEnable = true;   // necessary when using the BlueGiga devkit
               _serialPort.Open();

I hope it will help.

Ivan Dousa

Thank you Kevin.

Now it seems it is clear.

Hi Kevin_Fu,

Thank you for your message. 

So if I need to implement the secure boot together with support of OTA update with a signed and encrypted firmware image then I need to build my custom version of Gecko Bootloader ( "Internal Storage Bootloader (single image on 512kB device)" with enabled security features in the Gecko Bootloader configuration) as these features are not available in the present Apploader version. Do I understood it correctly?

Unfortunatelly, in that situation I need to allocate a storage slot for the firmware update image and the size of that storage slot is about the half of the available FLASH memory - about 240 kB for a 512 kB device.  So this configuration does not allow me to  use an application binary image larger then approximately 240 kB (in example 300 kB). Am I right?

If so, then it seems that for EFR32xB22 device there is no replacement for that original "Bluetooth In-place OTA DFU" Gecko Bootloader type" that could be used for some other device types and that enables to perform a secure boot with signed and encrypted firmware image without the necessity to allocate a half of device FLASH as a storage area for a new firmware image.

Or is there still some option how to implement "Bluetooth In-place OTA DFU" for a EFR32xB22 device where these security features (secure boot, signed and encrypted firmware image) are available?

Thank you for reply,

Ivan Dousa

Hi JJ,

Thank you for all details. In my case I need to add to the standard Apploader some additional security features, so I can use the secure boot together with a signed and encrypted firmware update image (similarly I used it for BGM113 device few years ago). For that reason I need to create a modified Apploader version from that template available in Simplicity Studio and I need to configure it correctly, so it is functional. For that reason I am discussing the resulting memmory map as I need to configure the bootloader storage slot size and location.

So please could you double check that I use the correct storage slot configuration?

Thank you and best regards,

Ivan Dousa

Hi J.J,

If I try to create an AppLoader for EFR32BG22C224F512IM40 based on that "Internal Storage Bootloader (single image on 512kB device)" template in Simplicity Stuido then I need to manually reconfigure the information about the used storage slot size and location . The default configuration is the one you can see on picture below:

Considering that I need to alocate 24 kB at the begging of the device FLASH for Bootloader, 56 kB for the AppLoader and additional 8 kB at the end of the device FLASH for NVM then the resulting memmory map could be as follows:

• 0x00000  - 0x05FFF  Bootloader region (24 kB)
• 0x06000  - 0x13FFF AppLoader region (56 kB) 
• 0x14000  - 0x7DFFF Application region (424 kB)
• 0x7E000  - 0x80000 NVM region (8 kB)

If so, then I need to configure in Simpilicity Studio the storage slot start address 0x14000  ( 81920) and storage size 0x69FFF (434175).

Please could you double check the provided memory map above (unfortunatelly it seems it is not available in any of these documents describing Bootloader/Aploader) and confirm that the proposed storage slot configuration is OK?

Thank you for your help.

Best regards,

Ivan Dousa

Hi J.J,

Great. Thank you for the information. I am going to test it and let you know if I face any issue with this configuration  or if I will miss ayny related details or documentation.

Thank you and best regards,

Ivan Dousa

Hi J.J,

Thank you for your reply. If I am not wrong that "Internal Storage Bootloader (single image on 512kB device)" provides me the maximim storage slot of about 240 kB as the available 512 kB device FLASH needs to be shared with the actual running firmware.  For that reason I am not able to updalod over the air a new firmware image with size above that 240 kB. 

So it seems that the original concept of that "Bluetooth In-place OTA DFU bootloder" is no more supported for EFR32BG22C224F512IM40 as the device firmware is not divided to separate Bluetooth stack and application image any more. Am I righ?

I when I tried to create a new gecko "Bluetooth In-place OTA DFU" bootloder for EFR32BG22C224F512IM40 device in Simplicity studio I discovered that not able to select any EFR32xB22 device in the list of available devices for that bootloder type. Does it mean that this boatloader type is not suported got EFR32XG22 device family?

Here is few print-screens from the project creation:

1. Stack selection:

2. Application type selection:

3. Device selection

If so, is there any other similar bootloder type I can use for this device without the necessity to reserve inside the device FLASH memmory a slot with size of about the half of the available FLASH memmory for the firmware image update?

It seems that I will need more than 300 kB for the Bluetooth application itself, soI am not able to create a seperate slot in internal FLASH for the firmware update.

Which version of IAR ide you are using.

have you tried to use the pack manager to update the IAR to support EFR32BG22.