embedded-debug.flash not working (ERROR: Sequence 'DebugPortSetup' failed) (RDDI-ERROR 13)

[kubichris]

Type: Bug Report

Describe the bug

• VS Code Version: 1.77.3 (user setup)
  Electron: 19.1.11
  Chromium: 102.0.5005.196
  Node.js: 16.14.2
  V8: 10.2.154.26-electron.0
  OS: Win11, Windows_NT x64 10.0.22621
• Extension Version: 0.9.0
• Target Device: J-Link, CMSIS-DAP, ST-LINK progrmmers

task.json:

{
            "label": "embedded-debug.flash: Flash Device",
            "type": "embedded-debug.flash",
            "serialNumber": "${command:device-manager.getSerialNumber}",
            "program": "${workspaceFolder}/Release/reader.axf",
            "cmsisPack": "${workspaceFolder}/Pack/NXP.PN7xxxxx.0.9.0.pack",
            "processorName": "cm0",
            "deviceName": "PN7462AU-C3-00",
            "problemMatcher": [],
            "group": {
                "kind": "build",
                "isDefault": true
              }
          }

Terminal output with J-Link:

*  Executing task: embedded-debug.flash: Flash Device 

Device Selected: Vxx9xCSE
Parse debug description...
Create system description...
Connect to debug unit (CMSIS-DAP)...
Configure debug unit (SWD @ 2000000 Hz)...
Create device map...
Add Flash Algorithm...
        'PN7xxxxx PF (Jun 15 2016)' (0x00203000 - 0x0022c5ff)
Add Flash Algorithm...
        'PN7xxxxx EE (Jun 15 2016)' (0x00201200 - 0x00201fff)
Connect ('haltOnConnect') to device PN7462AU-C3-00...
ERROR: Cannot connect to USB device, it may be already in use, need a firmware update, or need reconnecting (RDDI-ERROR 13)
ERROR: Sequence 'DebugPortSetup' failed
Disconnect from device...
Disconnect from debug unit...
Debug connection failed
Flash failed

 *  The terminal process terminated with exit code: 1. 

Same effect with other programmers
In extension settings, I modified the Embedded-debug: Logging Verbosity to debug, but it seems to have no effect.

[thegecko]

Hi @kubichris

Thanks for the feedback.

We only support CMSIS-DAP and ST-Link enabled boards, could you tell us what board you are using?

It would also be helpful if you could share the pack you are using, is it one available on https://www.keil.arm.com/?

cc @jreineckearm

[kubichris]

Hi! @jreineckearm

Thanks for fast reply.

I miswrote the adapter, we are using uLink2 CMSIS-DAP mode (intead of J-Link).
But we try with CMSIS-DAP adapter ( stm32F103CBT6 with DAP-Link firmware)
Target MCU: NXP PN7642AU
Pack made by NXP, and I used successfully in uVision V5

Another project with uLink2:

• Target MCU: STM32F030K6
• Pack: Keil.STM32F0xx_DFP.1.0.1.pack

 * Executing task: embedded-debug.flash: Flash Device 

Device Selected: V2xx9xCSE
Parse debug description...
Create system description...
Connect to debug unit (CMSIS-DAP)...
Configure debug unit (SWD @ 10000000 Hz)...
Create device map...
Add Flash Algorithm...
First argument to DataView constructor must be an ArrayBuffer
Flash failed

 *  The terminal process terminated with exit code: 1. 

Same on ST-Link V3

br.

[kubichris]

Update:

I replaced the pack to latest one (Keil.STM32F0xx_DFP.2.1.1.pack), and it works with ST-Link, but with uLink2 have the same error as before:

*  Executing task: embedded-debug.flash: Flash Device 

Device Selected: 0001A0000000
Parse debug description...
Create system description...
Connect to debug unit (CMSIS-DAP)...
Configure debug unit (SWD @ 10000000 Hz)...
Create device map...
Add Flash Algorithm...
       'STM32F0xx 32kB Flash' (0x08000000 - 0x08007fff)
Connect ('haltOnConnect') to device STM32F030K6Tx...
ERROR: Cannot connect to USB device, it may be already in use, need a firmware update, or need reconnecting (RDDI-ERROR 13)
ERROR: Sequence 'DebugPortSetup' failed
Disconnect from device...
Disconnect from debug unit...
Debug connection failed
Flash failed

