Debugging with GDB: M32R/D

Next: M68K, Previous: ARM, Up: Embedded Processors [Contents][Index]

#### 21.3.2 Renesas M32R/D and M32R/SDI

`target m32r dev`

  Renesas M32R/D ROM monitor.

`target m32rsdi dev`

  Renesas M32R SDI server, connected via parallel port to the board.

The following GDB commands are specific to the M32R monitor:

`set download-path path`

  Set the default path for finding downloadable SREC files.

`show download-path`

  Show the default path for downloadable SREC files.

`set board-address addr`

  Set the IP address for the M32R-EVA target board.

`show board-address`

  Show the current IP address of the target board.

`set server-address addr`

  Set the IP address for the download server, which is the GDB’s host machine.

`show server-address`

  Display the IP address of the download server.

`upload [file]`

  Upload the specified SREC file via the monitor’s Ethernet upload capability. If no file argument is given, the current executable file is uploaded.

`tload [file]`

  Test the `upload` command.

The following commands are available for M32R/SDI:

`sdireset`

  This command resets the SDI connection.

`sdistatus`

  This command shows the SDI connection status.

`debug_chaos`

  Instructs the remote that M32R/Chaos debugging is to be used.

`use_debug_dma`

  Instructs the remote to use the DEBUG_DMA method of accessing memory.

`use_mon_code`

  Instructs the remote to use the MON_CODE method of accessing memory.

`use_ib_break`

  Instructs the remote to set breakpoints by IB break.

`use_dbt_break`

  Instructs the remote to set breakpoints by DBT.

Next: M68K, Previous: ARM, Up: Embedded Processors [Contents][Index]