Multi-NUS on the nRF21540-DK

RE: Multi-NUS on the nRF21540-DK

user6207 — Tue, 14 Jun 2022 05:05:50 GMT

Please attach your project and I will try to fix the errors and make it compile.

RE: Multi-NUS on the nRF21540-DK

user68828 — Mon, 13 Jun 2022 21:42:35 GMT

The Kconfig file shows exactly the items you described. I remain skeptical that the application code need not change when adding features like the PA and the LNA, but I'll run with it until I can prove otherwise. What I need right now is a way to make it compile. The error messages do not lead me to any corrections I need to make. Help?!?

RE: Multi-NUS on the nRF21540-DK

user68828 — Mon, 13 Jun 2022 20:52:54 GMT

RE: Multi-NUS on the nRF21540-DK

user6207 — Mon, 13 Jun 2022 07:04:20 GMT

In the config file ncs\v1.9.1\nrf\subsys\mpsl\fem\Kconfig

config MPSL_FEM_NRF21540_TX_GAIN_DB_POUTA
	int "TX gain value (POUTA)"
	default 20
	help
	  The default value of 20 dB is based on nRF21540 Product Specification (v1.0) and it
	  corresponds to the configuration in which the pin MODE=0 and register POUTA_SEL=0.

	  Alternatively, if register POUTA_SEL=1, FEM will use TX gain value defined by the UICR.
	  In that case user must set value of this Kconfig option to match UICR content.

config MPSL_FEM_NRF21540_TX_GAIN_DB_POUTB
	int "TX gain value (POUTB)"
	default 10
	help
	  The default value of 10 dB is based on nRF21540 Product Specification (v1.0) and it
	  corresponds to the configuration in which the pin MODE=1 and register POUTB_SEL=0.

	  Alternatively, if register POUTB_SEL=1, FEM will use TX gain value defined by the UICR.
	  In that case user must set value of this Kconfig option to match UICR content.

I can understand that this configurations settings can be a bit confusing and if it feels better, there is a strong consideration of making these options easier in the coming releases.

As per your question, the FEM TX gain should match either POUTA or POUTB TX_GAIN and i am guessing you are trying the TX gain in your case which is not 20 or 10 (default values of POUTA_TX_GAIN and POUTB_TX_GAIN)

RE: Multi-NUS on the nRF21540-DK

user68828 — Wed, 08 Jun 2022 12:08:58 GMT

The word "should" is a wonderful modifier. The tools "should" do a lot of things.

By non-intuitively deleting the build configuration, and then non-intuitively selecting non-Nordic boards, notwithstanding the "Nordic" printed all over the 21540 DK, I was able to select the "nRF21540 DK NRF52840" configuration. Then doing "Build Configuration", I get a very long string of build script, ending with this:

In file included from D:\Nordic\v1.9.1\zephyr\include\toolchain.h:50,
                 from D:\Nordic\v1.9.1\zephyr\include\sys\printk.h:11,
                 from D:\Nordic\v1.9.1\zephyr\include\sys\__assert.h:11,
                 from D:\Nordic\v1.9.1\zephyr\include\drivers\gpio.h:18,
                 from D:\Nordic\v1.9.1\nrf\subsys\mpsl\fem\mpsl_fem.c:8:
D:/Nordic/v1.9.1/nrf/subsys/mpsl/fem/mpsl_fem.c: In function 'fem_nrf21540_gpio_configure':
D:\Nordic\v1.9.1\zephyr\include\toolchain\gcc.h:61:36: error: static assertion failed: ""
   61 | #define BUILD_ASSERT(EXPR, MSG...) _Static_assert(EXPR, "" MSG)
      |                                    ^~~~~~~~~~~~~~
