Are examples supposed to work for MM8108-EKH

General
1

Hi,

I was able to work with example EKH_Demo using STMCubeMX and STMCubeIDE. Using CMSIS pack 1.9 and the development board 8108-EKH05.

But the rest of examples they do not work, for example ping is missing some MBED TLS definitions.

I tried older versions, like 1.5. But in there it seems 8108 is not supported?

Please let me know, the whole development process is a bit confusing. Also the MM8108 user guide is wrong in several sections.

Thanks.

2

Hi @kaz

When you say they other examples don’t work, do you mean they don’t compile? Or that the compile, but don’t run when written to the board?

The examples should work, so if there are issues we’d like to resolve them.

Also the MM8108 user guide is wrong in several sections.

Could you share some more details on this so we can get them resolved?

Thanks

3

Hi Idennis, sure!

This is my setup.

  • Development Board 8108_EKH05.
  • CubeMX v6.18.0.
  • CubeIDE v2.2.0
  • MM_Iot pack v1.9.0
  • STM32Cube_FW_U5 v1.9.0
  • Embedded packages X-Cube-BLE2 and X-Cube-FreeRTOS installed.
  • MM8108-EKH05 User Guide v3.
  • OS Ubuntu Linux.

In CubeMX, you open the example “Halow_example_SPI”. It asks you if you want to continue using version 1.5 or “migrate” to 1.9. Then, in software packages / select components / MorseMicro MM_IoT / MM_Iot example you can choose between “Ping” / “Scan” / … and “EKH05 Demo”. I chose the latter. Then you press “Generate code”.

Then you open with the CubeIDE the generated code folder. You go to main.h and change the define 6108 to 8108.

If you decided to “continue” on v1.5, you can build and run the EKH05 Demo. I can see the output on my UART monitor. I can see the website on the browser.

If you start from scratch but for example you choose the “ping” example, it does not work. It does not build, with errors such as:

“../Middlewares/Third_Party/MorseMicro_FreeRTOS-Libs_FreeRTOS-libraries/freertos-libs-common/transport_interface.c:176:5: error: implicit declaration of function ‘mbedtls_x509_crt_init’; did you mean ‘mbedtls_x509_crl_init’? [-Wimplicit-function-declaration]”

Same thing if you don’t “continue” but “migrate”. But your user guide says to “continue” on page 27.

Also your MM8108 User Guide, for example, in Section 5 Software Development assumes a lot of things being done on the IDE, like Installing CMSIS Package, but it is actually done on CubeMX. Even on Figure28, you can still see the window title as IDE. Also a lot of screenshots clearly show v1.0.0 CMSIS-Pack, while its already v1.9.0. Some screenshots show version v1.6.0 which is not available on the releases page.

My question is really simple: how do I run other examples on CMSIS-Pack v1.9? Is the User Guide v3 the latest one for 8108? Should we “migrate” or “continue”?

Thanks in advance, let me know any test that I can do that is useful to you.

Kz

4

Hi @kaz
Thanks for the extra details - that’s much clearer now.

I’ve passed this one on to the team that maintains the CMSIS port, they take a look and get back to you.

– Luke

5

Hi Idennis, thanks.

Is the CMSIS port the recommended way / IDE to program it? I thought it was the one with better support for this board.

Let me know otherwise.

Thanks.

6

Hi Kaz,

For a more hands on developer, the recommended approach is to use the mm-iot-sdk directly:

But this is a more technically complex workflow.

Regarding your feedback on the CMSIS I spoke to the team:

Compilation issues: We have had other reports of users having trouble with v1.9 on Cube v2.X.
Can you try using cube v1.19 and see if you have the same issues?

Documentation accuracy: it sounds like there’s an updated version of the CMSIS documentation that should be published soon which should improve a lot of these issues. I’ll link this once it’s published.

Hope that helps!

7

Hi Idennis,

Tried version v.1.9. It adjusts more to your user guide so this confirms the latter is outdated. However, there are some figures such as Figure29 that they don’t appear in the IDE and you cannot choose 8108. Also, version 1.9 requires a lot of OLD libraries to be installed, such as libncurses5. I cannot really spend 3 days finding all type of issues to run a “ping” example. The demo example was nice though. Too bad the rest they don’t work on IDE v2.

I am sad to say that it seems to require a considerable amount of work to make this SDK work with STM32 tools. Please link the new user guide soon, maybe with some ping example running, and better if it is working with VSCode and STM32 plugin instead of STM32CubeIDE, because I am sad to say this 8108-EKH05 development environment is currently unusable / untrustable.

Thanks.

8

Hi Kaz,

I’m not sure if it would make a difference regarding the old libraries etc, but just to clarify the suggestion was to use v1.19 not v1.9 of STM cube.

Either way, we appreciate the feedback on the issues and frustration. I’ll make sure that Cube v2 is explicitly added to our CMSIS release testing.

As our SDK is not intended to only target STM32, our main point of delivery is a general command line based work flow, which you can find on the github linked above, docs linked on the readme:

With that said, we’re always looking for ways to improve, and we do know that user-friendly is one of those areas. It won’t be right away, but things like VSCode + STM32 plugin is a great suggestion.

Cheers,
Luke

9

Yes Idennis, you are right, I said v1.9 but I indeed tried v1.19. Great, will come back here in the future. Also the generated code is nice but… it is really so-so. And I say this after working with Texas Instruments for years, and having seen BAD things :slight_smile: ciao

10

Is this referring to the STM32 bsp code? It’s very much intended to be a best-effort starting point, rather than a production ready system :sweat_smile:

Again, appreciate you taking the time to share your experience and feedback