*  The terminal process terminated with exit code: 1. 

[thegecko]

@kubichris sorry for the late reply, this issue can occur if something else is using your USB device. Can you confirm if its still an issue?

[kubichris]

@thegecko No, the USB is not used by anything else. Only for debugger, and still an issue, when we using uLink2

[thegecko]

OK, one issue may be that ULINK2 is a HID device which we don't currently support. Let us investigate this further.

[vescovd1]

I also get the exact same issue. I am wondering just what the error code indicates.
I almost suspect sometimes the port is still active even though the previous session has ended or something like that.
I too am using the ULINK2 it seems to happen when going back and forth between flash task and debugging. I occasionally can get both to work individually but it does not like when I switch.

[jreineckearm]

@vescovd1 , thanks for adding the comment! Unfortunately, the situation hasn't changed yet for the "Arm Embedded Debugger" Extension: we currently don't support ULINK2 in it which is an HID device.

We do however now also have a preview release of the new "Arm Debugger" Extension which should support ULINK2 as a CMSIS-DAP debugger. Are you by any chance using that one?

The error shown further up in this thread basically says that the debugger cannot connect/claim the selected USB device. This could have multiple reasons, some of them indicated in the error message like an outdated or incorrect FW version which needs update, or another process claiming the USB device. Or, in the case of ULINK2, that the device class (HID) is not supported.

[jreineckearm]

@vescovd1 , could you please also share the relevant parts of your launch.json and task.json files?

[ssrb]

Same issue with Muselab Wireless CMSIS-DAP/DAPLink

It works with uvision but not with the debug extension:

"tasks": [
		{
			"type": "embedded-debug.flash",
			"serialNumber": "${command:device-manager.getSerialNumber}",
			"program": "${command:embedded-debug.getApplicationFile}",
			"cmsisPack": "${command:device-manager.getDevicePack}",
			"problemMatcher": [],
			"connectMode": "preReset",
			"resetMode": "hardware",
			"resetAfterConnect": true,
			"label": "embedded-debug.flash: Flash Device"
		}
	]

Device Selected: 0001A0000002
Parse debug description...
Create system description...
Connect to debug unit (CMSIS-DAP)...
Configure debug unit (SWD @ 10000000 Hz)...
Create device map...
Add Flash Algorithm...
        'STM32L4Rx 2MB Dual Bank Flash' (0x08000000 - 0x081fffff)
Connect ('preReset') to device STM32L4R5QIIx...
Pre-connect hardware reset...
ERROR: Cannot connect to USB device, it may be already in use, need a firmware update, or need reconnecting (RDDI-ERROR 13)
DSQ ERROR: DAP access error
ERROR: Sequence 'ResetHardware' failed
Disconnect from device...
Disconnect from debug unit...
Debug connection failed
Flash failed

Because of that I still need to use uvision.

[saurlax]

I am a newcomer to embedded systems and seem to have encountered the same problem.

I work on STM32F103C8T6, using an unknown CMSIS-DAP (maybe called DAPmini)

Pack: Keil::STM32F1xx DFP@2.4.1
Device: dapmini
Manufacturer: CMSIS-DAP by ARM
Product: CMSIS-DAP
Serial: 303030314130303030303030
VendorID: 0x483
ProductID: 0x572a

{
    "version": "2.0.0",
    "tasks": [
        {
            "label": "CMSIS Build",
            "type": "cmsis-csolution.build",
            "solution": "${command:cmsis-csolution.getSolutionPath}",
            "buildType": "${command:cmsis-csolution.getBuildType}",
            "targetType": "${command:cmsis-csolution.getTargetType}",
            "problemMatcher": [],
            "group": {
                "kind": "build",
                "isDefault": true
            }
        },
        {
            "label": "Flash Device",
            "type": "embedded-debug.flash",
            "program": "${command:embedded-debug.getApplicationFile}",
            "serialNumber": "${command:device-manager.getSerialNumber}",
            "cmsisPack": "${command:device-manager.getDevicePack}",
            "problemMatcher": [],
            "dependsOn": "CMSIS Build"
        }
    ]
}

