Cannot debug STM32H7

Hi experts,

my company is considering transitioning from uVision to Arm Development Studio.
I'm currently evaluating this using the 30 day trial by recreating our current setup.

I'm now trying to download and debug code on the MCU using the built-in CMSIS-DAP and an ST-LINK.
But when trying to debug, the process just fails without any apparent error after the autodetection. No error is present in the main log.

I originally noticed the behavior with a custom board using an STM32H745IIK6 and an ST-LINK V2 but have since than verified the issue is also present with the same setup and an ST-LINK V3, a second custom board using an STM32H745IIT6 and both ST-LINK V2 and V3 and the STM32H747I-DISCO (STM32H747XI6H) board using the internal ST-LINK V3.

The PCE Log looks okay but includes a warning and an error:

[19/05/21 10:57:12] WARNING - Multi-drop SWD is not supported, a single DAP on the scanchain has been assumed.
[19/05/21 10:57:13] Failed to read registers to identify component: Failed to read 16 bytes from address 0xE00F0FF0 on CSMEMAP_2

When I try "Target Configuration", the autodetect fails with an error

But that isn't helping much either... The PCE is showing the same output as it does when I try to debug.

At leats in this case, the main log includes a callstack:

!ENTRY com.arm.debug.cmsis 4 0 2021-05-19 11:03:42.538
!MESSAGE Failed to automatically detect what devices are present
!STACK 0
com.arm.pce.exceptions.DSDetectException: Failed to automatically detect what devices are present
	at com.arm.debug.cmsis.launch.LaunchDelegate.autodetectWrapper(LaunchDelegate.java:486)
	at com.arm.debug.cmsis.launch.LaunchDelegate.setupConfigFiles(LaunchDelegate.java:401)
	at com.arm.debug.cmsis.launch.CMSISLaunchTab$3.widgetSelected(CMSISLaunchTab.java:240)
	at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:252)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89)
	at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4105)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1037)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3922)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3524)
	at org.eclipse.jface.window.Window.runEventLoop(Window.java:823)
	at org.eclipse.jface.window.Window.open(Window.java:799)
	at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.open(LaunchConfigurationsDialog.java:1240)
	at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationPropertiesDialog.open(LaunchConfigurationPropertiesDialog.java:186)
	at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialog(DebugUITools.java:708)
	at com.arm.debug.launcher.DebugConfigurationLauncher.lambda$0(DebugConfigurationLauncher.java:23)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:40)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3897)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3527)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1160)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1049)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155)
	at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:658)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:557)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:154)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:150)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:401)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:657)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:594)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1447)

What am I doing wrong? At least accoridng to the PCE Log everything relevant is detected and working correctly.

Debugging using the same setup works without issues in Keil's uVision.

