Closed chrissnow closed 3 years ago
@chrissnow Have you identified any changes to STM32L1 family or this target in particular?
cc @ARMmbed/team-st-mcd
@chrissnow thank you for raising this issue.Please take a look at the following comments:
Could you add some more detail to the description? A good description should be at least 25 words.
NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'. This indicates to us that at least all the fields have been considered. Please update the issue header with the missing information, the issue will not be mirrored to our internal defect tracking system or investigated until this has been fully resolved.
@0xc0170 I did look and couldn't see anything obviously of interest in STM32L1 between releases. I suspect it may not be L1 specific, If i have time tomorrow I will try a different target.
Thank you for raising this detailed GitHub issue. I am now notifying our internal issue triagers. Internal Jira reference: https://jira.arm.com/browse/IOTOSM-3508
Hi Issue is known and corrected since #14032
My mistake...
Issue is known and corrected since #14032
Except for STM32L1... I need to update something else... You can remove these lines: https://github.com/ARMmbed/mbed-os/blob/master/targets/targets.json#L3312-L3314
Hi again Could you check #14337 ?
@chrissnow any update?
@0xc0170 Apologies for the delay, I was away on site late last week.
I haven't tested the change above, but the changes in #14337 wont build for me (comments left).
Let's retry with the new master branch ? Thx
@jeromecoutant all good now in master :-)
Description of defect
Debugging the XDOT_L151CC does not seem possible anymore, using a J-Link and SWD program succeeds but it disconnects immediately on connect. 6.5 works fine.
I have had a look at the changes between 6.5 and 6.6 and cant seen anything obvious.
Target(s) affected by this defect ?
XDOT_L151CC
Toolchain(s) (name and version) displaying this defect ?
ARMC6
What version of Mbed-os are you using (tag or sha) ?
mbed-os-6.6.0
What version(s) of tools are you using. List all that apply (E.g. mbed-cli)
uVision or CLI build
How is this defect reproduced ?
attempt to debug blinky 6.6 onwards with a j-link
Could affect other targets and debuggers.