Enaiel <ena...@gmail.com>: Jan 30 07:27PM -0800
Thanks 7alken and Ed Silky for your help. I scoured through GitHub and
cross-referenced datasheets to fix my symbols. I obsessively refined my
design for a year due to tariffs. I'm think I'm finally ready to send it
for production. I just have 20 ""Thermal relief connection to zone
incomplete" errors to fix in KiCad before I send it. Any tips on how to fix
these quickly?
Regards,
-Enaiel
On Tuesday, January 27, 2026 at 9:18:40 PM UTC-5 7alken wrote:
hi Enaiel, try to peek there for Johs schematics and boards also ... we
used all these;
https://github.com/Z80-Retro/2063-Z80
https://github.com/Z80-Retro
P.
On Monday, January 26, 2026 at 2:55:20 PM UTC+1 Enaiel wrote:
Hi all
I'm back to this project after a 1 year break due to tariffs. After
reviewing my schematics, I realized that many of the KiCad symbols I
downloaded from the internet have incorrectly numbered pins. Does anyone
have a KiCad symbol library with one or more of the following ICs that they
can share?
* Z80CPU
* AS6C4008
* SST39SF040
* Z80SIO/O
* DS1233
Additionally, a KiCad symbol for RCBus would be much appreciated.
Thanks,
-Enaiel
On Sunday, February 23, 2025 at 12:07:22 PM UTC-5 Enaiel wrote:
Hi Wayne
> Yes, using the MM_SBC memory manager w/ MPCL_RAM and MPCL_ROM set to the
same address would work fine for R---NNNN. That would allow you to bring
up your board with the existing RomWBW codebase.
I was able to compile and build a ROM image with this configuration, Now to
actually build the board and test it out.
> Ultimately, I would create a new memory manager for you that is more
optimized by avoiding the second port I/O.
That would be really awesome!
Thanks,
-Enaiel
On Monday, February 17, 2025 at 6:23:48 PM UTC-5 Wayne Warthen wrote:
Yes, using the MM_SBC memory manager w/ MPCL_RAM and MPCL_ROM set to the
same address would work fine for R---NNNN. That would allow you to bring
up your board with the existing RomWBW codebase.
Ultimately, I would create a new memory manager for you that is more
optimized by avoiding the second port I/O.
Thanks, Wayne
|