• State Verified Answer
  • Locked Locked
  • Replies 11 replies
  • Subscribers 77 subscribers
  • Views 2564 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 277614
Options
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

How to enable J-Link RTT Viewer on nRF5340 using the Enhanced shock burst (esb) sample code?

Anthony Shivakumar

Hi,

I am trying to get my nrf24L01+ to communicate with nrf5340 using the enhanced shock burst sample code. In the sample code there are LOG_INF, LOG_ERR, LOG_DBG commands available? How do I print them out on the console? I would prefer to use the J-LINK RTT Viewer. I have compiled the code for the cpu_net core.

Tank you so much for your help.

  • 0 in reply to Anthony Shivakumar

    Thank you for your reply.

    I think there is a deeper issue at play here.

    After the program is downloaded successfully, it says:

    Illegal value 0x21001450 written to register 66 (MSP_NS) ignored

    Is this something got to do with why the program/ console logs are not working?

    Yes, I added the for loop to print a msg. I still see nothing. I removed CONFIG_NCS_SAMPLES_DEFAULTS as well, and no logs seem to appear.

  • 0 in reply to Vidar Berg

    I have tried to verify the code.

    It appears nothing is downloaded to the the network core's flash. Is the core locked? How do I unlock it? When I compile and download It keeps saying successfully  downloaded, not sure what is it successfully downloading if the verification fails.

    Any comment on what all this is? I literally just need a console log out put. Seems like there are other issues that need to be addressed here :( .

  • +1 in reply to Anthony Shivakumar

    I see the same now when I try to use Segger Embedded Studio and I need more time to investigate. Are you able to work with the VS code extension or from the command line in the meantime?

    Building from the command line:

    // Update PATH to include the SDK build tools
c:\Users\<user>\ncs\v1.7.0>toolchain\cmd\env.cmd

// Change directory to sample folder
c:\Users\<user>\ncs\v1.7.0>cd nrf\samples\esb\prx

// Build command. Includes "empty app core" as a child image
c:\Users\<user>\ncs\v1.7.0\nrf\samples\esb\prx>west build -b nrf5340dk_nrf5340_cpunet -- -DCONFIG_NCS_SAMPLE_EMPTY_APP_CORE_CHILD_IMAGE=y

// Run recovery procedure, then flash both cores
c:\Users\<user>\ncs\v1.7.0\nrf\samples\esb\prx>west flash --recover

  • 0 in reply to Anthony Shivakumar

    Hi Vidar,

    I tried following the process using the command line tool. I am able to build using the command line tools. But unable to flash.

    So I used the nrf connect GUI tool:

    But still, I see no logging.

    Can you tell me what tools, setup and configuration, O.S you used to get the logging enabled. May be if I can replicate it exactly, I may be successful.

  • 0 in reply to Anthony Shivakumar

    Hi, 

    Please run the commands from cmd.exe instead. I see from the log that west is not invoking the python interpreter located in the SDKs toolchain directory indicating that the PATH was not updated correctly. Also, the file you want to program is merged_domains.hex as it includes the empty app core image needed for the Application processor. Zephyr.hex contains the esb application.

    I have the SDK installed via the toolchain manager and I’m running windows 10. Hope this helps.

Related
Terms of service