cancel
Showing results for 
Search instead for 
Did you mean: 

USBX System Stack Size is missing in USBX Configuration on STM32H7RSxx

Gaweringo
Associate II

The X-CUBE-AZRTOS-H7RS middleware is missing the setting to change the USBX System Stack Size which in turn means that the USBX_MEMORY_STACK_SIZE define in the app_usbx.h file can not be changed from its default of 1024. And because the define is not in a USER CODE section, any manual change will be overridden when re-generating code in CubeMX.

Here is an example when using USBX host stack, but it's the same for the device stack.

STM32H7RSxx:

Gaweringo_0-1770624045074.png

STM32H7A3ZIT:

Gaweringo_1-1770624411724.png

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

Hello @Gaweringo 

Let me thank you for bringing this issue to our attention.

The issue has been escalated internally to the dedicated team for further investigation and resolution (Ticket 

227182 )This is an internal tracking number and is not accessible or usable by customers.)

I will let you know when the issue is solved.

Thanks.

Mahmoud

 

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

View solution in original post

3 REPLIES 3
Mahmoud Ben Romdhane
ST Employee

Hello @Gaweringo 

Let me thank you for posting.

I am currently checking this behavior, and I will get back to you ASAP.

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

Thanks.

Mahmoud

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

Here's an exemplary .ioc file. It's not configured in a way that the resulting project would work (sizes aren't large enough, time source isn't changed from SysTick, ...) but UsbX is activated and doesn't show the option to change the USBX_MEMORY_STACK_SIZE.

I have also attached a .ioc file for a h7a3 where the option shows up.

Hello @Gaweringo 

Let me thank you for bringing this issue to our attention.

The issue has been escalated internally to the dedicated team for further investigation and resolution (Ticket 

227182 )This is an internal tracking number and is not accessible or usable by customers.)

I will let you know when the issue is solved.

Thanks.

Mahmoud

 

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.