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

Explain project
Write a project description
Find schematic issues
Create a test plan
Simulate a circuit
Prepare for Manufacturing
Component Selection Workflow
New Subsystem Wizard

Ready.


where to connect the other pins?

@copilot where to connect the other pins?
2y
To proceed with completing the connection of the rest of the pins, we need to establish the function of the project. Here, we're dealing with a Z80 CPU (U1), an ESP32 devkit (U2), and an AT28C64B EEPROM (U3). One common utilization scenario could be using the ESP32 to upload programs to the Z80 through the EEPROM. If that's the case, we'll have to set up the connection appropriately.
Making the assumption that you want to keep the GPIOs of ESP32 as flexible as possible, I recommend using some GPIOs for connecting to the control pins of Z80 and EEPROM to operate them properly like controlling program read/write.
Let's see how we can connect various control and data lines.
For Z80 CPU (U1), Here are the additional connections you might need to make:
  • Connect ~RESET~ (the reset pin) to ESP32's D4. This will allow you to reset the CPU using the ESP32.
  • Connect ~INT~ (Interrupt Request) and ~NMI~ (Non-Maskable Interrupt) to ESP32's D5 and D18 respectively. You can drive these pins high to interrupt the Z80.
  • Connect ~WAIT~ signal to ESP32's D19 which can be used to pause Z80 operation when necessary.
  • Other control signals like ~RD~ (Read), ~WR~ (Write), ~MREQ~ (Memory Request), and ~IORQ~ (I/O Request) should be controlled by ESP32 too. Connect them to ESP32's D21, RX0, TX0 and D22 respectively.
  • Also, ~BUSRQ~ and ~BUSACK~ signals could be connected to D23 and EN of ESP32 to control direct Bus Request and acknowledge mechanisms.
For EEPROM (U3):
  • Connect ~CE (Chip Enable) to VP on the ESP32. This will allow you to enable or disable the EEPROM using the ESP32.
  • Connect ~OE (Output Enable) to VN on ESP32 for controlling output enable-application of data from memory to the data bus.
  • ~WE (Write Enable) can be connected to D34 of ESP32 to control data write operations to the EEPROM.
Remember, these are just suggestions. It would be better to follow specific interfacing requirements from Z80 and ESP32 documentation and your application requirements.
Also, if any connections mentioned above conflict with the existing Nets in your project, please do rearrange these as per your convenience and requirement.
2y
ESP32 is there only to generate clock signal to clock pin on z80
2y
Ah, I see. If the ESP32 is only there to generate the clock signal for the Z80, then most of its pins can be left unconnected. You've already connected the ~CLK~ pin of the Z80 (U1) to the D13 pin of the ESP32 (U2), which is good for generating the clock signal.
The Z80 CPU (U1) and EEPROM (U3) connections seem to be complete for a basic operation where the Z80 would fetch instructions from the EEPROM. The address lines (A0 through A12) and data lines (D0 through D7) are properly connected between U1 and U3.
Nonetheless, there are some control signals that need to be addressed for both U1 and U3. For instance:
For Z80 (U1):
  • ~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.
  • Other signals like ~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.
For EEPROM (U3):
  • ~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.
Remember to check the specific datasheets of the components to see the effect of these signals and how they should be handled when not in use, as some signals can be left unconnected, others must be tied to VCC or GND.
Plus, you might need some additional components (e.g. decoupling capacitors near the power supply pins) to assure stability. Please account for them in your design.
2y
what about memory request on the z80?
2y
The ~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).
If the Z80 is only interacting with the EEPROM (U3) as its memory, there is no need for additional connections. However, if there were additional memory or peripheral devices, you would use ~MREQ~ in combination with ~RD~ or ~WR~ to orchestrate read or write operations.
You can consider connecting the ~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 ~CE line low).
Let's state it more formally:
  • Connect ~MREQ~ on the Z80 (U1) to ~CE on the EEPROM (U3)
Before you perform this step, make sure to study the datasheets of your components carefully to ensure that these operations are compatible with your memory modules and overall system design.
2y
How to connect other pins?

