Sunday, February 18th 2018, 5:44am 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.

dbeckwith

Beginner

Date of registration: Jun 10th 2016

Posts: 5

1

Tuesday, July 19th 2016, 9:44pm

Hardfault Using SystemView 2.38 and FreeRTOS

I recently updated to SystemView 2.38 from 2.36a and I am now getting a hard fault after about an hour of running. The hard fault seems to be occurring in SEGGER_SYSVIEW_OnUserStart_SYS when the RECORD_END macro is called. I can't find an large difference between the two versions. The other interesting detail is while I am running from my IAR debugger I haven't started a SystemView session and I am not recording.

Any thoughts?

Cheers,
Darren

SEGGER - Johannes

Super Moderator

Date of registration: Aug 31st 2012

Posts: 377

2

Monday, July 25th 2016, 6:53pm

Did I get this correct:
You included SystemView in your project but did not start the SystemView app on the host, but your application crashes?

When the SystemView app is not connected and recording is not started explicitly,
SystemView basically does nothing but discarding the event and checking for an incoming packet.
When SystemView is configured to use a static buffer (default) RECORD_END() will simply call SYSVIEW_UNLOCK().

I don't see how this could cause a hard fault.
Do you have high priority interrupts which are not disabled by SYSVIEW_LOCK()?

Best regards
Johannes