User`s manual

QDK™

Renesas RX with HEW

state-machine.com/rx

Debug - this configuration is built with full debugging information and minimal optimization. When the

QP framework finds no events to process, the framework busy-idles until there are new events to

process.

Release - this configuration is built with no debugging information and high optimization. Single-

stepping and debugging is effectively impossible due to the lack of debugging information and

optimized code, but the debugger can be used to download and start the executable. When the QP

framework finds no events to process, the framework puts the CPU to sleep until there are new

events to process.

Spy - like the debug variant, this variant is built with full debugging information and minimal

optimization. Additionally, it is build with the QP's Q-SPY trace functionality built in. The on-board

serial port and the Q-Spy host application are used for sending and viewing trace data. Like the

Debug configuration, the QP framework busy-idles until there are new events to process.

Figure 5: Building the QP libraries from the HEW IDE

The DPP-RX-Renesas contains the HEW workspace qp

.hws

and project file qp

_rx600.hwp

located in

the

<qp>\

ports\

rx\...

directory. For example, to build the QP libraries for the RX600 core with the QK

kernel, you launch the HEW IDE and open the workspace

<qpc>\

ports

\rx\qk\renesas\qp.hws

. You

can then batch-build all three configurations of the project qp

_rx600.hwp

, as shown in Figure 5.

The build process should produce the QP libraries in the locations:

<qp>\

ports

\rx\qk\renesas\-

Debug\qp_rx600.lib, <qp>\

ports

\rx\qk\renesas\Release\qp_rx600.lib, and <qp>\

ports

rx\qk\renesas\Spy\qp_rx600.lib

9 of 32