Creating and uploading SDK example ble_app_hids_mouse to BM833A

[RichardHdrd]

Dear community,

I compiled the ble_app_hids_mouse example from SDK 17.0.2. From the datasheet of BM833A, i can read:

Flash/RAM: 192KB/24KB

Compiling the project unmodified, it gives a 211 kB size hex image.

As there is a makefile given, it is possible to change:

OPT = -O3 -g3

to:

OPT = -Os

This now results in a hex-file of size 163kB

Using the Programmer obtained in from nrfconnect361x8664.AppImage via nRF52840-DK I can select the hex-file, but otherwise than other examples, it never shows up with a green footprint.

Is there a known reason, why a 163kB app cannot be uploaded to the BM833A@192kB?

Best regards to everyone,

Richard

[awneil]

RichardHdrd said:

211 kB size hex image

The size of an Intel Hex file is somewhat over twice the size of the actual binary which it represents.

[RichardHdrd]

Dear awneil,

The hex-file is created from gcc in Ubuntu using the gcc-arm-tool-chain. Even if I get the announcement, that there should be no problem creating w/o modification, the Readme.txt of the project states:

Keil license is required in order to build serialization example (code exceeds 32k limit). GCC makefile provided.

Also the original hex-file (being 211kB) does never get a green footprint using nrfconnect361x8664.AppImage Programmer.

Anyway thank you for your given answere.

Best regards,

Richard

[Sigurd]

Hi,

I compiled the ble_app_hids_mouse example

When I compile this example I get,

Linking target: _build/nrf52810_xxaa.out
   text    data     bss     dec     hex filename
  37916     720    2808   41444    a1e4 _build/nrf52810_xxaa.out
Preparing: _build/nrf52810_xxaa.hex
Preparing: _build/nrf52810_xxaa.bin
DONE nrf52810_xxaa

Size is text+data = 38636 bytes

Then you need to flash the SoftDevice as well, for S112, that is 100kB.

RichardHdrd said:

green footprint

 What do you mean by this?

Did you flash the SoftDevice?

You can find SoftDevice S112 in SDK_folder\components\softdevice\s112\hex