examples

Hi All.


A few years ago, Nordic documentation for developers included many "examples" to practice with and learn about this technology. For instance, ... >examples>ble peripheral>ble_app_uart>... etc. etc.
My question is: Is Nordic keeping this valuable information somewhere? Thanks.

Parents
  • Using the new SDK , you can find them under \ncs\v2.7.0\nrf\samples. Download the latest nrfconnect for desktop, click on the Toolchain Manager and download the latest (2.7.0 in my case). 
    Wait a long while it downloads the whole world (code and tools)  and you will find many of them in the relative directory I just specified.
    A M
    The old SDK still exists, but it isn't going to be supported. You can find it someplace on the website.

    How about a link
    nRF Connect for Desktop - Downloads - nordicsemi.com

    L
    ink to the old SDK
    nRF5 SDK downloads - nordicsemi.com

  • Hi AMarch01. Thanks for your time.

    In my case, I want to know the memory layout and size I need to choose the most convenient Nordic SoC and implement a transmitting-only beacon using the new toolchain and VSC IDE Nordic is now recommending.
    In the old SDK and for a Segger IDE environment, an example called ble_app_beacon was described. Still, unfortunately, the new nRF Connect SDK (v2.7.0 in my case) did not include this example. I could use the actual Segger IDE environment, but since the old nRF5 SDK hasn´t been maintained for some time, I suspect the setup will give errors.
    So my question is: Could I Build-Flash this old Segger .emProject file into my nRF52849 DK using the VSC IDE, toolchain, and nRF Connect SDK that Nordic recommends nowadays (i.e., the one described in the nRF Connect SDK Fundamentals DevAcademy course) and see the memory details I mentioned?

    Waiting for your comments,

    Regards,

    Juan

Reply
  • Hi AMarch01. Thanks for your time.

    In my case, I want to know the memory layout and size I need to choose the most convenient Nordic SoC and implement a transmitting-only beacon using the new toolchain and VSC IDE Nordic is now recommending.
    In the old SDK and for a Segger IDE environment, an example called ble_app_beacon was described. Still, unfortunately, the new nRF Connect SDK (v2.7.0 in my case) did not include this example. I could use the actual Segger IDE environment, but since the old nRF5 SDK hasn´t been maintained for some time, I suspect the setup will give errors.
    So my question is: Could I Build-Flash this old Segger .emProject file into my nRF52849 DK using the VSC IDE, toolchain, and nRF Connect SDK that Nordic recommends nowadays (i.e., the one described in the nRF Connect SDK Fundamentals DevAcademy course) and see the memory details I mentioned?

    Waiting for your comments,

    Regards,

    Juan

Children
  • I would imagine that such a task would be difficult, the nrfx library probably doesn't mesh together the same way and unraveling any pieces that are under cmake control would be an effort.

    Beacon appears to be a generic operation for BLE so a generic example would be found in 
    v2.7.0\zephyr\samples\bluetooth\beacon\ 

    I attempted to build this and when the zephyr build is completed using NCS under VS code I get an ending output report as follows:
    [186/186] Linking C executable zephyr\zephyr.elf
    Memory region Used Size Region Size %age Used
    FLASH:        99692 B    1 MB        9.51%
    RAM:          26632 B    256 KB      10.16%
    IDT_LIST:     0 GB       32 KB       0.00%

    This was to a nrf52840-DK target.

    It is a good idea to follow the Nordic education guides with the latest software products. There are guides on how to configure and use the nrf Connect SDK using VS Code.



Related