Thank you very much!
I recognized that i confused c:/LiteOS/... with /c/LiteOS/... in two different cases.
It's ok now.
But I have other trouble with sensorial application. The first time when I install LiteOS onto iris mote, it's ok with sensorial application( ./light 50 600, and it return 50 values with 600ms cycle). But now, I can't receive any other results more than "Get reading of 0".
There is an attached picture which I captured.

Thanks!

I could not copy Blink.lhex file from cygwin driver C:/LiteOS/.../Blink to
root directory of one mote. I followed the usermanual but it wasn't better.
How will I find the solution?
Thanks!
--------------------------
Nguyễn Tuấn Linh

Hi,

I would like to get the output from a few printf statements in the LiteOS kernel. Is there an easy way for doing that?
Another question that I had is what happens when the priority of a task is very high? If an application spawns 3 threads with priorities 1,2 and 100 does it mean that the 3rd thread will get more CPU time compared to the other threads? According to the function thread_get_next in threads.c, the thread with the highest remainingcredits should get the cpu time and its remainingcredits is decreased by 1 until it reaches 0 and then replenished with its priority value. But, I tried to test this with an application that spawns 3 threads each responsible for toggling a different led and assigned priorities 1,2 and 100 to them but they seem to be toggling at the same intervals. Even when I increase the priority of the 3rd thread to 2000, it remains the same. Could someone explain this phenomenon.

Kind regards,
 Debojit

Hi all!
I have a mote  uses atmega128 and xbee module.
It is possible to port LiteOS to this mote. Is LiteOS made for Micaz and IRIS only?

Thanks!
---------
 Linh

Hi

Hi,

I am a student at the university of British Columbia. While browsing through the liteOS code, I came across the file liteoscommon.h in the directory /LiteOs/Apps/Libraries/. Now there are several function calls in this file represented as  shown:

#define POST_TASK_SYSCALL                                             0xEA58

If someone could clarify me on this. How is the call actually being made to the functions and what does the address ' 0xEA58 ' signify?

Thanks,
Debojit

Hi, as I mentioned in this week's telecon, here is a summary the survey results on using LiteOS in class labs, received by Professor Tian He from his class students a while back. The attached document contains the summary. Meanwhile, we also received several project reports from Professor Stankovic's class and Professor Tian He's class, and the integration of these projects into the next version of LiteOS are currently under progress.

Thanks.
Qing