10 DEBUggEr
Notes
• Writing in units of 16 bits or 32 bits is performed in little endian format. However, when debugging a
program in simulator mode, you can set a specified area to big endian format in a parameter file.
• Even if the entire or a portion of the memory section specified for write is an unused area, no errors are
assumed. Data is rewritten, except in unused areas.
• The data write memory section is aligned to boundary addresses according to the size of data.
(gdb) c17 fw 0x3 0x9 0x0
For example, when a write memory section is specified as shown above, and because start address 0x3 and
end address 0x9 are not located on 32-bit data boundaries, both are aligned to boundary addresses by setting
the 2 low-order bits to 00 (LSB = 0 for 16 bits). The following shows the actually executed command, where
32-bit data addresses 0x0 to 0x8 (byte data addresses 0x0 to 0xb) are rewritten with data 0x00000000.
(gdb) c17 fw 0x0 0x8 0x0
• If the specified address exceeds the 24-bit range, an error is assumed.
• Data parameters are only effective for the 8 low-order bits for c17 fb, 16 low-order bits for c17 fh, and
32 low-order bits for c17 fw, with excessive bits being ignored. For example, when data 0x100 is specified
in c17 fb, it is processed as 0x00.
• If the end address is smaller than the start address, an error is assumed.
• Even when memory contents are modified by this command, the contents displayed in the [Memory] and
[Source] windows are not updated. Therefore, perform the appropriate operation to update display in each
window. Similarly, even when the program area is rewritten, the source displayed in a window remains
unchanged.
10-66
EPSOn
(C COMPilEr PaCkagE fOr S1C17 faMily) (Ver. 1.5.0)
S5U1C17001C ManUal
Need help?
Do you have a question about the S5U1C17001C and is the answer not in the manual?