This is the multi-page printable view of this section. Click here to print.
konsool hardware
- 1: Konsool specifications
- 1.1: Konsool battery
- 1.2: Konsool ESP-C6
- 1.3: Konsool ESP-P4
- 1.4: Konsool keyboard
- 1.5: Konsool screen
- 2: Konsool connectors
- 2.1: Konsool pinouts
- 2.1.1: ESP32-P4 pinout
- 2.1.2: Internal expansion port
- 3: Konsool expansion boards
- 4: Frontpanel
- 4.1: Konsool artwork
1 - Konsool specifications
#Main Processor ESP32 P4 400 MHz dual core 32MB PSRAM 16MB Flash Storage
#Radio Modules ESP32 C6 WiFi, Bluetooth, ZigBee Ai-Thinker Ra-01S(H)
#I/O CH32V003
#Display 800x480 MIPI-DSI display
#Battery Lithium polymer
#Connections and expansions Headphone jack Expansion ports on the side and back USB-A (Host) USB-C (Charging) (work in progress, please check this page again later)
1.1 - Konsool battery
1.2 - Konsool ESP-C6
specsheet for ESP-C6, to be reworked into better specification page https://www.espressif.com/sites/default/files/documentation/esp32-c6_datasheet_en.pdf
1.3 - Konsool ESP-P4
#Specifications
To Be added, not yet available from Espressif
1.4 - Konsool keyboard
#Specifications
QWERTY dome keyboard by Arturo
1.5 - Konsool screen
2 - Konsool connectors
2.1 - Konsool pinouts
In this section you can find the pinout of the chips and connectors of the device.
Chips
Connectors
2.1.1 - ESP32-P4 pinout
ESP32-P4 (U8)
LDO
Pin number | Pin name | Pin net |
---|---|---|
71 | VFB/VO1 | VFLASH |
72 | VFB/VO2 | VPSRAM |
73 | VFB/VO3 | VMIPI |
74 | VFB/VO4 | VSDCARD |
GPIO
GPIO | Direction / Bus | Function | Note |
---|---|---|---|
0 | User controlled | Internal Add-On: E2 | |
1 | Output | Camera GPIO 1 / LED enable | |
2 | User controlled | JTAG: MTCK, PMOD: IO | Can be used as JTAG interface or as generic GPIO on the external Add-On connector |
3 | User controlled | JTAG: MTDI, PMOD: IO | Can be used as JTAG interface or as generic GPIO on the external Add-On connector |
4 | User controlled | JTAG: MTMS, PMOD: IO | Can be used as JTAG interface or as generic GPIO on the external Add-On connector |
5 | User controlled | JTAG: MTDO, PMOD: IO | Can be used as JTAG interface or as generic GPIO on the external Add-On connector |
6 | Input | Interrupt from CH32V203 coprocessor | Read from the coprocessor I2C device to clear the interrupt condition |
7 | Input / User controlled | Interrupt from internal Add-On board | Can also be used as GPIO, depending on the needs of the internal Add-On board |
8 | Input | Interrupt from ESP32-C6 radio | Controlled by ESP-HOSTED component |
9 | I2C bus SDA | Internal I2C bus data | Internal I2C bus connecting the ESP32-P4 to the ESP32-C6, CH32V203 coprocessor, Bosch sensors and internal Add-On board |
10 | I2C bus SCL | Internal I2C bus clock | Internal I2C bus connecting the ESP32-P4 to the ESP32-C6, CH32V203 coprocessor, Bosch sensors and internal Add-On board |
11 | Input | LCD TE (Tearing effect) | Synchronization pin for frame sync, used to avoid tearing |
12 | User controlled | SAO: I2C SDA, PMOD: IO | Can be used as I2C interface for SAO Add-On boards or as generic GPIO on the external Add-On connector |
13 | User controlled | SAO: I2C SCL, PMOD: IO | Can be used as I2C interface for SAO Add-On boards or as generic GPIO on the external Add-On connector |
14 | Output | LCD reset | Hardware reset for the LCD controller |
15 | User controlled | SAO: IO1, PMOD: IO | Can be used as generic GPIO for SAO Add-On boards or as generic GPIO on the external Add-On connector |
16 | SDIO 2.0 | SDIO bus for ESP32-C6: CMD | Controlled by ESP-HOSTED component |
17 | SDIO 2.0 | SDIO bus for ESP32-C6: CLK | Controlled by ESP-HOSTED component |
18 | SDIO 2.0 | SDIO bus for ESP32-C6: D0 | Controlled by ESP-HOSTED component |
19 | SDIO 2.0 | SDIO bus for ESP32-C6: D1 | Controlled by ESP-HOSTED component |
20 | SDIO 2.0 | SDIO bus for ESP32-C6: D2 | Controlled by ESP-HOSTED component |
21 | SDIO 2.0 | SDIO bus for ESP32-C6: D3 | Controlled by ESP-HOSTED component |
22 | Bidirectional | CH32V203 programming interface: SWDIO | For coprocessor firmware updates |
23 | Output | CH32V203 programming interface: SWCLK | For coprocessor firmware updates |
24 | USB | USB DN, port 1 on USB hub (USB-C port) | |
25 | USB | USB DP, port 1 on USB hub (USB-C port) | |
26 | User controlled | Internal Add-On: USB DN or generic GPIO | |
27 | User controlled | Internal Add-On: USB DP or generic GPIO | |
28 | I2S | I2S: data | |
29 | I2S | I2S: sample clock | |
30 | I2S | I2S: master clock | |
31 | I2S | I2S: lr clock | |
32 | I3C | I2C/I3C QWIIC port: SDA | |
33 | I3C | I2C/I3C QWIIC port: SCL | |
34 | User controlled | SAO: IO2, PMOD: IO | |
35 | User controlled | Internal Add-On: E1 | |
36 | User controlled | Internal Add-On: E0 | |
37 | Output / User controlled | Debug UART transmit | |
38 | Input / User controlled | Debug UART receive | |
39 | SDIO 3.0 | SD card slot: D0 | |
40 | SDIO 3.0 | SD card slot: D1 | |
41 | SDIO 3.0 | SD card slot: D2 | |
42 | SDIO 3.0 | SD card slot: D3 | |
43 | SDIO 3.0 | SD card slot: CLK | |
44 | SDIO 3.0 | SD card slot: CMD | |
45 | User controlled | Internal Add-On: E3 | |
46 | User controlled | Internal Add-On: E6 | |
47 | User controlled | Internal Add-On: E5 | |
48 | User controlled | Internal Add-On: E4 | |
49 | User controlled | Internal Add-On: E7 | |
50 | User controlled | Internal Add-On: E8 | |
51 | User controlled | Internal Add-On: E9 | |
52 | User controlled | Internal Add-On: E10 | |
53 | User controlled | Internal Add-On: E11 | |
54 | User controlled | Internal Add-On: E12 |
2.1.2 - Internal expansion port
Internal expansion port
Pin | Type | Power domain | Maximum current | Name | P4 GPIO | Function |
---|---|---|---|---|---|---|
1 | Power | VOTG | 1A | VOTG | - | Supply rail of the USB-A plug, provides 5 volt if OTG boost is enabled or voltage of VSYS when OTG boost is disabled |
2 | USB | USB-C VBUS | - | HUB_USB1_P | - | USB port 4 on the internal USB hub, allows add-ons to make a device available to the host PC via the USB-C port |
3 | Power | VBATT (~3.7v) | 1A | VBATT | - | Direct connection to the Lithium Polymer battery, can also be used to supply current to the device if (AND ONLY IF) there is no battery connected to the battery connector |
4 | USB | 3.3v | - | HUB_USB1_N | - | USB port 4 on the internal USB hub, allows add-ons to make a device available to the host PC via the USB-C port |
5 | Power | VSYS (~3.7-5v) | 1A | VSYS | - | Same as VBATT but switched by the PMIC, turns off when the device is turned off via the soft power on/off feature |
6 | Power | GND | - | GND | - | Ground, voltage reference for all supply rails |
7 | Power | GND | - | GND | - | Ground, voltage reference for all supply rails |
8 | Power | 3.3v | 1A | +3.3V | - | Regulated 3.3v rail |
9 | I2C | 3.3v | 40mA source, 28mA sink | INT_SCL | 10 | Internal I2C bus SCL signal, can only be used for I2C communication. We recommend connecting an EEPROM for add-on identification to this bus |
10 | I2C | 3.3v | 40mA source, 28mA sink | INT_SDA | 9 | Internal I2C bus SDA signal, can only be used for I2C communication. We recommend connecting an EEPROM for add-on identification to this bus |
11 | GPIO | 3.3v | 40mA source, 28mA sink | E0 | 36 | GPIO, needs to remain HIGH level (4.7k pull-up on the mainboard) for USB firmware download boot option to function |
12 | GPIO | 3.3v | 40mA source, 28mA sink | E2 | 0 | GPIO |
13 | Power | VSDCARD | 50mA | VSDCARD | - | Supply rail for the micro SD card socket and some GPIO pins, can either be off, 3.3v or 1.8v depending on card type and communication speed and configuration in software |
14 | GPIO | VSDCARD | 40mA source, 28mA sink (limited by supply rail) | E3 | 45 | GPIO, uses VSDCARD supply rail! |
15 | GPIO | VSDCARD | 40mA source, 28mA sink (limited by supply rail) | E4 | 48 | GPIO, uses VSDCARD supply rail! |
16 | GPIO | VSDCARD | 40mA source, 28mA sink (limited by supply rail) | E5 | 47 | GPIO, uses VSDCARD supply rail! |
17 | GPIO | VSDCARD | 40mA source, 28mA sink (limited by supply rail) | E6 | 46 | GPIO, uses VSDCARD supply rail! |
18 | GPIO | 3.3v | 40mA source, 28mA sink | EXT_INT | 7 | GPIO, connected to GPIO in low power domain: can be used to wake up the ESP32-P4 from deep sleep, if the add-on requires an interrupt pin we recommend connecting it here, otherwise this pin can be used like any other GPIO |
19 | GPIO | 3.3v | 40mA source, 28mA sink | E12 | 54 | GPIO |
20 | GPIO | 3.3v | 40mA source, 28mA sink | E7 | 49 | GPIO |
21 | GPIO | 3.3v | 40mA source, 28mA sink | E11 | 53 | GPIO |
22 | GPIO | 3.3v | 40mA source, 28mA sink | EXT_USB_P | 27 | GPIO, USB full-speed PHY D+: can be used as either normal GPIO or to connect an USB device to the ESP32-P4 |
23 | GPIO | 3.3v | 40mA source, 28mA sink | E10 | 52 | GPIO |
24 | GPIO | 3.3v | 40mA source, 28mA sink | EXT_USB_N | 26 | GPIO, USB full-speed PHY D-: can be used as either normal GPIO or to connect an USB device to the ESP32-P4 |
25 | GPIO | 3.3v | 40mA source, 28mA sink | E9 | 51 | GPIO |
26 | GPIO | 3.3v | 40mA source, 28mA sink | P4_TX | 37 | GPIO |
27 | GPIO | 3.3v | 40mA source, 28mA sink | E8 | 50 | GPIO |
28 | GPIO | 3.3v | 40mA source, 28mA sink | P4_RX | 38 | GPIO |
29 | GPIO | 3.3v | 40mA source, 28mA sink | I2S_MCLK | 30 | GPIO |
30 | GPIO | 3.3v | 40mA source, 28mA sink | I2S_LRCK | 31 | GPIO |
31 | GPIO | 3.3v | 40mA source, 28mA sink | I2S_DATA | 28 | GPIO |
32 | GPIO | 3.3v | 40mA source, 28mA sink | I2S_SCLK | 29 | GPIO |
33 | Power | 3.3v | 1A | +3.3V | - | Regulated 3.3v rail |
34 | GPIO | 3.3v | 40mA source, 28mA sink | I3C_SDA | 33 | GPIO, connected to the QWIIC connector, I3C peripheral SDA pin |
35 | Power | GND | - | GND | - | Ground, voltage reference for all supply rails |
36 | GPIO | 3.3v | 40mA source, 28mA sink | I3C_SCL | 32 | GPIO, connected to the QWIIC connector, I3C peripheral SCL pin |
Limitations & warnings
- Total for all 3.3v outputs must not exceed 1A of current. It is generally adviced to stay well below this figure.
- VSDCARD power rail can supply at most 100mA total to both the SD card and the expansion header.
- Do not exceed a current of 1A from or to the battery when the battery is connected to the internal battery connector.
3 - Konsool expansion boards
#
##Specs
##use-case
(work in progress, please check this page again later)
4 - Frontpanel
This page describes how to design and order a Konsool badge frontpanel.
Designing a frontpanel using Inkscape, svg2shenzhen and Kicad
The first step of designing a frontpanel is creating artwork that can be converted into a Kicad footprint. For this Inkscape and the Inkscape plugin svg2shenzhen are used.
Of course it is also possible to use any other method which allows you to import a footprint into Kicad so if you’re using a different method then you can skip ahead to the Kicad section.
Instructions on how to install svg2shenzhen can be found in the readme of the repository.
After opening the design file in Inkscape you will notice that multiple layers are used. Each of the layers in the design corresponds with a Kicad layer, this allows you to define how a shape should appear on the circuit board.
The most important layers are:
- Edge.Cuts: this is the outline of the board, the PCB manufacturer will use a CNC mill to cut the board following the edges of the object on this layer.
- F.Cu and B.Cu: these layers define where to place copper on the front and back of the circuit board.
- F.Mask and B.Mask: all shapes drawn on this layer are cut out of the colored soldermask layer of the board.
- F.SilkS and B.SilkS: these layers are printed on the bront and back silkscreen layer respectively. The silkscreen layer is a non-conductive layer of ink usually used to add reference designators and text to a circuit board.
Mask layer
The mask layers are negative layers, the contents of the layer determine where NOT to place soldermask.Silkscreen
Silkscreen can only be placed on top of solder mask, silkscreen overlapping with any area defined in the mask layers will be removed by the board manufacturer. Keep in mind that Kicad will render the silkscreen in these locations but that this does not match the end result.Edge cut
Round shapes are not correctly exported to Kicad on the Edge.Cuts layer. Workaround is adding a lot more nodes and preferably setting segments to be straight.Export the design to Kicad by navigating to Extensions > Svg2Shenzhen > 2. Export to Kicad...
Kicad
…