I'm taking a Udemy course on using SystemView to debug FreeRTOS programs. Thank you for making a free version of SystemView for educational use! It is an awesome program! I hope one day to be able to order the commercial versions of your software.
I first modified my STM32F446RE-Nucleo board using your ST-Link Reflash Utility. Thank you for that also! It took several tries but once it worked, I was able to examine my project using SystemView. What an awesome tool!
Now I want to continue the course and of course I need to modify and then debug the C code in my project. I am using SW4STM32. The instructor wants us to restore my Nucleo board back to ST-Link in order to make changes and debug using breakpoints. And then refresh it back to J-Link to analyze with SystemView. I hope that rather than switch back and forth between J-Link and ST-Link that I can find a way to flash and debug using SW4STM32 with my Nucleo board flashed as J-Link.
So I found this article on your web site:
SystemWorkbench
My versions of eclipse and sw4stm32 are slightly newer than when you wrote the article and some of the settings are in different places, but I was able to make all the configuration changes shown in your article. However it does not work. Every time I try to debug, Eclipse returns and error: Error while launching command: gdb --version
Do you have any suggestions on how I can fix this?
For the time being I really want to continue using SW4STM32. Would purchasing a J-Link EDU solve the problem? I am afraid the problem is some software incompatibility between SW4STM32 and J-Link. Or possibly a configuration issue. In either case I am afraid the purchasing a J-Link EDU would not solve the problem.
In the event you cannot help me, I do have some other options I'd like to get your opinion on:
Options to prevent having to switch the Nucleo board back and forth between ST-Link and J-Link:
1. Purchase a J-Link EDU. Use it for SystemView. Configure the Nucleo board for ST-Link. Use SW4STM32 to build, flash and debug (set breakpoints, examine memory, etc). I hope I could keep both the Nucleo board ST-Link and the J-Link EDU plugged into my computer and that the various software would automatically use the proper USB connection. Will this work?
2. Configure the Nucleo board for J-Link. Use SEGGER Embedded Studio for development, flashing, and debugging. I am not yet and experienced embedded programmer and I'm a little worried about porting my code from SW4STM32 to Embedded Studio.
3. Configure the Nucleo board for J-Link. Use SW4STM32 for development and building only. Use Ozone for debugging.
Do you have any thoughts on these options?
Thank you for helping me. I am really impressed with your tools. I want to purchase a J-Link EDU so I hope you are able to reassure me that one of these solutions will be easy to implement using it.
Clark Sann
I first modified my STM32F446RE-Nucleo board using your ST-Link Reflash Utility. Thank you for that also! It took several tries but once it worked, I was able to examine my project using SystemView. What an awesome tool!
Now I want to continue the course and of course I need to modify and then debug the C code in my project. I am using SW4STM32. The instructor wants us to restore my Nucleo board back to ST-Link in order to make changes and debug using breakpoints. And then refresh it back to J-Link to analyze with SystemView. I hope that rather than switch back and forth between J-Link and ST-Link that I can find a way to flash and debug using SW4STM32 with my Nucleo board flashed as J-Link.
So I found this article on your web site:
SystemWorkbench
My versions of eclipse and sw4stm32 are slightly newer than when you wrote the article and some of the settings are in different places, but I was able to make all the configuration changes shown in your article. However it does not work. Every time I try to debug, Eclipse returns and error: Error while launching command: gdb --version
Do you have any suggestions on how I can fix this?
For the time being I really want to continue using SW4STM32. Would purchasing a J-Link EDU solve the problem? I am afraid the problem is some software incompatibility between SW4STM32 and J-Link. Or possibly a configuration issue. In either case I am afraid the purchasing a J-Link EDU would not solve the problem.
In the event you cannot help me, I do have some other options I'd like to get your opinion on:
Options to prevent having to switch the Nucleo board back and forth between ST-Link and J-Link:
1. Purchase a J-Link EDU. Use it for SystemView. Configure the Nucleo board for ST-Link. Use SW4STM32 to build, flash and debug (set breakpoints, examine memory, etc). I hope I could keep both the Nucleo board ST-Link and the J-Link EDU plugged into my computer and that the various software would automatically use the proper USB connection. Will this work?
2. Configure the Nucleo board for J-Link. Use SEGGER Embedded Studio for development, flashing, and debugging. I am not yet and experienced embedded programmer and I'm a little worried about porting my code from SW4STM32 to Embedded Studio.
3. Configure the Nucleo board for J-Link. Use SW4STM32 for development and building only. Use Ozone for debugging.
Do you have any thoughts on these options?
Thank you for helping me. I am really impressed with your tools. I want to purchase a J-Link EDU so I hope you are able to reassure me that one of these solutions will be easy to implement using it.
Clark Sann