Always make an error in the clock setting function

[yueduz]

I'm developing stm32h750. The same code uses stm32cubeide and debugs normally. When using Cortex Debug to debug, he made an error during the clock setting process. The location of the error is not fixed, but they are all in the clock setting function, and occasionally can run normally. I noticed that downloading using Cortex Debug is slower than stm32cubeide. When I use a lower cpu frequency to run it, the chance of error is lower.

[haneefdm]

As an experiment, you can comment out the SVD file in launch.json to see if it improves.

Cortex-Debug does not download the program to the device. that is done by gdb and the gdb-server (link). If JLink used a slow interface clock, then it would be slower. You can check the 'Output' Window and select 'Debug Adapter'. I am sorry, I don't how that translates to your language

[yueduz]

Now I don't use svd files, and reducing the frequency doesn't work anymore.

[yueduz]

I want to change Single run mode for a try, but how do I configure Single run mode in cortex-debug?

[haneefdm]

In launch.json, try "serverArgs" you can pass any command-line argument you want.

In this case, we request the server to exit if we started it. Is that not happening? It doesn't matter what single-run mode is, we use the same policy across all gdb servers. JLink is just one of them.

[yueduz]

I don't quite understand what you mean, I use Google Translate to translate our conversation. I used the "serverArgs" parameter and did not add it to the start command of jlink gdbserver, it seems to be added to the gdb client.

On the other hand, I manually run JLinkGDBServerExe. After a failure, I selected the option of image marking, and he succeeded. How can I add this option to cortex-debug?

[yueduz]

I don't quite understand what you mean, I use Google Translate to translate our conversation. I used the "serverArgs" parameter and did not add it to the start command of jlink gdbserver, it seems to be added to the gdb client.

On the other hand, I manually run JLinkGDBServerExe. After a failure, I selected the option of image marking, and he succeeded. How can I add this option to cortex-debug?

I was wrong, the parameters were passed in, but an error was reported in the clock function

[yueduz]

I found another difference, cortex-debug starts "jlinkGdbServer" Target connection timeout is always 0 ms

[haneefdm]

If you want a timeout, then add "-timeout", "5000" to your "serverArgs".

That is a loooong time btw. I can't help you with your clock function. There are too many things that can be going on and none of them are probably related to Cortex-Debug.

Since there are many command-line options to the Jlink gdb-server ... see Section 4.5 below

https://www.segger.com/downloads/jlink/UM08001

[yueduz]

Now, I added a delay to line 1097, and it runs normally. When I use stm32cbueide for debugging, it runs normally without delay. When using cortex-debug, a delay must be added.

[yueduz]

I'm very sorry that I opened this question again. Because I think I found the real reason. After carefully comparing the output of stm32cubeIDE, I found that commenting out lines 42 and 45 of jlink.ts, I was able to get my board to work normally. I cannot configure launchCommands in the configuration file, so I directly modified the source code. Should launchCommands provide configuration options in the configuration file? I don't know if this modification is compatible with other boards.

[yueduz]

I use the overrideLaunchCommands configuration item, but he pops up an error as shown in the figure

[yueduz]

            "overrideLaunchCommands": [
                "monitor reset",
                "-target-download",
                "-enable-pretty-printing"
            ]

I finally found a way to configure