51d941322911c405d4e3cdb74d60429554fdde82
Chip-cn-dat/everest-semi-dat/ES8311-dat/ES8311-dat.md
| ... | ... | @@ -0,0 +1,24 @@ |
| 1 | + |
|
| 2 | +# ES8311-dat |
|
| 3 | + |
|
| 4 | +## ES8311 |
|
| 5 | + |
|
| 6 | +refer use guide in [[I2S-SDK-dat]] |
|
| 7 | + |
|
| 8 | +Low Power Mono Audio CODEC |
|
| 9 | + |
|
| 10 | +FEATURES |
|
| 11 | + |
|
| 12 | +System |
|
| 13 | + |
|
| 14 | +- High performance and low power multibit delta-sigma audio ADC and DAC |
|
| 15 | +- I2S/PCM master or slave serial data port |
|
| 16 | +- 256/384Fs, USB 12/24 MHz and other non standard audio system clocks |
|
| 17 | +- I2C interface |
|
| 18 | + |
|
| 19 | +http://www.everest-semi.com/pdf/ES8311%20PB.pdf |
|
| 20 | + |
|
| 21 | + |
|
| 22 | +## ref |
|
| 23 | + |
|
| 24 | +- [[everest-semi-dat]] |
|
| ... | ... | \ No newline at end of file |
Chip-cn-dat/everest-semi-dat/everest-semi-dat.md
| ... | ... | @@ -1,20 +1,12 @@ |
| 1 | 1 | |
| 2 | 2 | # everest-semi-dat |
| 3 | 3 | |
| 4 | -## ES8311 |
|
| 4 | +- [[es8311-dat]] |
|
| 5 | 5 | |
| 6 | -Low Power Mono Audio CODEC |
|
| 7 | 6 | |
| 8 | -FEATURES |
|
| 9 | 7 | |
| 10 | -System |
|
| 11 | 8 | |
| 12 | -- High performance and low power multibit delta-sigma audio ADC and DAC |
|
| 13 | -- I2S/PCM master or slave serial data port |
|
| 14 | -- 256/384Fs, USB 12/24 MHz and other non standard audio system clocks |
|
| 15 | -- I2C interface |
|
| 16 | - |
|
| 17 | -http://www.everest-semi.com/pdf/ES8311%20PB.pdf |
|
| 9 | +## ref |
|
| 18 | 10 | |
| 19 | 11 | |
| 20 | 12 | - [[I2S-dat]] |
| ... | ... | \ No newline at end of file |
SDK-dat/display-sdk-dat/MIPI-DSI-SDK-dat/2025-08-09-13-29-58.png
| ... | ... | Binary files /dev/null and b/SDK-dat/display-sdk-dat/MIPI-DSI-SDK-dat/2025-08-09-13-29-58.png differ |
SDK-dat/display-sdk-dat/MIPI-DSI-SDK-dat/2025-08-09-13-30-30.png
| ... | ... | Binary files /dev/null and b/SDK-dat/display-sdk-dat/MIPI-DSI-SDK-dat/2025-08-09-13-30-30.png differ |
SDK-dat/display-sdk-dat/MIPI-DSI-SDK-dat/MIPI-DSI-SDK-dat.md
| ... | ... | @@ -0,0 +1,39 @@ |
| 1 | + |
|
| 2 | +# MIPI-DSI-SDK-dat |
|
| 3 | + |
|
| 4 | + |
|
| 5 | +## ESP-IDF MIPI-DSI LCD Example |
|
| 6 | + |
|
| 7 | +The ESP32-P4 uses the ESP32-P4NRW32 chip, which features: |
|
| 8 | + |
|
| 9 | +- Compliance with the MIPI-DSI protocol, using D-PHY v1.1, up to 2 lanes at 1.5Gbps each (total 3Gbps) |
|
| 10 | +- Support for RGB888, RGB565, and YUV422 input formats |
|
| 11 | +- Support for RGB888, RGB666, and RGB565 output formats |
|
| 12 | +- Video mode output for streaming video and fixed image patterns |
|
| 13 | +- MIPI-DSI image processing can also use the 2D-DMA controller, with support for PPA and JPEG codec peripherals |
|
| 14 | + |
|
| 15 | +### MIPI-DSI LCD Driver Principle |
|
| 16 | + |
|
| 17 | + |
|
| 18 | + |
|
| 19 | +### Required Hardware |
|
| 20 | + |
|
| 21 | +- 10.1-inch display and accessories |
|
| 22 | +- ESP32-P4 (host) |
|
| 23 | + |
|
| 24 | +### Steps to Light Up the Display |
|
| 25 | + |
|
| 26 | +1. The driver for the 10.1-inch display is packaged as a component and available in the ESP Component Registry. |
|
| 27 | +2. Add the component to your project: |
|
| 28 | + |
|
| 29 | + ```sh |
|
| 30 | + idf.py add-dependency "waveshare/esp_lcd_jd9365_10_1" |
|
| 31 | + ``` |
|
| 32 | +3. Open your project, select the esp32p4 core, then click the 🔥 (build/flash/monitor) button. When complete, you should see the screen light up and display color bars: |
|
| 33 | + |
|
| 34 | + |
|
| 35 | + |
|
| 36 | + |
|
| 37 | +## ref |
|
| 38 | + |
|
| 39 | +- [[display-SDK-dat]] |
|
| ... | ... | \ No newline at end of file |
SDK-dat/display-sdk-dat/display-sdk-dat.md
| ... | ... | @@ -2,6 +2,9 @@ |
| 2 | 2 | |
| 3 | 3 | # display-sdk-dat |
| 4 | 4 | |
| 5 | +- [[display-dat]] |
|
| 6 | + |
|
| 7 | +- [[interface-SDK-dat]] |
|
| 5 | 8 | |
| 6 | 9 | ## TFT |
| 7 | 10 |
SDK-dat/interface-SDK-dat/I2S-SDK-dat/2025-08-09-13-16-02.png
| ... | ... | Binary files /dev/null and b/SDK-dat/interface-SDK-dat/I2S-SDK-dat/2025-08-09-13-16-02.png differ |
SDK-dat/interface-SDK-dat/I2S-SDK-dat/2025-08-09-13-18-12.png
| ... | ... | Binary files /dev/null and b/SDK-dat/interface-SDK-dat/I2S-SDK-dat/2025-08-09-13-18-12.png differ |
SDK-dat/interface-SDK-dat/I2S-SDK-dat/2025-08-09-13-18-42.png
| ... | ... | Binary files /dev/null and b/SDK-dat/interface-SDK-dat/I2S-SDK-dat/2025-08-09-13-18-42.png differ |
SDK-dat/interface-SDK-dat/I2S-SDK-dat/2025-08-09-13-18-57.png
| ... | ... | Binary files /dev/null and b/SDK-dat/interface-SDK-dat/I2S-SDK-dat/2025-08-09-13-18-57.png differ |
SDK-dat/interface-SDK-dat/I2S-SDK-dat/2025-08-09-13-19-17.png
| ... | ... | Binary files /dev/null and b/SDK-dat/interface-SDK-dat/I2S-SDK-dat/2025-08-09-13-19-17.png differ |
SDK-dat/interface-SDK-dat/I2S-SDK-dat/I2S-SDK-dat.md
| ... | ... | @@ -0,0 +1,61 @@ |
| 1 | + |
|
| 2 | +# I2S-SDK-dat |
|
| 3 | + |
|
| 4 | +- [[I2S-dat]] - [[es8311-dat]] - [[NS4150-dat]] |
|
| 5 | + |
|
| 6 | + |
|
| 7 | +## ESP-IDF ES8311 - NS4150 - I2S Audio Example |
|
| 8 | + |
|
| 9 | +I2S (Inter-IC Sound) is a digital communication protocol for transmitting audio data. It is a serial bus interface mainly used for digital audio data transfer between devices such as DSPs, DACs, ADCs, and audio codecs. |
|
| 10 | + |
|
| 11 | +The ESP32-P4 includes one I2S peripheral. By configuring this peripheral, you can use the I2S driver to input and output sampled audio data. The ESP32-P4 board features an ES8311 codec chip and an NS4150B amplifier chip. The I2S bus and pin mapping are as follows: |
|
| 12 | + |
|
| 13 | +- **MCLK (Master Clock)**: Main clock signal, usually provided by an external device (MCU or DSP) to the ES8311 for its internal digital audio processing. |
|
| 14 | +- **SCLK (Serial Clock)**: Serial clock for I2S data transfer, generated by the master device to synchronize data rate. Each bit of audio data requires one clock cycle. |
|
| 15 | +- **ASDOUT (Audio Serial Data Output) / DOUT**: Audio data output pin. ES8311 outputs decoded digital audio data here, which is then sent to the amplifier or other audio devices. |
|
| 16 | +- **LRCK (Left/Right Clock) / WS (Word Select)**: Indicates whether the current data sample is for the left or right channel. In I2S, one clock cycle is for left channel data, the next for right channel data. |
|
| 17 | +- **DSDIN (Digital Serial Data Input) / DIN**: Receives digital audio data from external devices or the master. ES8311 decodes and processes this data internally. |
|
| 18 | + |
|
| 19 | + |
|
| 20 | + |
|
| 21 | +| Function Pin | ESP32-P4 Pin | |
|
| 22 | +|--------------|-------------| |
|
| 23 | +| MCLK | GPIO13 | |
|
| 24 | +| SCLK | GPIO12 | |
|
| 25 | +| ASDOUT | GPIO11 | |
|
| 26 | +| LRCK | GPIO10 | |
|
| 27 | +| DSDIN | GPIO9 | |
|
| 28 | +| PA_Ctrl (Amp Enable, High Active) | GPIO53 | |
|
| 29 | + |
|
| 30 | +The ES8311 driver for ESP32-P4 uses the ES8311 component, which can be added via the IDF Component Manager: |
|
| 31 | + |
|
| 32 | +```sh |
|
| 33 | +idf.py add-dependency "espressif/es8311" |
|
| 34 | +``` |
|
| 35 | + |
|
| 36 | +Open the `i2scodec` project and add the component as shown below: |
|
| 37 | + |
|
| 38 | + |
|
| 39 | + |
|
| 40 | +Steps: |
|
| 41 | +- Open the ESP-IDF Terminal. |
|
| 42 | +- Add the required component using the command above. |
|
| 43 | +- After successful addition, an `idf_component.yml` file will appear in the `main` folder. This file manages project components. |
|
| 44 | +- You will see the `espressif/es8311` component listed. It will be included during project build. |
|
| 45 | + |
|
| 46 | +Next, click the ⚙️ (settings) icon, search for "Example", and adjust the volume as needed. |
|
| 47 | + |
|
| 48 | + |
|
| 49 | + |
|
| 50 | +Connect a speaker, then click the 🔥 (build/flash/monitor) button. When complete, the terminal will show the result—your ESP32-P4 is now playing audio: |
|
| 51 | + |
|
| 52 | + |
|
| 53 | + |
|
| 54 | +If you set echo mode in the settings, audio will be captured by the microphone and output through the speaker: |
|
| 55 | + |
|
| 56 | + |
|
| 57 | + |
|
| 58 | + |
|
| 59 | +## ref |
|
| 60 | + |
|
| 61 | +- [[interface-SDK-dat]] |
|
| ... | ... | \ No newline at end of file |
SDK-dat/interface-SDK-dat/SD-SDK-dat/2025-08-09-13-09-09.png
| ... | ... | Binary files /dev/null and b/SDK-dat/interface-SDK-dat/SD-SDK-dat/2025-08-09-13-09-09.png differ |
SDK-dat/interface-SDK-dat/SD-SDK-dat/2025-08-09-13-09-28.png
| ... | ... | Binary files /dev/null and b/SDK-dat/interface-SDK-dat/SD-SDK-dat/2025-08-09-13-09-28.png differ |
SDK-dat/interface-SDK-dat/SD-SDK-dat/SD-SDK-dat.md
| ... | ... | @@ -0,0 +1,60 @@ |
| 1 | + |
|
| 2 | +# SD-SDK-dat |
|
| 3 | + |
|
| 4 | + |
|
| 5 | +## ESP-IDF |
|
| 6 | + |
|
| 7 | +### SDMMC Example |
|
| 8 | + |
|
| 9 | +The ESP32-P4 board features a 4-wire SDIO 3.0 card slot for external storage expansion. |
|
| 10 | + |
|
| 11 | +#### Supported Speed Modes |
|
| 12 | + |
|
| 13 | +- Default speed (20 MHz) |
|
| 14 | +- High-speed mode (40 MHz) |
|
| 15 | + |
|
| 16 | +#### Configuring Bus Width and Frequency |
|
| 17 | + |
|
| 18 | +In ESP-IDF, use `sdmmc_host_t` and `sdmmc_slot_config_t` to set up the SDMMC interface. For default 20 MHz frequency and 4-wire communication: |
|
| 19 | + |
|
| 20 | +```c |
|
| 21 | +sdmmc_host_t host = SDMMC_HOST_DEFAULT(); |
|
| 22 | +sdmmc_slot_config_t slot_config = SDMMC_SLOT_CONFIG_DEFAULT(); |
|
| 23 | +``` |
|
| 24 | + |
|
| 25 | +To support 40 MHz high-speed communication, adjust the `max_freq_khz` field in the `sdmmc_host_t` structure: |
|
| 26 | + |
|
| 27 | +```c |
|
| 28 | +sdmmc_host_t host = SDMMC_HOST_DEFAULT(); |
|
| 29 | +host.max_freq_khz = SDMMC_FREQ_HIGHSPEED; |
|
| 30 | +``` |
|
| 31 | + |
|
| 32 | +For ESP32-P4, the SDMMC 4-wire connection should be defined as: |
|
| 33 | + |
|
| 34 | +```c |
|
| 35 | +sdmmc_slot_config_t slot_config = SDMMC_SLOT_CONFIG_DEFAULT(); |
|
| 36 | +slot_config.width = 4; |
|
| 37 | +slot_config.clk = 43; |
|
| 38 | +slot_config.cmd = 44; |
|
| 39 | +slot_config.d0 = 39; |
|
| 40 | +slot_config.d1 = 40; |
|
| 41 | +slot_config.d2 = 41; |
|
| 42 | +slot_config.d3 = 42; |
|
| 43 | +slot_config.flags |= SDMMC_SLOT_FLAG_INTERNAL_PULLUP; |
|
| 44 | +``` |
|
| 45 | + |
|
| 46 | +#### Project Setup and Configuration |
|
| 47 | + |
|
| 48 | +Open the `sdmmc` project, select the correct COM port and chip model. The demo project defines pins as macros, so you may need to configure them, or you can enter the pin numbers directly. Click the ⚙️ (settings) icon to open the SDK Configuration Editor (menuconfig). Search for "sd" in the search bar; you will see the configuration options. Enable default initialization and default example file creation: |
|
| 49 | + |
|
| 50 | + |
|
| 51 | + |
|
| 52 | +#### Build, Flash, and Monitor |
|
| 53 | + |
|
| 54 | +Insert a prepared SD card, then click the 🔥 (build/flash/monitor) button. After completion, the terminal will display the contents of the SD card directory: |
|
| 55 | + |
|
| 56 | + |
|
| 57 | + |
|
| 58 | +## ref |
|
| 59 | + |
|
| 60 | +- [[interface-SDK-dat]] |
|
| ... | ... | \ No newline at end of file |
SDK-dat/interface-SDK-dat/interface-SDK-dat.md
| ... | ... | @@ -7,10 +7,13 @@ |
| 7 | 7 | |
| 8 | 8 | - [[ethernet-dat]] - [[ethernet-SDK-dat]] |
| 9 | 9 | |
| 10 | +- [[memory-dat]] - [[SD-dat]] - [[SD-SDK-dat]] |
|
| 10 | 11 | |
| 12 | +- [[wifi-dat]] - [[wifi-SDK-dat]] |
|
| 11 | 13 | |
| 14 | +- [[I2S-dat]] - [[I2S-SDK-dat]] |
|
| 12 | 15 | |
| 13 | - |
|
| 16 | +- [[display-dat]] - [[display-SDK-dat]] - [[MIPI-DSI-SDK-dat]] |
|
| 14 | 17 | |
| 15 | 18 | ## python on RPI |
| 16 | 19 |
SDK-dat/interface-SDK-dat/wifi-sdk-dat/2025-08-09-13-11-39.png
| ... | ... | Binary files /dev/null and b/SDK-dat/interface-SDK-dat/wifi-sdk-dat/2025-08-09-13-11-39.png differ |
SDK-dat/interface-SDK-dat/wifi-sdk-dat/2025-08-09-13-12-08.png
| ... | ... | Binary files /dev/null and b/SDK-dat/interface-SDK-dat/wifi-sdk-dat/2025-08-09-13-12-08.png differ |
SDK-dat/interface-SDK-dat/wifi-sdk-dat/2025-08-09-13-12-40.png
| ... | ... | Binary files /dev/null and b/SDK-dat/interface-SDK-dat/wifi-sdk-dat/2025-08-09-13-12-40.png differ |
SDK-dat/interface-SDK-dat/wifi-sdk-dat/wifi-sdk-dat.md
| ... | ... | @@ -0,0 +1,37 @@ |
| 1 | + |
|
| 2 | +# wifi-sdk-dat |
|
| 3 | + |
|
| 4 | + |
|
| 5 | +## ESP-IDF WiFi Networking Example |
|
| 6 | + |
|
| 7 | +The ESP32-P4 does not have built-in WiFi or Bluetooth. Instead, it uses an ESP32-C6 module connected via SDIO to provide WiFi functionality. The ESP32-C6 acts as a slave, supporting WiFi 6 and Bluetooth 5, while the ESP32-P4 acts as the host and communicates via SDIO. |
|
| 8 | + |
|
| 9 | +By adding two components, you can seamlessly use `esp_wifi` in your project: |
|
| 10 | + |
|
| 11 | +```sh |
|
| 12 | +idf.py add-dependency "espressif/esp_wifi_remote" |
|
| 13 | +idf.py add-dependency "espressif/esp_hosted" |
|
| 14 | +``` |
|
| 15 | + |
|
| 16 | +Open the `wifistation` project and add the components as shown below: |
|
| 17 | + |
|
| 18 | + |
|
| 19 | + |
|
| 20 | +Steps: |
|
| 21 | +- Open the ESP-IDF Terminal. |
|
| 22 | +- Add the required components using the commands above. |
|
| 23 | +- After successful addition, an `idf_component.yml` file will appear in the `main` folder. This file manages project components. |
|
| 24 | +- You will see `espressif/esp_hosted: "*"` and `espressif/esp_wifi_remote: "*"` listed. These will be included during project build. |
|
| 25 | + |
|
| 26 | +Next, click the ⚙️ (settings) icon and search for "Example". Set the WiFi SSID and password. Note: ESP32-C6 supports 2.4GHz WiFi 6 only, so ensure your target WiFi is 2.4GHz. Save your changes before proceeding! |
|
| 27 | + |
|
| 28 | + |
|
| 29 | + |
|
| 30 | +Finally, click the 🔥 (build/flash/monitor) button. When complete, the terminal will show the connection result—your ESP32-P4 is now connected to WiFi: |
|
| 31 | + |
|
| 32 | + |
|
| 33 | + |
|
| 34 | + |
|
| 35 | +## ref |
|
| 36 | + |
|
| 37 | +- [[wifi-dat]] - [[interface-SDK-dat]] |
|
| ... | ... | \ No newline at end of file |
Tech-dat/Interface-dat/I2S-dat/I2S-dat.md
| ... | ... | @@ -16,7 +16,6 @@ This makes I2S a popular choice for high-speed data transfer applications. |
| 16 | 16 | - [[everest-semi-dat]] |
| 17 | 17 | |
| 18 | 18 | |
| 19 | - |
|
| 20 | 19 | ## Common Microphone, Speaker Wiring |
| 21 | 20 | |
| 22 | 21 |  |
Tech-dat/Interface-dat/MIPI-dat/MIPI-DSI-dat/MIPI-DSI-dat.md
| ... | ... | @@ -3,4 +3,32 @@ |
| 3 | 3 | |
| 4 | 4 | MIPI serial display |
| 5 | 5 | |
| 6 | - |
|
| ... | ... | \ No newline at end of file |
| 0 | + |
|
| 1 | + |
|
| 2 | + |
|
| 3 | + |
|
| 4 | +### MIPI-DSI |
|
| 5 | + |
|
| 6 | +1. **Physical Layer (D-PHY)** |
|
| 7 | + - Uses **1 clock lane + 1–4 data lanes** (each differential pair). |
|
| 8 | + - Two modes: |
|
| 9 | + - **Low-Power (LP) mode** → for commands & initialization (slow, ~10 Mbps). |
|
| 10 | + - **High-Speed (HS) mode** → for pixel streaming (up to ~1–6 Gbps per lane). |
|
| 11 | + |
|
| 12 | +2. **Protocol Layers** |
|
| 13 | + - **Packet-based transmission**: |
|
| 14 | + - **Short packets** → commands, sync signals. |
|
| 15 | + - **Long packets** → pixel data for a line. |
|
| 16 | + - Works kind of like sending “frames” line by line over a high-speed serial link. |
|
| 17 | + |
|
| 18 | +3. **Video Modes** |
|
| 19 | + - **Command Mode** → SoC sends drawing commands (used with display’s own RAM). |
|
| 20 | + - **Video Mode** → Continuous stream of pixel data (panel shows it directly). |
|
| 21 | + |
|
| 22 | +4. **Key Advantages** |
|
| 23 | + - Fewer wires than parallel RGB. |
|
| 24 | + - High bandwidth for high-resolution displays. |
|
| 25 | + - Low EMI due to differential signaling. |
|
| 26 | + |
|
| 27 | +📌 **Flow in simple terms**: |
|
| 28 | +**SoC** prepares pixel data → wraps it in DSI packets → sends over differential lanes (HS mode) → **Display controller** unpacks → drives LCD pixels. |
Tech-dat/Network-dat/WIFI-DAT.md
| ... | ... | @@ -1,6 +1,8 @@ |
| 1 | 1 | |
| 2 | 2 | # Wifi |
| 3 | 3 | |
| 4 | +- [[wifi-sdk-dat]] |
|
| 5 | + |
|
| 4 | 6 | ## tech |
| 5 | 7 | |
| 6 | 8 | - [[IEEE-dat]] - [[WIFI-Halow-dat]] |
Tech-dat/interactive-dat/display-dat/LCD-dat/RGB-LCD-dat/2025-07-16-14-55-33.png
| ... | ... | Binary files a/Tech-dat/interactive-dat/display-dat/LCD-dat/RGB-LCD-dat/2025-07-16-14-55-33.png and /dev/null differ |
Tech-dat/interactive-dat/display-dat/LCD-dat/RGB-LCD-dat/4.3inch_FGD430A4005_Spec.pdf
| ... | ... | Binary files a/Tech-dat/interactive-dat/display-dat/LCD-dat/RGB-LCD-dat/4.3inch_FGD430A4005_Spec.pdf and /dev/null differ |
Tech-dat/interactive-dat/display-dat/LCD-dat/RGB-LCD-dat/AT050TN43 V.1 Pre Ver01 20100511 (A050-43-TT-11)_201102115899.pdf
| ... | ... | Binary files a/Tech-dat/interactive-dat/display-dat/LCD-dat/RGB-LCD-dat/AT050TN43 V.1 Pre Ver01 20100511 (A050-43-TT-11)_201102115899.pdf and /dev/null differ |
Tech-dat/interactive-dat/display-dat/LCD-dat/RGB-LCD-dat/RGB-LCD-dat.md
| ... | ... | @@ -1,62 +0,0 @@ |
| 1 | - |
|
| 2 | -# RGB-LCD-dat |
|
| 3 | - |
|
| 4 | - |
|
| 5 | -## datasheet |
|
| 6 | - |
|
| 7 | -- 5.0 AT050TN43 == [[AT050TN43 V.1 Pre Ver01 20100511 (A050-43-TT-11)_201102115899.pdf]] |
|
| 8 | -- 4.3 FGD430A4005 == [[4.3inch_FGD430A4005_Spec.pdf]] |
|
| 9 | - |
|
| 10 | - |
|
| 11 | -## RGB to LVDS |
|
| 12 | - |
|
| 13 | -- [[LVDS-dat]] |
|
| 14 | - |
|
| 15 | -- [[GM8283-dat]] |
|
| 16 | - |
|
| 17 | - |
|
| 18 | -3通道RGB转LVDS芯片: |
|
| 19 | - |
|
| 20 | -SN75LVDS84 |
|
| 21 | - |
|
| 22 | -SN75LVDS85 |
|
| 23 | - |
|
| 24 | -SN65LVDS84 |
|
| 25 | - |
|
| 26 | -DS90CF363 |
|
| 27 | - |
|
| 28 | -DS90C365 |
|
| 29 | - |
|
| 30 | -DS90CR217 |
|
| 31 | - |
|
| 32 | -国产: |
|
| 33 | - |
|
| 34 | -GM8184 |
|
| 35 | - |
|
| 36 | -GM8263C |
|
| 37 | - |
|
| 38 | - |
|
| 39 | - |
|
| 40 | -## RGB to LVDS |
|
| 41 | - |
|
| 42 | - |
|
| 43 | - |
|
| 44 | - |
|
| 45 | - |
|
| 46 | -## GM8283 |
|
| 47 | - |
|
| 48 | -GM8283型28位并串转换预加重LVDS发送器主要用于视频/图像传输中的发送部分;它可将并行输入的28 bits LVTTL/LVCMOS数据和参考时钟转换为4路的串行LVDS数据流和1路LVDS同步时钟;在每一时钟周期内,24 bits的RGB数据和3 bits的控制数据分别在4个LVDS串行通道中传输。输入参考时钟频率为10MHz~90MHz,总数据率最高可达2520Mbps。 |
|
| 49 | - |
|
| 50 | -GM8283内部模块由串行器、锁相环、LVDS驱动器和使能模块组成。内部工作情况如下:串行器载入28 bits并行数据后,在锁相环产生的多相位同步时钟的触发下将数据移出,同时利用多相位时钟将时钟信号与数据信号同步后输出。LVDS驱动器模块将串行器同步输出的4路串行数据流信号和1路同步时钟信号转化为LVDS形式的信号后输出。使能模块在待机状态下,可将内部模块电流关断,使器件进入低功耗状态。GM8283具有可编程数据选通控制功能,通过RFC控制可实现时钟对数据的上升沿采样或下降沿采样。 |
|
| 51 | - |
|
| 52 | -GM8283可PIN-to-PIN替换的国外产品为: DS90C383、DS90C383A、DS90C383B、DS90C385、DS90C385A、DS90CR281、DS90CR283、DS90CR285 和DS90CR287、SN75LVDS81、SN75LVDS83、SN75LVDS83A、SN75LVDS83B、SN65LVDS93、SN65LVDS93A; |
|
| 53 | - |
|
| 54 | -GM8283不可PIN-to-PIN替换的国外产品为:DS90CF383、DS90CF383A和DS90CF383B;除非国外产品第17脚的焊盘做了可选到GND的连接。 |
|
| 55 | - |
|
| 56 | -TI: SN75LVDS83 |
|
| 57 | - |
|
| 58 | -THINE: THC63LVDM83C/83R/83D |
|
| 59 | - |
|
| 60 | -DOESTEK: DTC34LM85A |
|
| 61 | - |
|
| 62 | -NationalSemiconductor: DS90C385 |
|
| ... | ... | \ No newline at end of file |
Tech-dat/interactive-dat/display-dat/LCD-dat/parallel-display-dat/RGB-LCD-dat/2025-07-16-14-55-33.png
| ... | ... | Binary files /dev/null and b/Tech-dat/interactive-dat/display-dat/LCD-dat/parallel-display-dat/RGB-LCD-dat/2025-07-16-14-55-33.png differ |
Tech-dat/interactive-dat/display-dat/LCD-dat/parallel-display-dat/RGB-LCD-dat/4.3inch_FGD430A4005_Spec.pdf
| ... | ... | Binary files /dev/null and b/Tech-dat/interactive-dat/display-dat/LCD-dat/parallel-display-dat/RGB-LCD-dat/4.3inch_FGD430A4005_Spec.pdf differ |
Tech-dat/interactive-dat/display-dat/LCD-dat/parallel-display-dat/RGB-LCD-dat/AT050TN43 V.1 Pre Ver01 20100511 (A050-43-TT-11)_201102115899.pdf
| ... | ... | Binary files /dev/null and b/Tech-dat/interactive-dat/display-dat/LCD-dat/parallel-display-dat/RGB-LCD-dat/AT050TN43 V.1 Pre Ver01 20100511 (A050-43-TT-11)_201102115899.pdf differ |
Tech-dat/interactive-dat/display-dat/LCD-dat/parallel-display-dat/RGB-LCD-dat/RGB-LCD-dat.md
| ... | ... | @@ -0,0 +1,62 @@ |
| 1 | + |
|
| 2 | +# RGB-LCD-dat |
|
| 3 | + |
|
| 4 | + |
|
| 5 | +## datasheet |
|
| 6 | + |
|
| 7 | +- 5.0 AT050TN43 == [[AT050TN43 V.1 Pre Ver01 20100511 (A050-43-TT-11)_201102115899.pdf]] |
|
| 8 | +- 4.3 FGD430A4005 == [[4.3inch_FGD430A4005_Spec.pdf]] |
|
| 9 | + |
|
| 10 | + |
|
| 11 | +## RGB to LVDS |
|
| 12 | + |
|
| 13 | +- [[LVDS-dat]] |
|
| 14 | + |
|
| 15 | +- [[GM8283-dat]] |
|
| 16 | + |
|
| 17 | + |
|
| 18 | +3通道RGB转LVDS芯片: |
|
| 19 | + |
|
| 20 | +SN75LVDS84 |
|
| 21 | + |
|
| 22 | +SN75LVDS85 |
|
| 23 | + |
|
| 24 | +SN65LVDS84 |
|
| 25 | + |
|
| 26 | +DS90CF363 |
|
| 27 | + |
|
| 28 | +DS90C365 |
|
| 29 | + |
|
| 30 | +DS90CR217 |
|
| 31 | + |
|
| 32 | +国产: |
|
| 33 | + |
|
| 34 | +GM8184 |
|
| 35 | + |
|
| 36 | +GM8263C |
|
| 37 | + |
|
| 38 | + |
|
| 39 | + |
|
| 40 | +## RGB to LVDS |
|
| 41 | + |
|
| 42 | + |
|
| 43 | + |
|
| 44 | + |
|
| 45 | + |
|
| 46 | +## GM8283 |
|
| 47 | + |
|
| 48 | +GM8283型28位并串转换预加重LVDS发送器主要用于视频/图像传输中的发送部分;它可将并行输入的28 bits LVTTL/LVCMOS数据和参考时钟转换为4路的串行LVDS数据流和1路LVDS同步时钟;在每一时钟周期内,24 bits的RGB数据和3 bits的控制数据分别在4个LVDS串行通道中传输。输入参考时钟频率为10MHz~90MHz,总数据率最高可达2520Mbps。 |
|
| 49 | + |
|
| 50 | +GM8283内部模块由串行器、锁相环、LVDS驱动器和使能模块组成。内部工作情况如下:串行器载入28 bits并行数据后,在锁相环产生的多相位同步时钟的触发下将数据移出,同时利用多相位时钟将时钟信号与数据信号同步后输出。LVDS驱动器模块将串行器同步输出的4路串行数据流信号和1路同步时钟信号转化为LVDS形式的信号后输出。使能模块在待机状态下,可将内部模块电流关断,使器件进入低功耗状态。GM8283具有可编程数据选通控制功能,通过RFC控制可实现时钟对数据的上升沿采样或下降沿采样。 |
|
| 51 | + |
|
| 52 | +GM8283可PIN-to-PIN替换的国外产品为: DS90C383、DS90C383A、DS90C383B、DS90C385、DS90C385A、DS90CR281、DS90CR283、DS90CR285 和DS90CR287、SN75LVDS81、SN75LVDS83、SN75LVDS83A、SN75LVDS83B、SN65LVDS93、SN65LVDS93A; |
|
| 53 | + |
|
| 54 | +GM8283不可PIN-to-PIN替换的国外产品为:DS90CF383、DS90CF383A和DS90CF383B;除非国外产品第17脚的焊盘做了可选到GND的连接。 |
|
| 55 | + |
|
| 56 | +TI: SN75LVDS83 |
|
| 57 | + |
|
| 58 | +THINE: THC63LVDM83C/83R/83D |
|
| 59 | + |
|
| 60 | +DOESTEK: DTC34LM85A |
|
| 61 | + |
|
| 62 | +NationalSemiconductor: DS90C385 |
|
| ... | ... | \ No newline at end of file |
Tech-dat/interactive-dat/display-dat/LCD-dat/parallel-display-dat/parallel-display-dat.md
| ... | ... | @@ -0,0 +1,3 @@ |
| 1 | + |
|
| 2 | +# parallel-display-dat |
|
| 3 | + |
Tech-dat/interactive-dat/display-dat/display-dat.md
| ... | ... | @@ -10,16 +10,66 @@ SPI interface LCDs - [[EDS-LCD-dat]] |
| 10 | 10 | - [[OLED-dat]] |
| 11 | 11 | |
| 12 | 12 | - [[e-paper-dat]] |
| 13 | + |
|
| 13 | 14 | - [[Nokia-5110-dat]] |
| 14 | 15 | |
| 16 | +- [[image-dat]] |
|
| 17 | + |
|
| 18 | +## display interface protocols |
|
| 19 | + |
|
| 20 | +**MIPI** stands for **Mobile Industry Processor Interface**. |
|
| 21 | + |
|
| 22 | +- [[MIPI-DSI-dat]] - [[HDMI-dat]] - [[LVDS-dat]] - [[VGA-dat]] |
|
| 23 | + |
|
| 24 | +- [[eDP-dat]] - [[SLVS-EC-dat]] |
|
| 25 | + |
|
| 26 | +- [[parallel-display-dat]] - [[RGB-LCD-dat]] |
|
| 27 | + |
|
| 28 | +- [[MIPI-CSI-DAT]] |
|
| 29 | + |
|
| 30 | +### Other Display Interfaces |
|
| 31 | + |
|
| 32 | +#### 1. **MIPI-CSI** (Camera Serial Interface) |
|
| 33 | +- **Direction:** Camera → Processor |
|
| 34 | +- Also uses MIPI D-PHY (similar electrical layer as DSI). |
|
| 35 | +- Serial, differential, high-speed. |
|
| 36 | +- Instead of pixel-out, it’s pixel-in. |
|
| 37 | + |
|
| 38 | +#### 2. **LVDS** (Low-Voltage Differential Signaling) |
|
| 39 | +- Parallel pixel data serialized over multiple lanes. |
|
| 40 | +- Widely used in laptops before MIPI-DSI became popular. |
|
| 41 | +- Lower data rate per lane (~945 Mbps) but can use many lanes. |
|
| 42 | +- Simpler than DSI (no packet protocol like DSI). |
|
| 15 | 43 | |
| 16 | -## display interface |
|
| 44 | +#### 3. **eDP** (Embedded DisplayPort) |
|
| 45 | +- Mostly used in laptops and tablets. |
|
| 46 | +- Based on DisplayPort standard. |
|
| 47 | +- Packet-based like DSI, but higher bandwidth (multi-Gbps per lane). |
|
| 48 | +- Supports very high resolutions (4K, 8K). |
|
| 17 | 49 | |
| 18 | -- [[RGB-LCD-dat]] - [[HDMI-dat]] - [[LVDS-dat]] - [[VGA-dat]] |
|
| 50 | +#### 4. **HDMI** |
|
| 51 | +- For external displays/TVs. |
|
| 52 | +- Packetized video + audio. |
|
| 53 | +- Higher voltage, not as power-efficient as DSI. |
|
| 54 | +- Not usually used for mobile internal displays. |
|
| 19 | 55 | |
| 56 | +#### 5. **Parallel RGB / TTL** |
|
| 57 | +- Old-school direct pixel bus (1 wire per color bit + sync signals). |
|
| 58 | +- Very high pin count, no serialization. |
|
| 59 | +- Easy to understand but not good for high resolution. |
|
| 20 | 60 | |
| 61 | +#### 6. **SLVS-EC** (Scalable Low Voltage Signaling – Embedded Clock) |
|
| 62 | +- Newer serial interface from Sony and others. |
|
| 63 | +- Competes with MIPI for camera & display links. |
|
| 64 | +- Higher speeds than D-PHY in some cases. |
|
| 21 | 65 | |
| 66 | +--- |
|
| 22 | 67 | |
| 68 | +💡 **Main takeaway:** |
|
| 69 | +- **MIPI-DSI** = optimized for **internal** mobile/tablet displays, low pin count, low EMI, power-efficient. |
|
| 70 | +- **LVDS** and **eDP** = laptop displays. |
|
| 71 | +- **HDMI** = external monitors/TVs. |
|
| 72 | +- **Parallel RGB** = simple, low-res systems. |
|
| 23 | 73 | |
| 24 | 74 | |
| 25 | 75 |
Tech-dat/media-dat/image-dat/image-dat.md
| ... | ... | @@ -1,3 +1,59 @@ |
| 1 | 1 | |
| 2 | 2 | # image-dat |
| 3 | 3 | |
| 4 | +## image formats |
|
| 5 | + |
|
| 6 | +## 🆔 Quick Comparison |
|
| 7 | + |
|
| 8 | +| Format | Bits/Pixel | Colors | Memory Size | Quality | Typical Use | |
|
| 9 | +|----------|------------|----------------|-------------|--------------|-----------------------| |
|
| 10 | +| RGB888 | 24 | ~16.7M | High | Excellent | Photography, UI, HDMI | |
|
| 11 | +| RGB565 | 16 | ~65K | Medium | Good | Small LCD, IoT | |
|
| 12 | +| YUV422 | 16 | N/A (diff model)| Medium | Good for video | Cameras, streaming | |
|
| 13 | + |
|
| 14 | +--- |
|
| 15 | + |
|
| 16 | +💡 **Summary:** |
|
| 17 | +- **RGB888** → Best color accuracy. |
|
| 18 | +- **RGB565** → Saves memory, okay for displays. |
|
| 19 | +- **YUV422** → Efficient for video, focuses on brightness detail. |
|
| 20 | + |
|
| 21 | +## YUV422 |
|
| 22 | + |
|
| 23 | +- **Meaning:** Y = Luma (brightness), U & V = Chrominance (color). |
|
| 24 | +- **"422"** means: |
|
| 25 | +- Y (brightness) sampled for **every pixel**. |
|
| 26 | +- U and V sampled for **every 2 pixels** (horizontally). |
|
| 27 | +- **Bits per pixel:** Usually 16 bits. |
|
| 28 | +- **Layout example (2 pixels):** |
|
| 29 | + |
|
| 30 | + Y0 U0 Y1 V0 |
|
| 31 | + |
|
| 32 | +- **Usage:** Video compression, cameras — reduces bandwidth while keeping brightness sharp. |
|
| 33 | + |
|
| 34 | +## RGB565 |
|
| 35 | + |
|
| 36 | +- **Meaning:** Red — 5 bits, Green — 6 bits, Blue — 5 bits. |
|
| 37 | +- **Bits per pixel:** `5 + 6 + 5 = 16 bits` (2 bytes) |
|
| 38 | +- **Color depth:** 65,536 colors. |
|
| 39 | +- **Layout example (per pixel):** |
|
| 40 | + |
|
| 41 | + RRRRR GGGGGG BBBBB |
|
| 42 | + |
|
| 43 | +- **Usage:** LCD displays, embedded systems where memory and bandwidth are limited. |
|
| 44 | + |
|
| 45 | +## RGB888 |
|
| 46 | + |
|
| 47 | +- **Meaning:** Red, Green, Blue — 8 bits per color channel. |
|
| 48 | +- **Bits per pixel:** `8 + 8 + 8 = 24 bits` (3 bytes) |
|
| 49 | +- **Color depth:** 16,777,216 colors. |
|
| 50 | +- **Layout example (per pixel):** |
|
| 51 | + |
|
| 52 | + RRRRRRRR GGGGGGGG BBBBBBBB |
|
| 53 | + |
|
| 54 | +- **Usage:** High-quality images, full color fidelity. |
|
| 55 | + |
|
| 56 | + |
|
| 57 | +## ref |
|
| 58 | + |
|
| 59 | +- [[image-dat]] |
|
| ... | ... | \ No newline at end of file |
Tech-dat/memory-dat/sd-dat/sd-dat.md
| ... | ... | @@ -1,6 +1,27 @@ |
| 1 | 1 | |
| 2 | 2 | # sd-dat |
| 3 | 3 | |
| 4 | +- [[microsd-dat]] - [[sd-flashing-dat]] |
|
| 5 | + |
|
| 6 | +- [[SD-SDK-dat]] |
|
| 7 | + |
|
| 8 | +## 4. 📍 Embedded vs. Removable == SD VS SDMMC |
|
| 9 | + |
|
| 10 | +| Feature | SD Card | eMMC / SDMMC-connected storage | |
|
| 11 | +| ----------- | ---------------------------- | ------------------------------ | |
|
| 12 | +| Removable | ✅ Yes | ❌ No (soldered) | |
|
| 13 | +| Typical use | Cameras, laptops, dev boards | Phones, tablets, SBC eMMC boot | |
|
| 14 | +| Speed | Good, but depends on class | Higher with HS200/HS400 modes | |
|
| 15 | +| Interface | SPI or SD native | SD/MMC native only | |
|
| 16 | + |
|
| 17 | +📝 Key Points |
|
| 18 | + |
|
| 19 | +- **SDMMC** usually refers to the **native high-speed SD/MMC bus** on MCUs/SoCs. |
|
| 20 | +- Normal **SD card** can use that SDMMC bus — or just SPI mode — depending on the hardware. |
|
| 21 | +- In embedded boards (like STM32, ESP32-S3, Raspberry Pi), **SDMMC peripheral** = faster, multi-bit parallel bus. |
|
| 22 | +- **eMMC** is basically an MMC chip soldered permanently, always accessed via the SDMMC interface. |
|
| 23 | + |
|
| 24 | + |
|
| 4 | 25 | ## Comparison: SDIO vs. SPI Interface |
| 5 | 26 | |
| 6 | 27 | Both **SDIO (Secure Digital Input Output)** and **SPI (Serial Peripheral Interface)** are used for communication with SD cards and other peripherals, but they have key differences in speed, complexity, and use cases. |