TDA4VM: The RTOS uses a mutex lock

Cherry Zhou

Part Number: TDA4VM

Hi team,

Here's an issue from the customer may need your help:

When using a mutex lock, calling the initialization function pthread_mutex_init causes all tasks to not run. Because mutex variables cannot be defined before the semaphore variable, it is fine if the mutex variable is defined after the semaphore.

As shown in the figure above, the results of code execution are completely different between the two places defined. Is this a mechanism that has been deliberately designed? And is there any routine for reference on the use of the mutex?

SDK version: 7.1.

Could you help check this case? Thanks.

Best Regards,

Cherry

over 3 years ago

0 Brijesh Jadav over 3 years ago

TI__Guru**** 482295 points

Hi Cherry,

I really doubt it makes difference in defining mutex variable before semaphore variable. May be there is some usage order in the task execution, because of which, you might be seeing issue..

Regards,

Brijesh

0 Cherry Zhou over 3 years ago in reply to Brijesh Jadav

TI__Mastermind 22235 points

Hi Brijesh,

Thanks and the customer find the case is they use the mutex lock inside the compiler for SDK/ti-cGT-arm_20.2.0.LTS/lib/. Regarding how the mutex is used in the BIOS documentation:

They've followed the way above but “Cannot open source file ’pthread.h‘ ”error when including header file pthread.h.

Thanks and regards,

Cherry

0 Parth Nagpal over 3 years ago in reply to Cherry Zhou

TI__Mastermind 42135 points

Hi Cherry,

Cherry Zhou said:
They've followed the way above but “Cannot open source file ’pthread.h‘ ”error when including header file pthread.h.

For this error can you please point them to TI-Posix user guide available at SDK\bios_6_83_02_07\docs\tiposix\Users_Guide.html and see if that helps.

Regards,
Parth

Processors

Processors forum

TDA4VM: The RTOS uses a mutex lock