#Eclipse script debugger install#

In a similar way I set up a variable to read the ‘reg’ variable of my application and store it into ‘test_val’:Ī one-liner compares the actual value with the expected value. For this I set up a scripting variable ‘test_expected’ and initialize it with a value of 0x40000 (the expected LED port value): To count the number of errors in my test script, I use an error counter: Next, I’m going to step over that line 9: Reg = (GPIO1_GetPortValue(NULL)&GPIO1_LED_R_MASK) /* get raw register value */ Then let’s run the application and hit that breakpoint: I’m using an ‘automatic’ break point (see Software and Hardware Breakpoints) on line 9, column 1: Next I set a breakpoint in my test program.

The first thing is to start the debugger: comparing variables with expected valuesīefore putting everything into a TCL script file, it makes sense to execute one command after each other from the Debugger Shell view.And instead typing in commands, I can save them into a file and execute it with the source command: Then much of the work has been already done.

#Eclipse script debugger install#

The Debugger shell is using TCL as scripting language (see Scripting: The Debugger Shell, Getting started…). First of all, install Eclipse Spring Tools as described in this tutorial: Choosing the IDE for Spring Boot development. Val = LED1_Get() /* LED shall be on, so val should be one */ Val = LED1_Get() /* LED shall be off, so val should be zero */ Reg=(GPIO1_GetPortValue(NULL)&GPIO1_LED_R_MASK) /* get raw register value */ So this is my simple test program ‘Test_LED.c’ for one of the LEDs: Now I want to write a small automated script which tests if the LED is working properly. I’m running my application on the Freedom-KL25Z board which is using the RGB LED on that board. This gives me a powerful way into automation and scripting with the debugger: from basic access to memory, to stepping and controlling the execution up to programming the flash memory. For this I use a tool in CodeWarrior: the Debugger Shellas command line debugger and using TCL as scripting language.

Debugging is something manual, but for testing and automation I want to develop scripts I can run in an automated fashion. The development cycle does not end with debugging.