SE050 Commercial middleware

[psvz]

I would like to start selling my solution using SE050 on a custom PCB integrated with IoT contraption.

I am using middleware downloaded as se05x_mw_v04.05.01.zip

1. Does license permit it (I do have the license but I can't figure out the meaning of pages of badly connected words)?

2. Compilation produces A LOT of deprecation warnings. Are we sure that code is maintained at all?

3. Python code is broken. You can't seriously expect to fix versions in your requirements.txt. And could you please explain this output:

root@edge:~/simw-top/pycli/src# python3 setup.py develop
/usr/local/lib/python3.11/dist-packages/setuptools/_distutils/dist.py:275: UserWarning: Unknown distribution option: 'console'
warnings.warn(msg)
running develop
running egg_info
file ssscli.py (for module ssscli) not found
writing manifest file 'ssscli.egg-info/SOURCES.txt'
running build_ext

[psvz]

Hi @Kan_Li 

Understood re python tooling.

The former question got confused I think. There should be ccmake command - I just do automated installs, so I need to change that compile option from openssl 1.1.1 to 3.0. As you showed I can do it in interactive screen, but i' like to change it from a script. I'm new to cmake in general.

[Kan_Li · Accepted solution]

Hi @psvz ,

Yes, it is possible to do it via the command line, for your case, please use the following commands.

cmake -DPTMW_OpenSSL=3_0 .
cmake --build .

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.
-------------------------------------------------------------------------------

[Kan_Li]

Hi @psvz ,

It is ok to use SE050 & MW on a custom PCB, so please just continue.  I am wondering the tool you use to compile the MW, would you please provide more details on it? such as the log? 

For your CLI tool installation issue , not sure which platform your are using, but for raspberry Pi, you have to install some python packages previously. Please kindly refer to the following for details.

Kan_Li_0-1734923943010.png

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.
-------------------------------------------------------------------------------

[psvz]

Hi @Kan_Li 

I do it on Raspberry Pi 5 and I follow all the procedures, so it is all done the way you describe, and compiled C libraries do work, I am only saying the compilation produces a lot of deprecation warnings, so your code isn't properly maintained, yet working somehow.

Re Python. You can't mix up apt and pip, and virtual environments aren't the answer because I want it all system-wide. Accordingly, all your requirements.txt are installed through apt-get. Apart from func-timeout, which is not available through apt-get, so I installed it into local folder (../simw-top/pycli) with pip. And that's not anything I need help with. What I say is that your key piece of software ssscli.py is missing in se05x_mw_v04.05.01.zip. So, the python part of your middleware is maintained so badly that it doesn't work

[Kan_Li]

Hi @psvz ,

May I have the version of Raspberry OS running on your Raspberry Pi 5? I will try to reproduce your issue here.

Thanks for your patience!

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.
-------------------------------------------------------------------------------

[psvz]

Hi @Kan_Li 

Yes, of course. I use very standard set-up with Raspberry Pi Imager App flashing memory card with Raspberry Pi OS Lite (64-bit) Released 2024-11-19, which is a port of Debian Bookworm. From the Pi itself:

# uname -a
Linux edge 6.6.51+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.51-1+rpt3 (2024-10-08) aarch64 GNU/Linux

[Kan_Li]

Hi @psvz ,

For the compilation issue, I found the Pi OS has openssl ver 3.0.15 preintalled, so you have to configure the cmake option before building the MW. you may run "ccmake ." to do that.

Kan_Li_0-1735287335416.png

The default value is still 1_1_1 here, so you will have warning during compilation. 

I am testing on Raspberry Pi 4 B+ instead, but the OS version is the same.

Kan_Li_1-1735287475803.png

Please kindly let me know if the problem is still there , and I will continue to investigate the ssscli installation issue.

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.
-------------------------------------------------------------------------------

[psvz]

Hi @Kan_Li 

Thanks for this. Is there a way to change openssl version on command line to make it non-interactive?

Also, what about the missing file in "/simw-top/pycli/src# python3 setup.py develop"?

[Kan_Li]

Hi @psvz ,

As far as I know, no openssl command can be used to switch the version, but it is ok to build it from source and install in a different folder, such as /usr/local/ssl11.

For the SSSCLI tool installation issue, I just confirmed with the expert that it is a known issue indeed and will be fixed in the next release which should be available in 2025Q1.

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.
-------------------------------------------------------------------------------