RE: application && bootloade IROM setting

Jørgen Holmefjord — Mon, 22 May 2023 15:46:22 GMT

Hi,

[quote user=""]I have implemented OTA upgrades on the ble_app_uart example. But one of the things I wonder about is that doesn't the IROM space of the application setup overlap with the IROM space of the bootloader? Why can the DFU upgrade successfully when there is a conflict?[/quote]

Yes, it seems to overlap in your images. You need to reduce the size of the application to make room for the bootloader when this is used on your chip. The example is by default made to not use a bootloader, so all available flash is assigned to the application. If the application is small enough to not overlap with the bootloader (i.e. there is no code data from the application in the flash are used by bootloader code data), both will likely work as expected when flashed subsequently, but this can change during your development when the application size grows. You should fix this right away to avoid problems in the future.

[quote user=""]Also,compared with S132 softdevice, could you please tell me what functions the S112softdevice lacks?[/quote]

You can read the feature set of each variant in their respective documentation pages: S112 - S132.

Main differences includes (but might not be complete):

S112 is peripheral only, S132 supports peripheral and central roles.
S112 supports up to 4 concurrent connections, S132 supports up to 20 concurrent connections.
S132 supports Data Length Extensions (DLE)
S132 supports Extended advertising

Best regards,
Jørgen

RE: application && bootloade IROM setting

Priyanka — Fri, 19 May 2023 11:41:04 GMT

Hello,
I am sorry, but we are short staffed this week due to Public Holidays in Norway. We will be back on Monday 22nd and hope to be able to answer all incoming requests within a couple of days, depending on the backlog. I am sorry for the inconvenience.

Best regards,
Priyanka