The politically correct way to specify GPIO pin 0 is by
its proper name of PL_IO_NUM_0_INT0. The INT0 in the
enum name tells us that this pin can also be used as an
interrupt pin. If you’re planning on driving an LED with
GPIO pin 0, you can hop over to the global tab and
enter your choice of these:
#define led0 0
#define led0 PL_IO_NUM_0_INT0
As you can see in Screenshot 1, I chose not to use
the politically correct name in my LED alias. I also chose
to go without the alias in the Screenshot 1 example.
By the way, Tibbo Basic
statements are not case sensitive.
The bottom line is that each
io.invert object function performs
the same task. I used an eight-input Saleae Logic device to
capture the pin 0 waveform you
see in Screenshot 2. The pulses
are 0.121 mS wide.
SCREENSHOT 1. This is as
fast as we can toggle
an EM500EV I/O pin.
SCREENSHOT 2. It doesn't get more
basic than this. The zero parameter
of the io.invert object function
specifies I/O port zero.
We’ve walked around Tibbo
Basic for quite a while now. It’s
time to fly this thing. Screenshot 3
is the first step towards putting
together a coherent networking
application with Tibbo Basic.
As you can see, we’ve
specified out a working
platform (EM500W) and
established a project.
In Screenshot 4, the
Device Explorer has sensed
our EM500EV and will fill in
those transport blanks in
Screenshot 3. The transport
information is used to allow
us to debug and program
the MiniMo module using
an LAN connection. Tibbo
Basic uses sockets to
establish TCP/IP connectivity.
A socket is simply an IP
address that is matched up with a port
address. The combined shots that
make up Screenshot 5 demonstrate
how to add socket support to our
application using Tibbo Basic’s sock
I’ve provided Screenshot 6 to give you an idea of how
the Tibbo Basic environment looks from a PC screen point
of view. As you can see, the socket support code was
SCREENSHOT 4. Never mind the
comment. We haven't uploaded
a TCP/IP application image yet.
The real purpose of this is to find
our EM500EV and attach it to
our new TCP/IP project.
SCREENSHOT 3. Tibbo BASIC requires the
specification of a platform, a transport and
target for each project. The transport and
target address are necessary for debugging
and program loading over an
added to TIDE via the work we performed in Screenshot 5.
The only relevant user code you don’t see in Screenshot 6
is under the global tab:
SERVO 08.2013 55