@copilot How to connect other pins?
2y
Based on the provided schematic connections, I can see that both memory and data address pins of the components are already connected, as well as power and ground. If you're looking to use more functionalities from your components, here are some suggestions:
ESP32-DEVKIT-V1 (U2) You can consider using the IO pins (D2, D4, D5, D15, D18, D19, D21, D22, D23, D25, D26, D27, D32, D33, D34, D35, RX2, TX2) for peripherals and there are possibilities for implementing communication protocols like SPI, I2C, or UART if needed[1].
However, note that you need to take care to avoid the strapping pins (EN, VP, and VN) at power-on because these pins are used to determine the boot mode of the module. These pins must be at certain logic levels upon startup.
Also, remember that some pins are dedicated to flash/PSRAM communication and should not be used for other purposes.
Z80 CPU (U1) For the Z80, there are some control signals that might be useful depending on your application:
  • RESET: You'd attach a digital signal that, when brought low, resets the Z80's internal registers and ceases all operations,
  • WAIT: You can use this pin to insert wait states into the Z80's memory access cycles,
  • INT and NMI: You can use these pins to attach interrupt-triggering signals,
  • BUSRQ/BUSACK: You can use these for processes that require direct access to the data or address buses of the CPU (DMA operations for instance).
AT28C64B-15PU (U3) For the EEPROM you might want to consider connecting the pin WE to activate the write enable[2].
Some of your ESP32 DEVKIT V1 are still disconnected. However, before proceeding to the connection of the extra pins, you need to clarify the functionality you want to add to your design, as the pins should be connected according to the desired functionality.
[2] Page 2
2y
2
U2
U1


  • Ground
    A common return path for electric current. Commonly known as ground.
  • Net Portal
    Wirelessly connects nets on schematic. Used to organize schematics and separate functional blocks. To wirelessly connect net portals, give them same designator. #portal
  • Power Net Portal
    Wirelessly connects power nets on schematic. Identical to the net portal, but with a power symbol. Used to organize schematics and separate functional blocks. To wirelessly connect power net portals, give them the same designator. #portal #power
  • Generic Resistor
    A generic fixed resistor for rapid developing circuit topology. Save precious design time by seamlessly add more information to this part (value, footprint, etc.) as it becomes available. Standard resistor values: 1.0Ω 10Ω 100Ω 1.0kΩ 10kΩ 100kΩ 1.0MΩ 1.1Ω 11Ω 110Ω 1.1kΩ 11kΩ 110kΩ 1.1MΩ 1.2Ω 12Ω 120Ω 1.2kΩ 12kΩ 120kΩ 1.2MΩ 1.3Ω 13Ω 130Ω 1.3kΩ 13kΩ 130kΩ 1.3MΩ 1.5Ω 15Ω 150Ω 1.5kΩ 15kΩ 150kΩ 1.5MΩ 1.6Ω 16Ω 160Ω 1.6kΩ 16kΩ 160kΩ 1.6MΩ 1.8Ω 18Ω 180Ω 1.8KΩ 18kΩ 180kΩ 1.8MΩ 2.0Ω 20Ω 200Ω 2.0kΩ 20kΩ 200kΩ 2.0MΩ 2.2Ω 22Ω 220Ω 2.2kΩ 22kΩ 220kΩ 2.2MΩ 2.4Ω 24Ω 240Ω 2.4kΩ 24kΩ 240kΩ 2.4MΩ 2.7Ω 27Ω 270Ω 2.7kΩ 27kΩ 270kΩ 2.7MΩ 3.0Ω 30Ω 300Ω 3.0KΩ 30KΩ 300KΩ 3.0MΩ 3.3Ω 33Ω 330Ω 3.3kΩ 33kΩ 330kΩ 3.3MΩ 3.6Ω 36Ω 360Ω 3.6kΩ 36kΩ 360kΩ 3.6MΩ 3.9Ω 39Ω 390Ω 3.9kΩ 39kΩ 390kΩ 3.9MΩ 4.3Ω 43Ω 430Ω 4.3kΩ 43KΩ 430KΩ 4.3MΩ 4.7Ω 47Ω 470Ω 4.7kΩ 47kΩ 470kΩ 4.7MΩ 5.1Ω 51Ω 510Ω 5.1kΩ 51kΩ 510kΩ 5.1MΩ 5.6Ω 56Ω 560Ω 5.6kΩ 56kΩ 560kΩ 5.6MΩ 6.2Ω 62Ω 620Ω 6.2kΩ 62KΩ 620KΩ 6.2MΩ 6.8Ω 68Ω 680Ω 6.8kΩ 68kΩ 680kΩ 6.8MΩ 7.5Ω 75Ω 750Ω 7.5kΩ 75kΩ 750kΩ 7.5MΩ 8.2Ω 82Ω 820Ω 8.2kΩ 82kΩ 820kΩ 8.2MΩ 9.1Ω 91Ω 910Ω 9.1kΩ 91kΩ 910kΩ 9.1MΩ #generics #CommonPartsLibrary
  • Generic Capacitor
    A generic fixed capacitor ideal for rapid circuit topology development. You can choose between polarized and non-polarized types, its symbol and the footprint will automatically adapt based on your selection. Supported options include standard SMD sizes for ceramic capacitors (e.g., 0402, 0603, 0805), SMD sizes for aluminum electrolytic capacitors, and through-hole footprints for polarized capacitors. Save precious design time by seamlessly add more information to this part (value, footprint, etc.) as it becomes available. Standard capacitor values: 1.0pF 10pF 100pF 1000pF 0.01uF 0.1uF 1.0uF 10uF 100uF 1000uF 10,000uF 1.1pF 11pF 110pF 1100pF 1.2pF 12pF 120pF 1200pF 1.3pF 13pF 130pF 1300pF 1.5pF 15pF 150pF 1500pF 0.015uF 0.15uF 1.5uF 15uF 150uF 1500uF 1.6pF 16pF 160pF 1600pF 1.8pF 18pF 180pF 1800pF 2.0pF 20pF 200pF 2000pF 2.2pF 22pF 20pF 2200pF 0.022uF 0.22uF 2.2uF 22uF 220uF 2200uF 2.4pF 24pF 240pF 2400pF 2.7pF 27pF 270pF 2700pF 3.0pF 30pF 300pF 3000pF 3.3pF 33pF 330pF 3300pF 0.033uF 0.33uF 3.3uF 33uF 330uF 3300uF 3.6pF 36pF 360pF 3600pF 3.9pF 39pF 390pF 3900pF 4.3pF 43pF 430pF 4300pF 4.7pF 47pF 470pF 4700pF 0.047uF 0.47uF 4.7uF 47uF 470uF 4700uF 5.1pF 51pF 510pF 5100pF 5.6pF 56pF 560pF 5600pF 6.2pF 62pF 620pF 6200pF 6.8pF 68pF 680pF 6800pF 0.068uF 0.68uF 6.8uF 68uF 680uF 6800uF 7.5pF 75pF 750pF 7500pF 8.2pF 82pF 820pF 8200pF 9.1pF 91pF 910pF 9100pF #generics #CommonPartsLibrary
  • Generic Inductor
    A generic fixed inductor for rapid developing circuit topology. *You can now change the footprint and 3D model at the top level anytime you want. This is the power of #generics
  • Terminal
    Terminal
    An electrical connector acting as reusable interface to a conductor and creating a point where external circuits can be connected.
  • RMCF0805JT47K0
    47 kOhms ±5% 0.125W, 1/8W Chip Resistor 0805 (2012 Metric) Automotive AEC-Q200 Thick Film #forLedBlink
  • 875105359001
    10uF Capacitor Aluminum Polymer 20% 16V SMD 5x5.3mm #forLedBlink #commonpartslibrary #capacitor #aluminumpolymer #radialcan
  • CTL1206FYW1T
    Yellow 595nm LED Indication - Discrete 1.7V 1206 (3216 Metric) #forLedBlink

Inspect

Environmental Lavender Flubber

Environmental Lavender Flubber
Description

Created
Last updated by networkjarwy
1 Contributor(s)
networkjarwy

Controls

Properties

Availability & Pricing

DistributorQty 1
Digi-Key$5.50
LCSC$12.93
Mouser$5.50

Assets