Stack Corruption: tx_queue_receive() with TX_WAIT_FOREVER Option about x-cube-azrtos-h7 HOT 7 CLOSED

Hi @ajitbasarur,

Thank you for your proposal.

With regards,

from x-cube-azrtos-h7.

Hi @ajitbasarur,

Thank you very much for this detailed and very clear report. Thank you also for the fix proposal.

Our development teams have already been notified. A fix will be made available in a future release.

With regards,

from x-cube-azrtos-h7.

ST Internal Reference: 114470

from x-cube-azrtos-h7.

Hi @ALABSTM ,

Thank you for your prompt response. Sure, please notify me once the new software is released with this particular fix. I will close this issue in Github.
Meanwhile, I suggest the following improvements to your code.
Whenever you call any ThreadX API, please check for the return value. For examle, compare with TX_SUCCESS and proceed further. This will help handle unknown bugs in the future.

Thanks again for the software.

Best Regards,
Ajit B

from x-cube-azrtos-h7.

Hi @ajitbasarur,

Thank you for your contribution. The fix you requested has been implemented and is now available in the frame of the latest
x-cube-azrtos-h7 package V2.0.1 release.

This issue can be closed now. Thank you again for your contribution.

With regards,

from x-cube-azrtos-h7.

Hi @RKOUSTM,

Thanks for the update. I will verify the code and then close the issue.
An update: I did a quick code check. My comments have only been incorporated in USB MSC related files. A question. Have you taken care of them in other projects as well? The issue appears if tx_queue size is not set properly, which is common across many projects. Could you please leave your comment on that as well?

Thanks and Best Regards,
Ajit B

from x-cube-azrtos-h7.

Hi @ajitbasarur,

First, allow me to thank you for this report, once again. According to our development teams, the point you have reported wasn't replicated in other projects.

Thank you again for your contribution. We are looking forward to reading from you again.

With regards,

from x-cube-azrtos-h7.