[SOLVED] Systemview freeRTOS start recording

rum · Jan 28th 2016, 12:35pm

Hello,
I have configured my application with freertos (without patch) to use Systemview. I start recording, target is reset after while I stop recording. But there is nothing recorded. I don't get any information about tasks. In my main I call "SEGGER_SYSVIEW_Conf()" Can you help? Attached is what I get.
rum

pruesch · Jan 29th 2016, 9:49am

Brainfuck Source Code

/*File : SEGGER_SYSVIEW_FreeRTOS.h Purpose : Interface between FreeRTOS and SystemView.
Include this file at the end of FreeRTOSConfig.h
--------- END-OF-HEADER ---------------------------------------------*/

maybe it helps to include SEGGER_SYSVIEW_FreeRTOS.h at the end of FreeRTOSConfig.h

rum · Jan 29th 2016, 11:47am

Of course file is included. When Systemview attaches, application will crash. I have increased stack for all tasks, now there is plenty of space >200byte as suggested. I have stack overflow monitor in place and I think it is not the stack. I cannot detect reason why application resets. There is no useful info from callstack. I find application sitting at reset vector. I have also applied patch to freeRTOS. What else can I check?

SEGGER - Johannes · Jan 29th 2016, 3:49pm

Hi,

Please update to the latest V2.30 sources,
which fix a bug in the FreeRTOS SystemView interface and could cause an assertion.

Best regards
Johannes

rum · Jan 30th 2016, 2:02am

Hello,
Thank you, new version 2.3 is much better and is running now on my XMC device. Great!
I have another problem. Recording halts after about 5sec with message "Invalid packet received, Recording stopped". Attached is screenshot with last actions recorded. Do you have any suggestions? I am running SWO interface at maximum speed 50MHz and I am using ULTRA+ probe.
rum

SEGGER - Johannes · Feb 2nd 2016, 9:16am

Hi,

Could you provide a SystemView recording which shows the invalid packet?

Best regards
Johannes

SEGGER - Johannes · Feb 4th 2016, 4:33pm

Problem has been solved via mail. For completeness:
The invalid packets where caused by a locking problem.
In the SEGGER_SYSVIEW_LOCK() / SEGGER_RTT_LOCK() all interrupts which could create SystemView events should be disabled (masked).

For FreeRTOS and Cortex-M3/4 use either following macro or redirect lock and unlock to the FreeRTOS functions.

C Source Code

#define SEGGER_RTT_LOCK() { \
unsigned int LockState; \
__asm volatile ("mrs %0, basepri \n\t" \
"mov r1, %1 \n\t" \
"msr basepri, r1 \n\t" \
: "=r" (LockState) \
: "i" ( configMAX_SYSCALL_INTERRUPT_PRIORITY) \
: "r1" \
);

- Johannes

rum · Feb 5th 2016, 8:03pm

Thank you Johannes for support and solving the problem.

shenj · Aug 22nd 2016, 8:21pm

for the lock function,
what is the complete macro for SEGGER_RTT_LOCK() and SEGGER_RTT_UNLOCK()?
I got the errors in the attachment.

SEGGER - Johannes · Aug 30th 2016, 9:16am

You missed the backspace in the first line:

C Source Code

#define SEGGER_RTT_LOCK() { \

Regards
Johannes

Brainfuck Source Code

C Source Code

C Source Code

Share