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

[RichardHdrd]

Dear Sigurd,

Compiling ble_app_hids_mouse, I get the following output:

Linking target: _build/nrf52840_xxaa.out
   text       data        bss        dec        hex    filename
  58760        748       5252      64760       fcf8    _build/nrf52840_xxaa.out
Preparing: _build/nrf52840_xxaa.hex
Preparing: _build/nrf52840_xxaa.bin
DONE nrf52840_xxaa

ls -l in the corresponding _build dir:

167483 Mai  4 13:21 nrf52840_xxaa.hex

The only available subpath in the example path is s140, not s112:

...../nRF5_SDK_17.0.2_d674dde/examples/ble_peripheral/ble_app_hids_mouse/pca10056

subdirs are src or s140.

For the green footprint, I added a screenshot, where I chose blinky example, where the green bar is visible (see attachment). If I choose to load example from ble_app_hids_mouse, the green bar never occurrs.

[Sigurd]

It seems like you are using a nRF52811

You should then use the project in pca10056e, i.e. /nRF5_SDK_17.0.2_d674dde/examples/ble_peripheral/ble_app_hids_mouse/pca10056e

See this link: https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.0.2/nrf52811_user_guide.html

[RichardHdrd]

Hello Sigurd,

again thank you for your help. I am using a nRF52840 DK (checked Box&PCB, both state that) together with a EV-BM833A.

The usage of nRF52840 DK was suggested in:

https://static1.squarespace.com/static/561459a2e4b0b39f5cefa12e/t/60218e821ee5037755726ad1/1612811918804/BM833_datasheets.pdf

I read, that the nRF52840 DK is PCA10056 at:

infocenter.nordicsemi.com/index.jsp

As you state, the board is (wrongly?) reported as nRF52811 in screenshot created during usage of the nrfconnect361x8664.AppImage Programmer, I downloaded the AppImage from:

www.nordicsemi.com/.../Download

I am using Ubuntu version x64, Version 20.04.

Any suggestions on proceeding?

Meanwhile I will switch, as suggested by you, to PCA10056e.

Best regards,

Richard

[Sigurd]

RichardHdrd said:

nRF52840 DK is PCA10056

 Correct. But EV-BM833A is using a nRF52811. You should use PCA10056e project for development then.