The attachment is located in post #5 https://www.edaboard.com/threads/128107/#post589983 [alexan_e]
;----- IPC0 Bits -----------------------------------------------------
.equiv INT0IP0, 0x0000
.equiv INT0IP1, 0x0001
.equiv INT0IP2, 0x0002
.equiv IC1IP0, 0x0004
.equiv IC1IP1, 0x0005
.equiv IC1IP2, 0x0006
.equiv OC1IP0, 0x0008
.equiv OC1IP1, 0x0009
.equiv OC1IP2, 0x000A
.equiv T1IP0, 0x000C
.equiv T1IP1, 0x000D
.equiv T1IP2, 0x000E ;This is the bit they missed!
Priority Inversion.
A problem that can occur with semaphores is that a task of low priority can block a task of higher priority while it uses a resource. One approach to solving this problem is to raise the priority of the task that is using the resource to the level of the task that is blocked. This gives the task more processor time to complete its use of the resource.
When the task releases the semaphore, its original lower priority is restored.
lafleur said:the need for optional % utilization/cpu/task is just a debug tool and not a feature, just like the stack checking tool that you have.... it help to find bugs in code.
yes, deterministic time function(s) are needed...
any examples you have talking to device would be of help to most users... USART, LCD, CAN, i2c, SPI ect...
tom lafleur
tom @ lafleur . us
btbass said:This rtos is lightweight and easy to use. The features implemented, semaphores, events and message passing are all very well documented and demonstrated with examples. It is suitable for a wide range of applications.
If you need more sophisticated features and data structures, then FreeRtos is a good choice. I believe it is in continual development with good supporting documentation.
Here is my Multitasking system for the Microchip Pic30, 33, 24 series of 16 bit micros.
This is a work in progress, so any feedback, comments, bug reports would be appreciated.
Please read the pdf file.
There are attachments in posts #5 and #8
https://www.edaboard.com/threads/128107/#post589983 post 5
https://www.edaboard.com/threads/128107/#post607337 post 8
Alex
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?