[SOLVED] I can view RTT message on "Debug Terminal" in emStudio, but can't see the message with Jlink RTT viewer

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • [SOLVED] I can view RTT message on "Debug Terminal" in emStudio, but can't see the message with Jlink RTT viewer

    Hello,
    I am trying J-Link RTT on Nuclei N101 core. Now I can successfully get the RTT message from function SEGGER_RTT_printf by "Debug Terminal" in emStudio. But if I use J-Link RTT viewer, I can't see any messages at all. The RTT viewer works well with another MCU STM32F103.
    Here is the output from RTT viewer log, there is nothing from the ternimal window.
    ==================
    LOG: J-Link RTT Viewer V6.80c: Logging started.
    LOG: Terminal 0 added.
    LOG: Connecting to J-Link via USB...
    LOG: Device "N101" selected.
    LOG: ConfigTargetSettings() start
    LOG: ConfigTargetSettings() end
    LOG: TotalIRLen = 5, IRPrint = 0x01
    LOG: JTAG chain detection found 1 devices:
    LOG: #0 Id: 0x11010A6D, IRLen: 05, Unknown device
    LOG: Debug architecture:
    LOG: RISC-V debug: 0.13
    LOG: AddrBits: 7
    LOG: DataBits: 32
    LOG: IdleClks: 7
    LOG: Memory access:
    LOG: Via system bus: No
    LOG: Via ProgBuf: Yes (2 ProgBuf entries)
    LOG: DataBuf: 4 entries
    LOG: autoexec[0] implemented: Yes
    LOG: Detected: RV32 core
    LOG: CSR access via abs. commands: No
    LOG: Temp. halted CPU for NumHWBP detection
    LOG: HW instruction/data BPs: 2
    LOG: Support set/clr BPs while running: No
    LOG: HW data BPs trigger before execution of inst
    LOG: RTT Viewer connected.
    LOG: RTT is running in stop mode: wiki.segger.com/RTT#Stop_mode
    ==================

    It is running on stop mode, it should work. I had suspect the problem is related to emStudio. But after I shutdown the emStudio, I still got nothing. I am sure the program is running, as I can get some messages from the UART port.

    BR
    /Li
  • Hi,
    Good to hear that you are up and running again.

    Did we enter a wrong value in the device xml or was the related entry added by yourself?

    Best regards,
    Fabian
    Please read the forum rules before posting: Forum Rules

    Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/


    Or you can contact us via e-mail.
  • Fabian,
    The xml from J-link dll is wrong. I have informed the chip maker Nuclei about the problem. And they will contact your company soon.
    Nuclei N101, according to the doc I got:
    QSPI flash controller address: 0x15000
    QSPI flash XIP address: 0x20000-0x3FFFF
    RAM address: 0x80000-0x9FFFF.

    I think Nuclei will give you the authoritative details.

    BR
    /Li
  • Hi Li,
    Nuclei contacted us regarding this.

    We will fix this issue as soon as possible.

    Stay up-to-date regarding J-Link:
    segger.com/notification/subscribe.php?prodid=7,94

    Best regards,
    Fabian
    Please read the forum rules before posting: Forum Rules

    Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/


    Or you can contact us via e-mail.