With partial decodes and all that (to save silicon), it may not even be a waitxxx instruction.
BTW, somewhere Chip has said the waitxxx instructions are in fact 6 cycles minimum. This may mean that the waitxxx instructions go to different states while waiting. We just do not know. The only thing that we could determine is where the input pin is sampled from using a scope and varying where the pin changed state. This is just too hard to bother.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔ Links to other interesting threads:
Something else to think about. What happens if the instruction is set to not execute due to the conditions/flags? Do the instructions take 4 cycles or 6 cycles?
stevenmess2004 said...
What happens if the instruction is set to not execute due to the conditions/flags? Do the instructions take 4 cycles or 6 cycles?
If it doesn't execute due to conditions it's a nop, therefore it takes 4 cycles.
Comments
-Phil
Addendum: Are you sure it's not a sub dst,src? That would make a little more sense, due to the compare.
-Phil
BTW, somewhere Chip has said the waitxxx instructions are in fact 6 cycles minimum. This may mean that the waitxxx instructions go to different states while waiting. We just do not know. The only thing that we could determine is where the input pin is sampled from using a scope and varying where the pin changed state. This is just too hard to bother.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Links to other interesting threads:
· Home of the MultiBladeProps: TriBladeProp, SixBladeProp, website (Multiple propeller pcbs)
· Single Board Computer:·3 Propeller ICs·and a·TriBladeProp board (ZiCog Z80 Emulator)
· Prop Tools under Development or Completed (Index)
· Emulators: Micros eg Altair, and Terminals eg VT100 (Index)
· Search the Propeller forums (via Google)
My cruising website is: ·www.bluemagic.biz·· MultiBladeProp is: www.bluemagic.biz/cluso.htm
-Phil