Hello all and thank you for reading, I am about to ask you to do something rather unusual, it is more like a favor actually. I am the owner of an open source kernel available for free download at sourceforge.net/.../ The thing is that I never got any feedback from anybody as to the quality of my work; I have no way to judge my efforts. I was hoping that you would be so kind to help me. Do you see any serious problems with it? What are the major deficiencies? Do you even like it? I know this is something you would probably expect from a boss of colleague. I'm asking it as a favor.
Thanks in advance, Tamir Michael
Sauli, Thanks for your insight. Well, you are right, but the core of the "problem" is that this sort of timer is not really suitable for a preemptive environment. The other kind of timers supported (utilized by 'rtos_callback_timer_inform_every' and 'rtos_callback_timer_inform_in') are much more accurate, as they can invoke a user provided callback onces expired. If the callback is lightweight, it is both a more accurate and useful solution. In my little spare time I am working of release 2.2 (based on your review and some bug fixes) which will be the last one for the C166. I am going to make a port for the ARM9, and hopefully I will be able to reuse a major parts of my previous work.
Dear Friends,
I have headache for UDP protocol, I want to open a port for connection, but ".Bind" command gives "Runtime Error 87" I did not found any info about this issue and i dont' think it can happen, if anybody does please give me hand.
Thank you,
of all threads in this forum, do you have to spam mine? I can help you but will not - get lost along with your UDP headache !