??? 08/16/05 19:30 Read: times |
#99525 - command interpreter Responding to: ???'s previous message |
Hi Peter.
I went back and looked at the original copy I downloaded and its does have the "MOV P0,#0FFh" commands in it. It also has P1,P2 and P3. Regardless, I finally got it to work. I didn't take the time to look through all of your initialization of TCON TMOD and SCON, but I went and got a copy of the same setups from some example programs I got with my eval board. Once I fixed the typos I posted about (I'm using ASEM-51 assembler), I finally got there. I even added my own test command definition and it worked first shot. Don't really understand the nuts and bolts of how/why it worked but it did. I'm curious about getting a parameter with the command next. And having a larger command buffer, the information I may ultimately send could have upwards of 64 bytes. I saw somewhere in somebody elses examples of placing a buffer in the DSEG? Sound right? and they used a full 255 bytes, that'd be nice, but in reality, for my needs, I probably only need 64 bytes X 2, plus 4 X 1 bytes for numbers that will never exceed 255. Thanks for having already created the basics. |
Topic | Author | Date |
command interpreter | 01/01/70 00:00 | |
What do you mean by 'command intepreter' | 01/01/70 00:00 | |
command interpreter | 01/01/70 00:00 | |
Nope | 01/01/70 00:00 | |
my command interpreter: | 01/01/70 00:00 | |
your command interpreter | 01/01/70 00:00 | |
Re: your command interpreter | 01/01/70 00:00 | |
command interpreter | 01/01/70 00:00 | |
SBCMON | 01/01/70 00:00 | |
Re: SBCMON | 01/01/70 00:00 | |
Single-letter commands | 01/01/70 00:00 | |
You Need a debugger | 01/01/70 00:00 | |
the ultimate learning tool is an ICE (eq | 01/01/70 00:00 | |
Yes, i done it | 01/01/70 00:00 | |
commands | 01/01/70 00:00 | |
How to get the parameters![]() | 01/01/70 00:00 |