1.0

Initial version

1.1

Clarification of naming

1.2

List of components and examples

pnio

Profinet Stack

fully supported

ecat

EtherCAT Stack

fully supported

eip

EtherNet/IP Stack

fully supported

http

Web Server

only recommended on targets with > 32kByte RAM available

net

UDP and TCP channels

only recommended on targets with > 32kByte RAM available

ccm

ccm module management

fully supported

plat_init

This function is called upon start of the application. It is required to initialize the required hardware peripherals here:

• SPI

• Timer

• I2C (optional)

• Memory HEAP

plat_spiTransfer

This function needs to transfer the given data (txBuf) with a length of size to the CCM module. The response data needs to be propagated into the rxBuf buffer. Only the amount of data (size) is allowed to write into rxBuf.

This function is called cyclically by the uGOAL framework.

plat_ledSet

This function can be used to set LED states acquired from the CC module, which may be required for some fieldbus protocol implementations.

plat_heapAllocDone

This function is called when dynamic memory allocation is done. It can be used to evaluate the memory utilisation.

plat_getMsTimer

This function needs to return the number of milliseconds from start of the system. It is needed for timed operations and timeouts.

plat_eventRegister

This optiona function registers a callback function for external interrupts used e.g. for EtherCAT DC. It also initializes the interrupts configured in the specific platform.

plat_eventEnable

Enables the configured events.

plat_eventDisable

Disables the configured events.

CONFIG_UGOAL_HEAP_BUFFER

0

By default uGOAL uses malloc for initial memory allocation. It can be forced to use a statically allocated buffer for initial memory allocation, if e.g. the underlying platform does not provide such functionality. In each case, behaviour will be the same. Only initially memory is allocated. During runtime of the application memory is static.

CONFIG_UGOAL_HEAP_BUFFER_ALIGNMENT

0

With this option allocated memory hunks can be forced to a specific alignment. This may be useful for platform specific adoption.

CONFIG_UGOAL_HEAP_BUFFER_SIZE

0

If the static memory buffer is enabled, with this option the size of the buffer needs to be defined.

CONFIG_UGOAL_DATAMAPPER

0

The data mapper provides an abstraction of the cyclic data channel. If enabled, the RPC stack wrappers will map process data to this entity. Thus access to process data is convenient. Without the data mapper process data needs to be accessed within the raw SPI frame. Usage of the data mapper costs some memory.

CONFIG_UGOAL_TIMEOUT_RPC

5000

This is the time (in milliseconds) before a RPC request is considered to be timed out. For debugging purpose this value may be set to 0, so a pause in execution of the application does not lead to communication errors. For production purpose this value is not allowed to be 0.

CONFIG_UGOAL_TIMEOUT_MEDIA

1000

This is the time (in milliseconds) before missing communication on the SPI is considered to be a fault. For debugging purpose this may be set to 0, so a pause in execution of the application does not lead to communication errors. For production purpose this value is not allowed to be 0.

CONFIG_UGOAL_INSTANCE

1

This option enables the optional support for instances of components in UGOAL. The data mapper and HTTP requires and automatically enables this feature. Otherwise it is not required, since it costs some memory.

CONFIG_UGOAL_MAINLOOP_REG

1

This option enables support for registration of cyclic functions during the execution of the application. The data mapper requires and automatically enables this feature. Otherwise it is not required, since it costs some memory.

CONFIG_UGOAL_LOGGING

0

This option enables UART logging.

CONFIG_UGOAL_RPC_RB_SIZE

274

This option configures the size of an entry within the RPC ring buffer. It defines the maximum size of a RPC request. This value is optimized for memory footprint. Some applications may require larger values, if e.g. larger amounts of data are transported via RPC.

CONFIG_UGOAL_RPC_RB_ENTRIES

1

This option configures the length of the ring buffer in chunks of CONFIG_UGOAL_RPC_RB_SIZE.

CONFIG_UGOAL_RPC_HANDLES

2

This option configures the amount of available RPC handles. Each component (e.g. a communication Stack wrapper) requires a handle. One handle is allocated by the base system.