Compiler question
lardom
Posts: 1,659
Where is the compiler located in the Propeller block diagram? I'm thinking that the compiler and the processor perform different functions and have different physical locations. (There is still a ton of stuff for me to learn and at the moment I'm trying to get a better grasp of Prop architecture.)
BTW it just occurred to me that cogs had to have processors located outside cog ram. Maybe the processor compiles code during the boot phase and then executes code during runtime.
While studying some simple PASM I thought that learning how the Prop handles code would answer a bunch of my questions.
BTW it just occurred to me that cogs had to have processors located outside cog ram. Maybe the processor compiles code during the boot phase and then executes code during runtime.
While studying some simple PASM I thought that learning how the Prop handles code would answer a bunch of my questions.
Comments
Oh boy, are you coming in from the wrong end
-Phil
(You are among those I owe a humongous thanks to whenever I look at the stuff I've created.)
When I read your post it seems as though you were reading through the prop manuals architecture section and got a little confused. The propeller has no compiler on it as stated above but it does have a Spin Interpreter built in, this would be analogous to python or QBasic on a PC. The propeller chip is made of 8 cores (or cogs in propeller speak) each core has 2k of ram attached to it which can only be accessed by that core. The propeller also has what is called the Hun which has 32k of ram, Hub ram can be accessed by all 8 cores but they have to take there turn reading and writing to it, the hub starts at the first core and lets it access hub ram then moves around to each core in numerical order doing the same, in a circular "round robin fashion". Te propeller has ROM built into it which holds the spin interpreter, when the chip is booted it loads the interpreter into cog0, then it fetches spin code it first looks at the the TX/RX serial pins to check for a pc connection if it doesnt find one it then moves on and loads code from the eeprom. The eeprom is basically just ROM where you save the spin/pasm/gcc code for your propeller to use when disconnected from the pc.
As I said im not sure if this is what you were talking about, but when I read your post it really made me think your were asking where the spin interpreter lives and how it executes code. If im way off from the original question I apologize but maybe this still helped you learn a little bit more about whats going on.