Mutual exclusion in libc and CTL V2
Hi,
1. If I use the 'New Project wizard' to create a 'CTL executable for a Atmel AT91SAM9G20_EK Board' the project setting 'Use Multi Threaded Libraries' will be set to 'No'. Why aren't multi-threaded libraries chosen for a CTL project by default?
2. The CrossWorks documentation says that if a CTL project is created using the 'New Project wizard', CrossWorks will provide implementations of the locking functions for heap, printf, scanf and debug_io. But I didn't I find the implementations of these functions in this project. Do I overlooked them?
3. The CrossWorks documentation says that for a multi-threaded environment under CrossWorks C library the locking functions for heap, printf, scanf and debug_io must be implemented. When I used the disassembler I have found that a function <ctl_events_wait> is called. Is the CrossWorks C library already equipped with these locking functions?
I use CrossWorks 2.3.5 for Windows, 'AT91SAM9 CPU Support Package 2.5' and 'AT91SAM9G20-EK Board Support Package 2.2'.
Thanks in advance.
Thomas
Link: file:///C:/Program Files (x86)/Rowley Associates Limited/CrossWorks for ARM 2.3/html/libc_mutex_locks.htm
Please sign in to leave a comment.
Comments
0 comments