[Itamare]

Thank you. Code now compiled and runs but the ‘Live Profiling’ is empty –

Tried to mark both instrument: all function/only the function selected below with only few functions checked.

 

 

Attachments:

You must be logged in to view attached files.

[Itamare]

Problem also exists when i open new project with just led blink.

Is it possible that this is related to the changes i made in the OpenOCD files?

[Itamare]

Yes. i am trying to operate the instrumentation-based profiler base on this tutorial –

https://visualgdb.com/tutorials/profiler/embedded/instrumentation/

I have the (#include <SysprogsProfiler.h>) and (InitializeSamplingProfiler()).

 

Problem still exists.

[Itamare]

Tried the profiler, another error:

Cannot find hook function (SysprogsInstrumentingProfilerHook) inside the ELF file.

 

followed this tutorial: https://visualgdb.com/tutorials/profiler/embedded/sampling/

 

 

[Itamare]

Got it.

Changed @SAMPLING_PROFILER_TIMER_INSTANCE

 

Thanks.

[Itamare]

Great. It works!

 

Thank you.

Sorry for too many questions, now when trying to analyze the code using VisualGDB, i got

‘multiple definition of TIM2_IRQHandler’, as i am using the timer for other purpose on my board.

Is it possible to tell the analyzer to use other timers which are not TIM1, TIM2, TIM6 and TIM11?

 

Appreciate your help.

[Itamare]

Hi.

Thanks for the reply, just too many issues with comping the script under VisualGDB, few more issues:

I am trying to compile and debug a custom board with F446RE on it, using the debugger(ST-LINK) from the Nucleo 446RE, this method absolutely works using SystemWorkbench – code runs perfectly.

I regenerate the code using CubeMX under GPDSC toolchain/IDE, import to visualGDB – get an error, openocd does not recognize my custom board with 446RE. Is there anything to do with it?

 

code compiles under Nucleo – STM32F446RET6U but not on custom board – STM32F446RET6

Thanks.

• This reply was modified 7 years, 2 months ago by Itamare.

[Itamare]

Hi.

Thanks for the reply, just too many issues with comping the script under VisualGDB, few more issues:

I am trying to compile and debug a custom board with F446RE on it, using the debugger(ST-LINK) from the Nucleo 446RE, this method absolutely works using SystemWorkbench – code runs perfectly.

I regenerate the code using CubeMX under GPDSC toolchain/IDE, import to visualGDB – get an error, openocd does not recognize my custom board with 446RE. Is there anything to do with it?

 

 

Thanks.

• This reply was modified 7 years, 2 months ago by Itamare.

[Itamare]

Solved by downgrading to Visual Studio 2015 –

STM32 – Failed to connect to debug stub

 

 

 

[Author]

Posts