Hi all, In RTX we can assign a function as a task with the _task_ #NO tag. When calling os_create_task we just pass this task number as a parameter. Assume one has to use banking, in this case, how does RTX identify, in which bank the function exists ? from where does rtx get information about the banks of any task at runtime ? regards pachu
RTOS ... Banking ... is this really a job for an 8051??
RTOS ... Banking ... is this really a job for an 8051?? Sure, just call it "Herbie" Erik
Yes, RTX and some more RTOS for 8051 support code banking. Can anyone throw some light on how rtx managing tasks when using code banking. How does RTX know about the bank of a particular task during run time...does it store some information in the TCB of each task ? Even if it stores some information of the bank for each task in the TCB, where does RTX get this info from ? regards pachu
"Yes, RTX and some more RTOS for 8051 support code banking." and floating-point maths, and dynamic memory allocation, and... Just because it can be done does not make it a good or sensible idea! My point is: if your project really needs both code-banking and an RTOS, is an 8051 really an appropriate target for it?
RTX and some more RTOS for 8051 support code banking If you race a Porsche with a VW you have the likelyhood of blowing the engine. What you are proposing may have been realistic some years ago when any other solution would be much more costly, but today where you e.g. can get an ARM for a couple of bucks it makes absolutely no sense. Now, when you have crammed all that into the poor little bugger, we expect your next post to be "can I clock a 12MHz chip with 50MHz" Erik
"What you are proposing may have been realistic some years ago when any other solution would be much more costly, but today where you e.g. can get an ARM for a couple of bucks it makes absolutely no sense." Maybe an ARM is unsuitable for his application. There is no reason why he shouldn't use an RTOS, code banking, floating point or whatever on an 8051 if the resulting system does what it is required to do. "Now, when you have crammed all that into the poor little bugger, we expect your next post to be "can I clock a 12MHz chip with 50MHz"" Now you're just being silly.
RTOS, code banking, floating point or whatever on an 8051 "Now, when you have crammed all that into the poor little bugger, we expect your next post to be "can I clock a 12MHz chip with 50MHz"" Now you're just being silly. Am I? with "RTOS, code banking, floating point and whatever" he will need better than 12MHz to get the result in "less than an hour". Erik
"Am I?" Yes. He's not going to ask whether he can clock a 12MHz chip at 50MHz. That would be a stupid question. As it happens, the derivative he's using can be clocked at 40MHz. "with "RTOS, code banking, floating point and whatever" he will need better than 12MHz to get the result in "less than an hour"." You don't know anything about the OP's project. He may well be able to achieve what he wants to do at 12MHz.
View all questions in Keil forum