Forum Replies Created
-
Posts
-
Great thanks for the info. The next question was going to be “What is the Hardware tracing for?”
So, to summarize, Software tracing is a cutdown tracing utility which can be useful if you are very smart, otherwise the Segger J-Trace Pro is the way to go but cost $4k or so.
With the trace, now that it is working, how do you view the last 1000 lines of code executed? I see that you can add tracepoint events but a trace is when you stop the code and view previous execution.
For example, I am pretty sure another service is coming in and interrupting the code which is why data is going missing. I am not sure how many services we have running but it would in the hundreds so impossible to find without a trace function.
OK, thanks. It looks like an elf file is always generated by gcc.
I did try to load a smaller project and it seems to work. It asked a question about relocating records which I didn’t get on the main project. I will keep trying. Thanks for the info.
Another update. The issue is still there, and I really need to use the Trace function. I have turned off the bin output file and now the arm GCC compiler generates an elf file. However Visual GDB does not seem to be able to find the file even though it is present in the output folder:
stm32-h7.elf: No such file or directory.
Quick update. I managed to fix the issue which was caused by the command buffer having an extra zero in the array and a length of 1. Resetting the buffer fixes the issue but there is still the question of how this random byte is getting set which is where a trace would be great. I will ask the team if anyone knows how to make an elf file from the arm compiler and come back here to report how it goes with an elf file. Thanks again for the help.
Thanks for the reply. Would hex files also work? There is no easy way I can see for gcc to make an elf file.
