API Interfaces

The Proteus API allows the user to develop their own applications running in addition to the Proteus core functions. These user applications are run by the Proteus processor under Chiron's Proteus Operating System. The user application is run in ROM external to the Proteus chip. This approach offers the user a number of benefits:

• The Proteus processor can be used to run user specific applications thereby avoiding the cost of an additional microprocessor

• Users can use their own software development resources, thereby reducing development costs

• The external PROM for user applications makes it simple to provide for different product variants, upgrades, country specific versions etc using the identical Proteus core.

The Proteus API provides the user with the following facilities:

• Upto 4 user programmed tasks that are run under the proteus scheduler
Program address space is allocated for user program object code. The user program is run in PROM external to the Proteus chip
• User memory (RAM) within the Proteus core
• Non-volatile memory within the Proteus core
• An I/O space for user I/O hardware. The user provides external address decoding as required

I/O facilities are provided within the Proteus core, depending on the configuration used, e.g. UART and tone generator. The user program has access to utilities in the core Proteus system

• Memory manager. Blocks of memory of upto 1K bytes can be allocated from and released to the Proteus 128K byte memory pool

• Mail manager. An incoming mailbox is allocated for each user task. The user tasks can exchange mail with each other and with tasks in the core Proteus system

• Timers. 10 user timers are provided. The user can start and stop each timer and control the timeout period. On expiry each timer causes a unique message to be sent to a user defined task

Two hardware pins are assigned for interrupts generated by user i/o hardware. Each has a separate vector into the user program area, Telephone-like call control interface into the Proteus core for voice call control. Communication is via the mail manager, with the following information exchanged

• On Hook
• Off Hook
• Keypress (0-9,*,#)
• Supplementary Service Request
• Incoming call
• Call waiting
• Calling number
• Called number
• Connected number
• Progress indicators:
• Dialtone
• Connected
• Busy N/U
• Disconnected

Hayes modem-like call control interface into the Proteus core for data call control. Communication is via the mail manager, with the following information exchanged:

• Hayes Commands
• On-line data
• Control signals:
• DTR
• RTS Hayes Result Codes
• On-line data
• Control signals:
• DCD
• CTS

Error diagnostic information within the Proteus core utilities. e.g. memory pool violation, undefined mailbox etc

Back to top