You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that the cat_init() function supports an argument for a mutex.
Is the mutex intended to be used to protect in environments with multiple core CPU?
One of the project I am working on uses the cAT library for unit test and target deployment.
In the unit-test (running on a multi core system) the AT-commands are written to a circular buffer
and the cAT library writes out its responses back to a file in the filesystem that is then compared
against an expected response.
If I run this in a multi CPU core environment, some test fails with responses that does not match
the expected response. However, if I restrict the test to a single core
(e.g. using taskset -c 1 in linux), all the test will pass.
If I am missing something, what are the recommended
practices for using the library in a multi core CPU environment?
Thank you for everyone's time!
The text was updated successfully, but these errors were encountered:
Hello,
I noticed that the
cat_init()
function supports an argument for a mutex.Is the mutex intended to be used to protect in environments with multiple core CPU?
One of the project I am working on uses the cAT library for unit test and target deployment.
In the unit-test (running on a multi core system) the AT-commands are written to a circular buffer
and the cAT library writes out its responses back to a file in the filesystem that is then compared
against an expected response.
If I run this in a multi CPU core environment, some test fails with responses that does not match
the expected response. However, if I restrict the test to a single core
(e.g. using
taskset -c 1
in linux), all the test will pass.If I am missing something, what are the recommended
practices for using the library in a multi core CPU environment?
Thank you for everyone's time!
The text was updated successfully, but these errors were encountered: