Saturday, April 21st 2018, 3:36pm UTC+2

You are not logged in.

  • Login
  • Register

Installation of Ozone on new computer crashes when attempting to view FreeRTOS threads

bamos

Beginner

Date of registration: Jul 7th 2017

Posts: 2

1

Friday, July 7th 2017, 5:42pm

Installation of Ozone on new computer crashes when attempting to view FreeRTOS threads

I've recently moved to a new computer and installed Ozone 2.42. When trying to view tasks with a project using freeRTOS (View->FreeRTOS->Tasks) Ozone crashes. It only crashes if the task view is enabled.

I'm on a fresh Windows 7 installation, running Ozone through a j-trace and j-trace pro on an STM32F7. I've tried uninstalling and re-installing with no luck, as well as installing an older version of Ozone, but the crash persists when trying to view freeRTOS tasks.


Any suggestions?

The error follows:
"Problem signature:
Problem Event Name: APPCRASH
Application Name: Ozone.exe
Application Version: 2.4.2.0
Application Timestamp: 594bb22e
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.23807
Fault Module Timestamp: 5915fdce
Exception Code: c0000005
Exception Offset: 000000000004f23c
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: d54b
Additional Information 2: d54b2e50f8000514d2345d55eaebc4ac
Additional Information 3: bbcf
Additional Information 4: bbcfb80054e569d43ef7909c45db91f0
"

Also, here's some information from Microsoft's "Application Verifier"

Source code

 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<avrf:logfile xmlns:avrf="Application Verifier">
	<avrf:logSession TimeStarted="2017-07-07 : 11:32:25" PID="9856" Version="2">
		<avrf:logEntry Time="2017-07-07 : 11:35:42" LayerName="Heaps" StopCode="0x13" Severity="Error">
			<avrf:message>First chance access violation for current stack trace.</avrf:message>
			<avrf:parameter1>69b1d7000 - Invalid address causing the exception.</avrf:parameter1>
			<avrf:parameter2>7900c032 - Code address executing the invalid access.</avrf:parameter2>
			<avrf:parameter3>1b9e30 - Exception record.</avrf:parameter3>
			<avrf:parameter4>1b9940 - Context record.</avrf:parameter4>
			<avrf:stackTrace>
				<avrf:trace>vrfcore!VerifierDisableVerifier+934 ( @ 0)</avrf:trace>
				<avrf:trace>ntdll!RtlApplicationVerifierStop+d3 ( @ 0)</avrf:trace>
				<avrf:trace>vfbasics!+7fed69d6377 ( @ 0)</avrf:trace>
				<avrf:trace>vfbasics!+7fed69d7c9b ( @ 0)</avrf:trace>
				<avrf:trace>vfbasics!+7fed69d7392 ( @ 0)</avrf:trace>
				<avrf:trace>ntdll!vsprintf_s+12b ( @ 0)</avrf:trace>
				<avrf:trace>ntdll!RtlUnwindEx+852 ( @ 0)</avrf:trace>
				<avrf:trace>ntdll!KiUserExceptionDispatcher+2e ( @ 0)</avrf:trace>
				<avrf:trace>MSVCR100!memmove+d2 ( @ 0)</avrf:trace>
				<avrf:trace>Ozone!+13f5f2800 ( @ 0)</avrf:trace>
				<avrf:trace>Ozone!+13f5f2912 ( @ 0)</avrf:trace>
				<avrf:trace>Ozone!+13f43646a ( @ 0)</avrf:trace>
				<avrf:trace>Ozone!+13f437549 ( @ 0)</avrf:trace>
				<avrf:trace>Ozone!+13f5a2198 ( @ 0)</avrf:trace>
				<avrf:trace>FreeRTOSPlugin!+7fee4c01b56 ( @ 0)</avrf:trace>
				<avrf:trace>FreeRTOSPlugin!+7fee4c01db8 ( @ 0)</avrf:trace>
				<avrf:trace>FreeRTOSPlugin!+7fee4c0200f ( @ 0)</avrf:trace>
				<avrf:trace>FreeRTOSPlugin!+7fee4c02968 ( @ 0)</avrf:trace>
				<avrf:trace>FreeRTOSPlugin!+7fee4c02c2d ( @ 0)</avrf:trace>
				<avrf:trace>Ozone!+13f5da430 ( @ 0)</avrf:trace>
				<avrf:trace>Ozone!+13f523204 ( @ 0)</avrf:trace>
				<avrf:trace>Ozone!+13f6038cb ( @ 0)</avrf:trace>
				<avrf:trace>QtCore4!QMetaObject::activate+53c ( @ 0)</avrf:trace>
				<avrf:trace>Ozone!+13f602e6e ( @ 0)</avrf:trace>
				<avrf:trace>QtCore4!QMetaObject::activate+53c ( @ 0)</avrf:trace>
				<avrf:trace>QtGui4!QDockWidget::visibilityChanged+33 ( @ 0)</avrf:trace>
				<avrf:trace>QtGui4!QDockWidget::event+a4 ( @ 0)</avrf:trace>
				<avrf:trace>QtGui4!QApplicationPrivate::notify_helper+f6 ( @ 0)</avrf:trace>
				<avrf:trace>QtGui4!QApplication::notify+1818 ( @ 0)</avrf:trace>
				<avrf:trace>QtCore4!QCoreApplication::notifyInternal+72 ( @ 0)</avrf:trace>
				<avrf:trace>QtGui4!QWidgetPrivate::show_helper+208 ( @ 0)</avrf:trace>
				<avrf:trace>QtGui4!QWidget::setVisible+30c ( @ 0)</avrf:trace>
				<avrf:trace>Ozone!+13f500718 ( @ 0)</avrf:trace>
				<avrf:trace>Ozone!+13f5fb6a6 ( @ 0)</avrf:trace>
				<avrf:trace>QtCore4!QMetaObject::activate+53c ( @ 0)</avrf:trace>
				<avrf:trace>QtGui4!QAction::activate+e0 ( @ 0)</avrf:trace>
				<avrf:trace>Ozone!+13f5b0346 ( @ 0)</avrf:trace>
				<avrf:trace>Ozone!+13f5b0565 ( @ 0)</avrf:trace>
				<avrf:trace>Ozone!+13f5005bc ( @ 0)</avrf:trace>
				<avrf:trace>Ozone!+13f5fb6b3 ( @ 0)</avrf:trace>
				<avrf:trace>QtCore4!QMetaObject::activate+53c ( @ 0)</avrf:trace>
				<avrf:trace>QtGui4!QAction::activate+e0 ( @ 0)</avrf:trace>
				<avrf:trace>QtGui4!QMenu::findIdForAction+328 ( @ 0)</avrf:trace>
				<avrf:trace>QtGui4!QMenu::internalDelayedPopup+8c2 ( @ 0)</avrf:trace>
				<avrf:trace>QtGui4!QWidget::event+d5 ( @ 0)</avrf:trace>
				<avrf:trace>QtGui4!QMenu::event+2a3 ( @ 0)</avrf:trace>
				<avrf:trace>QtGui4!QApplicationPrivate::notify_helper+f6 ( @ 0)</avrf:trace>
				<avrf:trace>QtGui4!QApplication::notify+720 ( @ 0)</avrf:trace>
				<avrf:trace>QtCore4!QCoreApplication::notifyInternal+72 ( @ 0)</avrf:trace>
				<avrf:trace>QtGui4!QApplicationPrivate::sendMouseEvent+1de ( @ 0)</avrf:trace>
				<avrf:trace>QtGui4!QApplication::winFocus+9db ( @ 0)</avrf:trace>
				<avrf:trace>QtGui4!QApplication::restoreOverrideCursor+93d ( @ 0)</avrf:trace>
				<avrf:trace>USER32!TranslateMessageEx+29d ( @ 0)</avrf:trace>
				<avrf:trace>USER32!TranslateMessage+1e2 ( @ 0)</avrf:trace>
				<avrf:trace>QtCore4!QEventDispatcherWin32::processEvents+3ba ( @ 0)</avrf:trace>
				<avrf:trace>QtGui4!QApplicationPrivate::translateTouchEvent+885 ( @ 0)</avrf:trace>
				<avrf:trace>QtCore4!QEventLoop::exec+231 ( @ 0)</avrf:trace>
				<avrf:trace>QtCore4!QCoreApplication::exec+e0 ( @ 0)</avrf:trace>
				<avrf:trace>Ozone!+13f5f5169 ( @ 0)</avrf:trace>
				<avrf:trace>Ozone!+13f6258ce ( @ 0)</avrf:trace>
				<avrf:trace>kernel32!BaseThreadInitThunk+d ( @ 0)</avrf:trace>
				<avrf:trace>ntdll!RtlUserThreadStart+21 ( @ 0)</avrf:trace>
			</avrf:stackTrace>
		</avrf:logEntry>
	</avrf:logSession>
