??? 01/28/05 22:43 Read: times |
#86072 - In all sorts of sizes of chips Responding to: ???'s previous message |
Erik Malund said:
I specifically asked for an example of relevant use of a URTOS on a system with no more than 128 RAM 4k code as you specify you are designing for. Erik I never intended that it should be limited to only such small systems, but that is should be capable of running on them. Also, a standard 8051 could have 64K of external code memory yet still be limited to two timers and 128 bytes of RAM. Having said that, I do expect there will be many applications for it on small systems. Not only that, as it will be feely available with source code, I sincerely hope it will be used by hobbyists as an introduction to the efficient design of reliable real time systems. Your initial question was: I would like you to suggest - just one - application running on a 128RAM (remember - none such exist with more than 4k FLASH/ROM) where a URTOS would have any benefits. The benefits of using an RTOS can include simpler development, fewer design errors, improved reliability, easier modification and maintainability. I would argue that almost any application with time related tasks could potentially benefit from a cooperative RTOS. I recommend you look at this page for a consideration of the advantages and disadvantages of different approaches to real time programmes. http://instruct1.cit.cornell.edu/courses/e...76/PgmOrg/ This is specific to the AVR but is generally applicable to any micro. Ian |
Topic | Author | Date |
Computed Call | 01/01/70 00:00 | |
Computed Call | 01/01/70 00:00 | |
simulate an LCALL @A+DPTR instruction? | 01/01/70 00:00 | |
Solution | 01/01/70 00:00 | |
Computed LCALL | 01/01/70 00:00 | |
Computed LCALL | 01/01/70 00:00 | |
Table offset | 01/01/70 00:00 | |
x2, not x3 | 01/01/70 00:00 | |
what is the problem | 01/01/70 00:00 | |
My Problem | 01/01/70 00:00 | |
never heard of it | 01/01/70 00:00 | |
It is....... | 01/01/70 00:00 | |
RTOS | 01/01/70 00:00 | |
8051 RTOs Limitations/Issues/Opportunity | 01/01/70 00:00 | |
How? | 01/01/70 00:00 | |
Decisions, decisions | 01/01/70 00:00 | |
Small systems - task scheduling | 01/01/70 00:00 | |
Worth it? | 01/01/70 00:00 | |
Scheduler | 01/01/70 00:00 | |
Scheduler | 01/01/70 00:00 | |
running small in a big way | 01/01/70 00:00 | |
Example | 01/01/70 00:00 | |
in very small chips | 01/01/70 00:00 | |
In all sorts of sizes of chips | 01/01/70 00:00 | |
time dependednt | 01/01/70 00:00 | |
RTOS or Not | 01/01/70 00:00 | |
opinion piece | 01/01/70 00:00 | |
fact piece | 01/01/70 00:00 | |
Opinion piece | 01/01/70 00:00 | |
suggestion piece | 01/01/70 00:00 | |
reasons | 01/01/70 00:00 | |
Polite discussion | 01/01/70 00:00 | |
Politeness | 01/01/70 00:00 | |
Thanks | 01/01/70 00:00 | |
Politeness | 01/01/70 00:00 | |
What are you Rabbiting on about? | 01/01/70 00:00 | |
Close but no Cigar | 01/01/70 00:00 | |
Rabbit food | 01/01/70 00:00 | |
Plessey | 01/01/70 00:00 | |
small world | 01/01/70 00:00 | |
Smaller than you imagine!![]() | 01/01/70 00:00 | |
I use the computed LCALL ... | 01/01/70 00:00 | |
go it | 01/01/70 00:00 | |
Call tabs in-line | 01/01/70 00:00 | |
abbreviated | 01/01/70 00:00 | |
... and further optimized... | 01/01/70 00:00 | |
has been already disscussed | 01/01/70 00:00 | |
Scheduler of course | 01/01/70 00:00 | |
Scheduler | 01/01/70 00:00 |