Loading...
 

STM32MP1 support available in SW4STM32

   With System Workbench for Linux, Embedded Linux on the STM32MP1 family of MPUs from ST was never as simple to build and maintain, even for newcomers in the Linux world.
And, if you install System Workbench for Linux in System Workbench for STM32 you can seamlessly develop and debug asymmetric applications running partly on Linux, partly on the Cortex-M4; you can download a short video showcasing this on the ac6-tools website (registration required).

System Workbench for STM32


Step over C statement is too slow

Steping over some c statement is too slow
this seam related to use of single step until reaching next c statement instead of cmore common set a temp brrakpoint at next c statement

baicaly my c code is
> BoardDevsi.I2cAddr = 0x52;
/* to detect device presence try to read it’s dev id */
status = VL6180x_RdByte(&BoardDevsi, IDENTIFICATION_MODEL_ID, &id);

when i step over that i can see many log in the openocd console

Info : halted: PC: 0x08001e62
Info : halted: PC: 0x08001e66
Info : halted: PC: 0x08001e68
Info : halted: PC: 0x08001e6c
Info : halted: PC: 0x08001e6e
Info : halted: PC: 0x08001e70
Info : halted: PC: 0x08001e72
Info : halted: PC: 0x08001e74

that confirm we steped in all instruction , the di-asm is

766 BoardDevsi.I2cAddr = 0x52;
08001e60: ldr r2, pc, #616  ; (0x80020cc )
08001e62: ldr.w r3, r7, #404  ; 0x194
08001e66: movs r1, #212  ; 0xd4
08001e68: mul.w r3, r1, r3
08001e6c: add r3, r2
08001e6e: adds r3, #208  ; 0xd0
08001e70: movs r2, #82  ; 0x52
08001e72: strb r2, r3, #0
768 status = VL6180x_RdByte(&BoardDevsi, IDENTIFICATION_MODEL_ID, &id);

i don’t t remenber any such behavior with luna/kepler and h/w gdb debug and use of openocd externaly (up to version 0.9) or using over gdb plugin.

Is this linked to eclipse mars ? some configurable sfeature? ac6 openocd plugin?
broken workspace of eclipse install?

My eclipse get install very long time ago and went true several update (is also configure with over arm and openocd plug in)

Dear,

I have the same behavior when I step over, the console shows each assembly line which slows down a lot the debugging.
Did you solve it.

Thanks & regards


nope no solution
a work arround can be to select next line and then use “run to line”
that wil be done as a fastet temp brakepoint + run instead of single steping into all asm until it reach next “c line”
that migth be some “safe way” to step until reaching next valid c line that work even in optimized code
where trying to set a “tmp brake” base on some “next c line ” commonklty fail and won’t brake at all