I posted this on the ST forums and the reply doesn't work, and that's
the end of it - the place gets so many posts, mostly never solved...
Clearly there are multiple configs for this around the place. The file
config.txt, which in my case is found at
has a value in it but it is commented-out, and anyway has no effect.
The default value is 31 but it somehow got changed to 1 when I was
trying different debugger settings (speeds, jtag or sw, etc).
There is only the one config.txt file in the whole \ST directory.
Many thanks for any ideas :) Not a huge deal, but a slight irritation
to lose the debug output during loading.
Currently I am using STLINK V3, which runs OK at 24MHz and fairly
solidly at 8MHz. The ISOL version (an extra board) runs ok at 8MHz. It
was changing from STLINK V2 to STLINK V3 (which *is* a lot faster)
which produced this mysterious change.
In the directory
is a batch file containing this
cmd /K "ST-LINK_gdbserver.exe -c config.txt || echo GDB server exited"
and the above executable, and some other stuff.
However this may be totally unrelated to the Cube IDE logging level.
Reply by Don Y●May 2, 20212021-05-02
On 5/2/2021 4:16 AM, John-Smith wrote:
> Don Y <email@example.com> wrote
>> On 5/1/2021 5:07 PM, Don Y wrote:
>>> On 4/30/2021 10:52 PM, John-Smith wrote:
>>>> This bit
>>>> I posted this on the ST forums and the reply doesn't work, and that's
>>>> the end of it - the place gets so many posts, mostly never solved...
>>>> Clearly there are multiple configs for this around the place. The file
>>>> config.txt, which in my case is found at
>>> Does the log file start out with an indication of how it has been
>> Or invoked?
>> Perhaps you can look back *up* the process tree to see if there are
>> any arguments passed to its invocation (?)
>>> Are there any pathname referenced in the log file?
> In the directory
> is a batch file containing this
> @echo off
> cmd /K "ST-LINK_gdbserver.exe -c config.txt || echo GDB server exited"
> and the above executable, and some other stuff.
> However this may be totally unrelated to the Cube IDE logging level.
Change the name of the file -- temporarily -- and restart the tool.
If the file is actually *doing* something, then you should get a "file
not found" error.
If everything proceeds as normal, then you know it is being started
[process monitor should let you look back up the process tree to see
the actual command line used]