??? 12/19/06 00:38 Read: times |
#129706 - the reason is Responding to: ???'s previous message |
David , with mov dptr,#base+5 The assembler avaluates this and calculates base+5 but when a variable is involved, that has to be solved at run time by the cpu as Hans explained. Your understanding of the carry bit is correct. In the instruction reference there is a description of the instruction and what flags it changes and how it is changed. For example, nop doesn't change any flags, clr and setb don't change flags UNLESS you are changing the flags themselves like clr C. |
Topic | Author | Date |
newbie: offsetting the dptr | 01/01/70 00:00 | |
additional info | 01/01/70 00:00 | |
do you have external data memory at all? | 01/01/70 00:00 | |
Exteranal or Internal RAM | 01/01/70 00:00 | |
In response to Jan and Neil | 01/01/70 00:00 | |
MOVX @DPTR,A | 01/01/70 00:00 | |
In response to Jon | 01/01/70 00:00 | |
Indexing | 01/01/70 00:00 | |
In response to Hans | 01/01/70 00:00 | |
Indexing | 01/01/70 00:00 | |
In response to Hans | 01/01/70 00:00 | |
the reason is | 01/01/70 00:00 | |
In response to Russell | 01/01/70 00:00 | |
Be careful who you listen to! | 01/01/70 00:00 | |
movx a,@dptr | 01/01/70 00:00 | |
In response to Neil | 01/01/70 00:00 | |
It Adds | 01/01/70 00:00 | |
?????? | 01/01/70 00:00 | |
oopps no | 01/01/70 00:00 | |
error | 01/01/70 00:00 | |
error | 01/01/70 00:00 | |
movx/movc![]() | 01/01/70 00:00 |