At 10:04 AM 8/12/03 +0200, you wrote:

...
>This code works fine. But I have the message "NO XTL port".
>So it's not possible to test interactively.
>That's why I think TESTER BUILD should always be immediately followed by
>TESTER ACTIVATE.

That message is an indication of a procedural error, that you have not
established an XTL connection. Remember that with an AVR you need to do a
new download and DEBUG every time you change your kernel.

There is no reason to immediately follow a task BUILD with an ACTIVATE;
it's much better to do the BUILD with your power-up code and your ACTIVATEs
in the control words.

Cheers,
Elizabeth

==================================================
Elizabeth D. Rather (US & Canada) 800-55-FORTH
FORTH Inc. +1 310-491-3356
5155 W. Rosecrans Ave. #1018 Fax: +1 310-978-9454
Hawthorne, CA 90250
http://www.forth.com

"Forth-based products and Services for real-time
applications since 1973."
==================================================

----------------------------------------------------------------------
swiftx_at_forth.com The SwiftX programming discussion email list
To unsubscribe, send subject "unsubscribe" to swiftx-request_at_forth.com
For list command help, send subject "help" to swiftx-request_at_forth.com
Message archives are located at http://www.forth.com/archive/swiftx
----------------------------------------------------------------------
This list is a forum for SwiftX users. For product support and bug
reports, please send email to support_at_forth.com
----------------------------------------------------------------------
Received on Tue Aug 12 2003 - 10:42:02 PDT