Error trying to make a TLS connection between server and SE05x with raspberry pi 3

raul22520 · ‎10-20-2023

**Subject:** Issue with EdgeLock Middleware on Raspberry Pi 3 - Seeking Assistance

**Message:**

Hello,

I'm facing a challenging problem while using the EdgeLock middleware on my Raspberry Pi 3, trying to make a TLS client with se05x connected to a TLS server. The issue pertains to the execution of libraries and a specific error that I've encountered during compilation and linking.

Here is the error message I'm encountering:

```
root@raspberrypi:/home/pi/simw-top/demos/linux/tls_client/build# cmake --build .
[ 25%] Building CXX object CMakeFiles/tlsSe050Client.dir/home/pi/simw-top/demos/linux/common/snw_sss.cpp.o
[ 50%] Building CXX object CMakeFiles/tlsSe050Client.dir/home/pi/simw-top/demos/linux/common/snw_util.cpp.o
[ 75%] Building CXX object CMakeFiles/tlsSe050Client.dir/src/tlsSe050Client.cpp.o
/home/pi/simw-top/demos/linux/tls_client/src/tlsSe050Client.cpp: In function 'int main(int, char**)':
/home/pi/simw-top/demos/linux/tls_client/src/tlsSe050Client.cpp:268:27: warning: 'ENGINE* ENGINE_by_id(const char*)' is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations]
268 | if (!(e = ENGINE_by_id(engineId)))
| ~~~~~~~~~~~~^~~~~~~~~~
/usr/include/openssl/engine.h:336:31: note: declared here
336 | OSSL_DEPRECATEDIN_3_0 ENGINE *ENGINE_by_id(const char *id);
| ^~~~~~~~~~~~
/home/pi/simw-top/demos/linux/tls_client/src/tlsSe050Client.cpp:283:20: warning: 'int ENGINE_ctrl(ENGINE*, int, long int, void*, void (*)())' is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations]
283 | ENGINE_ctrl(e, ENGINE_CMD_BASE, logLevel, NULL, NULL);
| ~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/openssl/engine.h:429:27: note: declared here
429 | OSSL_DEPRECATEDIN_3_0 int ENGINE_ctrl(ENGINE *e, int cmd, long i, void *p,
| ^~~~~~~~~~~
/home/pi/simw-top/demos/linux/tls_client/src/tlsSe050Client.cpp:406:16: warning: 'int ENGINE_ctrl(ENGINE*, int, long int, void*, void (*)())' is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations]
406 | ENGINE_ctrl(e, ENGINE_CMD_BASE+2, 0, NULL, NULL);
| ~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/openssl/engine.h:429:27: note: declared here
429 | OSSL_DEPRECATEDIN_3_0 int ENGINE_ctrl(ENGINE *e, int cmd, long i, void *p,
| ^~~~~~~~~~~
/home/pi/simw-top/demos/linux/tls_client/src/tlsSe050Client.cpp:434:16: warning: 'int ENGINE_ctrl(ENGINE*, int, long int, void*, void (*)())' is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations]
434 | ENGINE_ctrl(e, ENGINE_CMD_BASE+1, 0, NULL, NULL);
| ~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/openssl/engine.h:429:27: note: declared here
429 | OSSL_DEPRECATEDIN_3_0 int ENGINE_ctrl(ENGINE *e, int cmd, long i, void *p,
| ^~~~~~~~~~~
[100%] Linking CXX executable tlsSe050Client
/usr/bin/ld: cannot find -l-la7x_utils: No such file or directory
collect2: error: ld returned 1 exit status
gmake[2]: *** [CMakeFiles/tlsSe050Client.dir/build.make:131: tlsSe050Client] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:83: CMakeFiles/tlsSe050Client.dir/all] Error 2
```

I am using the EdgeLock middleware on my Raspberry Pi 3, and this issue is preventing the proper execution of libraries. I would greatly appreciate any insights or guidance on how to resolve this problem.

Thank you in advance for your assistance.

Best regards,
Raul

Kan_Li · ‎10-22-2023

Hi @raul22520 ,

May I have your openssl version on the raspberry pi 3? and also what is the raspbian version ? Buster?

Have a great day,
Kan

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

raul22520 · ‎10-23-2023

OpenSSL 3.0.11
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 12 (bookworm)
Release: 12
Codename: bookworm

Kan_Li · ‎10-24-2023

Hi @raul22520 ,

Thanks for the information! Actually this demo supports openssl 1.1.1l, I think that is why you could not build it from your side, but we are working on evaluating this topic, I will let you know if I have any more info.

Have a great day,
Kan

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

raul22520 · ‎10-24-2023

Hi,

I have installed the raspbian version and openssl that you mentioned (re-building all the EdgeLock middleware from zero), but the error still remains when building the tls_se050Client example:

Openssl version 1.1.1i

root@raspberrypi:/home/pi/simw-top/demos/linux/tls_client/build# cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

Thank you in advance,

R.

Kan_Li · ‎10-24-2023

Hi @raul22520 ,

This issue is due to the demo supports A71CH and SE05x_C only, if you build the MW for other applets such as SE050_E, you have to update the CMakeLists.txt file in "/home/pi/simw-top/demos/linux/tls_client" manually as below:

Hope that helps,

Have a great day,
Kan

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------