I'm using `_Static_assert` for compile-time validation.  When I build the project it builds with zero errors and zero warnings.  However, the syntax parser in the editor flags my `_Static_assert` as having a syntax error.  I already have the language mapping for C source files set to GNU C, as detailed in this post.  How can I clear the syntax error warning?

#define I2C_IEN_SUPPORTED() (                                              \
     /* I2C_IEN_START   | */ /* START condition Interrupt Flag          */ \
     /* I2C_IEN_RSTART  | */ /* Repeated START condition Interrupt Flag */ \
     /* I2C_IEN_ADDR    | */ /* Address Interrupt Flag                  */ \
     /* I2C_IEN_TXC     | */ /* Transfer Completed Interrupt Flag       */ \
     /* I2C_IEN_TXBL    | */ /* Transmit Buffer Level Interrupt Flag    */ \
        I2C_IEN_RXDATAV |    /* Receive Data Valid Interrupt Flag       */ \
     /* I2C_IEN_ACK     | */ /* Acknowledge Received Interrupt Flag     */ \
        I2C_IEN_NACK    |    /* Not Acknowledge Received Interrupt Flag */ \
     /* I2C_IEN_MSTOP   | */ /* Master STOP Condition Interrupt Flag    */ \
        I2C_IEN_ARBLOST |    /* Arbitration Lost Interrupt Flag         */ \
        I2C_IEN_BUSERR  |    /* Bus Error Interrupt Flag                */ \
        I2C_IEN_BUSHOLD |    /* Bus Held Interrupt Flag                 */ \
     /* I2C_IEN_TXOF    | */ /* Transmit Buffer Overflow Interrupt Flag */ \
     /* I2C_IEN_RXUF    | */ /* Receive Buffer Underflow Interrupt Flag */ \
     /* I2C_IEN_BITO    | */ /* Bus Idle Timeout Interrupt Flag         */ \
     /* I2C_IEN_CLTO    | */ /* Clock Low Timeout Interrupt Flag        */ \
        I2C_IEN_SSTOP   |    /* Slave STOP condition Interrupt Flag     */ \
     /* I2C_IEN_RXFULL  | */ /* Receive Buffer Full Interrupt Flag      */ \
        I2C_IEN_CLERR   |    /* Clock Low Error Interrupt Flag          */ \
        I2C_IEN_SCLERR  |    /* SCL Error Interrupt Flag                */ \
        I2C_IEN_SDAERR       /* SDA Error Interrupt Flag                */ \
        )

#define I2C_IF_SUPPORTED() (                                               \
     /* I2C_IF_START    | */ /* START condition Interrupt Flag          */ \
     /* I2C_IF_RSTART   | */ /* Repeated START condition Interrupt Flag */ \
     /* I2C_IF_ADDR     | */ /* Address Interrupt Flag                  */ \
     /* I2C_IF_TXC      | */ /* Transfer Completed Interrupt Flag       */ \
     /* I2C_IF_TXBL     | */ /* Transmit Buffer Level Interrupt Flag    */ \
        I2C_IF_RXDATAV  |    /* Receive Data Valid Interrupt Flag       */ \
     /* I2C_IF_ACK      | */ /* Acknowledge Received Interrupt Flag     */ \
        I2C_IF_NACK     |    /* Not Acknowledge Received Interrupt Flag */ \
     /* I2C_IF_MSTOP    | */ /* Master STOP Condition Interrupt Flag    */ \
        I2C_IF_ARBLOST  |    /* Arbitration Lost Interrupt Flag         */ \
        I2C_IF_BUSERR   |    /* Bus Error Interrupt Flag                */ \
        I2C_IF_BUSHOLD  |    /* Bus Held Interrupt Flag                 */ \
     /* I2C_IF_TXOF     | */ /* Transmit Buffer Overflow Interrupt Flag */ \
     /* I2C_IF_RXUF     | */ /* Receive Buffer Underflow Interrupt Flag */ \
     /* I2C_IF_BITO     | */ /* Bus Idle Timeout Interrupt Flag         */ \
     /* I2C_IF_CLTO     | */ /* Clock Low Timeout Interrupt Flag        */ \
        I2C_IF_SSTOP    |    /* Slave STOP condition Interrupt Flag     */ \
     /* I2C_IF_RXFULL   | */ /* Receive Buffer Full Interrupt Flag      */ \
        I2C_IF_CLERR    |    /* Clock Low Error Interrupt Flag          */ \
        I2C_IF_SCLERR   |    /* SCL Error Interrupt Flag                */ \
        I2C_IF_SDAERR        /* SDA Error Interrupt Flag                */ \
        )

_Static_assert((I2C_IEN_SUPPORTED() == I2C_IF_SUPPORTED()), "I2C flags I2C_IEN_SUPPORTED and I2C_IF_SUPPORTED do not match.");

 

Where can I find documentation of how to interface/use the example UART bootloader with the ERF32MG22?  I have the Wireless Gecko dev kit and the bootloader-uart-bgapi example loaded.  Where is the protocol used by the UART bootloader defined or--better yet--documented or--better yet--implemented as an example PC application?

The closest that I have been able to find is this knowledge base article for the BLE drop-in modules.  Is the protocol it outlines applicable to the bootloader-uart-bgapi example for ERF32MG22?  Presumably not, so where is the protocol documented?

@jpitt To get Simplicity Studio to appear in the Programming group on my system (Ubuntu 20.04) I had to set the Categories entry in studio.desktop to `Categories=GTK;Development;`.  I noticed that Meld used this (working) assignment by default when I installed it.

@tenager Thanks for the response.  Specifically, I am attempting to use the example projects Bluetooth - SoC Thermometer and SPI Flash Storage Bootloader (single image).  

1. First, I build and load the bootloader example without any changes. 
2. Then I build the build the thermometer application example.  I have tried it without changes, as well as setting the FLASH ORIGIN in the linker (ld) file to 0x6000.
3. After building the application, I use Simplicity Commander to convert the s37 output file to gbl and save the gbl file to my Android mobile device.
4. Launch the EFR Connect browser on my Android mobile device and connect to the OTA Bluetooth device.
5. Expand the three-dot More menu and select OTA DFU.
6. It defaults to PARTIAL OTA, and I select the gbl file that was earlier saved to my Android mobile device.
7. Tap the OTA button leaving all other options in their default state.
8. In some cases, I get the 0x83 (GATT_DB_FULL) error, mentioned in my original post, or 0x87 (GATT ILLEGAL PARAMETER).  New application image is rejected because it would overlap with the AppLoader.

@jpitt Which version/update of SS5 is supposed to support Eclipse Marketplace?  I'm running v5.1.1, and I don't see the Eclipse Marketplace.

I am having the same problem updating firmware for my Gecko EFR32xG22 mainboard with Simplicity Studio 5 running on Ubuntu 20.04 (x64).  I've tried the different methods described in this thread, but I still get the "Timed out waiting for kit to reset" error message.  My log file is attached.