User manual

110
requests” ”, Using this function could require Stromasys consulting. They are initiated by
the device instance. The CHARON core is defined as a target of these operations.
Particular event specific details are provided in chapters below.
4.30.1 read bus timeout
In order to perform the operation, the initiator invokes a routine identified by the
read_bus_timeout field of the chapi_in descriptor. The procedure is invoked as follows:
const chapi_in * ci = …;
if (ci->read_bus_timeout) {
ci-> read_bus_timeout (ci);
}
4.30.2 read bus abort
In order to perform the operation, the initiator invokes a routine identified by the
read_bus_abort field of the chapi_in descriptor. The procedure is invoked as follows:
const chapi_in * ci = …;
if (ci->read_bus_abort) {
ci-> read_bus_ abort (ci);
}
4.30.3 write bus timeout
In order to perform the operation, the initiator invokes a routine identified by the
write_bus_timeout field of the chapi_in descriptor. The procedure is invoked as follows:
const chapi_in * ci = …;
if (ci->write_bus_timeout) {
ci-> write_bus_timeout (ci);
}
4.30.4 write bus abort
In order to perform the operation, the initiator invokes a routine identified by the
write_bus_abort field of the chapi_in descriptor. The procedure is invoked as follows:
const chapi_in * ci = …;
if (ci->write_bus_abort) {
ci-> write_bus_abort (ci);
}
The examples above show that the CHARON core is not obliged to support the indicated
operations. It also shows why the loadable component instance must retain the chapi_in
descriptor.