Guide to Server Integration and Configuration

Whether you prefer working with the low-level C/C++ API or the high-level Lua Scripting Language API, this documentation covers everything. If you're working on an embedded system with limited memory, you can exclusively utilize the Web Server and the C and/or C++ API. However, throughout the documentation, many examples focus on the Lua API, which is more straightforward than the C API. Even if you decide not to use the LSP plugin, we strongly recommend reading the introductory Lua examples. These examples will introduce you to the Virtual File System (VFS), an essential concept to understand in Barracuda.

Typical Uses of the Barracuda Servers

The Barracuda App Server and the Barracuda Web Server are C source code libraries specifically designed for being embedded into another computer program. The C source code libraries are designed to be linked into and be an integral component of the computer program being designed.

Typical uses of the Barracuda App Server & Barracuda Web Server include:

• Integrate into the firmware in an embedded system; example project: Xedge
• Assemble as a standalone component; example project: Mako Server
• Integrate into a desktop computer program

Keep in mind that the Barracuda App Server is a multi-protocol stack and toolkit that includes a powerful integrated scripting engine and support for a wide range of client/server protocols. This makes it a versatile platform for building custom applications and services.

Porting Barracuda to an Embedded System

Supported environments (pre-ported):
The Server has been ported to many embedded operating systems including: VxWorks, QNX, Zephyr, FreeRTOS+TCP or lwIP, Embedded Linux, INTEGRITY, Windows & Win CE, ThreadX, NuttX, Nucleus RTOS, embOS, RTXC, SMX, MQX, RTOS-32, Mac, and UNIX/POSIX.

Porting:
The Barracuda App/Web Servers can be ported to any RTOS powered embedded device.

Memory:

• Barracuda Web Server: the server requires at a minimum 200K ROM and 30K RAM.
• Barracuda Application Server: the server requires 600K ROM and 500K RAM. The 500K RAM is a suggested minimum. Starting the Xedge, a tool implemented in Lua, and using this tool to load one additional LSP application (a total of two Lua applications running) consumes 150Kb RAM. A 500K RAM minimum enables your LSP application to easily expand in size without running into any memory fragmentation issues. The ROM size can also be made smaller by excluding the optional auxiliary API. The IAR compiler in optimization mode produced a 545K ARM9 binary module when compiling the complete app server and all plugins.

CPU:
The Barracuda App/Web Server runs on several microprocessors including, but not limited to: the X86 family, the PowerPC family, the ColdFire family, MIPS, and the ARM family. The server is designed to run on 32 and 64 bit microprocessors and is not suitable for 8 or 16 bit microprocessors.

Ready-to-Run Reference Builds for the Barracuda App Server

• Mako Server - Designed for high-level operating systems (HLOS) like embedded Linux, it runs as a standalone process.
  • How to use Mako Server
  • How to build Mako Server
• Xedge - Ideal for embedding BAS into firmware or other software applications, integrating BAS as part of a larger system.
  • How to use Xedge
  • How to build Xedge
• Direct Integration – For developers using BAS or BWS without basing the design on the two reference builds depicted below but instead creating their own BAS/BWS startup code. See the OEM Getting Started for details.