| ??? 05/15/06 12:29 Read: times |
#116213 - Re: >256 byte long table Responding to: ???'s previous message |
If less code space was an issue, then try to reach all functions within a 2kB range (AJMP) and place the AJMP-Table on an address, where the low byte was zero:
mov dph, #high(Table)
mov dpl, a
jmp @a+dptr
org ($ + 0FFh) and 0FF00h
Table:
ajmp fkt0
ajmp fkt1
...
Peter |
| Topic | Author | Date |
| interrupt table copy | 01/01/70 00:00 | |
| optimisation | 01/01/70 00:00 | |
| yes i had that in mind but... | 01/01/70 00:00 | |
| No P2 worries | 01/01/70 00:00 | |
| thanks for making this clear! | 01/01/70 00:00 | |
| single chip solutions | 01/01/70 00:00 | |
| Ofcourse | 01/01/70 00:00 | |
| Why does it need optimising? | 01/01/70 00:00 | |
| Not necessarily! | 01/01/70 00:00 | |
| are you sure this is OK? | 01/01/70 00:00 | |
| THANKS! | 01/01/70 00:00 | |
| >256 byte long table | 01/01/70 00:00 | |
| I'll give it a go... | 01/01/70 00:00 | |
| worked! | 01/01/70 00:00 | |
| Re: >256 byte long table | 01/01/70 00:00 | |
| not quite this issue | 01/01/70 00:00 | |
issue resolved | 01/01/70 00:00 |