zapta / pio_tft

A library to interface a TFT to a Pico RP2040 using PIO and a parallel data path.
The Unlicense
40 stars 6 forks source link

16bit 8080 #3

Open WanaGo opened 5 months ago

WanaGo commented 5 months ago

Hi, Just wondering if there is a limitation to 8bit MCU 8080 for a display, or if its possible to expand this to 16bit 8080 too? Just curious if you encountered a limitation and stuck with 8bit only for a reason etc Thanks

zapta commented 5 months ago

If I recall correctly it was a matter of pin availability on the PIco. I think that the Pico's PIO requires the 16 bits to be specific pins which in my application conflicted with other pins I needed. Not 100% sure though, it was some time ago.

On Thu, Feb 22, 2024 at 6:09 PM James @.***> wrote:

Hi, Just wondering if there is a limitation to 8bit MCU 8080 for a display, or if its possible to expand this to 16bit 8080 too? Just curious if you encountered a limitation and stuck with 8bit only for a reason etc Thanks

— Reply to this email directly, view it on GitHub https://github.com/zapta/pio_tft/issues/3, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAQVMQKUR57OZ35TRDBXHQTYU725PAVCNFSM6AAAAABDV7NWF2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGE2TAMRUHEZTSMQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

bdbarnett commented 5 months ago

@WanaGo Sorry I just saw your message. I don't have a 16-bit 8080 to test with. I wrote _i80bus.py so that it SHOULD work for 16 pins with a couple of modifications.

It's worth a shot. If you try it, will you please let me know whether it works for you?