The FPGA config is locked in after programming so you only ever have to do this once. But you do need to cycle power first time after configuration though. Your terminal can toggle DTR which will generate a reset through the PropPlug or ^G from PNut will reset the P2.

The moment I power up my FPGA I just type the two autobaud characters "> " + ESC ($3E,$20,$1B) and I am up and running in TAQOZ

I got it working and I think I figured out that one of the buttons on the Prop123-A9 board resets the P2. Now I'll wait for a TAQOZ document before doing any more playing. I can guess simple Forth commands but I won't be able to do anything with the P2 hardware without more docs.

It was easier to set them up with the TAQOZ kernel in each unused cog with cogs 1..7 running an idle loop that pauses for 10ms and checks to see if it has received a task. You can stop cog 7 with "7 COGSTOP" or type "8 1 DO I COGSTOP LOOP" or "1 7 ADO I COGSTOP LOOP" to stop all other cogs.

Wow Peter,
Just noticed you used up almost all of ROM!
I just put in my patches and went from $FFF20 to $FFF40

I noticed that Chip must have added some code too but TAQOZ gets copied to lower RAM so it doesn't matter if we overwrite the last 1k (or more) with debug routines. I only have the dictionary sitting there anyway which is only read on a cold start and moved into another area in lower RAM.

@Tubular - we have an FPGA and PNut version which allows us to load up 1MB up to the hub ROM for testing so I have that loaded up on another FPGA board for that purpose.
You can though release Write Protect (actually, I don't think it is set at the moment) and write to the hub ROM.

The FPGA config is locked in after programming so you only ever have to do this once. But you do need to cycle power first time after configuration though. Your terminal can toggle DTR which will generate a reset through the PropPlug or ^G from PNut will reset the P2.

The moment I power up my FPGA I just type the two autobaud characters "> " + ESC ($3E,$20,$1B) and I am up and running in TAQOZ

I got it working and I think I figured out that one of the buttons on the Prop123-A9 board resets the P2. Now I'll wait for a TAQOZ document before doing any more playing. I can guess simple Forth commands but I won't be able to do anything with the P2 hardware without more docs.

I will add some simple examples right now to get you started.

Examples would be nice. Also, is there a doc that describes the hardware on the Prop123-A9 board? In other words, what onboard hardware is connected to P2 pins if any? In particular, is there a P2 pin connected to any of the LEDs or buttons?

On the Prop123-A9, latest image, the buttons PB3..1 connect to pin P55..57. PB0 is used as a reset button.
The red leds indicate which cogs are running. I guess you could use them as indicators by starting/stopping cogs.

I don't know if the WS2812B's are connected, I suspect not. I'm not sure what the green leds are connected to.

A question for @Cluso99, @Peter Jakacki, and/or @cgracey about the boot ROM. I just added some checking to fastspin for flags not being set in instructions like cmp (it's something I forget a lot), and got two warnings from ROM_137PBJ,spin2:

ROM_137PBJ.spin2:247: warning: instruction cmp used without flags being set
ROM_137PBJ.spin2:1019: warning: instruction cmp used without flags being set

Line 247 looks like a slightly tricky but legal re-use of _ret_ to save a long, so the warning there is probably spurious.
Line 1019 looks suspicious though; should that cmp have a "wz" on it to be used by the following "if_ne"?

Yep, line 1019 is an error. Thanks for picking this up.
I often forget the # on JMP/call/djnz etc. a warning would be nice here also. There is one case near Cmd_G where this is legit. It's commented to ensure it's this way.
When Brad wrote bst there was a warning option for the JMP/call/djnz and it picked up a few bugs in ZiCog.

Updated my Prop123-A9 to P2v32f and having a blast exploring the monitor and TAQOZ -- great work guys!

I've been trying to get SD card boot going but so far, no joy. If I read the notes correctly, the pin connections should be:

61 - CSn with external pull-up (10k)?
60 - CLK
59 - DO
58 - DI

The SD card (1GB) is formatted FAT32 with a single P2 .obj file named _BOOT_P2.BIX in the root dir. No load at boot, and using the monitor "R _BOOT_P2.BIX" cmd results in a "!" response. Does anyone with a Prop123-A9 have SD boot up and running?

Updated my Prop123-A9 to P2v32f and having a blast exploring the monitor and TAQOZ -- great work guys!

I've been trying to get SD card boot going but so far, no joy. If I read the notes correctly, the pin connections should be:

61 - CSn with external pull-up (10k)?
60 - CLK
59 - DO
58 - DI

The SD card (1GB) is formatted FAT32 with a single P2 .obj file named _BOOT_P2.BIX in the root dir. No load at boot, and using the monitor "R _BOOT_P2.BIX" cmd results in a "!" response. Does anyone with a Prop123-A9 have SD boot up and running?

Garry, Cluso forgot to mention that P59=DI and P58=DO for both SPI and SD.

I just updated the booter documention at the end of the Google Doc with two tables that show resistor settings and SPI/SD hookups:

Thanks! Besides having clk/cs wrong, I had an open pin->SD_DO connection :surprise:

Still no joy on the file load though. The file doesn't load/run at startup, but I can start the monitor. When I try the "R_BOOT_P2.BIX" command it hangs. I ran your "SD Test & Debugger v121a" program and its output showed MBR and DIR data that looked OK, so I'm not quite sure where to go from here. What's your usual procedure for preparing an SD card for use? It's a 1GB microSD with a single partition sized at ~500MB and FAT32 file system with the default 4KB cluster size. The P2 object file is the correct size (19,136 bytes), the data is contiguous, and was written from offset 0x102c00 to 0x1076c0 (sectors 2,070 to 2,107).

Chip,
Autobaud is not working at 4800 baud and below. Probably a timeout preventing it working as switching back to 9600 and above and entering "> " and Ctl-D works.
Not sure if you want it to work below 9600.

Here is a little demo to call some of the ROM routines.
It's purpose if for Garry to try and find why his SD card is not working.

Garry, compile and download this program using pnut. If your SD had been working and there was valid boot code, this program would not run. So you would need to insert the SD card after the "Demo.." message while the program stalls waiting for operator input. Once you hit enter, the program will try the SD card and report a couple of status points reached. Let me know where it fails please, and I will break it down some more.

All. The demo shows how to initialise and run a few of the Monitor Serial routines and also call the SD high level routines which is able to load and run a file from SD.

Tip: To avoid loading SD on power up, don't have files "_BOOT_P2.BIX" and "_BOOT_P2.BIY" on your SD card. This Demo will try to load a file "_BOOT_P2.BIZ" on the SD. You can test this works from the monitor using the run command.

Garry, compile and download this program using pnut. If your SD had been working and there was valid boot code, this program would not run. So you would need to insert the SD card after the "Demo.." message while the program stalls waiting for operator input. Once you hit enter, the program will try the SD card and report a couple of status points reached. Let me know where it fails please, and I will break it down some more.

Renamed the file to run to "_BOOT_P2.BIZ".
At the "Demo..." prompt I insert the SDCard then Enter and get:

Init passed
MBR passed
DIR passed

No further messages appear, so it looks like something may be going awry in the monitor #readFILE routine, as I assume that "File failed" should be output if the call had returned with an error status?