Of course, gdb_agent_console may be launched from the stand-alone Terminal. solutions using hooks and for the major IDEs, Visual Studio and CLion. To launch GDB proxy (aka agent, aka server) there is a Bash Configuration: In order to run a debug session and step into the source code, the debugger needs. So the debugging that I've managed to implement, is only with the eZ-FET probe. My tries to use the MSPDEBUG and CLion Bundled debugger were rather unsuccessful. Configuring the debugging sessiont with a. The new (above Building) setting is Debugger: we use the one form MSP430-GCC toolchain (64 bit). In Clion configure a new Embedded GDBServer Run / Debug configuration: This Run- Configuration- Type supports a Build- Step before the debugging session so you can build and debug with a single SHIFT F9 Keystroke. All scripts may be downloaded from the repo. Please ensure that you have following configuration: Select the MenuItem Run/EditConfigurations. The scripts used are very simple, but such a structure allows easily to add any new probe and the set of commands to be invoked. The scripts used are very simple, but such a structure allows easily to add any new probe and the set of commands to be invoked.Īll scripts may be downloaded from the repo.įile -> Settings -> Build, Execution, Deployment -> Toolchains: we add a new toolchain I'm using out of the box CLion installation on my Apple MacBook, creating new C++ project, selecting proper build configuration, putting breakpoint on first line of hello world application (in other words doing everything necessary to start a debug build) BUT after pressing debug button nothing happens. After setting the configuration to Debug all the breakpoints are hit. Now the Build All compiles the project and Run for eZ-configurations performs the loading of the program on the MCU Flash or FRAM memory. To choose the probe as late as possible, I created such Configurations: I have a new MSP-EXP430FR5969 probe, it is supported by CCS and solves the task of uploading and debugging programs in CCS.īut we have set the task of switching to CLion IDE - and we will switch! The eZ-FET probes are the next generation, as it seems. I may say that not once I used stand-alone MSPDEBUG as a hard-debugging tool - and with a pleasure! As a probe, I use MSP-EXP430FR5739 board re-programmed to eZ430 a long time ago. But well known MSPDEBUG utility supports eZ430 (as rf2500 protocol) and so the simple and not costly launchpads may be used for uploading programs and even for debugging them. Unfortunately, it's not supported by TI CCS running on Linux. The eZ430 protocol is used in cheap probes and is based on an MSP430F1612 and a TUSB3410 pair of chips. Leaving aside the task of their review, I will deal with protocols (or probe families): eZ430 and eZ-FET. Texas Instruments, as well as third companies, propose a lot of debug probes. Now it's time to look at the next part of developing embedded systems: deployment of the program to a target chip and debugging the program. In part 1 I've described the setting of CLion to compile C-programs for msp430 MCUs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |