Multi-NUS on the nRF21540-DK

I have succeeded in running the Multi-NUS package on the nRF52840DK. My client's client learned of the nRF21540EK and wants to try using it to extend the range in the present application. Is there an equivalent of the Multi-NUS package available for this board? Fallback would be an NUS application whereby i could gather the routines to access the control lines for the 21540 and merge it with the Multi-NUS software.

Parents Reply Children
  • # 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 :Slight smile)

    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

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

    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.

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

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

    SteveHx said:
    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?

    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.


    SteveHx said:
    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.

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

  • 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.

  • SteveHx said:
    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.

    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.

    SteveHx said:
    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.

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

Related