Loading 3D model… large boards can take a moment.
Contains KiCad footprints and symbols shared across multiple Neotron projects. It also contains example schematics for circuits we expect to see on most Neotron boards.
Power-on Reset sequencing, soft shutdown, voltage monitoring and PS/2 interfacing is handled by a separate STM32F0 SoC.
| Pin | Name | Signal | Function |
|---|---|---|---|
| 02 | PF0 | nBUTTON_PWR | Power Button Input (active low) |
| 03 | PF1 | nBUTTON_RST | Reset Button Input (active low) |
| 06 | PA0 | MON_3V3 | 3.3V rail monitor Input (1.65V nominal) |
| 07 | PA1 | MON_5V | 5.0V rail monitor Input (1.65V nominal) |
| 08 | PA2 | nSYS_RESET | Reset Output to reset the rest of the system |
| 09 | PA3 | DC_ON | PSU Enable Output |
| 10 | PA4 | SPI1_NSS | SPI Chip Select Input (active low) |
| 11 | PA5 | SPI1_SCK | SPI Clock Input |
| 12 | PA6 | SPI1_CIPO | SPI Data Output |
| 13 | PA7 | SPI1_COPI | SPI Data Input |
| 14 | PB0 | LED0 | PWM output for first Status LED |
| 15 | PB1 | LED1 | PWM output for second Status LED |
| 18 | PA8 | nHOST_IRQ | Interrupt Output to the Host (active low) |
| 19 | PA9 | USART1_TX | UART Transmit Output |
| 20 | PA10 | USART1_RX | UART Receive Input |
| 21 | PA11 | USART1_CTS | UART Clear-to-Send Output |
| 22 | PA12 | USART1_RTS | UART Ready-to-Receive Input |
| 23 | PA13 | SWDIO | SWD Progamming Data Input |
| 24 | PA14 | SWCLK | SWD Programming Clock Input |
| 25 | PA15 | PS2_CLK0 | Keyboard Clock Input |
| 26 | PB3 | PS2_CLK1 | Mouse Clock Input |
| 27 | PB4 | PS2_DAT0 | Keyboard Data Input |
| 28 | PB5 | PS2_DAT1 | Mouse Data Input |
| 29 | PB6 | I2C1_SCL | I²C Clock |
| 30 | PB7 | I2C1_SDA | I²C Data |
Note that in the above table, the UART signals labelled from the point of view of the BMC chip (i.e. UART_RX is an input to the BMC). The PS/2 signals are 5V open-collector, and so must be on 5V tolerant pins. Everything else runs at 3.3V.
This design should also be pin-compatible with the following SoCs (although the software may need recompiling with a different Peripheral Access Crate):
Note that not all STM32 pins are 5V-tolerant, and as noted above, the PS/2 pins are 5V open-collector. You must therefore ensure that whichever part you pick has 5V-tolerant pins (marked FT or FTt in the datasheet) for the PS/2 signals. All of the parts above should be OK, but they haven't been tested. Let us know if you try one!
The CPU can either be designed to solder direct to your particular motherboard design, or it can be fitted to a second PCB 'CPU card' which plugs into a socket on the motherboard. We have designed a special 80-pin socket pinout, which provides all the signals for required for the standard peripherals available in this design.
The socket is basically two 2x20 pin headers, placed 130 mil apart. This should give enough space to fit even a TQFP-176 microcontroller and some TSOP-54 SDRAM.
The pins are labelled in row.column fashion, i.e. 1.1 is top left, 1.20 is top right and 4.20 is bottom right.
+----- Pin 1.1
|
v
+---------------------------------------+
|o o o o o o o o o o o o o o o o o o o o|
|o o o o o o o o o o o o o o o o o o o o|
+---------------------------------------+
+---------------------------------------+
|o o o o o o o o o o o o o o o o o o o o|
|o o o o o o o o o o o o o o o o o o o o|
+---------------------------------------+
^
|
Pin 4.20 -----+
| Pin | Function |
|---|---|
| 1.1 | VGA_RED5 |
| 1.2 | VGA_RED4 |
| 1.3 | VGA_RED3 |
| 1.4 | VGA_RED2 |
| 1.5 | VGA_RED1 |
| 1.6 | VGA_RED0 |
| 1.7 | VGA_GREEN5 |
| 1.8 | VGA_GREEN4 |
| 1.9 | VGA_GREEN3 |
| 1.10 | VGA_GREEN2 |
| 1.11 | VGA_GREEN1 |
| 1.12 | VGA_GREEN0 |
| 1.13 | VGA_BLUE5 |
| 1.14 | VGA_BLUE4 |
| 1.15 | VGA_BLUE3 |
| 1.16 | VGA_BLUE2 |
| 1.17 | VGA_BLUE1 |
| 1.18 | VGA_BLUE0 |
| 1.19 | VGA_HSYNC |
| 1.20 | VGA_VSYNC |
| 2.1 | VGA_DDC_SDA |
| 2.2 | VGA_DDC_SCL |
| 2.3 | UART_RX |
| 2.4 | UART_TX |
| 2.7 | 3V3 |
| 2.8 | 3V3 |
| 2.9 | 3V3 |
| 2.10 | GND |
| 2.11 | GND |
| 2.12 | GND |
| 2.13 | AUDIO_BCLK_TO_CODEC |
| 2.14 | AUDIO_DAT_TO_CODEC |
| 2.15 | AUDIO_LR_TO_CODEC |
| 2.16 | AUDIO_DAT_FROM_CODEC |
| 2.17 | AUDIO_LR_FROM_CODEC |
| 2.18 | USB_EN |
| 2.19 | USB_D- |
| 2.20 | USB_D+ |
| 3.1 | I2C_SDA |
| 3.2 | I2C_SCL |
| 3.3 | UART_CTS |
| 3.4 | UART_RTS |
| 3.7 | GND |
| 3.8 | GND |
| 3.9 | GND |
| 3.10 | 5V |
| 3.11 | 5V |
| 3.12 | 5V |
| 3.13 | ~SPI_CS7 |
| 3.14 | ~SPI_CS6 |
| 3.15 | ~SPI_CS5 |
| 3.16 | ~SPI_CS4 |
| 3.17 | ~SPI_CS3 |
| 3.18 | ~SPI_CS2 |
| 3.19 | ~SPI_CS1 |
| 3.20 | ~SPI_CS0 |
| 4.1 | ~SDMMC_CARD_DETECT |
| 4.2 | ~SDMMC_WRITE_PROT |
| 4.3 | SDMMC_DAT2 |
| 4.4 | SDMMC_DAT3 |
| 4.5 | SDMMC_CMD |
| 4.6 | SDMMC_CLK |
| 4.7 | SDMMC_DAT0 |
| 4.8 | SDMMC_DAT1 |
| 4.9 | SPI_COPI |
| 4.10 | SPI_CIPO |
| 4.11 | SPI_CLK |
| 4.12 | ~RESET |
| 4.13 | ~IRQ7 |
| 4.14 | ~IRQ6 |
| 4.15 | ~IRQ5 |
| 4.16 | ~IRQ4 |
| 4.17 | ~IRQ3 |
| 4.18 | ~IRQ2 |
| 4.19 | ~IRQ1 |
| 4.20 | ~IRQ0 |
The (up-to) seven expansion sockets allow you to add on I²C or SPI based devices at a later date. Each provides a single chip-select and a single IRQ line - the motherboard design should ensure each socket gets a unique signal for each of these. Each expansion device should also contain a AT24C256 or similar EEPROM device. To allow these EEPROM devices to be scanned, each slot also contains three EEPROM_ADDRESS pins, tied to Vcc or GND in a unique combination. These should be connected through to the EEPROM address lines on your AT24C256, thus ensuring that each expansion card has its EEPROM at a unique address - 0x50 on Slot 0 through to a maximum possible 0x57 for Slot 7. Where your board has on-board devices, you should fit an AT24C256 EEPROM for each device so that the on-board devices can be discovered, exactly as if they were on an expansion card.
The expansion slot is a simple 2x10 header. We suggest the use of a TE card-edge connector, but you could equally use two 1x10 pin-headers if desired.
The pin functions are:
SPI_COPI 1 2 GND
SPI_CIPO 3 4 GND
SPI_CLK 5 6 GND
~SPI_CS 7 8 ~IRQ
I2C_SDA 9 10 I2C_SCL
EEPROM_ADDR0 11 12 EEPROM_ADDR1
EEPROM_ADDR2 13 14 ~RESET
5V 15 16 5V
3V3 17 18 3V3
GND 19 20 GND
There are symbols and footprints for the mainboard side (card-edge socket, supplies power), and the expansion card side (golden-finger edge connector, receives power).
Why not design and build your own expansion card? You could try designing:
See CHANGELOG.md for a list of detailed changes.
We recommend you have the following Git config set:
$ git config --global filter.kicad_project.clean "sed -E 's/^update=.*$/update=Date/'"
$ git config --global filter.kicad_project.smudge cat
$ git config --global filter.kicad_sch.clean "sed -E 's/#(PWR|FLG)[0-9]+/#\1?/'"
$ git config --global filter.kicad_sch.smudge cat
See https://jnavila.github.io/plotkicadsch/ for details.
This project treats a PCB like embedded firmware:
./Kicad)We do not check build outputs into this repository - ever. Instead, we run a Github Action which uses KiBot to generate our outputs. On a regular Pull Request, the build outputs are stored as artefacts against the particular Github Action run. When a new version is tagged, the build outputs are stored as files against a Github Release.
Of course, the PCB in this project isn't useful by itself - it's a starting point for your project. You should probably include this repo as a Git Submodule, and add the symbol library and footprint library to your own KiCAD project.
You can build locally using the KiBot docker container:
~/Neotron-Common-Hardware $ docker run --rm -ti -v $(pwd):/work setsoft/kicad_auto:dev_k6
root@12345678:/# cd /work/Kicad
root@12345678:/work/Kicad# kibot -c docs.kibot.yml -e Neotron-Common-Hardware.kicad_sch -b Neotron-Common-Hardware.kicad_pcb -d docs
This will build everything and put it in the ./Kicad/docs directory. Note there is a bug in KiCAD 6.0.8 and 6.0.9 which fails ERC looking at our hierarchical sheets. This is fixed in 6.0.10, or you can use the setsoft/kicad_auto:ki6.0.7_Debian container.
This schematic and PCB design is Copyright (c) The Neotron Developers.
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be licensed as above, without any additional terms or conditions.
No comments yet. Be the first to ask about this board.