Chat
Welcome to Flux
Treat Flux like your intern. Tell it what you'd like to build and it'll get to work. You can also ask it questions, brainstorm ideas, and teach it your preferences. Learn More
Ready.
Reviews
Inspect
Environmental Lavender Flubber
Controls
Properties
Availability & Pricing
| Distributor | Qty 1 | |
|---|---|---|
| Digi-Key | $5.50 | |
| LCSC | $12.93 | |
| Mouser | $5.50 | |
Assets
Welcome 👋
Flux helps you build PCBs faster with an AI teammate!
Create your account to collaborate, stay updated, fork your own version, and get instant answers from our AI agent.
networkjarwy
copilot
~RESET~(the reset pin) to ESP32'sD4. This will allow you to reset the CPU using the ESP32.~INT~(Interrupt Request) and~NMI~(Non-Maskable Interrupt) to ESP32'sD5andD18respectively. You can drive these pins high to interrupt the Z80.~WAIT~signal to ESP32'sD19which can be used to pause Z80 operation when necessary.~RD~(Read),~WR~(Write),~MREQ~(Memory Request), and~IORQ~(I/O Request) should be controlled by ESP32 too. Connect them to ESP32'sD21,RX0,TX0andD22respectively.~BUSRQ~and~BUSACK~signals could be connected toD23andENof ESP32 to control direct Bus Request and acknowledge mechanisms.~CE(Chip Enable) toVPon the ESP32. This will allow you to enable or disable the EEPROM using the ESP32.~OE(Output Enable) toVNon ESP32 for controlling output enable-application of data from memory to the data bus.~WE(Write Enable) can be connected toD34of ESP32 to control data write operations to the EEPROM.networkjarwy
copilot
~CLK~pin of the Z80 (U1) to theD13pin of the ESP32 (U2), which is good for generating the clock signal.A0throughA12) and data lines (D0throughD7) are properly connected between U1 and U3.-
-
-
-
-
Other signals like
For EEPROM (U3):~RESET~: This may need to be driven high or low to reset the Z80 depending on your application need. You can connect a push button to it that, when pressed, ties the pin to GND. A pull up resistor to VCC should be added.~INT~and~NMI~: If you don't intend to use interrupt requests, both these pins should be tied high (to VCC) because they are active low signals.~WAIT~: If the Z80 doesn't need to be paused, this pin can also be tied high (to VCC).~BUSRQ~,~BUSACK~: If these signals are not used for external bus requests, they can be left unconnected, but again check the specific datasheet for actual instruction.~RD~,~WR~,~MREQ~,~IORQ~are essential signals for operation. These would normally connect to distinct memory or IO devices apart from the EEPROM. If there's no other devices, it should be okay to leave them unconnected.~CE: The Chip Enable pin can be tied to GND because it's an active low pin. Tying it to GND permanently enables the chip.~OE: Output Enable pin can be connected to the~RD~signal at the Z80. This would mean data is put on the data bus by EEPROM when a read signal is activated by Z80 CPU.~WE: Write Enable pin should be tied high if you're not planning to write into the EEPROM from Z80. If you aim to write into it at a later stage, consider connecting it to the~WR~signal from Z80 CPU.networkjarwy
copilot
~MREQ~(Memory Request) line is an active low control signal output by the Z80 (U1) to indicate when it's trying to perform a read or write operation with memory (as opposed to an I/O device).~MREQ~in combination with~RD~or~WR~to orchestrate read or write operations.~MREQ~line from the Z80 (U1) to the~CE(Chip Enable) line of the EEPROM (U3). This coupling can help manage the enabling of the chip. When~MREQ~is active (low), it indicates that a memory-related operation is being requested, so the EEPROM can be enabled (making~CEline low).~MREQ~on the Z80 (U1) to~CEon the EEPROM (U3)