User manual

• Procedure identified by entry point connect_bus_request in the chapi_in communication

context descriptor shall be invoked from the routine identified by setup_bus_requests

entry in chapi_out communication context descriptor.

• All the procedures identified by entry points stored in the create_io_space and

destroy_io_space fields of a chapi_in communication context descriptor shall be invoked

in the same execution context. Therefore the loadable component shall call these

routines only from the routines identified by the start and the stop fields of the chapi_out

communication context descriptor.

• Procedure identified by entry point add_config_option in the chapi_in communication

context descriptor shall be invoked from the loadable component initialization routine

(<COMPONENT_NAME>_INIT). In this case newly added configuration options will be

available in configuration file at any line going after dll parameter specification for the

loadable component.

• All the procedures identified by entry points stored in the read_bus_timeout and

read_bus_abort fields of a chapi_in communication context descriptor shall be called by

loadable component only from the routine identified by the read field of the chapi_out

communication context descriptor. Using this function could require Stromasys

consulting.

• All the procedures identified by entry points stored in the write_bus_timeout and

write_bus_abort fields of a chapi_in communication context descriptor shall be called by

loadable component only from the routine identified by the write field of the chapi_out

communication context descriptor. Using this function could require Stromasys

consulting.

The CHAPI also guarantees that:

• All the procedures identified by entry points stored in read, write, and reset fields of a

chapi_out communication context descriptor are invoked in the execution context

synchronized to the CPU emulator thread.

• All the procedures identified by the fun argument in the procedure calls to put_ast,

put_sst, and put_irq procedures, identified by corresponding fields of a chapi_in

communication context descriptor, are invoked in the execution context synchronized

to the CPU emulator thread.

• All the procedures identified by entry points stored in start and stop fields of a

chapi_out communication context are invoked in the same execution context.

• Procedure identified by the entry point stored in the set_configuration field of a chapi_out

communication context is called each time parameter configuration option of loadable

component is modified in the CHARON configuration file.