Hello Everyone,
My IDE-Version:
µVision V5.25.1.0Copyright (C) 2018 ARM Ltd and ARM Germany GmbH. All rights reserved.
Tool Version Numbers:Toolchain: MDK-ARM Professional Version: 5.25.1.0Toolchain 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 V5.25.1.0Dialog DLL: DCM.DLL V1.17.0.0Target DLL: ULPL2CM3.dll V0.4.7.0Dialog DLL: TCM.DLL V1.34.0.0
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]'.
Hello mjkhtx,
we are investigating this issue right now. Currently, there's no known work around available. I will keep you updated.
Kind regards,
Christopher
Hello,
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.
Best regards,
Paolo
A resolution for this issue is scheduled for the next release of MDK which should arrive in this quarter.
Please name the release you are talking about. Is it 5.26.x.y?
Is 'this quarter' Q3-2018?What is the schedule for release?
Keil v5.28.0 still exhibits the same issue, I cannot debug my application because it is not possible to show threads and what they are pending on.
While we're at 5.34 right now, there's no immediate solution available. This is a debug adapter bandwidth issue as explained in KBA3564.