11.07.2015 Views

section 7 - Index of

section 7 - Index of

section 7 - Index of

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Note that the "ap" term in Table A-a and Table A-9 for the P memory move representsthe wait states spent when accessing the program memory during DATA read or writeoperations and does not refer to instruction fetches.Table A-10 Bit Manipulation Timing Summary (see Note 2)Bit Manipulation Operation+mvbCyclesCommentsBxxx Peripheral 2 * aio See Note 1Bxxx X Memory ea + (2 * ax) See Note 1Bxxx Y Memory ea+ (2 * ay) See Note 1Bxxx Register Direct 0 See Note 1BTST PeripheralBTST X MemoryBTST Y Memoryaioea+ axea+ ayNote 1: Bxxx = BCHG, BCLR, or BSET.Note 2: If assumliion 4 is not applicable, then to each one-word instruction timing,a"+ ap" term should be added, and to each two-word instruction, a"+ (2 * ap)"term should be added to account for the program memory wait states spent t<strong>of</strong>etch an instruction word to fill the pipeline.Table A-11 Jump Instruction Timing SummaryJump Instruction OperationJbit Register DirectJbit PeripheralJbitXMemoryJbitYMemory+JxCycles2 * apaio + (2 * ap)ea+ ax+ (2 * ap)ea+ ay+ (2 * ap)Jxxxea + (2 * ap)Note 1: Jbit = JCLR, JSCLR, JSET, and JSSETNote 2: Jxxx = Jcc, JMP, JScc, and JSRCommentsSee Note 1See Note 1See Note 1See Note 1See Note 2All one-word jump instructions execute TWO program memory fetches to refill the pipeline,which is represented by the "+(2 * ap)" term.All two-word jumps execute THREE program memory fetches to refill the pipeline, butone <strong>of</strong> those fetches is sequential (the instruction word located at the jump instruction2nd word address+ 1), so it is not counted as per assumption 4. If the jump instructionwas fetched from a program memory segment with wait states, another "ap" should beadded to account for that third fetch.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!