Hitachi 109
6.3.2
Break on Instruction Fetch Cycle
1.
When CPU/instruction fetch/read/word is set in the break bus cycle registers (BBRA/BBRB),
the break condition becomes the CPU’s instruction fetch cycle. Whether it then breaks before
or after the execution of the instruction can then be selected with the PCBA/PCBB bits of the
break control register (BRCR) for the appropriate channel.
2.
The instruction fetch cycle always fetches 32 bits (two instructions). Only one bus cycle
occurs, but breaks can be placed on each instruction individually by setting the respective
addresses in the break address registers (BARA, BARB).
3.
An instruction set for a break before execution breaks when it is confirmed that the instruction
has been fetched and will be executed. This means this feature cannot be used on instructions
fetched by overrun (instructions fetched at a branch or during an interrupt transition, but not
to be executed). When this kind of break is set for the delay slot of a delay branch instruction
or an instruction following an interrupt-disabled instruction, such as LDC, the interrupt is
generated prior to execution of the instruction that then first accepts the interrupt.
4.
When the condition stipulates after execution, the instruction set with the break condition is
executed and then the interrupt is generated prior to the execution of the next instruction. As
with pre-execution breaks, this cannot be used with overrun fetch instructions. When this kind
of break is set for a delay branch instruction or an interrupt-disabled instruction, such as LDC,
the interrupt is generated at the instruction that then first accepts the interrupt.
5.
When an instruction fetch cycle is set for channel B, break data register B (BDRB) is ignored.
There is thus no need to set break data for the break of the instruction fetch cycle.
6.3.3
Break on Data Access Cycle
1.
The memory cycles in which CPU data access breaks occur are: memory cycles from
instructions, and stacking and vector reads during exception processing. These breaks cannot
be used in dummy cycles for single reads of synchronous DRAM.
2.
The relationship between the data access cycle address and the comparison condition for
operand size are shown in table 6.3. This means that when address H'00001003 is set without
specifying the size condition, for example, the bus cycle in which the break condition is
satisfied is as follows (where other conditions are met):
Longword access at H'00001000
Word access at H'00001002
Byte access at H'00001003
Summary of Contents for SH7095
Page 1: ...SH7095 Hardware User Manual ...
Page 23: ...12 Hitachi ...
Page 63: ...52 Hitachi ...
Page 77: ...66 Hitachi ...
Page 105: ...94 Hitachi Figure 5 14 Pipeline Operation when Interrupts are Enabled by Changing the SR ...
Page 127: ...116 Hitachi ...
Page 152: ...Hitachi 141 Figure 7 8 Example of 32 Bit Data Width SRAM Connection ...
Page 157: ...146 Hitachi Figure 7 13 Synchronous DRAM 32 bit Device Connection ...
Page 161: ...150 Hitachi Figure 7 15 Basic Burst Read Timing Auto Precharge ...
Page 167: ...156 Hitachi Figure 7 20 Burst Read Timing Bank Active Same Row Address ...
Page 168: ...Hitachi 157 Figure 7 21 Burst Read Timing Bank Active Different Row Addresses ...
Page 169: ...158 Hitachi Figure 7 22 Write Timing No Precharge ...
Page 170: ...Hitachi 159 Figure 7 23 Write Timing Bank Active Same Row Address ...
Page 180: ...Hitachi 169 Figure 7 29 Example of a DRAM Connection 32 Bit Data Width ...
Page 190: ...Hitachi 179 Figure 7 36 Example of Pseudo SRAM Connection 1 M pseudo SRAM ...
Page 191: ...180 Hitachi Figure 7 37 Example of Pseudo SRAM Connection 4 M pseudo SRAM ...
Page 209: ...198 Hitachi Figure 7 50 Master and Partial Share Master Connections ...
Page 231: ...220 Hitachi ...
Page 287: ...276 Hitachi ...
Page 307: ...296 Hitachi Note For a CPU writing H AA55 to FRC Figure 11 2 FRC Access Operation Write ...
Page 308: ...Hitachi 297 Note For an FRC reading from a CPU H AA55 Figure 11 3 FRC Access Operation Read ...
Page 333: ...322 Hitachi ...
Page 370: ...Hitachi 359 Figure 13 12 Sample Flowchart for Receiving Multiprocessor Serial Data ...
Page 371: ...360 Hitachi Figure 13 12 Sample Flowchart for Receiving Multiprocessor Serial Data cont ...
Page 395: ...384 Hitachi ...
Page 402: ...Hitachi 391 Figure 15 6 PLL Synchronization Settling Timing ...
Page 408: ...Hitachi 397 Figure 15 13 Bus Release Timing Slave Mode With PLL1 Off ...
Page 436: ...Hitachi 425 Figure 15 33 Synchronous DRAM Mode Register Write Cycle TRP 1 Cycle ...
Page 437: ...426 Hitachi Figure 15 34 Synchronous DRAM Mode Register Write Cycle TRP 2 Cycles ...
Page 449: ...438 Hitachi Figure 15 46 DRAM CAS Before RAS Refresh Cycle TRP 1 Cycle TRAS 2 Cycles PLL On ...
Page 454: ...Hitachi 443 Figure 15 51 DRAM CAS Before RAS Refresh Cycle TRP 1 Cycle TRAS 2 Cycles PLL Off ...
Page 461: ...450 Hitachi Figure 15 58 Pseudo SRAM Auto Refresh Cycle PLL On TRP 1 Cycle TRAS 2 Cycles ...
Page 462: ...Hitachi 451 Figure 15 59 Pseudo SRAM Self Refresh Cycle PLL On TRP 1 Cycle TRAS 2 Cycles ...
Page 467: ...456 Hitachi Figure 15 64 Pseudo SRAM Auto Refresh Cycle PLL Off TRP 1 Cycle TRAS 2 Cycles ...
Page 468: ...Hitachi 457 Figure 15 65 Pseudo SRAM Self Refresh Cycle PLL Off TRP 1 Cycle TRAS 2 Cycles ...
Page 471: ...460 Hitachi Figure 15 68 Interrupt Vector Fetch Cycle PLL On No Waits ...
Page 472: ...Hitachi 461 Figure 15 69 Interrupt Vector Fetch Cycle PLL Off No Waits ...
Page 473: ...462 Hitachi Figure 15 70 Interrupt Vector Fetch Cycle 1 External Wait Cycle ...
Page 474: ...Hitachi 463 Figure 15 71 Address Monitor Cycle ...
Page 490: ...Hitachi 479 B 2 Register Chart ...