• State Verified Answer
  • Locked Locked
  • Replies 34 replies
  • Subscribers 61 subscribers
  • Views 21443 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 100036
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

nRF UART App

bayi255

where is "nRF UART App" nRF51822 code ?

  • 0

    Hi,

    please see the attached .zip file for a counter-part for the nRF UART iOS app. Note that this firmware is given as-is, and is not optimized in any way. It is made as an example on how to communicate with the app.

    General note regarding "SPP" for low energy: There is not a direct equivalent to the SPP in low energy. Much of the philosophy with low energy is that you are not restricted to using the official profiles, compared to BR/EDR. It's very easy to create your own profile and proprietary service, to enable you to transfer data in sensible chunks instead of just cramming all kinds of data together in serial packages.

    Therefore, an SPP isn't really useful for BLE, and the best solution would be to create your own service to cover the exact data you need to transfer. You also don't have to think about master support, as the profile support is on the application level and not on the OS or stack level, as is common for Bluetooth Classic.

    Best regards, Håkon

    ble_app_uart.zip

  • 0 in reply to Håkon Alseth

    Hello Håkon,

    I've tried to build your code in the muVision 4 environment but I constantly get the following error message:

    ..........\Include\nrf.h(56): error:
    #35: #error directive: "Device variant must be defined. See nrf.h."

    This problem does not occur when I build other example projects from the nRF51 SDK pack. What is going wrong here?

    Alec

  • 0 in reply to Håkon Alseth

    Hello Håkon,

    I've tried to build your code in the muVision 4 environment but I constantly get the following error message:

    ..........\Include\nrf.h(56): error:
    #35: #error directive: "Device variant must be defined. See nrf.h."

    This problem does not occur when I build other example projects from the nRF51 SDK pack. What is going wrong here?

    Alec

  • 0

    The other zip here works with SDK 4.2, but SDK 4.3 introduced two changes:

    1. A chip variant must be defined in the project settings (typically NRF51822_QFAA_CA for most kits).
    2. The on_conn_params_evt() will be called with a new event, causing the default handler from 4.2 to fail. See this question.

    I've fixed both in the attached zip.

    ble_app_uart-sdk4.3.zip

Related