Device Selected: 303030314130303030303030
Parse debug description...
Create system description...
Connect to debug unit (CMSIS-DAP)...
Configure debug unit (SWD @ 10000000 Hz)...
Create device map...
Add Flash Algorithm...
        'STM32F10x Med-density Flash' (0x08000000 - 0x0801ffff)
Connect ('haltOnConnect') to device STM32F103C8...
ERROR: Cannot connect to USB device, it may be already in use, need a firmware update, or need reconnecting (RDDI-ERROR 13)
ERROR: Sequence 'DebugPortSetup' failed
Disconnect from device...
Disconnect from debug unit...
Debug connection failed
Flash failed

I really want to use Keil Studio. Should I switch to ST-LINK currently?

[saurlax]

Since buying an ST-LINK v2 and trying it out, I have successfully flashed the program into my stm32 🎉. It seems that currently I need to use ST-LINK instead of CMSIS-DAP.

[thegecko]

@saurlax I'm glad you now have this working. TBH, I've never used CMSIS-DAP with an ST device, so not sure if your original approach should have worked.

@ssrb I'm not aware of that debug probe, if it supports daplink (and you only need flashing) then the embedded-debug.daplink-flash task may work better?

@kubichris @vescovd1 We don't support ulink2 in the embedded debugger so we are intrigued that you got this to work at all. Could you share your launch config?
As @jreineckearm mentions, we have a preview out now of the arm debugger which does support this debug probe.

[kubichris]

Sorry for late answer. Now, we in another project, but same results with ulink2 as a CMSIS-DAP device: [image: 338cb406-60d5-4aa3-8cce-100b1a1869c0.png] So, the ulink firmwared as CMSIS-DAP adapter. Configuration: { "label": "embedded-debug.flash: Flash Device", "type": "embedded-debug.flash", "serialNumber": "${command:device-manager.getSerialNumber}", "program": "${workspaceFolder}/build/ePaper.bin", "cmsisPack": "${workspaceFolder}/Pack/Keil.STM32U5xx_DFP.2.0.3.pack", "deviceName": "STM32U575AIIx", "problemMatcher": [], "group": { "kind": "build" } } Result (:

Device Selected: V2291CSE Parse debug description... Create system description... Connect to debug unit (CMSIS-DAP)... Configure debug unit (SWD @ 10000000 Hz)... Create device map... Add Flash Algorithm... 'STM32U5xx 2M NSecure Flash' (0x08000000 - 0x081fffff) Add Flash Algorithm... 'STM32U5xx 2M Secure Flash' (0x0c000000 - 0x0c1fffff) Connect ('haltOnConnect') to device STM32U575AIIx... ERROR: Cannot connect to USB device, it may be already in use, need a firmware update, or need reconnecting (RDDI-ERROR 13) ERROR: Sequence 'DebugPortSetup' failed Disconnect from device... Disconnect from debug unit... Debug connection failed Flash failed

Chris. Rob Moran ***@***.***> ezt írta (időpont: 2024. jan. 22., H, 18:18):

…

@saurlax <https://github.com/saurlax> I'm glad you now have this working. TBH, I've never used CMSIS-DAP with an ST device, so not sure if your original approach should have worked. @ssrb <https://github.com/ssrb> I'm not aware of that debug probe, if it supports daplink (and you only need flashing) then the embedded-debug.daplink-flash task may work better? @kubichris <https://github.com/kubichris> @vescovd1 <https://github.com/vescovd1> We don't support ulink2 in the embedded debugger so we are intrigued that you got this to work at all. Could you share your launch config? As @jreineckearm <https://github.com/jreineckearm> mentions, we have a preview out now of the arm debugger which does support this debug probe. — Reply to this email directly, view it on GitHub <#16 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIUL4WPEXRPOYXU7HHS4XI3YP2NMRAVCNFSM6AAAAAAW4YUHIWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBUGQ2TMOJWGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- [image: Untitled.png]*Gondolj az élő környezetre, mielőtt kinyomtatod ezt a levelet.* *P**lease consider the environment before printing this e-mail* Üdvözlettel: *Kübler Krisztián* Mail: ***@***.*** GSM: +36 30 747-65-68 [image: qr-kod]