• State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 69 subscribers
  • Views 5699 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 286331
Options
Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
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

nRF5 SDK 17.1.0 examples is not compiling in latest SES (6.20a)

Nicholas Lee

None of our existing software projects (based closely on Nordic example projects) will build when the SEGGER IDE is upgraded from 5.70a to the latest 6.20a

The public forum post mentioning this issue contains some replies from staff, but none of these replies have enabled us to get the projects working.
Ref: https://devzone.nordicsemi.com/f/nordic-q-a/85405/nrf5-sdk-17-1-0-examples-is-not-compiling-in-latest-ses-6-20a

When the sdk_config entry RETARGET_ENABLED is set to 0, and the project file SEGGER_RTT_Syscalls_SES.C is set to "exclude from build", we were expecting the build to the proceed unhindered.

However, instead we were greeted by the list of errors shown in the attached image file.

i.e. parts of the system can't find stdout or 'putchar', or 'getchar'. 

What step(s) are we missing to make this work?

Parents
  • +1

    I know what it 'should' do, but I already said that performing those steps did not work for us, and I reported the resulting list of errors.
    Our software project was based on the ble_app_uart_pca10056_s140 example project.

    The main changes to the project are adding the use of the SPIM3 and SAADC devices for audio input/output. None of which should make any real difference to this issue. I suspect the most likely culprit is using NRF_LOG_INFO to report debug messages to the messages window within the SEGGER IDE.
    Can the whole  NRF_LOG_INFO logging system now be replaced with PRINTF instead, or is that not how debugging is supposed to be implemented?
    NB: I am using the nRF5_SDK_17.1.0_ddde560 together with the s140 softdevice

    I tried to include the sdk_config.h file which contains all the relevant settings for the project, but the forum gave the following error:
    "We apologize, but an unexpected issue prevented the page you requested from being available. We've logged the issue so the site administrator can resolve the problem. "

Reply
  • +1

    I know what it 'should' do, but I already said that performing those steps did not work for us, and I reported the resulting list of errors.
    Our software project was based on the ble_app_uart_pca10056_s140 example project.

    The main changes to the project are adding the use of the SPIM3 and SAADC devices for audio input/output. None of which should make any real difference to this issue. I suspect the most likely culprit is using NRF_LOG_INFO to report debug messages to the messages window within the SEGGER IDE.
    Can the whole  NRF_LOG_INFO logging system now be replaced with PRINTF instead, or is that not how debugging is supposed to be implemented?
    NB: I am using the nRF5_SDK_17.1.0_ddde560 together with the s140 softdevice

    I tried to include the sdk_config.h file which contains all the relevant settings for the project, but the forum gave the following error:
    "We apologize, but an unexpected issue prevented the page you requested from being available. We've logged the issue so the site administrator can resolve the problem. "

Children
  • 0 in reply to Nicholas Lee

    I see the same with the ble_app_uart_pca10056_s140 example project. The issue and fix is described in this thread.

    Clarification for future reference:

    1. In most cases getting RTT to work with Segger Embedded Studio >= 6.20a just involved removing SEGGER_RTT_Syscalls_SES.c from the project. See this thread for more details.
    2. In some cases (like with ble_app_uart) you also need to do the following (see this thread for more info):
      1. Remove retarget.c from the project.
      2. Update the project configuration as shows in this screenshot.

Related