Search Results
Search results 1-7 of 7.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
Hi, having used Keil's uVision 4, I was used to call it with command line parameters to provide a set of uvproj-uvopt-axf files, allowing it to setup trace, flash the axf file, set a log file, do code coverage and run until it stops at a specified point : keil.com/support/man/docs/uv4/uv4_debug_commands.htm Basically, the script file would looks like this : Brainfuck Source Code (45 lines)Now using J-Link Commander, is it possible to do something similar in functionalities ? wiki.segger.com/J-Li…
-
Using a STM32L476, but that's not the point, just as I stated in my OP, we already have a toolchain ready. The fact is that switching from an uart based output to an itm based output leads to corruption because there is no swo stream filtering from your side. We always get '\0x01' bytes interlaced with every byte sent into the itm port 0, which is done through 'ITM_SendChar' (see core_cm4.h) that is purposely made to replace the original sendchar(char c) function. Hence, all what I want is to ge…
-
Hi, using Visual Studio 2017 15.8.1 + VisualGDB 5.4.4.2400 + Jtrace Pro 6.34a Configured ITM/SWO output to print into the VisualGDB "raw terminal" through gdb localhost:2332. It works somehow but I get garbage in the output : sysprogs.com/w/forums/topic/an…equences-in-raw-terminal/ According to sysprogs, ITM packets should be filtered. Obviously TrueStudio do that with SWV consoles : blog.atollic.com/cortex-m-debu…sole-using-swv/itm-part-1 Now is there a way to filter the ITM output and redirect…
-
Yeah, the original development took place using ST-Link. I then switched to J-Link/J-Trace (using GNU MCU Eclipse) but no luck. Tried to switch back to ST-Link but converted to J-Link but no luck either. So the problem is not the bridge (connector) Is the problem from the j-Link firmware (option byte, flashing dual bank) ? I will try J-Link Commander asap.
-
Hi, trying to switch from ST-Link to J-Link without much success. A- STM32L476RCTx based custom board B- OpenSTM32 / AC6 GCC based toolchain C- Nucleo-64 L476RG based ST-Link v2.1 debugger D- Using 'STM32 ST-LINK Utility.exe', did a 'Erase Chip'. 0x1FFF7800 = FFEFF8AA 00100755 FFFFFFFF 00000000 0x1FFF7810 = 7FFF0000 8000FFFF FF00FFFF 00FF0000 0x1FFF7820 = FF00FFFF 00FF0000 FFFFFFFF FFFFFFFF Works, slow but works (limited to 4 breakpoints though, if you want to have success with 'step out'/'run t…