Attachments (1) Download All
Nordic Case Info
  • Case ID: 244360
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Debug -> Go In valid ELF file

linh

Hi,

I am a beginner with nrf9160 DK and followed the instruction in https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/gs_programming.html#gs-programming to build and programm the example mqtt_simple. But in step 6, when i click Debug -> Go following warning occurs even though the Project is built.

Then i click Yes and following error occurs:

Do you know what is the Problem? Thank you

Regards,

Linh

Parents
  • 0

    Hi.

    Which commit are you on in the nrf repo?

    To find out, you can open a terminal inside <your NCS folder>/nrf, and enter the command "git rev-parse HEAD".

    There is also a new version of Segger Embedded Studio. Could you try the new version, and see if you still have the problem?

    You can find a link to the new version in the Getting Started Assistant application in nRF Connect for Desktop.

    Here is a link for the 64-bit Windows version: segger.com/downloads/embedded-studio/embeddedstudio_arm_nordic_win_x64

    Best regards,

    Didrik

  • 0 in reply to Didrik Rokhaug

    Hi,

    thank you for answering me. There are more errors occur when i use the new version.This is how it looks like

    Regards,

    Linh

  • 0 in reply to linh

    Did you check the "Clean build folder" checkbox when you opened the project?

    If not, could you try to import it again with the checkbox checked?

    Also, you are not using NCS v1.0.0 as your folder name indicates.

    You can either try to upgrade to the latest master branch (git pull, west update), or you can revert to the previous release (git checkout v1.1.0, west update)

  • 0 in reply to Didrik Rokhaug

    I go to path <sourcecode_root>\ncs\nrf in cmd as admin and then do git checkout v1.1.0, west update.

    The result of "git rev-parse HEAD" in side my <NCS folder>/nrf is

    d3130d77559e2206a2541b09dd26e9be2f8532ed

    Then I opened the Project again with checking "Clean build folder" check box. But now I can't event build the Project with Build -> Build Solution. It Looks like this after "Build Solution"

    should I try git checkout and west update again or try an other Version of NCS?

Reply
  • 0 in reply to Didrik Rokhaug

    I go to path <sourcecode_root>\ncs\nrf in cmd as admin and then do git checkout v1.1.0, west update.

    The result of "git rev-parse HEAD" in side my <NCS folder>/nrf is

    d3130d77559e2206a2541b09dd26e9be2f8532ed

    Then I opened the Project again with checking "Clean build folder" check box. But now I can't event build the Project with Build -> Build Solution. It Looks like this after "Build Solution"

    should I try git checkout and west update again or try an other Version of NCS?

Children
  • +1 in reply to linh

    The problem might be due to a too-long file path.

    Try to move your NCS directory closer to the root of your file system.

  • 0 in reply to Didrik Rokhaug

    Hi,

    Thank you for your answer. I try do move to other directory and it's work with Segger Embedded Studio v 4.3. With verson 4.4 there are a Problem with Target -> Download zephyr/merged.hex. At least it works for one of them so it's ok.

    Regards,

    Linh

  • 0 in reply to linh

    Hi, great to hear that it is now working for you!

    However, I am interested in knowing more about the error you get in SES v4.42a.

    If it is not too much to ask, could you change the drop-down menu in the "Output" panel from "Tasks" to "Output" and send me the output?

    Also, you can try to run "nrfjprog -e" in a terminal, then download the application from SES v4.42a. I believe it should work then.

    Best regards,

    Didrik

  • 0 in reply to Didrik Rokhaug

    Hi, 

    Hier is the Output. 

    Where should i run nrfjprog -e. i try to run it in cmd.exe but got a message that the command nrfjprog is not found. By the way i cannot install  nRF Command Line Tools . After running the nRF-Command-Line-Tools_10_6_0_Installer.exe I got the following Log file. Maybe, it is relevant.

    Fullscreen _.log Download
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    [29EC:27A8][2020-02-18T11:57:31]i001: Burn v3.11.1.2318, Windows v10.0 (Build 16299: Service Pack 0), path: C:\WINDOWS\Temp\{0B2BE5FE-FCAE-40FE-BE91-AC1005372E2C}\.cr\nRF-Command-Line-Tools_10_6_0_Installer.exe
    [29EC:27A8][2020-02-18T11:57:31]i000: Initializing version variable 'SeggerNewVersion' to value '6.54.3.0'
    [29EC:27A8][2020-02-18T11:57:31]i000: Initializing version variable 'VC2017INSTALLINGVER' to value '14.15.26706'
    [29EC:27A8][2020-02-18T11:57:31]i009: Command Line: '-burn.clean.room=C:\Draeger\Install\nRF-Command-Line-Tools_10_6_0_Installer.exe -burn.filehandle.attached=688 -burn.filehandle.self=704'
    [29EC:27A8][2020-02-18T11:57:31]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\Draeger\Install\nRF-Command-Line-Tools_10_6_0_Installer.exe'
    [29EC:27A8][2020-02-18T11:57:31]i000: Setting string variable 'WixBundleOriginalSourceFolder' to value 'C:\Draeger\Install\'
    [29EC:27A8][2020-02-18T11:57:31]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\lethuyli\AppData\Local\Temp\nRF-Command-Line-Tools_10_6_0_20200218115731.log'
    [29EC:27A8][2020-02-18T11:57:31]i000: Setting string variable 'WixBundleName' to value 'nRF-Command-Line-Tools_10_6_0'
    [29EC:27A8][2020-02-18T11:57:31]i000: Setting string variable 'WixBundleManufacturer' to value 'Nordic Semiconductor'
    [29EC:0BA4][2020-02-18T11:57:31]i000: Setting numeric variable 'WixStdBALanguageId' to value 1033
    [29EC:0BA4][2020-02-18T11:57:31]i000: Setting version variable 'WixBundleFileVersion' to value '10.6.0.0'
    [29EC:27A8][2020-02-18T11:57:31]i100: Detect begin, 3 packages
    [29EC:27A8][2020-02-18T11:57:31]i000: Setting numeric variable 'SeggerInHKCU' to value 1
    [29EC:27A8][2020-02-18T11:57:31]i052: Condition 'SeggerInHKCU' evaluates to true.
    [29EC:27A8][2020-02-18T11:57:31]i000: Setting string variable 'SeggerHKCUInstallPath' to value 'C:\Program Files (x86)\SEGGER\JLink'
    [29EC:27A8][2020-02-18T11:57:31]i000: Setting numeric variable 'SeggerInHKLM' to value 1
    [29EC:27A8][2020-02-18T11:57:31]i052: Condition 'SeggerInHKLM' evaluates to true.
    [29EC:27A8][2020-02-18T11:57:31]i000: Setting string variable 'SeggerHKLMInstallPath' to value 'C:\Program Files (x86)\SEGGER\JLink\'
    [29EC:27A8][2020-02-18T11:57:31]i052: Condition 'SeggerInHKCU' evaluates to true.
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to linh

    We have seen that issue internally as well.

    If you have nRF Connect for Desktop, you can use the programmer application there instead of nrfjprog.

Terms of service