Forum Replies Created
-
Posts
-
No, I don’t have such a tool that would interface between Segger’s telnet port and forward VisualGDB with a filtered stream. Obviously I’m not the only one expecting this :
https://github.com/gnu-mcu-eclipse/eclipse-plugins/issues/311
This project might help, but I have no clue how to interface it with VisualGDB :
Could it be integrated into the “raw terminal” ?
So between the ARM ITM output on the SWO pin and your raw terminal, there is only Segger able to do something about it ?
Not using any software to do the decoding, just writing to ITM and using the appropriate ‘monitor SWO EnableTarget 24000000 0 0x01 0’ command into the VisualGDB properties, additional GDB commands, to enable the tracing from the probe.
I do hack a few DBGMCU, ITM, TPI, DWT registers to get the ITM.port[O] working though, but I squeeze out everything to just keep the SWO output. Now if you tell me I have to decode the frames and filter out things, I’d be glad to have a few hints.
Tried to force tpi.ffcr.enfcont to 0 but it is even worse. But I suspect there is something going on about the formatter but I cannot see what.
Got this, that might explain things:
01 74 01 65 01 73 01 74 01 0a 01 1b 01 5b 01 31 01 3b 01 32 01 48 01 32 01 1b 01 5b 01 31 01 3b 01 31 01 48It’s the following in ITM_SendChar that send the couple ’01 xx’ when ‘ch’ holds ‘xx’ :
ITM->PORT[0U].u8 = (uint8_t)ch;Now looking at possible bad configuration of the trace register.
Thanks, just tested your last build, but still doesn’t work, even if previous text flushed things clean beforehand.
Yup, that’s why I posted the solution and I’m grateful to you for providing a way to select a third party toolchain.
Please keep in mind I am in full ‘freestanding’, ‘nostdlib’, ‘nostartfiles’, ‘nodefaultlibs’, ‘no-builtin’ mode, hence the compiler should find the absolutely right compiler as it cannot make the usual guesses and find a fallback toolchain suitable enough. It has to be the one !
Your ‘arm-eabi’ BSP doesn’t provide anything about HARD FPV4-SP libraries. That’s just it. Using a full featured BSP like the one provided with AC6 or directly from ARM (link provided above) solves the problem.
This BSP works out of the box : https://developer.arm.com/open-source/gnu-toolchain/gnu-rm/downloads (‘gcc-arm-none-eabi-7-2017-q4-major-win32.zip’ ZIP download)
Once unzipped into, say, “c:\GCC\gcc-arm-none-eabi-7-2017-q4-major-win32\”, you just have to locate the GDB exe and let VisualGDB do the rest.
Btw the GDB’s version parsing is broken, it always show “GDB(“, have to edit the ‘toolchain.xml’ file by hand (<GDBVersion>).
Another problem lies in the fact if you change the project’s ‘Property Pages / Configuration Properties / General / General / Output Directory’ to something else than the default “$(SolutionDir)$(Platform)\$(Configuration)\”, well, “you’re gonna have a bad time” trying to debug the project.
Same problem with ‘Property Pages / Configuration Properties / C/C++ / Output/ Object File Path’ into something else than the default “$(IntDir)” (ie. like “$(OutDir)”) doesn’t even compile at all, as if all object files had to be aggregated into one file.
