lliont wrote: Tue Nov 14, 2023 8:32 am
I'll add extra sound channels, a msec timer and potentially useful things like reading the current vertical line and I think that will be a good point to finalize the first version of the project.
Truly impressive! Thank you for continuing to develop this project!
If you haven't already nailed-down the future features, could I request a micro-second (1MHz) timer or even slightly more granular (say 4MHz) instead of milli-sec?
Having developed around Peter's Q68 HW timer/counter for the ND-Q68 driver (and also used it for a prototype MDV driver - MD-Q68), I find having access to a high-precision timer allows for some interesting developments that simply don't work reliably with SW timing loops alone - especially now we have a broader range of CPU clocks to programme for...
lliont wrote: Tue Nov 14, 2023 9:50 am
Sorry Peter I misunderstood from this post viewtopic.php?p=50846#p50846, and because for me the 144 is not that hard I assumed it will be relatively "easy" to solder the BGA too.
Ah that explains it! For me, handsoldering 144 pins of 0.5 mm pitch is not easy. I'm not saying you can not solder BGA. But you'd need experiments until you have a working process, PCB tricks and suitable equipment. Also the type of BGA case matters. In the end it might even be easy for you. But if I understand correctly, you don't offer series production, and BGA would not be a design a tinkerer could reproduce with reasonable effort.
lliont wrote: Tue Nov 14, 2023 9:50 am
here is a picture of my board:
Almost makes me wonder why there still is a 68008, if you reached such a high design complexity anyway.
Would be no rocket science to provide an 8 bit data bus for the FX68K core.
Well maybe I'll try the FX68k in the future although this core uses about 5K of the precious fpga sram and 5K LE so I would have to use a bigger fpga, maybe I can use the not cycle accurate TG68K that is much more lighter.
martyn_hill wrote: Tue Nov 14, 2023 11:16 am
If you haven't already nailed-down the future features, could I request a micro-second (1MHz) timer or even slightly more granular (say 4MHz) instead of milli-sec?
Pr0f wrote: Tue Nov 14, 2023 2:07 pm
I think the clue there is the forum title for this thread.
Why? The QL CPU is replaced by a faster one, which is far more than a ZX8301 replacement either way.
Apologies - no offence was meant - but I think he probably covers the addition of the faster CPU with the "and more"
...but I think the original direction seemed to be to offer a possible replacement for those that have suffered a dead ZX8301 - most of those that are left are pulled from QL's that have died. And this chip seems the most prone to being 'blown' by plugging / unplugging monitors when it's on.
long time no talk. Hope you are doing well? I have a more basic question,. Do you plan to make your development available to the community as a ready plug in board. Maybe to different version:
1. Just a basic ZX8301 replacement. No extras just the most simple one?
2. The most sophisticated version, with all the ad ons?
Pr0f wrote: Tue Nov 14, 2023 8:08 pm
...but I think the original direction seemed to be to offer a possible replacement for those that have suffered a dead ZX8301 - most of those that are left are pulled from QL's that have died.
Yes of course, that's a good thing. I wasn't saying I want a CPU in the design. But you may have noticed that the latest version includes a new CPU anyway. And then it could make sense to move it into the FPGA.
Maskenlos wrote: Tue Nov 14, 2023 8:42 pm
1. Just a basic ZX8301 replacement. No extras just the most simple one?
That would be my personal favorite.
lliont wrote: Tue Nov 14, 2023 4:16 pm
Well maybe I'll try the FX68k in the future although this core uses about 5K of the precious fpga sram and 5K LE so I would have to use a bigger fpga, maybe
Thanks for the explanation. Sorry I was not aware you're short of resources in the FPGA.