After updating to 3.7.0, my system no longer works.

[PaulB_1]

Hello, after updating to 3.7.0, my system no longer works. I can't debug and now get an error message. It was still working an hour ago.

[PaulB_1]

ok What helped me was
“deviceCore”: “Cortex-M7,”
unfortunately there are no suggestions, so you don't know what form it needs to be in.

[PaulB_1]

Unfortunately, it still doesn't work smoothly with two NUCLEO BOARDS H7S3L8. I always have to start board 2 first, then board 1, otherwise I keep getting this error message. However, if I start board 2 first, then board 1, it works.

Reading symbols from d:/Projekte/Test/Cube/Board2/Test/Boot/build/test.elf...
Exit.
cube has exited with code 0Ignoring packet error, continuing...
warning: unrecognized item "timeout" in "qSupported" response

[Florent V]

Hi Paul,

Your first error indicates that the device core cannot be found automatically.
The project setup was likely incomplete. Therefore, please execute the command "STM32Cube: Setup STM32Cube project(s)" via the command palette or thanks to the menu in the STM32Cube activity bar (recommended solution):

Alternatively, you can add the "deviceCore" attribute with the value Cortex-M7 in your case.

Concerning the multiple boards connected, you need to specify the serial number using the attribute

"serverSerialNumber": "<the serial number>",

the serial number can be copied in the "STM32Cube Devices and Boards" view here:

Without the serial number attribute, the debug session cannot determine which board is the correct one.

KR,
Flo

[PaulB_1]

Hello Florent, I was able to resolve the issue with the attributes. The serial number is already included for me, otherwise it did not work at all. However, even if the serial number is available, for some reason only the sequence mentioned above works, which is quite annoying, but still better than the old IDE Cube.

Thank you for your support.

[EPoulsen]

Hi there

While developing today my system suddenly stopped being able to start the debugger. I suspect this is due to VSCode updating the extension to 3.7.0. I get the same error as Paul above:

bound doStepConnectToTarget Failed: Remote replied unexpectedly to 'vMustReplyEmpty': timeout

The debug console shows:

Reading symbols from PATH TO elf...

Ignoring packet error, continuing...

warning: unrecognized item "timeout" in "qSupported" response

Ignoring packet error, continuing...

I only have a single STLink connected, and have tested two individual board (one custom, one STM32F411E-DISCO).

Any clues to what could fix this issue?

Thanks!

Best,

Ebbe