Alfat Sd/mmc

[eoasap]

serin2 ALFAT_TX,84,bufchar]

there should be a '[' before bufchar, right?

do i need to declare bufchar as a byte ?

Is there a loop for the serin2 alfat_tx,84, [bufchar] ?

How do i use datardy?

I was getting errors using 'read:' also, so changed it to read1:

[Ron Marcus]

serin2 ALFAT_TX,84,bufchar]

there should be a '[' before bufchar, right?

do i need to declare bufchar as a byte ?

Is there a loop for the serin2 alfat_tx,84, [bufchar] ?

How do i use datardy?

I was getting errors using 'read:' also, so changed it to read1:

Sorry, I was doing it from memory. "READ" is a reserved word. My bad. DATARDY is a pin on Alfat. If it is high, then Alfat has data to send. It takes about ten microseconds to change states if it is empty, or transitions high. It is a flag and should be aliased as a bit variable, just as ALFAT_BUSY should.

Ron

[eoasap]

is the rest of it right? because i still can't quite get it.

[Ron Marcus]

It works for me. Any output from Alfat at all?

[eoasap]

what i'm doing is declaring bufchar as a byte, and then loop at the end of

read:
serin2 ALFAT_TX,84,[bufchar]
lcdout bufchar
goto read

like that, i get a bunch of gibberish. yesterday i was getting numbers like 292 (clears screen) 302 (clears screen) 306 (clears screen) .... etc

[Ron Marcus]

what i'm doing is declaring bufchar as a byte, and then loop at the end of

read:
serin2 ALFAT_TX,84,[bufchar]
lcdout bufchar
goto read

like that, i get a bunch of gibberish. yesterday i was getting numbers like 292 (clears screen) 302 (clears screen) 306 (clears screen) .... etc

When I get to my lab, I will send you a snippet of code. bufchar is a byte variable. It can't go over 255, so there must be a couple of variables in there.

[eoasap]

Thanks Ron, i'm sure there's just something minor i'm leaving out (hopefully!) you've already been such a big help! thanks