Hello Kan,
Thank you for your answer.
For test purposes, the Rapsberry Pi 3 with Raspbian was used as a platform with pigpio (bit banged I2C) not to have to setup an i.Mx7 Yocto with the SW package yet.
The OM3710A71CHARD was used hooked to the configured I2C pins.
The default demo examples (A71CH_i2c_native, A71CHlight_i2c_native, a71chConfig_i2c_native) are functional as well as the calls to the config tool with some exceptions like this one (-c parameter possible values do not match the Doxygen documentation with "get pub" & "refpem" commands).
=====================
I actually ran into other issues meanwhile with the software package trying to det up the OpenSSL engine:
(Let me know if I shall instead open another ticket for this):
>> unable to compile the A71CH_LINKED_ENGINE as indicated on the Doxygen documentation (recipe fails)
>> recipe fails regardless of the specified build platform with sm_types.h & ax_api.h apparently not linked properly in the Makefile under the /linux subfolder.

Using the library built with the A71CH_ENGINE parameter instead and linking the openssl .cnf file under /etc/ssl/, the a71CH generated libraty under /usr/lib and setting up export OPENSSL_CONF= /etc/ssl/<a71ch_openssl.cnf> does not appear to work.
When running the ./a71chRandDemo.sh Openssl runs as if no a71ch (no connect attempt) was present and no activity is measured with the logic analyzer on the I2C bus (example from hostLib/embSeEngine/a71chDemo/scripts/):

(Followed axHostSw/doc/a71chDoxy/html/page_imx6ul_setup_openssl_engine.html guidelines)
I guess this has to do with the openssl v1.1.0j being installed while the libdev v1.0+ was used for compilation (the Host SW package does not support openssl V1.1+). I will try to see if a downgrade is feasible.
Thank you for your time and support.