[sidprice]

I have tried the Chronometer, but it does not show what I want.

I have set two breakpoints with actions to simply output a message and continue. The Chronometer does not show the time between those two breakpoints. It shows the time between the individual breakpoints. For example BP 1 is hit it shows the time since BP 1 was last hit.

Can Chronometer always show the time since the last event, even when the event is a different one?

[sidprice]

I have checked my project settings, as well as I can, against the demo project and see nothing that looks wrong. When I last worked on this, some months ago, semihosting worked for me. I would really appreciate some help in tracking this down.

The failure mode is different for the regular and the fast semihosting. With the regular an exception is thrown when either puts or printf is called. With fast semihosting the following line in FastSemihosting.cpp causes an exception:

asm volatile(“mov r0, %1; mov r1, %0; bkpt %a2” ::”r”(&s_FastSemihostingState), “r”(SysprogsSemihostingReasonBase + kInitializeFastSemihosting), “i”(AngelSWI)
: “r0”, “r1”, “r2”, “r3”, “ip”, “lr”, “memory”, “cc”);

Again, I understand you can’t debug user project settings, however, I am completely lost as to how to resolve this.

[sidprice]

The exception I am getting is in the call to “puts”, this suggests that the issue is not related to libOpenCM3.

Sid

[sidprice]

Yes, the example code works for both normal semihosting and fast semihosting.

Note that this project uses libOpenCM3 and not HAL. Semihosting has previously worked for the project.

Sid

[sidprice]

More information:

I have made a little progress, now I am getting an exception on line #58/59 of “FastSemihosting.cpp” :

asm volatile(“mov r0, %1; mov r1, %0; bkpt %a2” ::”r”(&s_FastSemihostingState), “r”(SysprogsSemihostingReasonBase + kInitializeFastSemihosting), “i”(AngelSWI)
: “r0”, “r1”, “r2”, “r3”, “ip”, “lr”, “memory”, “cc”);

Received a SIGTRAP: Trace/breakpoint trap occurred

[sidprice]

Thank you so much for the suggestion to examine the “GDB Session” window. The problem was a “.gdbinit” file in the GDB HOME folder. I had been doing other testing and need that file.

 

Now I need to find a way to have those commands for the other project automatically executed.

Great support!

Sid

[sidprice]

Thanks, manual update went without issues,

Sid

[sidprice]

Yes, my pre-build script works well. Here is a screen-shot.

Sid

Attachments:

You must be logged in to view attached files.

[sidprice]

I had to remove the “static” qualifier, strange because GDB is supposed to be able to handle that, thnaks

Sid

[sidprice]

Sorry, now I see them in the VGDB project properties under “Custom build steps”. I was looking in the VS project properties for them, which is where they are for a non-VGDB project.

Sid

[sidprice]

OK, thanks,

Sid

[sidprice]

Very good,thank you for the great support,

Sid

[sidprice]

Embarrassing … thank you :o(

[sidprice]

I created a new project and it also does not show any semihosting output.

https://github.com/sidprice/vgdb_semihosting_test

Sid

[sidprice]

Thank you, I was confused by the tutorial for semihosting and did not know the enable for it was on the Embedded Debug Tweaking TAB. I have that set to enable and the window now appears. However, I am not seeing any messages printed to the window.

I have selected the “Fast Semihosting and Embedded Profiler” framework, is there more I need to do?

Sid

Attachments:

You must be logged in to view attached files.

[Author]

Posts