Search:

Home > Online Support > 8 and 16-bit devices > Renesas M16C

Support for M16C C compiler toolset

Frequently Asked Questions

This page contains answers to common questions handled by our support staff, along with some tips and tricks that we have found useful and presented here as questions. This list is under development currently and will be extended with new topics soon.

Please Note: Mitsubishi M16C is now known as Renesas M16C.

Contents

How do I enable the TASKING M16C ROM monitor debugger, in combination with a Mitsubishi 3Diamond evaluationboard?

Select the applicable example project (e.g. 3diamonds-62P_adc) and set as Current Project.

A project file to build the TASKING ROM Monitor for your specific 3diamonds board can be found in the 'c-monitor' directory of the installed product. You can either open this project file directly or open the project space 'C-Monitor.psp'. This will open a project space containing all available ROM monitor projects. Now you can build the ROM monitor using the 'Rebuild' button in the 'Build' toolbar and flash it to your target board using the 'Flash' button in the same toolbar. Once flashed correctly you can go back to this example project.

The 'Build' toolbar also contains a 'Sync' button (right next to the 'flash' button) that can be used to check the ROM monitor on the target board. Pressing this 'Sync' button will popup a dialog that directly triggers the ROM monitor for a response which will be displayed in the dialog. If the response window keeps blank you might try using a different baud rate and/or COM port.

Another useful feature of the 'Sync' dialog is to synchronize all project settings with the ROM monitor. This won't be necessary for selected dedicated example project as it is already configured correctly. But for any new project that needs to run under the ROM monitor you can use the 'Sync' button to set options required for running under the given ROM monitor, like special processor and memory settings.

My program is very slow when using floating point

Switch to single precision floating point by checking the use single precision floating point only checkbox in Project->Project Options->C Compiler->Floating Point. If you don't need floating point exception handling, be sure to uncheck the Floating point trap/exception handling checkbox in Project->Project Options->C Compiler->Floating Point, for an extra speed gain

When compiling the fpsigfpe and fptrap examples using single precision floating point I get linker warning W112: Type conflict for symbol <_fp_install_trap_handler> in except.obj

You can safely ignore this warning. It will occur when using floating point trapping/exception handling in combination with single precision floating point.

CrossView 'Communication Error' by using GLYN and/or Mitsubishi 3Diamond boards.

By default the examples for the GLYN & Mitsubishi 3Diamond board makes use for debugging of Mitsubishi's Rom Monitor version 2;

If version 1 of this monitor is to be used, change the line

ROM_MONITOR_VERSION equ 2 in file vects32.src to ROM_MONITOR_VERSION equ 1.

If version 2 of this monitor is to be used, change the line

ROM_MONITOR_VERSION equ 1 in file vects32.src to ROM_MONITOR_VERSION equ 2.