embedded systems developers tools, cross compilers
  Home  |   SwiftX Archive  |   SwiftForth Archive  |

Re: GO for Debug + App

From: Leon Wagner <leon_at_forth.com>
Date: Fri, 19 Apr 2002 11:35:11 -0700

You don't need the [IF] if APP-LOOP is always defined. But if you are moving
things between APP.F and DEBUG.F, this is a handy trick.

> -----Original Message-----
> From: swiftx-bounce_at_forth.com [mailto:swiftx-bounce_at_forth.com]On Behalf
> Of Bulgrien, Dennis
> Sent: Friday, April 19, 2002 11:29 AM
> To: swiftx_at_forth.com
> Subject: [swiftx] Re: GO for Debug + App
>
>
>
> Please tell me why you recommend the [IF]. I'm short of understanding.
> APP-LOOP would always be defined so the [IF] wouldn't branch. During
> development that's what is interactively typed in after TARGET READY; after
> production that's what is supposed to run automatically.
>
> Maybe I don't understand how SwiftX's handshaking partner works, the one
> that runs on the development hardware and talks to SwiftX on the PC. Isn't
> that called DEBUG-LOOP ? I have a directory supplied by Forth Inc. that
> contains my platform minimals: for us its called platform\cpu30\; for other
> folks, its like SwiftX\Src\68K\SBC332\. With cpu30\project.swx a target.bin
> and target.s19 are created for the app.f that contains GO DEBUG-LOOP . I
> think that is what we put on the development board flash to handshake with
> SwiftX.
>
> -----Original Message-----
> From: Leon Wagner [mailto:leon_at_forth.com]
> Sent: Friday, April 19, 2002 12:43
> To: Bulgrien, Dennis; swiftx_at_forth.com
> Subject: RE: [swiftx] GO for Debug + App
>
>
> Consider something like this:
>
> [DEFINED] APP-LOOP [IF]
>
> : GO ( -- ) ?XTL IF DEBUG-LOOP THEN APP-LOOP ;
>
> [ELSE]
>
> : GO ( -- ) DEBUG-LOOP ;
>
> [THEN]
>
>
> > -----Original Message-----
> > From: swiftx-bounce_at_forth.com [mailto:swiftx-bounce_at_forth.com]On Behalf
> > Of Bulgrien, Dennis
> > Sent: Friday, April 19, 2002 8:46 AM
> > To: swiftx_at_forth.com
> > Subject: [swiftx] GO for Debug + App
> >
> >
> >
> > By default--
> >
> > : GO ( -- ) DEBUG-LOOP ;
> >
> > Could the live GO check a flag, ?XTL ( -- flag ) DIPSWITCH @ for instance,
> > and either run the talker debug loop or the app?
> >
> > : GO ( -- ) ?XTL IF DEBUG-LOOP ELSE APP-LOOP THEN ABORT ;
> >
> > ?XTL IF ACK STOP ... is what was done before. If I can use this new GO,
> > then I can replace my platform's small talker target.bin on the board's
> > flash with my app's target.bin and get both my app and the interactive
> > talker (one or the other of course).
> ----------------------------------------------------------------------
> swiftx_at_forth.com The SwiftX programming discussion email list
> To unsubscribe, send subject "unsubscribe swiftx" to listar_at_forth.com
> For help with listar commands, send subject "help" to listar_at_forth.com
> Archives are located at http://www.forth.com/swiftx -- check them out!
> ----------------------------------------------------------------------
> THIS LIST IS NOT FOR BUG REPORTS! Send bug reports to support_at_forth.com.

----------------------------------------------------------------------
swiftx_at_forth.com The SwiftX programming discussion email list
To unsubscribe, send subject "unsubscribe swiftx" to listar_at_forth.com
For help with listar commands, send subject "help" to listar_at_forth.com
Archives are located at http://www.forth.com/swiftx -- check them out!
----------------------------------------------------------------------
THIS LIST IS NOT FOR BUG REPORTS! Send bug reports to support_at_forth.com.
Received on Fri Apr 19 2002 - 11:34:47 PDT

This archive was generated by hypermail 2.2.0 : Wed Jan 07 2009 - 03:04:24 PST