Propeller to the Nth. (and if you act now, "Prop Ring" is yours free!)
Clock Loop
Posts: 2,069
Propeller program in a propeller program,
in a propeller program,
in a propeller program,
in a propeller program,
in a propeller program,
in a propeller program in a eeprom (or downloaded from prop tool)
SOMEBODY STOP MEH!.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
TERMS OF USE: MIT License
"Permission is hereby granted, free of charge, to any pers...........................
..............................OMITTED FOR FORUM...............................................
.................. OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. "
The dsp/fpga king is dead, long live the prop.
Post Edited (Clock Loop) : 8/27/2009 8:28:37 PM GMT
in a propeller program,
in a propeller program,
in a propeller program,
in a propeller program,
in a propeller program in a eeprom (or downloaded from prop tool)
SOMEBODY STOP MEH!.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
TERMS OF USE: MIT License
"Permission is hereby granted, free of charge, to any pers...........................
..............................OMITTED FOR FORUM...............................................
.................. OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. "
The dsp/fpga king is dead, long live the prop.
Post Edited (Clock Loop) : 8/27/2009 8:28:37 PM GMT
1280 x 393 - 67K
Comments
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
--Steve
Propeller Tools
Thanks!
Using the PROPELLER LOADER, the FREQ SYNTH, and the FULL DUPLEX SERIAL objects one can control and program as many props as one has.
As you can see, any data that gets from one side to the other, must travel through every single prop,
if that data is near the end.
However, I often think about the situation where you eventually loop the thing.
Any prop would transmit data to the left or right depending on its destination.
Thats like a bidirectional - bidirectional link.
(but the last and first prop would only be able to communicate,
the XI and RESET line between them would be unused by the first prop.)
It could be put into operation, so the thing is a loop, but you would have cascading resets, unless you could get the first prop to somehow run off the last props freqout, after the first prop was already running. The reset line would need to be hardwired on for one of the props 10k to 3.3v. And that same prop would need an eeprom.
But if the reset output line of the first prop ever let go, the whole thing would cascade reset, which would work around to the last props FREQOUT, then the first prop would stop running. AT that point a power reset would only get it going again.
Prop Ring?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
TERMS OF USE: MIT License
"Permission is hereby granted, free of charge, to any pers...........................
..............................OMITTED FOR FORUM...............................................
.................. OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. "
The dsp/fpga king is dead, long live the prop.
Post Edited (Clock Loop) : 8/27/2009 7:47:49 PM GMT
All you need now is a connection from the last one back to the first one, then it could be a token-ring.
A serial-mesh would be faster but messy. A parallel bus would be easier to connect [noparse]:)[/noparse]
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
--Steve
Propeller Tools
The circuit I attached on the first post is wrong. Heres why.
The Propeller Loader object drives the other Propeller's RESn line, so it is recommended that
the other Propeller's BOEn pin be tied high and that its RESn pin be pulled
to VSS with a 1M resistor to keep it on ice until showtime.
So if you do this, make sure you correct the circuit. (im too lazy to fix it now, heheh)
Post Edited (Clock Loop) : 9/2/2009 9:57:26 AM GMT
After all are booted, the main code starts with a CASE statement to jump to the proper code the propeller running the code
pub afterBoot
···· case propIdentifier
··········· 0:
·············· runProp0Code
············1:
···············runProp1Code
·············etc
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Caught in the PropWash