Platforms, Syscalls, and Objects

As explained in the previous topic, Tibbo BASIC and C are "pure" languages — they only provide the language constructs, but not the input/output facilities.

All input/output facilities are defined in platforms. Each type of a Tibbo programmable device is represented by a platform describing its capabilities — memory capacity, available features, and so on.

The TIDE Project Settings button.You have to select a platform for every Tibbo IDE (TIDE) project you create. This is done in the Project Settings dialog (File > Project Settings).

Each platform provides a set of syscalls and a set of objects.

Syscalls ("system calls") form a well-developed API with convenient calls for string handling, encryption, and other handy functions.

Objects package large chunks of device functionality. Available objects are so sophisticated that many of your programs will end up containing nothing but the "glue code" tying objects together.

Here is a little taste of what's available:

The adc. object icon. adc. object


The beep. object icon beep. object


The bt. object icon. bt. object


The button. object icon. button. object

Main button

The fd. object icon. fd. object

Flash disk

The io. object icon. io. object

Digital I/O

The kp. object icon. kp. object


The lcd. object icon. lcd. object


The net. object icon. net. object


The pat. object icon. pat. object

Status LEDs

The ppp. object icon. ppp. object


The pppoe. object icon. pppoe. object


The romfile. object icon. romfile. object

Fixed data

The rtc. object icon. rtc. object

Real-time clock

The ser. object icon. ser. object

Serial ports

The sock. object icon. sock. object


The ssi. object icon. ssi. object

I²C and SPI

The stor. object icon. stor. object


The sys. object icon. sys. object

System control

The wln. object icon. wln. object


For additional information, see Platforms and Objects.