D:\Nordic\v1.9.1\nrf\subsys\mpsl\fem\mpsl_fem.c:280:2: note: in expansion of macro 'BUILD_ASSERT'
280 | BUILD_ASSERT(
      | ^~~~~~~~~~~~
[194/236] Building C object zephyr/kernel/CMakeFiles/kernel.dir/errno.c.obj
[195/236] Linking C static library modules\nrf\subsys\mpsl\init\lib..__nrf__subsys__mpsl__init.a
[196/236] Building C object zephyr/kernel/CMakeFiles/kernel.dir/init.c.obj
[197/236] Building C object modules/nrf/subsys/bluetooth/controller/CMakeFiles/..__nrf__subsys__bluetooth__controller.dir/hci_driver.c.obj
[198/236] Building C object zephyr/kernel/CMakeFiles/kernel.dir/fatal.c.obj
[199/236] Building C object zephyr/kernel/CMakeFiles/kernel.dir/kheap.c.obj
[200/236] Building C object zephyr/kernel/CMakeFiles/kernel.dir/mem_slab.c.obj
[201/236] Building C object modules/nrf/drivers/mpsl/flash_sync/CMakeFiles/..__nrf__drivers__mpsl__flash_sync.dir/flash_sync_mpsl.c.obj
[202/236] Building C object zephyr/subsys/bluetooth/host/CMakeFiles/subsys__bluetooth__host.dir/gatt.c.obj
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: 'd:\Nordic\v1.9.1\toolchain\opt\bin\cmake.EXE' --build 'd:\304\FW\Hook\examples\ble_central\multi-NUS-master21540\build'
The terminal process terminated with exit code: 1.

Terminal will be reused by tasks, press any key to close it.

Apparently an ASSERT macro is trying to warn me about something, but I can't figure out its meaning. Next??

RE: Multi-NUS on the nRF21540-DK

user6207 — Wed, 08 Jun 2022 11:35:27 GMT

If you have used the Toolchain manager to install the SDK, then the only path that matters is the path to the toolchain folder as I showed earlier.

If you have set it right, and removed your old build folder, then it should show up all the boards

If it doesn't, then your toolchain is not properly installed. I did not see that behavior myself before. So if the problem persists, you can attach your project here and I can try to resolve the dependencies.

RE: Multi-NUS on the nRF21540-DK

user68828 — Wed, 08 Jun 2022 10:22:46 GMT

The problem is not errors. I simply cannot find a way to set the configuration for the nRF21540. The only "board" that shows up is the nRF52840DK. There is most likely some path configured incorrectly. But what?

RE: Multi-NUS on the nRF21540-DK

user6207 — Wed, 08 Jun 2022 08:36:03 GMT

I thought that I have given you enough information on how to work with the nRF51540 EK and the integration notes around it. Maybe it is better to work step by step with errors you get. What error are you getting after at this point?

RE: Multi-NUS on the nRF21540-DK

user68828 — Tue, 07 Jun 2022 10:35:25 GMT

Thank you for responding to that much. I am still standing by for a way to configure the project for the nRF21540.

RE: Multi-NUS on the nRF21540-DK

user6207 — Tue, 07 Jun 2022 08:48:08 GMT

Even though a minor nit, but valid observation.

I always assumed that this lack of highlight on the window in focus is due to the dark mode I was using. Also I thought that this highlight is a VSC native feature that we have not changed. There might be some settings in VSC that might help in the colors and highlighted of items in focus. I have not spent time in configuration of my editor.

RE: Multi-NUS on the nRF21540-DK

user68828 — Fri, 03 Jun 2022 13:06:57 GMT

One other minor nit where it doesn't follow Windows standard: When the window has the focus, there should be some indication such as a change of title bar color or a highlighted border. Hard to know that I'm going to get the right screen when I captured the screen below.

My screen looks exactly like yours, except that my toolchain is installed (automatically) in a different location, and I have the project open as well.

RE: Multi-NUS on the nRF21540-DK

user6207 — Fri, 03 Jun 2022 11:00:03 GMT

[quote user="SteveHx"]That dialog box is well-hidden, but I found it. Whether I select Nordic Boards or All Boards, there is nothing that includes 21540 nor any permutation thereof.[/quote]

Are you sure you have selected the right toolchain and choosing the right board genre?

If everything is set right, and still you can't see it, then I would have to assume that your toolchain is not correctly setup.

[quote user="SteveHx"]One additional small nit to pass to the developers: The system icon at the extreme top left of the window (in the caption bar) does not follow Windows standards. In any other application (except one unrelated one that I've already complained to the mfr about), a dblclk on that icon closes the application and all its windows. Here, it pops the app to full-screen.[/quote]

Noted, feedback like this is appreciated. Ill pass it on to the team.

RE: Multi-NUS on the nRF21540-DK

user68828 — Thu, 02 Jun 2022 15:18:20 GMT

That dialog box is well-hidden, but I found it. Whether I select Nordic Boards or All Boards, there is nothing that includes 21540 nor any permutation thereof.

I cannot find the basic set of examples for use with VS Code. I'd like to see if the Uart Central app would work with this board, which would at least give me a branch to swing from.

One additional small nit to pass to the developers: The system icon at the extreme top left of the window (in the caption bar) does not follow Windows standards. In any other application (except one unrelated one that I've already complained to the mfr about), a dblclk on that icon closes the application and all its windows. Here, it pops the app to full-screen.

RE: Multi-NUS on the nRF21540-DK

user6207 — Tue, 31 May 2022 04:55:52 GMT

[quote user="SteveHx"]1) I'm not "creating the project", but using a supplied project, even if it's not one normally supplied with nRF Connect.[/quote]

If you are using one of our samples from the sdk as a template, then it should be a good start.

[quote user="SteveHx"]2) I can't find a way to select the right board (bored?) files. The only thing I see available is nRF52840DK. How do I add additional board files?[/quote]

In the VSC (Visual Studio Code), the selection of board should be 21540 like below.

If you are not able to do that, then there is something wrong with the path you are executing this sample.

[quote user="SteveHx"]I can see prj.conf, and I'm assuming it doesn't matter if I add your suggestion to the beginning or end of that file.[/quote]

It does not matter if you add FEM configs in the beginning or end of the proj.conf file.

RE: Multi-NUS on the nRF21540-DK

user68828 — Fri, 27 May 2022 14:22:56 GMT

[quote userid="6207" url="~/f/nordic-q-a/88165/multi-nus-on-the-nrf21540-dk/369731#369731"]

In simple, select the right board files when creating the project and add this to proj.conf

Fullscreen

[/quote]

Here we have two key issues (so I'm at least entering orbit around your planet):

1) I'm not "creating the project", but using a supplied project, even if it's not one normally supplied with nRF Connect.

2) I can't find a way to select the right board (bored?) files. The only thing I see available is nRF52840DK. How do I add additional board files?

