With a support entitlement you can also get direct access to our team of highly-qualified Arm experts 24-hours a day
Open a support case
µVision V126.96.36.199Copyright (C) 2018 ARM Ltd and ARM Germany GmbH. All rights reserved.
Tool Version Numbers:Toolchain: MDK-ARM Professional Version: 188.8.131.52Toolchain Path: C:\Keil_v525\ARM\ARMCLANG\BinC Compiler: ArmClang.exe V6.9Assembler: Armasm.exe V6.9Linker/Locator: ArmLink.exe V6.9Library Manager: ArmAr.exe V6.9Hex Converter: FromElf.exe V6.9CPU DLL: SARMCM3.DLL V184.108.40.206Dialog DLL: DCM.DLL V220.127.116.11Target DLL: ULPL2CM3.dll V0.4.7.0Dialog DLL: TCM.DLL V18.104.22.168
The debugger is an arm ULINK plus.
The event recorder is enabled for 'EventRecordAll', the Event Recorder window only shows single 'Init Event' events.The RTX RTOS window shows the 'E306' line.The Command Window repeats the 'E306' line roughly once per second.The source code editor windows takes around one second to move the line highlight to a different line when clicking with the mouse.
All of this combined makes the Event Recorder unusable.
Has anyone experienced this?
Does anyone know of a workaround?
I tried to log a support case but for the last two days I just get (with a promise to resolve the issue):
'We're sorry, but something went wrong. Error ID # [c6ddd09a-144c-4375-9f19-8c8112c621f2]'.
we are investigating this issue right now. Currently, there's no known work around available. I will keep you updated.
is there any plan to solve this issue?
It has been a few months that I'm stuck without a debugger for my RTOS2 application.
I'm not using the Event Recorder, I get the error when just a few threads are initialized.