K.I.S.S. Design for Prop II or III concept...
First off, please know that i'm not an IC layout engineer, IC design engineer, and my profession (until the layoff at least) has nothing to do with MCU's. This is more or less something I thought up as a concept.
Instead of 8 segregated cogs, each with their own counters and VSU's, why not make the individual resources globally accessable to any cog. One cog having acess to all 16 counters may seem a bit extreme, but if counters and VSU's could be acessed as a spinoff of COGNEW, wouldn't programs be a bit easier to write if you didn't have to launch chunks of code as COGNEW to give your porgram acess to multiple resources? Wouldn't that scheme also allow acess to unsused cogs for additional processing, kinda like a co-processor?
From my P.O.V. when programming the prop, it appears that your main program divides up tasks for 8 individual 32 bit MCU's with individual CTR & VSU units·in an optimised pkg design with shared I/O acess, an inter-cog data buss,·a global clock, PLL, and power. I'm not knocking the Propeller at all, this processor is awesome. And I can only imagine what it would take to make what I described a possibility while being fast, reliable and efficient.
This is more of a daydream than a suggestion or question, & I realize the devil is in the details,·but isn't that how the·Apple & IBM PC started?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
E3 = Thought
http://folding.stanford.edu/·- Donating some CPU/GPU downtime just might lead to a cure for cancer! My team stats.
Instead of 8 segregated cogs, each with their own counters and VSU's, why not make the individual resources globally accessable to any cog. One cog having acess to all 16 counters may seem a bit extreme, but if counters and VSU's could be acessed as a spinoff of COGNEW, wouldn't programs be a bit easier to write if you didn't have to launch chunks of code as COGNEW to give your porgram acess to multiple resources? Wouldn't that scheme also allow acess to unsused cogs for additional processing, kinda like a co-processor?
From my P.O.V. when programming the prop, it appears that your main program divides up tasks for 8 individual 32 bit MCU's with individual CTR & VSU units·in an optimised pkg design with shared I/O acess, an inter-cog data buss,·a global clock, PLL, and power. I'm not knocking the Propeller at all, this processor is awesome. And I can only imagine what it would take to make what I described a possibility while being fast, reliable and efficient.
This is more of a daydream than a suggestion or question, & I realize the devil is in the details,·but isn't that how the·Apple & IBM PC started?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
E3 = Thought
http://folding.stanford.edu/·- Donating some CPU/GPU downtime just might lead to a cure for cancer! My team stats.
Comments
Some problems should be resolved using just what is needed for the task, without generalizing, because it may only provide bloat and unused features. (Something I always forget).
-Phil
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
'Still some PropSTICK Kit bare PCBs left!
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
E3 = Thought
http://folding.stanford.edu/·- Donating some CPU/GPU downtime just might lead to a cure for cancer! My team stats.