What it is not designed to do:
Of course the gotcha here is that I've totally no experience writing Propeller assembly language.
But in 2017 it was the same for Z80. How hard can it be?
So this is a bit of a meaty longer term project.
Anyway, the hardware design is now done, and I'm about to hit up Seeed to get a PCB Built.
If anyone wants a PCB to experiment (particularly if you're in Australia/NZ) let me know.
In Northern Hemisphere, if you're interested drop me a note and I'll send you the Gerbers.
Enjoy, Phillip
Il 24/09/20 09:40, Phillip Stevens ha scritto:
Had only a quick look at the schematic and pcb, just a note: be sure to
have a bypass capacitor on both power pins otherwise the internal PLL
may be damaged.
> Have you done a "modern" vector graphics kind of interface previously? I'm
> thinking something like the FTDI EVE FT800 graphics devices. That style of
> GPU is perfect to implement with the Propeller, as there is no frame store
> needed, but rather a vector instruction store that holds information so the
> scan line can be generated dynamically just before it is displayed.
No, but this thread on the Parallax forum looks interesting.
http://forums.parallax.com/discussion/171856/wip-beam-chasing-polygon-rasterizer
Had only a quick look at the schematic and pcb, just a note: be sure to
have a bypass capacitor on both power pins otherwise the internal PLL
may be damaged.Marco, thanks. You must be reading my mind...I spent 15 minutes (literally) looking at that capacitor, wondering whether it was needed, or not.I was going to ask, but you've given me the answer already.
Since the EEPROM address (0xA0) is hardcoded into the Propeller ROM boot-loader, something needed to change.
P.
--
You received this message because you are subscribed to the Google Groups "RC2014-Z80" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rc2014-z80+...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rc2014-z80/949658b7-f293-40bb-b35a-489b49f3941bo%40googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rc2014-z80/CALc%3DYoO7ivc56gObnNdTyF-39R4kGACjM-0HKpBLfh%2BMeTZBhQ%40mail.gmail.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rc2014-z80/CANDE_bm7FHQpv_6%3DCcAcobQdZZV2EkQxTKMCuYu66BkU%2BG0B7A%40mail.gmail.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rc2014-z80/CANDE_bm7FHQpv_6%3DCcAcobQdZZV2EkQxTKMCuYu66BkU%2BG0B7A%40mail.gmail.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rc2014-z80/CALc%3DYoNxGJNDw3kztn6-150Lva8TLwABM%2BOXNVixAQzyhK%3DdSQ%40mail.gmail.com.
Phil, nice module!
I have several of Marco's terminal module which I am very pleased with.What is the difference between your and Marco's module?The PS2 keyboard connector is obvious, but I am thinking more on the software part?
You may find some useful code in the RetroComp PropIO V2 project found at https://www.retrobrewcomputers.org/doku.php?id=boards:ecb:propio:start
This board is supported by RomWBW, but interfaces directlly via the bus (does not emulate ACIA, SIO, etc.).
Regardless, you will find some decent code for VT100 terminal emulation as well as screen and keyboard interface examples for the Propeller.
Following a short intermission, the UX Module has been assembled, and passed the smoke test and it also produced a "Hello World".This means that the FTDI serial interface, I2C EEPROM, Oscillator, and 3V3 power supply are all working as expected.The rest, as they say, is "just software".
This is 640x480 demo (squashed onto a shared screen with my workstation.
It is using the internal font stored as part of the system ROM, so there is no need to fill the user ROM with additional fonts.
I've got a VGA->HDMI adapter from Vention on AliExpress. It works as expected (which is lucky).
Because this first module was for testing, I left the resistors on the VGA outpu standing proud a little.
This makes hooking test probes easier.
Now, to take a step back and work out how these pieces will play nicely together.
P.
Following a short intermission, the UX Module has been assembled, and passed the smoke test and it also produced a "Hello World".This means that the FTDI serial interface, I2C EEPROM, Oscillator, and 3V3 power supply are all working as expected.The rest, as they say, is "just software".
You may want to check out the !WAIT circuit on Wayne's board. I believe it was added because the PROP could not respond fast enough...(Wayne please correct me if I am wrong)...
You may want to check out the !WAIT circuit on Wayne's board. I believe it was added because the PROP could not respond fast enough...(Wayne please correct me if I am wrong)...
Colin, you are correct. The PropIO v1 did not have the !WAIT circuit and could only handle CPU speeds of about 6MHz. The new !WAIT circuit (on PropIO v2) is effective up to about 16MHz in my testing.