STM32CubeMX 6.16.0 - STM32H563 - Values not being updated

[Sander_UP]

Hello!

I wanted to set up some settings from CubeMX, specifically NX_IP_PERIODIC_RATE in NetXDuo and Rx Descriptor Length in ETH section. 

NX_IP_PERIODIC_RATE default value is set to 100, but when I set it to 1000, the value does not change when re-generating the code.

Rx Descriptor Length default value is set to 4, but when I set it to 8/16/32, the value does not change when re-generating the code.

Right now, whenever I re-generate the code, I just manually change these settings in my code due to these settings being set to their default ones. The same problem occurred in CubeMX version 6.15. One thing to point out also, is that the settings I changed are not set back to their default ones in CubeMX, only in the generated code. Also, no errors or warnings are displayed.

Is this a bug or am I supposed to do something else before being able to change and apply these settings?

[Mahmoud Ben Romdhane]

Hello @Sander_UP ,

Let me thank you for posting.

For more investigation, I suggest that you provide your Ioc.File.

Thanks.

Mahmoud

[Sander_UP]

Hello @Mahmoud Ben Romdhane 

I will attach the ioc file to this post.

[Mahmoud Ben Romdhane]

Hello @Sander_UP ,

Let me thank you for bringing those issues to our attention.

° NX_IP_PERIODIC_RATE is not updated if it is equal to TX_TIMER_TICKS_PER_SECOND.

An Internal Ticket Number is raised to the dedicated team (Ticket Number:  222964)

° TX and RX Descriptor Length are not being updated after the code generation.

An Internal Ticket Number is raised to the dedicated team Ticket Number: (Ticket Number 222956)

I will let you know when those issues are solved.

Thanks.

Mahmoud

[Sander_UP]

Hello @Mahmoud Ben Romdhane 

I found a couple more things regarding NetX Duo and its settings. The same .ioc file is being used.

Three more things I found:

1. NX_CRYPTO_DRBG_PREDICTION_RESISTANCE - the default definition is still included, and the user defined one is not used. If commenting out the default, the one in the nx_secure_user.h file is not used, and when compiling, then errors will be shown.
2. NX_CRYPTO_AES_USE_RAM_TABLES - in the file nx_crypto_aes.h it is not recoqnized that it is defined after re-generating the code (nx_secure_user.h file not included?). It is always as NX_CRYPTO_AES_USE_RAM_TABLES is not defined.
3. NX_CRYPTO_HARDWARE_RAND_INITIALIZE - it seems that it has no purposes. No code has it included. I assume it is related to the macro NX_RAND, which by default uses the software random number generator. Or I am missing something?

[Mahmoud Ben Romdhane]

Hello @Sander_UP ,

Could you provide please more details about the issues shared on the last comment.

Thanks.

Mahmoud

[Sander_UP]

Hello @Mahmoud Ben Romdhane 

I do not exactly know what more details I can provide or is needed from me. The problem with the three settings is that whenever I wanted to enable those three settings, they did not do anything as I would have expected. When enabling NX_CRYPTO_DRBG_PREDICTION_RESISTANCE, NX_CRYPTO_AES_USE_RAM_TABLES and NX_CRYPTO_HARDWARE_RAND_INITIALIZE, and then regenerating the code, they had no effect (nothing new was added or default defines together with default values were still in use).

For example, for the NX_CRYPTO_HARDWARE_RAND_INITIALIZE as already mentioned, when enabling did not provide any way to use the RNG capabilities (which was enabled from the CubeMX).

If you would like to get more details or information that I have not yet offered, please let me know!