| ??? 02/22/05 23:42 Read: times |
#88192 - I doubt we are Responding to: ???'s previous message |
Ian seems to be making a cogent argument but Erik, you seem to be trying to preach to the converted. I fully understand what you're saying and I'm sure Ian does. You seem to be tied up in the semantics. As I've mentioned before the term 'task' is really just a concept - in your workloop you might have something like
main_loop: call do_comms call update_lcd if timer_tick call process_io etc goto main_loop One could call them tasks - you can call them anything you like. I know I would call them tasks and Ian might also and we would both understand what we were describing. I'm coming from a computer science perspective as opposed to an engineering perspective where these concepts are named and described. Also lets not get tied up with the word 'concurrency' - as we all know that the micro only executes one instruction at a time (let's not get into the nitty gritty of cpu architecture!) - so concurrency depends on the time scale you're talking about - things appear to execute 'concurrently' but we all know they don't! To suggest that using a pre-emtive RTOS on a 8051 is verboten is dated - I would suggest in many cases it is un-needed, but I have seen successful products use a RTOS and very successfully at that. The same goes for floating point math - I try to avoid it - especially on a 8051 but in my current project I use floating point math! And succesfully at that! Many years ago I ran a system called os/9 on a 2mhz 6809 cpu - I dare say a 100mhz 8051 variant wouldn't have too much trouble in beating the performance of this old cpu! Times change, yesterday's solution may not be the best today. I keep a toolbox of 'solutions' and I try to choose the best tool for the job - no one tool is the 'cure all'. Small embedded systems require specialised knowlege and skills which are normally not required in PCs, conversely writing GUI apps requires different knowlege and skills to writing small embedded apps. Lets not argue over the semantics as we're not adding any value to the subject - the subject just becomes boring to those others reading it. |
| Topic | Author | Date |
| please expalin RTOS, UnRTOS, MTOS... | 01/01/70 00:00 | |
| Os's | 01/01/70 00:00 | |
| thanks ...and now for Erik... | 01/01/70 00:00 | |
| MicroC O/S II works fine | 01/01/70 00:00 | |
| Threads? | 01/01/70 00:00 | |
| Threads, Real Time and Multitasking | 01/01/70 00:00 | |
| Just for clarification | 01/01/70 00:00 | |
| Multiprocessing | 01/01/70 00:00 | |
| Multiprocessing | 01/01/70 00:00 | |
| Further clarification | 01/01/70 00:00 | |
| Threads | 01/01/70 00:00 | |
| Windoze | 01/01/70 00:00 | |
| More Windoze | 01/01/70 00:00 | |
| Ah... | 01/01/70 00:00 | |
| Basic Info | 01/01/70 00:00 | |
| extract from the above with translation | 01/01/70 00:00 | |
| Completed | 01/01/70 00:00 | |
| who are we | 01/01/70 00:00 | |
Tics | 01/01/70 00:00 | |
| the rest | 01/01/70 00:00 | |
| But wait..there's more! | 01/01/70 00:00 | |
| Real Time Info | 01/01/70 00:00 | |
| hard/soft | 01/01/70 00:00 | |
| Real Time Info | 01/01/70 00:00 | |
| m,y opinion | 01/01/70 00:00 | |
| why so late | 01/01/70 00:00 | |
| one more thing | 01/01/70 00:00 | |
| Architecture Independent | 01/01/70 00:00 | |
| just to clarify | 01/01/70 00:00 | |
| No. | 01/01/70 00:00 | |
| RTOS on a 51?? | 01/01/70 00:00 | |
| not the thing but the word | 01/01/70 00:00 | |
| A Distinction (with a difference) | 01/01/70 00:00 | |
| Tasks or Applications? | 01/01/70 00:00 | |
| Multi Tasking | 01/01/70 00:00 | |
| a dot matrix printer must be one task | 01/01/70 00:00 | |
| One task or three | 01/01/70 00:00 | |
| pray explain | 01/01/70 00:00 | |
| Tasks and Functions | 01/01/70 00:00 | |
| we are getting closer | 01/01/70 00:00 | |
| Not that far apart | 01/01/70 00:00 | |
| I doubt we are | 01/01/70 00:00 | |
| discussed | 01/01/70 00:00 | |
| TTCS | 01/01/70 00:00 |