cogid behavior



  • localroger wrote: »
    I guess it depends on what's more important. Using PAR burns several COG longs for each purpose, while the wait for a cog to launch before doing the next one is almost exactly 1 millisecond at 80 MHz. Considering how long it takes the Prop to boot from EEPROM, that's unlikely to be noticed but I've had lots of situations where a few COG longs were critical.

    That's a good point. Moving initialization code from PASM to Spin is almost always better. I tend to never use par at all, but I usually just differentiate by cogid when launching multiple instances of the same code instead of passing the ID in here.
Sign In or Register to comment.