</avrf:logfile>

SEGGER - Johannes

Super Moderator

Date of registration: Aug 31st 2012

Posts: 377

2

Monday, July 10th 2017, 2:11pm

Hi,

The FreeRTOS plugin in general works, so we would need more information to analyze the problem.

Are you using the 64-bit or 32-bit version?
Which version of FreeRTOS do you use?
Would it be possible to provide your application elf file?
Do you use a standard eval board or custom hardware?
Could you provide a Ozone log file of a crashed session? (start Ozone with --logfile=<PathToLogfile>)

Best regards
Johannes

bamos

Beginner

Date of registration: Jul 7th 2017

Posts: 2

3

Monday, July 10th 2017, 10:08pm

Yes, the FreeRTOS plugin has been working well for us across multiple machines, hardware platforms and firmware projects for months. I'm not sure what happened. We even have a laptop that sat untouched for a month which no longer works with the same two jtrace programmers we've been using.

Also of note: I noticed on one machine Ozone uses all available RAM (~14GB) when opening a project file, which I don't remember being normal behavior. . .

The answers to your previous questions:

- We're using Windows 7 64 bit
- FreeRTOS 9.0.0
- I'll PM a hex file (and the project file)
- custom hardware (3 different boards and two different MCU's, none of which don't work now)
- log is attached (logging had to be started in the project file rather than from the command line)

thanks,
Brian
bamos has attached the following file:
  • ozoneLog.txt (27.26 kB - 104 times downloaded - Last download: Today, 6:21am)

Similar threads