Sunday, February 25th 2018, 6:18pm UTC+1

You are not logged in.

  • Login
  • Register

Dear visitor, welcome to SEGGER Forum. If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

pruesch

Beginner

Date of registration: Jun 11th 2015

Posts: 84

1

Tuesday, April 5th 2016, 4:01pm

[Solved] prevent SystemView from crashing on high load situations

Hi,

I'm successfully running SystemView with my STM32F429 target.
The target runs FreeRTOS with lwip (TCP/IP Stack) and an iperf server. I'm using a J-Trace Cortex-M to connect to the target.



as soon as I start the bandwithtest, SystemView just displays an error message:
Invalid packet received. recording stopped.


the test finishes and shows respectable values.


I set the SWD frequency to 20MHz, the SystemView Up-Buffer is set to 8KB.


How can I prevent SystemView from crashing in this benchmark test?






Best Regards

SEGGER - Johannes

Super Moderator

Date of registration: Aug 31st 2012

Posts: 377

2

Thursday, April 7th 2016, 9:55am

Hi,

Invalid packets are most commonly caused by not locking everything which creates SystemView events or causes context switches.
Could you make sure that SEGGER_SYSVIEW_LOCK() / SEGGER_RTT_LOCK() are defined to disable all interrrupts which do so?
To be sure this caused the problem, disable all interrupts.

Best regards
Johannes

pruesch

Beginner

Date of registration: Jun 11th 2015

Posts: 84

3

Tuesday, April 12th 2016, 3:15pm

Hi Johannes,

thanks for your attention.

you are right; SEGGER_RTT_LOCK is not defined during the build... need to look into it.
regards

pruesch

Beginner

Date of registration: Jun 11th 2015

Posts: 84

4

Tuesday, April 12th 2016, 5:53pm

aargh...
the reflection in the IDE was wrong.
the RTT_LOCK symbol is defined!
...and it gets called!

So my problem is not solved :(

SEGGER - Johannes

Super Moderator

Date of registration: Aug 31st 2012

Posts: 377

5

Thursday, April 28th 2016, 4:18pm

Hi,

Could you give the latest beta (V2.35) SystemViewer a try?
It fixes one issue which could cause invalid packets in high load situations, too.

Regards
Johannes

pruesch

Beginner

Date of registration: Jun 11th 2015

Posts: 84

6

Friday, May 13th 2016, 2:25pm

what are the changes in 2.34 that could improve the stability under high load situations?

SEGGER - Johannes

Super Moderator

Date of registration: Aug 31st 2012

Posts: 377

7

Wednesday, May 18th 2016, 10:14am

Hi,

In some cases SystemViewer could have read incomplete events from the target,
which led to the invalid packet message.

This has been improved.

Regards
Johannes

pruesch

Beginner

Date of registration: Jun 11th 2015

Posts: 84

8

Wednesday, May 25th 2016, 2:12pm

I upgraded to 2.34 and it crashes no more!

my next problem will be lots of dropped packets but this is likely because the target interface speed changes from what I defined in the command line of the gdb server.

SEGGER - Johannes

Super Moderator

Date of registration: Aug 31st 2012

Posts: 377

9

Wednesday, June 1st 2016, 5:44pm

Hi,

Great to read it is working now.

If you started GDB Server before the SystemVIew recording, the data is read via this J-Link connection.
In this case you should set a higher interface speed in GDB Server.
If this does not completely help, you will need to increase the SystemView buffer size.

Regards
Johannes