I can see prj.conf, and I'm assuming it doesn't matter if I add your suggestion to the beginning or end of that file.

RE: Multi-NUS on the nRF21540-DK

user6207 — Fri, 27 May 2022 08:30:18 GMT

# FEM
CONFIG_MPSL_FEM=y
CONFIG_BT_CTLR_TX_PWR_DYNAMIC_CONTROL=y
CONFIG_MPSL_FEM_NRF21540_RX_GAIN_DB=0
CONFIG_MPSL_FEM_NRF21540_TX_GAIN_DB=20

Haha, very funny :🙂)

You said you have a Multi-NUS application that is working on nRF52840 and want to make it work on nRF21540 DK.
> For that I told you that the application remains same and you only need to change the configuration (board file and enable FEM). I asked you to enable FEM, since I thought that is the main motivation for you to move from nRF52840 DK -> nRF21540 DK.

The resent struggle you seem is to enable FEM and seems like you have trouble understanding the documentation link I attached to my reply.

In simple, select the right board files when creating the project and add this to proj.conf

# FEM
CONFIG_MPSL_FEM=y
CONFIG_BT_CTLR_TX_PWR_DYNAMIC_CONTROL=y
CONFIG_MPSL_FEM_NRF21540_RX_GAIN_DB=0
CONFIG_MPSL_FEM_NRF21540_TX_GAIN_DB=0

FEM should then be enabled pn the nRF21540 DK with TX_GAIN set to 20.
Hopefully you feel that we are on the same planet after this :D

RE: Multi-NUS on the nRF21540-DK

user68828 — Thu, 26 May 2022 20:30:29 GMT

We are somehow not just on two different planets, we're in two different universes. I have no idea where this CONFIG_MPSL is nor how it fits into hte scheme of things. What am I missing?

RE: Multi-NUS on the nRF21540-DK

user6207 — Wed, 25 May 2022 07:37:43 GMT

Here is the documentation CONFIG_MPSL

RE: Multi-NUS on the nRF21540-DK

user68828 — Tue, 24 May 2022 17:49:58 GMT

Yes, that is correct, 1.9.1.

RE: Multi-NUS on the nRF21540-DK

user6207 — Tue, 24 May 2022 17:41:06 GMT

I assumed that you are using our latest nRF Connect SDKv1.9.1, might be a wrong assumption on my end. Can you please let me know which sdk you are using?

RE: Multi-NUS on the nRF21540-DK

user68828 — Tue, 24 May 2022 14:26:39 GMT

Okay, apparently somebdoy thought further ahead than I thought. But in attempting to follow the instructions you referenced, I'm stuck at this step:

Enable support for MPSL implementation in nRF Connect SDK by setting the CONFIG_MPSL Kconfig option to y.

I find no such option, and I've searched pretty thoroughly (there are certainly a BUNCH of options!).

I also note that the only Board Selection option is the nRF52840 DevKit. Should there be an option for the nRF21540 DevKit?

RE: Multi-NUS on the nRF21540-DK

user6207 — Tue, 24 May 2022 05:32:56 GMT

[quote user="SteveHx"]Not true. There must be some added code to switch between tx and rx[/quote]

Like I said before, there is no code change in the application itself but there are only build time configuration changes to enable FEM. The details of these are given here. If you read the details carefully, you will see that there are configurations to device tree and project configurations that are needed to enable FEM. No logical changes to the application code are needed, only configurational build time changes are needed.

RE: Multi-NUS on the nRF21540-DK

user68828 — Mon, 23 May 2022 12:15:29 GMT

Not true. There must be some added code to switch between tx and rx - that is, to turn the PA and the LNA on and off. Lacking such an adaptation of Multi-NUS, I could at least study the standard NUS application code to learn where in that complex and convoluted code such action needs to happen. Is there in fact some sample code for using the nRF21450? I couldn't find any.

RE: Multi-NUS on the nRF21540-DK

user6207 — Mon, 23 May 2022 11:31:41 GMT

The application that you made with Multi-NUS should not change when you add front end modules like nRF21540. The application remains the same and what changes is the configuration of pins that are connected to your MCU and the nRF21540.