Propeller Gurus -
Ordinarily I'd go back through all the present documentation and attempt to find my own answer for this, as it seems to be a rather simple question. I'm just afraid it would be a waste of time, since the present documentation is so sparse and preliminary so far (just an observation, not a complaint!).
Embedded chip programmers are usually faced with an all-or-nothing proposition in loading their programs even when bootloaders are available, since (as far as I'm aware) no microcontroller or similar device has offered a dynamic link/loader with which to load program segments (post-execution), or to create what many of us have come to know as a "dynamic overlay structure".
Now, with the Propeller we have the ability to use one or more separate COGs for our·programs or systems, to start and stop our own COGs at will, and to have a fair degree of control-yet-autonomy with/within each of the COGs, with the proper programming techniques, and adequate programmer skills.
Often times a program/programmer may be faced with a large amount of "housekeeping"· or one-time initialization, at or near the beginning of a program. This can chew up a·fair amount·of memory or data space, and heretofore we've had to pretty much live with that issue. I suspect this can be overcome with the Propeller, so that we can free this formerly locked memory/data space.
Can a (say) SPIN program (necessarily the first to execute as I understand things), perform these various and necesssary "housekeeping" or initialization chores, and then cause another program (SPIN or assembler) to overlay itself, then·have it·go on with the ordinary course of events, with all 8 cogs (itself + 7 others) now available to it?