How to build sample project for nrf desktop kit (nrf528)

[koichi@tp]

I am trying to evaluate 2.4Ghz wireless and Bluetooth using the nrf Desktop kit.

I saw that the sample project for the nRF52810 Desktop Mouse can be imported making the following selections.

---------------------------------------------------

---------------------------------------------------

However, for projects imported this way,
CMakefile.txt and main.c do not exist,
build is not possible.

When I build, I get the following error code.
--------------------------------------------------

ERROR: c:/xxxxx/nrf52810dmouse_nrf52810 doesn't contain a CMakeLists.txt
FATAL ERROR: refusing to proceed without --force due to above error
--------------------------------------------------

I am new to using Nordic products.
I would appreciate it if you could tell me how I can achieve my goal.

[Sigurd Hellesvik]

Hi,

Have you seen our getting started tutorial at https://academy.nordicsemi.com/? Try that and see if you are able to make this work after that?

However, for projects imported this way,
CMakefile.txt and main.c do not exist,
build is not possible.

Can you send me a screenshot of the contents of the folder so I can see what exists and what does not?

Regards,
Sigurd Hellesvik

[koichi@tp]

Thank you for your reply.

I checked Lesson 1 of the nRF Connect SDK Fundamentals course on Devzon and
Part 1 to Part 3 of nRF Connect for VS Code tutorials on Youtube.

In Devzone, it is stated that building an app when Workspace is selected is not covered in this course,
I was wondering where I can find the reference.

The folder structure when a workspace is selected is as follows.

Only when the app type is set to Workspace,
I thought I could get the sample code for nrf52810dmouse,
but when I created, built, and flashed the app with the following settings,
I was able to confirm that it works as a BLE mouse.
(However, I am concerned about some warnings during the build.)

The warning will appear as follows

=================
warning: Experimental symbol BT_LL_SW_SPLIT is enabled.

CMake Warning at C:/ncs/v2.4.0/zephyr/CMakeLists.txt:838 (message):
No SOURCES given to Zephyr library: lib__libc__common

Excluding target from build.

CMake Warning at C:/ncs/v2.4.0/zephyr/CMakeLists.txt:1864 (message):
__ASSERT() statements are globally ENABLED

=================

If the build option is enabled,
The following overflow occurs.

=================

c:/ncs/toolchains/31f4403e35/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: zephyr\zephyr_pre0.elf section `rodata' will not fit in region `FLASH'
c:/ncs/toolchains/31f4403e35/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: region `FLASH' overflowed by 5460 bytes
collect2.exe: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\31f4403e35\opt\bin\cmake.EXE' --build 'c:\ncs\projects\nrf_desktop\build'

=================

[Sigurd Hellesvik]

koichi@tp said:

CMake Warning at C:/ncs/v2.4.0/zephyr/CMakeLists.txt:838 (message):
No SOURCES given to Zephyr library: lib__libc__common

Excluding target from build.

 Peripheral LBS example: Policy CMP0010 is not set and No SOURCES given to Zephyr library: lib__libc__common 

koichi@tp said:

If the build option is enabled,
The following overflow occurs.

Which build option?

[koichi@tp]

Sorry for the late reply.

With the workaround you gave me,
I was able to clear the warning (lib__libc__common).
thank you.

Which build option?

I have the debug option enabled as shown in the image below.

[ovrebekk]

Hi 

Sigurd is currently on vacation, and I will help out in the mean time. 

If the flash overflows you are essentially running out of code space, which is not unexpected if you are running a multiprotocol example on the nRF52810. 

What is the flash usage when you have debug options disabled? 
I am guessing you are pretty close to the limit to make everything fit, and enabling the debug options is enough to hit the flash size limitation. 

You can analyze ROM and RAM usage in more detail by clicking the Memory report action in the nRF Connect VSCode interface. Then you will see a detailed breakdown of what the ROM/RAM is used for. 

Best regards
Torbjørn

[koichi@tp]

Thank you for your response.

When I disable the debug option,
I get the following output after build.

=====

Memory region Used Size Region Size %age Used
FLASH: 175796 B 192 KB 89.41%
RAM: 24076 B 24 KB 97.97%
IDT_LIST: 0 GB 2 KB 0.00%

=====

I don't know the basic operation which files to include in the build target, etc.
I will examine them and try to adjust the unnecessary parts.

[ovrebekk]

Hi 

Did you manage to compile the memory report? 

Then you should get a view similar to this, where you can really dig into the details of which modules and libraries are occupying the most in terms of ROM and RAM:

Best regards
Torbjørn