>
> OK, I'll bite. How do you guys do debugging of ooPIC code? I have put
> together a moderately complex state machine that is not behaving as I
> expect it should. So I need to track events and state transitions. (I
> am not using ooPIC events as they are not working right now in C.1.1+.)
I don't do complex stuff with an OOPic.
Perhaps you can output the state 'number' to a few oDIOs. Maybe
wiggle some oDIOs in the event code (N/A for C.1.1+).
You could send the same kind of stuff out an oSPI or oI2C port. Maybe
write the info to EEPROM and review it later.
Maybe come up with enough oDIOs to drive a logic analyzer.
Or, maybe use a uC that has a full C compiler and build the state
machine in a data structure. One of the downsides to cc5x as a C
compiler for the 16F877 is that it doesn't support function pointers
as array elements. Bummer...
Richard
------------------------------------
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