Thanks in advance!
Sven

  • Here's an exemplary PCE Log

    Starting debug server
    Waiting for debug server to start accepting connections
    Debug server started successfully
    
    [19/05/21 11:09:29] WARNING - Multi-drop SWD is not supported, a single DAP on the scanchain has been assumed.
    [19/05/21 11:09:29] --- --- ---
    [19/05/21 11:09:29] Enumerating AP devices for DAP at scanchain index 0:
    [19/05/21 11:09:29] Number of AP buses detected: 4
    [19/05/21 11:09:29] AP types:
    [19/05/21 11:09:29] 		AHB-AP
    [19/05/21 11:09:29] 		AHB-AP
    [19/05/21 11:09:29] 		APB-AP
    [19/05/21 11:09:29] 		AHB-AP
    [19/05/21 11:09:29] --- --- ---
    [19/05/21 11:09:29] --- --- ---
    [19/05/21 11:09:29] Looking for ROM tables on AP0 (AHB-AP)
    [19/05/21 11:09:29] AHB-AP ROM table base address detected as 0xE00FE003
    [19/05/21 11:09:29] 
        Reading ROM table for AP index 0, base address = 0xE00FE003
    [19/05/21 11:09:29]         Component ID registers:
    [19/05/21 11:09:29]             CID 0: 0x0d
    [19/05/21 11:09:29]             CID 1: 0x10
    [19/05/21 11:09:29]             CID 2: 0x05
    [19/05/21 11:09:29]             CID 3: 0xb1
    [19/05/21 11:09:29]         ROM table part number = 0x450
    [19/05/21 11:09:29]         ROM table JEP ID = 0x20
    [19/05/21 11:09:29]         ROM table JEP Continuation Code = 0x0
    [19/05/21 11:09:29]         ROM table revision number = 0x0
    [19/05/21 11:09:29]         JEDEC used = True
    [19/05/21 11:09:29]         RevAnd = 0x0
    [19/05/21 11:09:29]         Customer modified = 0x0
    [19/05/21 11:09:29]     Valid ROM table entries are:
    [19/05/21 11:09:29]         0x00001003 (component base address: 0xE00FF000)
    [19/05/21 11:09:29]         0xFFF43003 (component base address: 0xE0041000)
    [19/05/21 11:09:29]         0xFFF45003 (component base address: 0xE0043000)
    [19/05/21 11:09:29]         0x1FF02002 (component base address: 0x00000000 - Entry Present bit not set, no device interrogation will occur.)
    [19/05/21 11:09:29]     Reading peripheral and component ID registers of device at address 0xE00FF000
    [19/05/21 11:09:29]         Component ID registers:
    [19/05/21 11:09:29]             CID 0: 0x0d
    [19/05/21 11:09:29]             CID 1: 0x10
    [19/05/21 11:09:29]             CID 2: 0x05
    [19/05/21 11:09:29]             CID 3: 0xb1
    [19/05/21 11:09:29]         Found a nested ROM table
    [19/05/21 11:09:29]                 Component ID registers:
    [19/05/21 11:09:29]                     CID 0: 0x0d
    [19/05/21 11:09:29]                     CID 1: 0x10
    [19/05/21 11:09:29]                     CID 2: 0x05
    [19/05/21 11:09:29]                     CID 3: 0xb1
    [19/05/21 11:09:29]                 ROM table part number = 0x4C7
    [19/05/21 11:09:29]                 ROM table JEP ID = 0x3B
    [19/05/21 11:09:29]                 ROM table JEP Continuation Code = 0x4
    [19/05/21 11:09:29]                 ROM table revision number = 0x0
    [19/05/21 11:09:29]                 JEDEC used = True
    [19/05/21 11:09:29]                 RevAnd = 0x0
    [19/05/21 11:09:29]                 Customer modified = 0x0
    [19/05/21 11:09:29]             Valid ROM table entries are:
    [19/05/21 11:09:29]                 0xFFF0F003 (component base address: 0xE000E000)
    [19/05/21 11:09:29]                 0xFFF02003 (component base address: 0xE0001000)
    [19/05/21 11:09:29]                 0xFFF03003 (component base address: 0xE0002000)
    [19/05/21 11:09:29]                 0xFFF01003 (component base address: 0xE0000000)
    [19/05/21 11:09:29]                 0xFFF41002 (component base address: 0xE0040000 - Entry Present bit not set, no device interrogation will occur.)
    [19/05/21 11:09:29]                 0xFFF42002 (component base address: 0xE0041000 - Entry Present bit not set, no device interrogation will occur.)
    [19/05/21 11:09:29]             Reading peripheral and component ID registers of device at address 0xE000E000
    [19/05/21 11:09:29]                 Component ID registers:
    [19/05/21 11:09:29]                     CID 0: 0x0d
    [19/05/21 11:09:29]                     CID 1: 0xe0
    [19/05/21 11:09:29]                     CID 2: 0x05
    [19/05/21 11:09:29]                     CID 3: 0xb1
    [19/05/21 11:09:29]             Cortex-M7 found at address 0xE000E000
    [19/05/21 11:09:29]             Reading peripheral and component ID registers of device at address 0xE0001000
    [19/05/21 11:09:29]                 Component ID registers:
    [19/05/21 11:09:29]                     CID 0: 0x0d
    [19/05/21 11:09:29]                     CID 1: 0xe0
    [19/05/21 11:09:29]                     CID 2: 0x05
    [19/05/21 11:09:29]                     CID 3: 0xb1
    [19/05/21 11:09:29]                 Peripheral ID registers:
    [19/05/21 11:09:29]                     PID 4: 0x04
    [19/05/21 11:09:29]                     PID 5: 0x00
    [19/05/21 11:09:29]                     PID 6: 0x00
    [19/05/21 11:09:29]                     PID 7: 0x00
    [19/05/21 11:09:29]                     PID 0: 0x02
    [19/05/21 11:09:29]                     PID 1: 0xb0
    [19/05/21 11:09:29]                     PID 2: 0x0b
    [19/05/21 11:09:29]                     PID 3: 0x00
    [19/05/21 11:09:29]                 Peripheral ID = 0x2, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x0, DEVARCH = 0x0, Revision = 0x0
    [19/05/21 11:09:29]             CSDWT found at address 0xE0001000
    [19/05/21 11:09:29]             Reading peripheral and component ID registers of device at address 0xE0002000
    [19/05/21 11:09:29]                 Component ID registers:
    [19/05/21 11:09:29]                     CID 0: 0x0d
    [19/05/21 11:09:29]                     CID 1: 0xe0
    [19/05/21 11:09:29]                     CID 2: 0x05
    [19/05/21 11:09:29]                     CID 3: 0xb1
    [19/05/21 11:09:29]                 Peripheral ID registers:
    [19/05/21 11:09:29]                     PID 4: 0x04
    [19/05/21 11:09:29]                     PID 5: 0x00
    [19/05/21 11:09:29]                     PID 6: 0x00
    [19/05/21 11:09:29]                     PID 7: 0x00
    [19/05/21 11:09:29]                     PID 0: 0x0e
    [19/05/21 11:09:29]                     PID 1: 0xb0
    [19/05/21 11:09:29]                     PID 2: 0x0b
    [19/05/21 11:09:29]                     PID 3: 0x00
    [19/05/21 11:09:29]                 Peripheral ID = 0xe, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x0, DEVARCH = 0x0, Revision = 0x0
    [19/05/21 11:09:29]             CSFPB found at address 0xE0002000
    [19/05/21 11:09:29]             Reading peripheral and component ID registers of device at address 0xE0000000
    [19/05/21 11:09:29]                 Component ID registers:
    [19/05/21 11:09:29]                     CID 0: 0x0d
    [19/05/21 11:09:29]                     CID 1: 0xe0
    [19/05/21 11:09:29]                     CID 2: 0x05
    [19/05/21 11:09:29]                     CID 3: 0xb1
    [19/05/21 11:09:29]                 Peripheral ID registers:
    [19/05/21 11:09:29]                     PID 4: 0x04
    [19/05/21 11:09:29]                     PID 5: 0x00
    [19/05/21 11:09:29]                     PID 6: 0x00
    [19/05/21 11:09:29]                     PID 7: 0x00
    [19/05/21 11:09:29]                     PID 0: 0x01
    [19/05/21 11:09:29]                     PID 1: 0xb0
    [19/05/21 11:09:29]                     PID 2: 0x0b
    [19/05/21 11:09:29]                     PID 3: 0x00
    [19/05/21 11:09:29]                 Peripheral ID = 0x1, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x0, DEVARCH = 0x0, Revision = 0x0
    [19/05/21 11:09:29]             CSITM found at address 0xE0000000
    [19/05/21 11:09:29]         End of ROM table
    [19/05/21 11:09:29]     Reading peripheral and component ID registers of device at address 0xE0041000
    [19/05/21 11:09:29]         Component ID registers:
    [19/05/21 11:09:29]             CID 0: 0x0d
    [19/05/21 11:09:29]             CID 1: 0x90
    [19/05/21 11:09:29]             CID 2: 0x05
    [19/05/21 11:09:29]             CID 3: 0xb1
    [19/05/21 11:09:29]         Peripheral ID registers:
    [19/05/21 11:09:29]             PID 4: 0x04
    [19/05/21 11:09:29]             PID 5: 0x00
    [19/05/21 11:09:29]             PID 6: 0x00
    [19/05/21 11:09:29]             PID 7: 0x00
    [19/05/21 11:09:29]             PID 0: 0x75
    [19/05/21 11:09:29]             PID 1: 0xb9
    [19/05/21 11:09:29]             PID 2: 0x1b
    [19/05/21 11:09:29]             PID 3: 0x00
    [19/05/21 11:09:29]         Peripheral ID = 0x975, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x13, DEVARCH = 0x4a13, Revision = 0x1
    [19/05/21 11:09:29]     CSETM found at address 0xE0041000
    [19/05/21 11:09:29]     Reading peripheral and component ID registers of device at address 0xE0043000
    [19/05/21 11:09:29]         Component ID registers:
    [19/05/21 11:09:29]             CID 0: 0x0d
    [19/05/21 11:09:29]             CID 1: 0x90
    [19/05/21 11:09:29]             CID 2: 0x05
    [19/05/21 11:09:29]             CID 3: 0xb1
    [19/05/21 11:09:29]         Peripheral ID registers:
    [19/05/21 11:09:29]             PID 4: 0x04
    [19/05/21 11:09:29]             PID 5: 0x00
    [19/05/21 11:09:29]             PID 6: 0x00
    [19/05/21 11:09:29]             PID 7: 0x00
    [19/05/21 11:09:29]             PID 0: 0x06
    [19/05/21 11:09:29]             PID 1: 0xb9
    [19/05/21 11:09:29]             PID 2: 0x4b
    [19/05/21 11:09:29]             PID 3: 0x00
    [19/05/21 11:09:29]         Peripheral ID = 0x906, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x14, DEVARCH = 0x0, Revision = 0x4
    [19/05/21 11:09:29]     CSCTI found at address 0xE0043000
    [19/05/21 11:09:29] End of ROM table
    [19/05/21 11:09:29] --- --- ---
    [19/05/21 11:09:29] Looking for ROM tables on AP1 (AHB-AP)
    [19/05/21 11:09:29] AHB-AP ROM table base address detected as 0x00000002
    [19/05/21 11:09:29] No ROM table is present on this AP
    [19/05/21 11:09:29] --- --- ---
    [19/05/21 11:09:29] Looking for ROM tables on AP2 (APB-AP)
    [19/05/21 11:09:29] APB-AP ROM table base address detected as 0xE00E0003
    [19/05/21 11:09:29] 
        Reading ROM table for AP index 2, base address = 0xE00E0003
    [19/05/21 11:09:29]         Component ID registers:
    [19/05/21 11:09:29]             CID 0: 0x0d
    [19/05/21 11:09:29]             CID 1: 0x10
    [19/05/21 11:09:29]             CID 2: 0x05
    [19/05/21 11:09:29]             CID 3: 0xb1
    [19/05/21 11:09:29]         ROM table part number = 0x450
    [19/05/21 11:09:29]         ROM table JEP ID = 0x20
    [19/05/21 11:09:29]         ROM table JEP Continuation Code = 0x0
    [19/05/21 11:09:29]         ROM table revision number = 0x0
    [19/05/21 11:09:29]         JEDEC used = True
    [19/05/21 11:09:29]         RevAnd = 0x0
    [19/05/21 11:09:29]         Customer modified = 0x0
    [19/05/21 11:09:29]     Valid ROM table entries are:
    [19/05/21 11:09:29]         0x00001002 (component base address: 0xE00E1000 - Entry Present bit not set, no device interrogation will occur.)
    [19/05/21 11:09:29]         0x00002002 (component base address: 0xE00E2000 - Entry Present bit not set, no device interrogation will occur.)
    [19/05/21 11:09:29]         0x00003003 (component base address: 0xE00E3000)
    [19/05/21 11:09:29]         0x00004003 (component base address: 0xE00E4000)
    [19/05/21 11:09:29]         0x00005003 (component base address: 0xE00E5000)
    [19/05/21 11:09:29]         0x00010003 (component base address: 0xE00F0000)
    [19/05/21 11:09:29]     Reading peripheral and component ID registers of device at address 0xE00E3000
    [19/05/21 11:09:29]         Component ID registers:
    [19/05/21 11:09:29]             CID 0: 0x00
    [19/05/21 11:09:29]             CID 1: 0x00
    [19/05/21 11:09:29]             CID 2: 0x00
    [19/05/21 11:09:29]             CID 3: 0x00
    [19/05/21 11:09:29]         Peripheral ID registers:
    [19/05/21 11:09:29]             PID 4: 0x00
    [19/05/21 11:09:29]             PID 5: 0x00
    [19/05/21 11:09:29]             PID 6: 0x00
    [19/05/21 11:09:29]             PID 7: 0x00
    [19/05/21 11:09:29]             PID 0: 0x00
    [19/05/21 11:09:29]             PID 1: 0x00
    [19/05/21 11:09:29]             PID 2: 0x00
    [19/05/21 11:09:29]             PID 3: 0x00
    [19/05/21 11:09:29]         Peripheral ID = 0x0, JEP-106 code, including continuation = 0x0, DEVTYPE = 0x0, DEVARCH = 0x0, Revision = 0x0
    [19/05/21 11:09:29]     Unknown device found at address 0xE00E3000, peripheral ID = 0x0
    [19/05/21 11:09:29]     Reading peripheral and component ID registers of device at address 0xE00E4000
    [19/05/21 11:09:29]         Component ID registers:
    [19/05/21 11:09:29]             CID 0: 0x00
    [19/05/21 11:09:29]             CID 1: 0x00
    [19/05/21 11:09:29]             CID 2: 0x00
    [19/05/21 11:09:29]             CID 3: 0x00
    [19/05/21 11:09:29]         Peripheral ID registers:
    [19/05/21 11:09:29]             PID 4: 0x00
    [19/05/21 11:09:29]             PID 5: 0x00
    [19/05/21 11:09:29]             PID 6: 0x00
    [19/05/21 11:09:29]             PID 7: 0x00
    [19/05/21 11:09:29]             PID 0: 0x00
    [19/05/21 11:09:29]             PID 1: 0x00
    [19/05/21 11:09:29]             PID 2: 0x00
    [19/05/21 11:09:29]             PID 3: 0x00
    [19/05/21 11:09:29]         Peripheral ID = 0x0, JEP-106 code, including continuation = 0x0, DEVTYPE = 0x0, DEVARCH = 0x0, Revision = 0x0
    [19/05/21 11:09:29]     Unknown device found at address 0xE00E4000, peripheral ID = 0x0
    [19/05/21 11:09:29]     Reading peripheral and component ID registers of device at address 0xE00E5000
    [19/05/21 11:09:29]         Component ID registers:
    [19/05/21 11:09:29]             CID 0: 0x0d
    [19/05/21 11:09:29]             CID 1: 0xf0
    [19/05/21 11:09:29]             CID 2: 0x05
    [19/05/21 11:09:29]             CID 3: 0xb1
    [19/05/21 11:09:29]         Peripheral ID registers:
    [19/05/21 11:09:29]             PID 4: 0x04
    [19/05/21 11:09:29]             PID 5: 0x00
    [19/05/21 11:09:29]             PID 6: 0x00
    [19/05/21 11:09:29]             PID 7: 0x00
    [19/05/21 11:09:29]             PID 0: 0x01
    [19/05/21 11:09:29]             PID 1: 0xb1
    [19/05/21 11:09:29]             PID 2: 0x1b
    [19/05/21 11:09:29]             PID 3: 0x00
    [19/05/21 11:09:29]         Peripheral ID = 0x101, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x0, DEVARCH = 0x0, Revision = 0x1
    [19/05/21 11:09:29]     Timestamp Generator found at address 0xE00E5000
    [19/05/21 11:09:29]     Reading peripheral and component ID registers of device at address 0xE00F0000
    [19/05/21 11:09:29] Failed to read registers to identify component: Failed to read 16 bytes from address 0xE00F0FF0 on CSMEMAP_2
    [19/05/21 11:09:29] End of ROM table
    [19/05/21 11:09:29] --- --- ---
    [19/05/21 11:09:29] Looking for ROM tables on AP3 (AHB-AP)
    [19/05/21 11:09:29] AHB-AP ROM table base address detected as 0xE00FF003
    [19/05/21 11:09:29] 
        Reading ROM table for AP index 3, base address = 0xE00FF003
    [19/05/21 11:09:29]         Component ID registers:
    [19/05/21 11:09:29]             CID 0: 0x0d
    [19/05/21 11:09:29]             CID 1: 0x10
    [19/05/21 11:09:29]             CID 2: 0x05
    [19/05/21 11:09:29]             CID 3: 0xb1
    [19/05/21 11:09:29]         ROM table part number = 0x450
    [19/05/21 11:09:29]         ROM table JEP ID = 0x20
    [19/05/21 11:09:29]         ROM table JEP Continuation Code = 0x0
    [19/05/21 11:09:29]         ROM table revision number = 0x0
    [19/05/21 11:09:29]         JEDEC used = True
    [19/05/21 11:09:29]         RevAnd = 0x0
    [19/05/21 11:09:29]         Customer modified = 0x0
    [19/05/21 11:09:29]     Valid ROM table entries are:
    [19/05/21 11:09:29]         0xFFF0F003 (component base address: 0xE000E000)
    [19/05/21 11:09:29]         0xFFF02003 (component base address: 0xE0001000)
    [19/05/21 11:09:29]         0xFFF03003 (component base address: 0xE0002000)
    [19/05/21 11:09:29]         0xFFF01003 (component base address: 0xE0000000)
    [19/05/21 11:09:29]         0xFFF41002 (component base address: 0xE0040000 - Entry Present bit not set, no device interrogation will occur.)
    [19/05/21 11:09:29]         0xFFF42003 (component base address: 0xE0041000)
    [19/05/21 11:09:29]         0xFFF44003 (component base address: 0xE0043000)
    [19/05/21 11:09:29]     Reading peripheral and component ID registers of device at address 0xE000E000
    [19/05/21 11:09:29]         Component ID registers:
    [19/05/21 11:09:29]             CID 0: 0x0d
    [19/05/21 11:09:29]             CID 1: 0xe0
    [19/05/21 11:09:29]             CID 2: 0x05
    [19/05/21 11:09:29]             CID 3: 0xb1
    [19/05/21 11:09:29]     Cortex-M4 found at address 0xE000E000
    [19/05/21 11:09:29]     Reading peripheral and component ID registers of device at address 0xE0001000
    [19/05/21 11:09:29]         Component ID registers:
    [19/05/21 11:09:29]             CID 0: 0x0d
    [19/05/21 11:09:29]             CID 1: 0xe0
    [19/05/21 11:09:29]             CID 2: 0x05
    [19/05/21 11:09:29]             CID 3: 0xb1
    [19/05/21 11:09:29]         Peripheral ID registers:
    [19/05/21 11:09:29]             PID 4: 0x04
    [19/05/21 11:09:29]             PID 5: 0x00
    [19/05/21 11:09:29]             PID 6: 0x00
    [19/05/21 11:09:29]             PID 7: 0x00
    [19/05/21 11:09:29]             PID 0: 0x02
    [19/05/21 11:09:29]             PID 1: 0xb0
    [19/05/21 11:09:29]             PID 2: 0x3b
    [19/05/21 11:09:29]             PID 3: 0x00
    [19/05/21 11:09:29]         Peripheral ID = 0x2, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x0, DEVARCH = 0x0, Revision = 0x3
    [19/05/21 11:09:29]     CSDWT found at address 0xE0001000
    [19/05/21 11:09:29]     Reading peripheral and component ID registers of device at address 0xE0002000
    [19/05/21 11:09:29]         Component ID registers:
    [19/05/21 11:09:29]             CID 0: 0x0d
    [19/05/21 11:09:29]             CID 1: 0xe0
    [19/05/21 11:09:29]             CID 2: 0x05
    [19/05/21 11:09:29]             CID 3: 0xb1
    [19/05/21 11:09:29]         Peripheral ID registers:
    [19/05/21 11:09:29]             PID 4: 0x04
    [19/05/21 11:09:29]             PID 5: 0x00
    [19/05/21 11:09:29]             PID 6: 0x00
    [19/05/21 11:09:29]             PID 7: 0x00
    [19/05/21 11:09:29]             PID 0: 0x03
    [19/05/21 11:09:29]             PID 1: 0xb0
    [19/05/21 11:09:29]             PID 2: 0x2b
    [19/05/21 11:09:29]             PID 3: 0x00
    [19/05/21 11:09:29]         Peripheral ID = 0x3, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x0, DEVARCH = 0x0, Revision = 0x2
    [19/05/21 11:09:29]     CSFPB found at address 0xE0002000
    [19/05/21 11:09:29]     Reading peripheral and component ID registers of device at address 0xE0000000
    [19/05/21 11:09:29]         Component ID registers:
    [19/05/21 11:09:29]             CID 0: 0x0d
    [19/05/21 11:09:29]             CID 1: 0xe0
    [19/05/21 11:09:29]             CID 2: 0x05
    [19/05/21 11:09:29]             CID 3: 0xb1
    [19/05/21 11:09:29]         Peripheral ID registers:
    [19/05/21 11:09:29]             PID 4: 0x04
    [19/05/21 11:09:29]             PID 5: 0x00
    [19/05/21 11:09:29]             PID 6: 0x00
    [19/05/21 11:09:29]             PID 7: 0x00
    [19/05/21 11:09:29]             PID 0: 0x01
    [19/05/21 11:09:29]             PID 1: 0xb0
    [19/05/21 11:09:29]             PID 2: 0x3b
    [19/05/21 11:09:29]             PID 3: 0x00
    [19/05/21 11:09:29]         Peripheral ID = 0x1, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x0, DEVARCH = 0x0, Revision = 0x3
    [19/05/21 11:09:29]     CSITM found at address 0xE0000000
    [19/05/21 11:09:29]     Reading peripheral and component ID registers of device at address 0xE0041000
    [19/05/21 11:09:29]         Component ID registers:
    [19/05/21 11:09:29]             CID 0: 0x0d
    [19/05/21 11:09:29]             CID 1: 0x90
    [19/05/21 11:09:29]             CID 2: 0x05
    [19/05/21 11:09:29]             CID 3: 0xb1
    [19/05/21 11:09:29]         Peripheral ID registers:
    [19/05/21 11:09:29]             PID 4: 0x04
    [19/05/21 11:09:29]             PID 5: 0x00
    [19/05/21 11:09:29]             PID 6: 0x00
    [19/05/21 11:09:29]             PID 7: 0x00
    [19/05/21 11:09:29]             PID 0: 0x25
    [19/05/21 11:09:29]             PID 1: 0xb9
    [19/05/21 11:09:29]             PID 2: 0x0b
    [19/05/21 11:09:29]             PID 3: 0x00
    [19/05/21 11:09:29]         Peripheral ID = 0x925, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x13, DEVARCH = 0x0, Revision = 0x0
    [19/05/21 11:09:29]     CSETM found at address 0xE0041000
    [19/05/21 11:09:29]     Reading peripheral and component ID registers of device at address 0xE0043000
    [19/05/21 11:09:29]         Component ID registers:
    [19/05/21 11:09:29]             CID 0: 0x0d
    [19/05/21 11:09:29]             CID 1: 0x90
    [19/05/21 11:09:29]             CID 2: 0x05
    [19/05/21 11:09:29]             CID 3: 0xb1
    [19/05/21 11:09:29]         Peripheral ID registers:
    [19/05/21 11:09:29]             PID 4: 0x04
    [19/05/21 11:09:29]             PID 5: 0x00
    [19/05/21 11:09:29]             PID 6: 0x00
    [19/05/21 11:09:29]             PID 7: 0x00
    [19/05/21 11:09:29]             PID 0: 0x06
    [19/05/21 11:09:29]             PID 1: 0xb9
    [19/05/21 11:09:29]             PID 2: 0x5b
    [19/05/21 11:09:29]             PID 3: 0x00
    [19/05/21 11:09:29]         Peripheral ID = 0x906, JEP-106 code, including continuation = 0x43b, DEVTYPE = 0x14, DEVARCH = 0x0, Revision = 0x5
    [19/05/21 11:09:29]     CSCTI found at address 0xE0043000
    [19/05/21 11:09:29] End of ROM table
    [19/05/21 11:09:29] --- --- ---
    [19/05/21 11:09:29] --- --- ---
    [19/05/21 11:09:29] --- --- ---
    [19/05/21 11:09:29] Acquiring device info for CSETM_0 (0xE0041000):
    [19/05/21 11:09:29]     Device supports timestamps
    [19/05/21 11:09:29]     Device does not support context IDs
    [19/05/21 11:09:29]     Device supports cycle accurate trace
    [19/05/21 11:09:29]     Device does not support data address trace
    [19/05/21 11:09:29]     Device does not support data value trace
    [19/05/21 11:09:29]     Device does not support trace range
    [19/05/21 11:09:29]     ETM Version: 4.0
    [19/05/21 11:09:29] 
    [19/05/21 11:09:29] --- --- ---
    [19/05/21 11:09:29] --- --- ---
    [19/05/21 11:09:29] --- --- ---
    [19/05/21 11:09:29] Acquiring device info for CSETM_1 (0xE0041000):
    [19/05/21 11:09:29]     Device CSETM_1 (0xE0041000) is locked - unlocking
    [19/05/21 11:09:29]     CSETM_1 (0xE0041000) successfully powered-up
    [19/05/21 11:09:29]     Device supports timestamps
    [19/05/21 11:09:29]     Device does not support context IDs
    [19/05/21 11:09:29]     Device does not support cycle accurate trace
    [19/05/21 11:09:29]     Device does not support data address trace
    [19/05/21 11:09:29]     Device does not support data value trace
    [19/05/21 11:09:29]     Device does not support data only mode
    [19/05/21 11:09:29]     Device does not support trace range
    [19/05/21 11:09:29]     ETM Version: 3.5
    [19/05/21 11:09:29] 
    [19/05/21 11:09:29] --- --- ---
    [19/05/21 11:09:29] Detecting topology ... (may take several seconds)
    [19/05/21 11:09:29] --- --- ---
    [19/05/21 11:09:29] Testing ATB topology:
    [19/05/21 11:09:29]     Device CSITM_1 (0xE0000000) is locked - unlocking
    [19/05/21 11:09:29] --- --- ---
    [19/05/21 11:09:29] Testing core-source topology:
    [19/05/21 11:09:30] --- --- ---
    [19/05/21 11:09:30] Asserting missing topology using existing link information:
    [19/05/21 11:09:30] --- --- ---
    [19/05/21 11:09:30] Testing CTI topology:
    [19/05/21 11:09:30] MASTER = CSETM_1 (0xE0041000)  	SLAVE = CSCTI_1 (0xE0043000)  	Trigger = 6
    [19/05/21 11:09:30] --- --- ---
    [19/05/21 11:09:30] Asserting M-class topology using device base addresses:
    [19/05/21 11:09:30] MASTER = Cortex-M7 (0xE000E000)  	SLAVE = CSETM_0 (0xE0041000)
    [19/05/21 11:09:30] MASTER = Cortex-M4 (0xE000E000)  	SLAVE = CSETM_1 (0xE0041000)
    [19/05/21 11:09:30] --- --- ---
    [19/05/21 11:09:30] Asserting missing topology using existing link information:
    [19/05/21 11:09:30] MASTER = Cortex-M4 (0xE000E000)  	SLAVE = CSCTI_1 (0xE0043000)  	Trigger = 7
    [19/05/21 11:09:30] MASTER = Cortex-M4 (0xE000E000)  	SLAVE = CSETM_1 (0xE0041000)
    [19/05/21 11:09:30] --- --- ---
    Debug server shutdown application
    Debug server shut down attempted
    Done
    

  • Hi Sven

    Thanks for trying out Arm Development Studio!  Sorry to hear that you've hit this problem.

    The warning about Multi-drop SWD isn't the issue here, but the error
    Failed to read registers to identify component: Failed to read 16 bytes from address 0xE00F0FF0 on CSMEMAP_2
    may be the cause of the problem.

    You don't say which type of processor/board you are trying to connect to, but this problem is best investigated as a Support Case with Arm, so that Arm support and engineering teams can properly investigate.

    Please open a Support Case using the "Support > Open a Support Case" option at the top of this page, including more details such as the processor/board you are trying to connect to, and the full failing PCE log.

    Hope this helps,

    Stephen

  • Hi Robert,

    thank you for your quick response! What you describe is exactly what I tried to use.

    I'm currently in homeoffice and don't have access to other debuggers here. I'll make sure to at least try a J-Link soon but don't have access to a DSTREAM-ST. In the meantime, I could properly connect to an STM32F4 and an NRF52840 so this issue seems to be specific to the H7 series of dual-core MCUs (maybe alsothe single core versions but I can not test this).

    Do you have access to a STM32H74x/75x, i.e., a dual-core model to check if it works with the DSTREAM-ST?

    Development Studio gives me two possible debug configurations:

    1. CMSIS C/C++ Application
    2. Generic Arm C/C++ Application

    The second works (altough I would need to provide my own programming algoriithm), the first fails to generate its "platform.sdf" and silently fails (at least that's what my findings show).

    By having a close look at what Development Studio (and expecially the com.arm.debug.cmsis module that is causing the error) is doing different if it works,I have since found a workaround:

    1. Create a *.sdf configuration using the auto detection as accessed by New->Platform Configuration and selecting "Automatic/simple platform detection" and following the steps for your debugger.
    2. Save the configuration to any database.
    3. Copy the resulting *.sdf to: Development Studio Workspace\.metadata\.plugins\com.arm.debug.cmsis\DS-MDK\STM32H7xx_DFP_STM32H745IIKx
      Obviously, replace "STM32H7xx_DFP_STM32H745IIKx" by the name of the chip from the CMSIS package. For me the folder was already created after trying to connect once.

    While this works, it is annoying that the auto detection does not seem to be able to automatically generate this file (when it is obviously supposed to do this and is failing without it).

    I will leave this here for future reference but definitely hope that that this bug can be fixed.

    Best Regards,

    Sven

More questions in this forum
There are no posts to show. This could be because there are no posts in this forum or due to a filter.