Creating a TRACE32 startup script

To work with the TRACE32-ICD, you need to configure it for your specific hardware and OS image. You can automate the configuration by creating a startup script.

You may use the TRACE32 debugger to initialize the target hardware, download the QNX IFS onto the target, and start the image. Or, you may start your target hardware with the newly created image as usual (e.g., by booting from Flash), then attach the debugger to the running image. In either case, the debugger setup is done by a script that runs in the TRACE32 software on the host.

The writing of such a script depends heavily on the actual hardware and your preferred methodology and hence, is not covered here. For hardware setup, refer to the architecture-specific Lauterbach documentation; for configuring the debugger for QNX, refer to the RTOS Debugger for QNX – Stop Mode Lauterbach document (rtos_qnx_stop.pdf) found on the TRACE32 download page. Some sample scripts are found in install_dir/demo/arch/kernel/qnx.

When you've developed the startup script, you can prepare for debugging as follows:
  1. Power up the TRACE32 hardware.
  2. Start the TRACE32 software.
  3. Power up the target hardware.
  4. Run the script.
QNX Neutrino should now be running on the target and the debugger should be attached to it.

Screenshot of TRACE32 Development System with the running message displayed at the bottom

You can now debug your OS image and its applications through the TRACE32 software, as explained in RTOS Debugger for QNX – Stop Mode. The next section explains how to debug through the IDE.