wrote:
>
> I would break the 'H..J' and the 'M' commands up and explicitly
address
> them. There is a possibility that your first command isn't done before
> the second one tries to execute. SCP commands are not necessarily done
> serially. I like to keep commands "atomic" and no more than 8 bytes
> long if possible. This means that I would do the Because you were
> accessing RAM and not object memory you'll go over my 8 byte "comfort
> zone", but it should still work - As long as the C firmware puts
things
> in the same place! I'll contact the developer to make sure this is so.
>
> In short, set the memory in one SCP command, read or write it in
another
> one.
>
> DLC
>
> --
> ------------------------------------------------------
> Dennis Clark ooPIC Tech Support
> www.oopic.com
> ------------------------------------------------------
>
Hi Dennis et. al.,
Thanks for the tip. I'll probably put it into practice. However, in my
simple test the problem seems to be only with the selection of the
correct memory bank in the sub address register. In another sub thread,
I have a working test.
In that test I seem to have no problem what so ever sending a string
like: "0H126J0LM" in one go. Maybe it is because I previously sent the
"U" command which eliminated any return messages until it reached the
"M" command at the end.
I'll probably use your advice to be safe.
Thanks,
Dogulas
[Non-text portions of this message have been removed]
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/oopic/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/oopic/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:oopic-digest@yahoogroups.com
mailto:oopic-fullfeatured@yahoogroups.com
<*> To unsubscribe from this group, send an email to:
oopic-unsubscribe@yahoogroups.com
<*> Your use of Yahoo! Groups is subject to:
No comments:
Post a Comment