J-Link RTT Viewer doesn't show output

⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.wsdof.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
9 posts / 0 new
Last post
Thu, 2017-10-05 06:11
#1
xiaojie
Offline
Last seen:1 year 8 months ago
Joined:2017-08-13 06:56
J-Link RTT Viewer doesn't show output

Hello,

I am working on DA14681 development board - basic and trying to get RTT work.

I tried the ble_multi_link and peripherals_demo and I was able to get printf work with UART on COM port.

然后我试着freertos_rtt例子,”#define CONFIG_RTT' in custom_config_qspi.h.

After compiling and programmed with program_qspi_jtag_win, I connected the board using J-link Commander (v6.20a, parameter: CORTEX-M0, SWD, 4000Hz). In the J-link commander terminal, it showed:
================================================

Connecting to target via SWD
Found SW-DP with ID 0x0BB11477
Scanning AP map to find all available APs
AP[1]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x04770021)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FF000
CPUID register: 0x410CC200. Implementer code: 0x41 (ARM)
Found Cortex-M0 r0p0, Little endian.
FPUnit: 4 code (BP) slots and 0 literal slots
CoreSight components:
ROMTbl[0] @ E00FF000
ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB008 SCS
ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 000BB00A DWT
ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 000BB00B FPB
Cortex-M0 identified.
J-Link>

================================================

Then I opened J-Link RTT viewer (v6.20a) and selected connect existing session with auto reconnect on. I saw following message in RTT viewer:
================================================

0> SEGGER J-Link V6.20a - Real time terminal output
0> SEGGER J-Link OB-SAM3U128 V1.0, SN=480059040
0> Process: JLink.exe

================================================
But I didn't see it prints the "#" characters.

Is there anything wrong with my procedure? Is there any setting do I need to change to make RTT work? Thanks.

Device:
DA14580
Thu, 2017-10-05 10:39
STS_Dialog (not verified)
Hi xiaojie,

Hi xiaojie,

Please for proper setup checkUM-B-044 "DA1468x Software Platform Reference" at pages 159-161from Documents tab at software Development Kit Section.

Note: For this demo code it is not needed to make any stack/heap size changes.

After that you should connect to J-Link RTT Viewer using the following configurations.

BR,

STS_Dialog.

Accepted answer
Fri, 2017-10-06 05:40
xiaojie
Offline
Last seen:1 year 8 months ago
Joined:2017-08-13 06:56
Hello STS_Dialog,

Hello STS_Dialog,

Thanks a lot for your reply. I am able to get SystemView work and have output from RTT Viewer based on the information you provided.

I have another questions regarding this, in my eclipse welcome page, I don't see SystemViewer icon like the one showed in Figure.66 of the document you mentioned. Could you please tell me how to add it? Thanks.

Mon, 2017-10-09 10:34
STS_Dialog (not verified)
Hi,

Hi,

As far as your last query is concerned, please try to delete the.metadata文件夹中保存的目录the SDK. With that action, SmartSnippets Studio deletes its state from its memory and upon reopening SmartSnippets Studio, you will be asked to setup it again (as you did at the very first time). If that doesn’t work I’ll come back to you when I have something else to suggest (I have already asked for that our SDK team and I am waiting their response)

BR,

STS_Dialog.

Mon, 2017-10-09 17:30
xiaojie
Offline
Last seen:1 year 8 months ago
Joined:2017-08-13 06:56
Hello STS_Dialog,

Hello STS_Dialog,

I tried to delete the .metadata folder but still don't see Systemviewer button in the welcome page. Thanks.

Tue, 2017-10-10 14:59
STS_Dialog (not verified)
Hi xiaojie,

Hi xiaojie,

Set as a directory of the created workspace a path that is located in the SDK itself (the .metadata folder should be inside the DA1468x_DA15xxx_SDK_1.0.10.1072 folder) and as soon as you open this file you should see the .metadata, binaries, config and all the rest of the folders of the SDK.

Thanks STS_dialog

Accepted answer
Wed, 2017-10-11 04:08
xiaojie
Offline
Last seen:1 year 8 months ago
Joined:2017-08-13 06:56
Hi STS_dialog,

Hi STS_dialog,

I deleted old .metadata folder in my workspace folder and copied config/ folder from SDK folder to my workspace folder. Now I can see Systemviewer button. Thanks a lot for your help.

Xiaojie

Wed, 2017-12-13 00:15
uta_lc
Offline
Last seen:1 year 2 weeks ago
Joined:2016-05-03 07:39
Hi Dialogue,

Hi Dialogue,

Do you have the corresponding configuration for DA14581? Looks like DA14581 should support RTT as well given it is using cortex-M0?

Thanks for your attention,
uta_lc

Wed, 2017-12-13 15:40
(Reply to #8)
MT_dialog
Offline
Last seen:2 months 1 week ago
Staff
Joined:2015-06-08 11:34
Hi uta_lc,

Hi uta_lc,

Well, on the 58x family the RTT printing is not officially supported, but from a quick test on the blinky project i could include the proper file of the RTT module (SEGGER_RTT.h and SEGGER_RTT.c) invoke the SEGGER_RTT_WriteString(0, "test\n"); and opening the RTT_Viewer and by providing to the RTT Control Block the proper address (check from the map file generated when you build the project) i could print data on the RTT_Viewer.

Thanks MT_dialog