96b895d63ce20422e4f9118af90dc28d1e86803c
Chip-cn-dat/WCH-dat/CH343-dat/2025-07-30-16-59-11.png
| ... | ... | Binary files /dev/null and b/Chip-cn-dat/WCH-dat/CH343-dat/2025-07-30-16-59-11.png differ |
Chip-cn-dat/WCH-dat/CH343-dat/CH343-dat.md
| ... | ... | @@ -1,6 +1,7 @@ |
| 1 | 1 | |
| 2 | 2 | # CH343-dat |
| 3 | 3 | |
| 4 | +- [[serial-dat]] |
|
| 4 | 5 | |
| 5 | 6 | ## Features |
| 6 | 7 | |
| ... | ... | @@ -28,6 +29,12 @@ |
| 28 | 29 |  |
| 29 | 30 | |
| 30 | 31 | |
| 32 | +## linux |
|
| 33 | + |
|
| 34 | + |
|
| 35 | + |
|
| 36 | + |
|
| 37 | + |
|
| 31 | 38 | ## ref |
| 32 | 39 | |
| 33 | 40 | - [[CH343DS1.pdf]] |
SDK-dat/ESP-SDK-dat/esp-idf-dat/esp-idf-dat.md
| ... | ... | @@ -2,7 +2,9 @@ |
| 2 | 2 | |
| 3 | 3 | # ESP IDF |
| 4 | 4 | |
| 5 | -- [[esp-idf-vscode-dat]] |
|
| 5 | +## install |
|
| 6 | + |
|
| 7 | +- [[esp-idf-vscode-dat]] - [[vscode-dat]] |
|
| 6 | 8 | |
| 7 | 9 | * [esp-idf github](https://github.com/espressif/esp-idf) |
| 8 | 10 | |
| ... | ... | @@ -62,6 +64,11 @@ Setting up Python environment |
| 62 | 64 | Creating a new Python environment in C:\Users\Administrator\.espressif\python_env\idf5.0_py3.10_env |
| 63 | 65 | |
| 64 | 66 | |
| 67 | +## start a project |
|
| 68 | + |
|
| 69 | +- [[template-app-dat]] |
|
| 70 | + |
|
| 71 | + |
|
| 65 | 72 | |
| 66 | 73 | ## example - blink |
| 67 | 74 | |
| ... | ... | @@ -99,6 +106,21 @@ Advanced |
| 99 | 106 | |
| 100 | 107 | ## compile |
| 101 | 108 | |
| 109 | + |
|
| 110 | + |
|
| 111 | + |
|
| 112 | + |
|
| 113 | + |
|
| 114 | + ******************************************************************************* |
|
| 115 | + # ESP-IDF Partition Table |
|
| 116 | + # Name, Type, SubType, Offset, Size, Flags |
|
| 117 | + nvs,data,nvs,0x9000,24K, |
|
| 118 | + phy_init,data,phy,0xf000,4K, |
|
| 119 | + factory,app,factory,0x10000,1M, |
|
| 120 | + ******************************************************************************* |
|
| 121 | + [75/1063] Building C object esp-idf/esp_driver_i2s/CMakeFiles/__idf_esp_driver_i2s.dir/i2s_tdm.c.obj |
|
| 122 | + |
|
| 123 | + |
|
| 102 | 124 | ### compile ninja |
| 103 | 125 | |
| 104 | 126 | * Executing task: e:\work-data\IDF_tools\tools\ninja\1.12.1\ninja.EXE |
| ... | ... | @@ -111,7 +133,6 @@ Advanced |
| 111 | 133 | [4/4] Completed 'bootloader' |
| 112 | 134 | |
| 113 | 135 | |
| 114 | - |
|
| 115 | 136 | ### compile summary |
| 116 | 137 | |
| 117 | 138 | Memory Type Usage Summary |
| ... | ... | @@ -164,3 +185,41 @@ UART == [[serial-dat]] |
| 164 | 185 | --- esp-idf-monitor 1.7.0 on \\.\COM1 115200 |
| 165 | 186 | --- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H |
| 166 | 187 | |
| 188 | + |
|
| 189 | + |
|
| 190 | + |
|
| 191 | +## SDKCONFIG |
|
| 192 | + |
|
| 193 | +- sdkconfig |
|
| 194 | +- sdkconfig.defaults |
|
| 195 | +- sdkconfig.defaults.esp32 |
|
| 196 | +- sdkconfig.defaults.esp32c3 |
|
| 197 | +- sdkconfig.defaults.esp32c5 |
|
| 198 | +- sdkconfig.defaults.esp32c6 |
|
| 199 | +- sdkconfig.defaults.esp32c61 |
|
| 200 | +- sdkconfig.defaults.esp32h2 |
|
| 201 | +- sdkconfig.defaults.esp32p4 |
|
| 202 | +- sdkconfig.defaults.esp32s2 |
|
| 203 | +- sdkconfig.defaults.esp32s3 |
|
| 204 | + |
|
| 205 | +### ✅ Required Files (For ESP32-S3 Only) |
|
| 206 | + |
|
| 207 | +| File Name | Required | Description | |
|
| 208 | +|-----------------------------|----------|-----------------------------------------------------------| |
|
| 209 | +| `sdkconfig.defaults.esp32s3`| ✅ | Default configuration specific to ESP32-S3 | |
|
| 210 | +| `sdkconfig` | ✅ | Generated after `idf.py menuconfig` or first build | |
|
| 211 | + |
|
| 212 | + |
|
| 213 | +✅ Optional Simplification |
|
| 214 | + |
|
| 215 | +If you're only working with ESP32-S3, you can rename: |
|
| 216 | + |
|
| 217 | + mv sdkconfig.defaults.esp32s3 sdkconfig.defaults |
|
| 218 | + |
|
| 219 | +Then build normally: |
|
| 220 | + |
|
| 221 | + idf.py build |
|
| 222 | + |
|
| 223 | +## IDF.py |
|
| 224 | + |
|
| 225 | + |
SDK-dat/ESP-SDK-dat/esp-idf-dat/esp-idf-error-dat.md
| ... | ... | @@ -0,0 +1,41 @@ |
| 1 | + |
|
| 2 | +# esp-idf-error-dat.md |
|
| 3 | + |
|
| 4 | + * Executing task: e:\work-data\IDF_tools\tools\cmake\3.30.2\bin\cmake.exe -G Ninja -DPYTHON_DEPS_CHECKED=1 -DESP_PLATFORM=1 -B e:\Git-category\Git-Arduino\esp-idf-code\build -S e:\Git-category\Git-Arduino\esp-idf-code -DSDKCONFIG='e:\Git-category\Git-Arduino\esp-idf-code\sdkconfig' |
|
| 5 | + |
|
| 6 | + CMake Error: The source directory "E:/Git-category/Git-Arduino/esp-idf-code" does not appear to contain CMakeLists.txt. |
|
| 7 | + Specify --help for usage, or press the help button on the CMake GUI. |
|
| 8 | + |
|
| 9 | + * The terminal process "e:\work-data\IDF_tools\tools\cmake\3.30.2\bin\cmake.exe '-G', 'Ninja', '-DPYTHON_DEPS_CHECKED=1', '-DESP_PLATFORM=1', '-B', 'e:\Git-category\Git-Arduino\esp-idf-code\build', '-S', 'e:\Git-category\Git-Arduino\esp-idf-code', '-DSDKCONFIG='e:\Git-category\Git-Arduino\esp-idf-code\sdkconfig''" terminated with exit code: 1. |
|
| 10 | + |
|
| 11 | + |
|
| 12 | + |
|
| 13 | + |
|
| 14 | + |
|
| 15 | + |
|
| 16 | + ModuleNotFoundError: No module named 'setuptools.command.build' |
|
| 17 | + |
|
| 18 | + python.exe -m pip install --upgrade pip |
|
| 19 | + |
|
| 20 | + |
|
| 21 | + C:\Users\Administrator\.espressif\python_env\idf5.0_py3.8_env |
|
| 22 | + |
|
| 23 | + C:\Users\Administrator\.espressif\python_env\idf5.0_py3.8_env>scripts\activate.bat |
|
| 24 | + |
|
| 25 | + >python -m pip install --upgrade pip setuptools wheel |
|
| 26 | + |
|
| 27 | + |
|
| 28 | + |
|
| 29 | + |
|
| 30 | + (idf5.0_py3.8_env) C:\Users\Administrator\.espressif\python_env\idf5.0_py3.8_env>python -m pip install --upgrade pip setuptools wheel |
|
| 31 | + Requirement already satisfied: pip in c:\users\administrator\.espressif\python_env\idf5.0_py3.8_env\lib\site-packages (22.3.1) |
|
| 32 | + Requirement already satisfied: setuptools in c:\users\administrator\.espressif\python_env\idf5.0_py3.8_env\lib\site-packages (65.6.3) |
|
| 33 | + Requirement already satisfied: wheel in c:\users\administrator\.espressif\python_env\idf5.0_py3.8_env\lib\site-packages (0.38.4) |
|
| 34 | + |
|
| 35 | + |
|
| 36 | + import setuptools.command.build |
|
| 37 | + ok |
|
| 38 | + |
|
| 39 | + |
|
| 40 | + |
|
| 41 | + |
SDK-dat/ESP-SDK-dat/esp-idf-dat/esp-idf-error.md
| ... | ... | @@ -1,26 +0,0 @@ |
| 1 | - |
|
| 2 | - |
|
| 3 | - |
|
| 4 | -ModuleNotFoundError: No module named 'setuptools.command.build' |
|
| 5 | - |
|
| 6 | -python.exe -m pip install --upgrade pip |
|
| 7 | - |
|
| 8 | - |
|
| 9 | -C:\Users\Administrator\.espressif\python_env\idf5.0_py3.8_env |
|
| 10 | - |
|
| 11 | -C:\Users\Administrator\.espressif\python_env\idf5.0_py3.8_env>scripts\activate.bat |
|
| 12 | - |
|
| 13 | ->python -m pip install --upgrade pip setuptools wheel |
|
| 14 | - |
|
| 15 | - |
|
| 16 | - |
|
| 17 | - |
|
| 18 | -(idf5.0_py3.8_env) C:\Users\Administrator\.espressif\python_env\idf5.0_py3.8_env>python -m pip install --upgrade pip setuptools wheel |
|
| 19 | -Requirement already satisfied: pip in c:\users\administrator\.espressif\python_env\idf5.0_py3.8_env\lib\site-packages (22.3.1) |
|
| 20 | -Requirement already satisfied: setuptools in c:\users\administrator\.espressif\python_env\idf5.0_py3.8_env\lib\site-packages (65.6.3) |
|
| 21 | -Requirement already satisfied: wheel in c:\users\administrator\.espressif\python_env\idf5.0_py3.8_env\lib\site-packages (0.38.4) |
|
| 22 | - |
|
| 23 | - |
|
| 24 | -import setuptools.command.build |
|
| 25 | -ok |
|
| 26 | - |
SDK-dat/ESP-SDK-dat/esp-idf-dat/menuconfig-dat.md
| ... | ... | @@ -0,0 +1,27 @@ |
| 1 | + |
|
| 2 | + |
|
| 3 | +menuconfig里面找到ESP PSRAM并打开,勾选support for external ,SPI -connected RAM,spiram的模式就选择 quad,如果自己的板子后面在调试监视的时候报错,就更换成另外一种模式,自动检测使用SPIRAM类型,设置RAM的时钟速度为80MHZ,并且勾选Initialize SPI RAM during startup,这样就可以在初始化的过程中自己识别PSRAM的芯片类型并且在监视中显示出来了,这一步是初始化camera的关键,然后记得保存。 |
|
| 4 | + |
|
| 5 | +然后还有关键的一步,需要给现有的工程添加esp_camera的依赖库 |
|
| 6 | + |
|
| 7 | +通过idf的终端,输入指令: |
|
| 8 | + |
|
| 9 | +idf.py add-dependency "espressif/esp32-camera" |
|
| 10 | + |
|
| 11 | +即可在现有工程中添加相机库的依赖,引用esp_camera.h |
|
| 12 | + |
|
| 13 | +这里面为了确保psram确实已经得到了初始化,我们添加如下代码,显示如下: |
|
| 14 | + |
|
| 15 | + |
|
| 16 | + // 检测 PSRAM 存在性和大小 |
|
| 17 | + if(esp_psram_get_size() == 0) { |
|
| 18 | + ESP_LOGE("BOOT", "PSRAM NOT DETECTED! Check hardware connection."); |
|
| 19 | + vTaskDelay(pdMS_TO_TICKS(1000)); |
|
| 20 | + esp_restart(); // 自动重启 |
|
| 21 | + } |
|
| 22 | + |
|
| 23 | + ESP_LOGI("BOOT", "PSRAM Size: %d KB", esp_psram_get_size() / 1024); |
|
| 24 | + |
|
| 25 | + // 初始化 PSRAM 缓存 |
|
| 26 | + esp_psram_init(); |
|
| 27 | + |
SDK-dat/ESP-SDK-dat/esp-idf-dat/sdkconfig-dat/sdkconfig-dat.md
| ... | ... | @@ -0,0 +1,7 @@ |
| 1 | + |
|
| 2 | + |
|
| 3 | + |
|
| 4 | +# sdkconfig-dat |
|
| 5 | + |
|
| 6 | + |
|
| 7 | +- CONFIG_ESPTOOLPY_MONITOR_BAUD=74880 |
|
| ... | ... | \ No newline at end of file |
SDK-dat/ESP-SDK-dat/esp-idf-dat/sdkconfig/sdkconfig.md
| ... | ... | @@ -1,3 +0,0 @@ |
| 1 | - |
|
| 2 | - |
|
| 3 | -- CONFIG_ESPTOOLPY_MONITOR_BAUD=74880 |
|
| ... | ... | \ No newline at end of file |
SDK-dat/ESP-SDK-dat/esp-idf-dat/template-app-dat.md
| ... | ... | @@ -0,0 +1,11 @@ |
| 1 | + |
|
| 2 | +# template-app-dat.md |
|
| 3 | + |
|
| 4 | + ├── CMakeLists.txt |
|
| 5 | + ├── main |
|
| 6 | + │ ├── CMakeLists.txt |
|
| 7 | + │ └── main.c |
|
| 8 | + └── README.md This is the file you are currently reading |
|
| 9 | + |
|
| 10 | +Additionally, the sample project contains Makefile and component.mk files, used for the legacy Make based build system. |
|
| 11 | +They are not used or needed when building with CMake and idf.py. |
|
| ... | ... | \ No newline at end of file |
SDK-dat/vscode-dat/vscode-dat.md
| ... | ... | @@ -29,5 +29,5 @@ https://github.com/microsoft/vscode-serial-monitor.git |
| 29 | 29 | - python - jupyter |
| 30 | 30 | - serial monitor |
| 31 | 31 | - code runner |
| 32 | - |
|
| 32 | +- [[vs-cpp-dat]] |
|
| 33 | 33 |
Tech-dat/Network-dat/Bluetooth-dat/BLE-dat/BLE-dat.md
| ... | ... | @@ -17,6 +17,8 @@ For Android devices, you can directly install the following apps: |
| 17 | 17 | |
| 18 | 18 |  |
| 19 | 19 | |
| 20 | +- [[BLE蓝牙调试助手.apk.1]] - [[BT-Connect.apk]] |
|
| 21 | + |
|
| 20 | 22 | ## BLE Operations Guide |
| 21 | 23 | |
| 22 | 24 | ### Reading and Writing Bluetooth Data |
| ... | ... | @@ -46,7 +48,7 @@ For Android devices, you can directly install the following apps: |
| 46 | 48 | |
| 47 | 49 | - https://play.google.com/store/apps/dev?id=7265678888812659353&hl=en_US |
| 48 | 50 | |
| 49 | -- [[JDY-dat]] - [[JDY-25M-dat]] - [[BT Connect.apk]] |
|
| 51 | +- [[JDY-dat]] - [[JDY-25M-dat]] |
|
| 50 | 52 | |
| 51 | 53 | - Wireshark |
| 52 | 54 |
Tech-dat/Network-dat/Bluetooth-dat/BLE-dat/BLE\350\223\235\347\211\231\350\260\203\350\257\225\345\212\251\346\211\213.apk.1
| ... | ... | Binary files /dev/null and "b/Tech-dat/Network-dat/Bluetooth-dat/BLE-dat/BLE\350\223\235\347\211\231\350\260\203\350\257\225\345\212\251\346\211\213.apk.1" differ |
Tech-dat/Network-dat/Bluetooth-dat/BLE-dat/BT Connect.apk
| ... | ... | Binary files a/Tech-dat/Network-dat/Bluetooth-dat/BLE-dat/BT Connect.apk and /dev/null differ |
Tech-dat/Network-dat/Bluetooth-dat/BLE-dat/BT-Connect.apk
| ... | ... | Binary files /dev/null and b/Tech-dat/Network-dat/Bluetooth-dat/BLE-dat/BT-Connect.apk differ |
Tech-dat/tech-dat.md
| ... | ... | @@ -73,6 +73,8 @@ |
| 73 | 73 | |
| 74 | 74 | - [[ethernet-dat]] - [[USB-dat]] |
| 75 | 75 | |
| 76 | +- [[bluetooth-dat]] - [[ble-dat]] |
|
| 77 | + |
|
| 76 | 78 | ### MCU / CTRL / Processing |
| 77 | 79 | |
| 78 | 80 | - [[mcu-dat]] - [[development-board-dat]] |