Bill Lamie

It looks like all this is missing are the prototypes in tx_port.h, e.g., the VFP code and enable/disable APIs are in the assembly port files. You do need to build...

The rule is that tx_mutex_get cannot be called from a non-thread context with a suspension option. This is checked for in the error checking for tx_mutex_get, namely txe_mutex_get. Error checking...

I agree Pat. It is nicer to have the use of volatile hidden from the outside.

Another option would be to make the tx_byte_pool_owner structure member in TX_BYTE_POOL volatile, like the following: struct TX_THREAD_STRUCT volatile *tx_byte_pool_owner; This is a slightly smaller change and something that might...

LDREX and STREX are being used for the locking mechansim. Are you suggesting additional locations?

Since I last looked at this code some queuing logic was also added. In some of the other SMP port-specific code, the queuing logic was then removed. More investigation is...

Your English is good, and I'm happy to hear everything is working. I recommend issuing a pull request with your fix so it gets properly reviewed.

Thank you for providing this information. What is interesting about this issue is that the FileX API utilizes an internal mutex to protect itself from multiple-thread access. Can you verify...

Yes, I see what you are talking about now. A good approach is to move the FX_PROTECT call earlier in the function, so the global data is under protection. Please...

It would be good to understand better the strange issues that occur when trace is enabled and used, e.g., are the issues related to the operation of ThreadX or problems...