2023-12-20 02:29 PM
I have problems with remote debugging of an STM32L432 device from STM cube ide ver 1.9 on arch linux.g
I can connect and debug with cube with the target directly connected.
When i connect to a remote raspberry with the same tarrgeti i get an error: "Could not verify ST device".
In the gdb log in stmcube i get the following:
877,561 &"monitor ReadAPEx 0x0 0xF8\n"
877,566 @"invalid command name \"ReadAPEx\"\n"
877,567 &"Protocol error with Rcmd\n"
877,567 24^error,msg="Protocol error with Rcmd"
it seems ReadAPEx command is unavalible.
Debugging with cli-gdb seem to work, but has no ReadAPEx instruction.
I can connect with an old version of stmcube on windows platform, but this version does not seem to send the ReadAPEx command.
I have tried openocd version 0.12 and pyocd 0.36 on the raspberry and result is the same with both servers.
st-util 1.7 is not working, neither with new or old cube.
Anyone experienced the same thing? I found some thread about mod_cmd_extended.cfg but this files seem to be non-existing on all my stm32 installations.
2024-07-19 08:33 AM
Me too with a different target STM32F103ZCHx
Did you get anywhere?
/Peter
2024-08-12 12:23 AM
Unfortionately not.
I ended up with installing VirtualHere USB driver and thus "moving" the port to the IDE machine.
Anoying, but couldnt find any other solution.