Yes, this is the board. And here is its schematic: https://www.parallax.com/sites/default/ ... t-RevB.pdf
What other parts are needed to connect to raspbian and ultibo?
To Raspbian: USB cable. The board has FTDI chip on it so it will be visible as serial-on-usb by Raspbian. The cable will also provide the power supply
To Ultibo: I don't know if it has driver for FTDi chip used in the board. If yes: USB cable.
If no: modding needed. The path from a buffer to Propeller RxD pin need to be cut. After this you need 5 cables: RxD, TxD, reset, ground, Vcc.
This is also valid if you want to connect bare Propeller to RPi. You can also use RPi as an external clock source. It has internal one but its frequency depends on temperature etc. The standard is a 5 MHz quartz oscillator. There is semi-official overclocking (they even sell 6.25 MHz quartz oscillators for this purpose)
And as many cables as you want to connect RPi GPIO with Propeller GPIO. Maybe serial resistors for safety and capacitors for decoupling. Both devices are 3.3V
The Propeller boot procedure:
(1) it initializes
(2) it sends some bytes to the host via UART and waits for a proper answer
If the answer is OK, then the host takes control. It can send a command "Load the program to RAM" or "Load the program to RAM and SPI eeprom". Then it has to send the binary code to the Propeller.
If the command was "write to SPI eeprom" then Propeller will do it
After this, the SPIN interpreter is loaded from ROM to cog 0 local RAM and the cog 0 starts to interpret what was loaded to the Propeller's memory
If there is no answer, the Propeller starts to load 32 kB from SPI eeprom to its main RAM (called HUB RAM), then loads the interpreter and starts interpreting.
If there is no host and no eeprom, it will go to idle mode until the next reset.
The progam for the Propeller is done like this: the main code is written in Spin. This is high level interpreted language. The code in Spin can start another Spin interpreters in other cogs (there is 8 of them) or (this is more often) load assembly programs into the rest of cogs and start them. The last thing it may do is to overwrite itself by some assembly code but normally program in Spin is used to "rule them all"
As the Propeller is now fully open sourced (the Verilog code is available) all of these details including boot rom, boot protocol and interpreter are accessible and fully described in the Propeller forum.