完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
开发环境
系统:macOS 11.5.2 idf:v4.3.1,2e74914051 esp-dev-kits:master,ec03a13333a9 我们的操作步骤以及问题套件是在淘宝旗舰店买的,收到后最外面的箱子已经摔难了,不要问问什么不当面签收,因为现在大部分快递都不打电话,放菜鸟了。 然后用连接苹果电脑连接开发板的USB UART接口(没有连接任何附赠的线,因为没看到官方文档说要连接),此时不显示内容,黑屏,只有微弱背光亮,如下图: 按100键没有什么反应,触摸也没有任何反应,按rst键屏幕背光会闪一下,还是继续黑屏,所以 问题1:套件买回来后是不是就是黑屏,还是能显示内容? 然后我们觉得可能是官方套件没有初始化程序,就配置idf环境,然后拉取esp-dev-kits代码后,用默认配置编译esp-dev-kits/esp32-s2-hmi-devkit-1/examples/get-started/led_blink并刷入开发板,led能正常闪烁,此时屏幕依然是上面的情况。然后刷入其他的实例代码,包括sensors,smart-panel,power,都能正常刷入并看到日志显示正常工作,屏幕还是上面的情况;对于刷入power实例后,屏幕能触摸改变led颜色,但还是无任何显示;例如:刷入sensors,期间数据线换到mcu usb口,按几个键,但最终屏幕还是不显示,完整日志如下: Executing action: flashRunning ninja in directory /Users/super/esp/esp-dev-kits/esp32-s2-hmi-devkit-1/examples/sensors/buildExecuting "ninja flash"...[0/1] Re-running CMake...-- Component directory /Users/super/esp/esp-idf/components/esp_phy does not contain a CMakeLists.txt file. No component will be added-- Component directory /Users/super/esp/esp-idf/components/ieee802154 does not contain a CMakeLists.txt file. No component will be added-- Component directory /Users/super/esp/esp-idf/components/openthread does not contain a CMakeLists.txt file. No component will be added-- Building ESP-IDF components for target esp32s2-- Project sdkconfig file /Users/super/esp/esp-dev-kits/esp32-s2-hmi-devkit-1/examples/sensors/sdkconfigLoading defaults file /Users/super/esp/esp-dev-kits/esp32-s2-hmi-devkit-1/examples/sensors/sdkconfig.defaults...-- App "sensor" version: ec03a13-- Adding linker script /Users/super/esp/esp-idf/components/esp_rom/esp32s2/ld/esp32s2.rom.ld-- Adding linker script /Users/super/esp/esp-idf/components/esp_rom/esp32s2/ld/esp32s2.rom.api.ld-- Adding linker script /Users/super/esp/esp-idf/components/esp_rom/esp32s2/ld/esp32s2.rom.libgcc.ld-- Adding linker script /Users/super/esp/esp-idf/components/esp_rom/esp32s2/ld/esp32s2.rom.newlib-funcs.ld-- Adding linker script /Users/super/esp/esp-idf/components/esp_rom/esp32s2/ld/esp32s2.rom.newlib-data.ld-- Adding linker script /Users/super/esp/esp-idf/components/esp_rom/esp32s2/ld/esp32s2.rom.spiflash.ld-- Adding linker script /Users/super/esp/esp-dev-kits/esp32-s2-hmi-devkit-1/examples/sensors/build/esp-idf/esp32s2/esp32s2_out.ld-- Adding linker script /Users/super/esp/esp-idf/components/esp32s2/ld/esp32s2.project.ld.in-- Adding linker script /Users/super/esp/esp-idf/components/esp32s2/ld/esp32s2.peripherals.ld-- Components: app_trace app_update asio audio bootloader bootloader_support bsp bt cbor cmock coap console cxx driver efuse esp-qcloud esp-tls esp32s2 esp_adc_cal esp_common esp_eth esp_event esp_gdbstub esp_hid esp_http_client esp_http_server esp_https_ota esp_https_server esp_hw_support esp_ipc esp_local_ctrl esp_netif esp_pm esp_ringbuf esp_rom esp_serial_slave_link esp_system esp_timer esp_websocket_client esp_wifi espcoredump esptool_py expat fatfs file_system freemodbus freertos hal heap i2c_bus i2c_devices i2s_bus idf_test jsmn json led_strip libsodium log lvgl lwip main mbedtls mdns mqtt network newlib nghttp nvs_flash openssl partition_table perfmon protobuf-c protocomm pthread screen sdmmc soc spi_bus spi_flash spiffs tcp_transport tcpip_adapter tinyusb touch_element ulp unity vfs wear_levelling wifi_provisioning wpa_supplicant xtensa-- Component paths: /Users/super/esp/esp-idf/components/app_trace /Users/super/esp/esp-idf/components/app_update /Users/super/esp/esp-idf/components/asio /Users/super/esp/esp-dev-kits/esp32-s2-hmi-devkit-1/components/audio /Users/super/esp/esp-idf/components/bootloader /Users/super/esp/esp-idf/components/bootloader_support /Users/super/esp/esp-dev-kits/esp32-s2-hmi-devkit-1/components/bsp /Users/super/esp/esp-idf/components/bt /Users/super/esp/esp-idf/components/cbor /Users/super/esp/esp-idf/components/cmock /Users/super/esp/esp-idf/components/coap /Users/super/esp/esp-idf/components/console /Users/super/esp/esp-idf/components/cxx /Users/super/esp/esp-idf/components/driver /Users/super/esp/esp-idf/components/efuse /Users/super/esp/esp-dev-kits/esp32-s2-hmi-devkit-1/components/esp-qcloud /Users/super/esp/esp-idf/components/esp-tls /Users/super/esp/esp-idf/components/esp32s2 /Users/super/esp/esp-idf/components/esp_adc_cal /Users/super/esp/esp-idf/components/esp_common /Users/super/esp/esp-idf/components/esp_eth /Users/super/esp/esp-idf/components/esp_event /Users/super/esp/esp-idf/components/esp_gdbstub /Users/super/esp/esp-idf/components/esp_hid /Users/super/esp/esp-idf/components/esp_http_client /Users/super/esp/esp-idf/components/esp_http_server /Users/super/esp/esp-idf/components/esp_https_ota /Users/super/esp/esp-idf/components/esp_https_server /Users/super/esp/esp-idf/components/esp_hw_support /Users/super/esp/esp-idf/components/esp_ipc /Users/super/esp/esp-idf/components/esp_local_ctrl /Users/super/esp/esp-idf/components/esp_netif /Users/super/esp/esp-idf/components/esp_pm /Users/super/esp/esp-idf/components/esp_ringbuf /Users/super/esp/esp-idf/components/esp_rom /Users/super/esp/esp-idf/components/esp_serial_slave_link /Users/super/esp/esp-idf/components/esp_system /Users/super/esp/esp-idf/components/esp_timer /Users/super/esp/esp-idf/components/esp_websocket_client /Users/super/esp/esp-idf/components/esp_wifi /Users/super/esp/esp-idf/components/espcoredump /Users/super/esp/esp-idf/components/esptool_py /Users/super/esp/esp-idf/components/expat /Users/super/esp/esp-idf/components/fatfs /Users/super/esp/esp-dev-kits/esp32-s2-hmi-devkit-1/components/file_system /Users/super/esp/esp-idf/components/freemodbus /Users/super/esp/esp-idf/components/freertos /Users/super/esp/esp-idf/components/hal /Users/super/esp/esp-idf/components/heap /Users/super/esp/esp-dev-kits/esp32-s2-hmi-devkit-1/components/i2c_bus /Users/super/esp/esp-dev-kits/esp32-s2-hmi-devkit-1/components/i2c_devices /Users/super/esp/esp-dev-kits/esp32-s2-hmi-devkit-1/components/i2s_bus /Users/super/esp/esp-idf/components/idf_test /Users/super/esp/esp-idf/components/jsmn /Users/super/esp/esp-idf/components/json /Users/super/esp/esp-dev-kits/esp32-s2-hmi-devkit-1/components/led_strip /Users/super/esp/esp-idf/components/libsodium /Users/super/esp/esp-idf/components/log /Users/super/esp/esp-dev-kits/esp32-s2-hmi-devkit-1/components/lvgl /Users/super/esp/esp-idf/components/lwip /Users/super/esp/esp-dev-kits/esp32-s2-hmi-devkit-1/examples/sensors/main /Users/super/esp/esp-idf/components/mbedtls /Users/super/esp/esp-idf/components/mdns /Users/super/esp/esp-idf/components/mqtt /Users/super/esp/esp-dev-kits/esp32-s2-hmi-devkit-1/components/network /Users/super/esp/esp-idf/components/newlib /Users/super/esp/esp-idf/components/nghttp /Users/super/esp/esp-idf/components/nvs_flash /Users/super/esp/esp-idf/components/openssl /Users/super/esp/esp-idf/components/partition_table /Users/super/esp/esp-idf/components/perfmon /Users/super/esp/esp-idf/components/protobuf-c /Users/super/esp/esp-idf/components/protocomm /Users/super/esp/esp-idf/components/pthread /Users/super/esp/esp-dev-kits/esp32-s2-hmi-devkit-1/components/screen /Users/super/esp/esp-idf/components/sdmmc /Users/super/esp/esp-idf/components/soc /Users/super/esp/esp-dev-kits/esp32-s2-hmi-devkit-1/components/spi_bus /Users/super/esp/esp-idf/components/spi_flash /Users/super/esp/esp-idf/components/spiffs /Users/super/esp/esp-idf/components/tcp_transport /Users/super/esp/esp-idf/components/tcpip_adapter /Users/super/esp/esp-idf/components/tinyusb /Users/super/esp/esp-idf/components/touch_element /Users/super/esp/esp-idf/components/ulp /Users/super/esp/esp-idf/components/unity /Users/super/esp/esp-idf/components/vfs /Users/super/esp/esp-idf/components/wear_levelling /Users/super/esp/esp-idf/components/wifi_provisioning /Users/super/esp/esp-idf/components/wpa_supplicant /Users/super/esp/esp-idf/components/xtensa-- Configuring done-- Generating done-- Build files have been written to: /Users/super/esp/esp-dev-kits/esp32-s2-hmi-devkit-1/examples/sensors/build[1/7] Performing build step for 'bootloader'[0/1] Re-running CMake...-- Component directory /Users/super/esp/esp-idf/components/esp_phy does not contain a CMakeLists.txt file. No component will be added-- Component directory /Users/super/esp/esp-idf/components/ieee802154 does not contain a CMakeLists.txt file. No component will be added-- Component directory /Users/super/esp/esp-idf/components/openthread does not contain a CMakeLists.txt file. No component will be added-- Building ESP-IDF components for target esp32s2-- Project sdkconfig file /Users/super/esp/esp-dev-kits/esp32-s2-hmi-devkit-1/examples/sensors/sdkconfig-- Adding linker script /Users/super/esp/esp-idf/components/esp32s2/ld/esp32s2.peripherals.ld-- Adding linker script /Users/super/esp/esp-idf/components/esp_rom/esp32s2/ld/esp32s2.rom.ld-- Adding linker script /Users/super/esp/esp-idf/components/esp_rom/esp32s2/ld/esp32s2.rom.api.ld-- Adding linker script /Users/super/esp/esp-idf/components/esp_rom/esp32s2/ld/esp32s2.rom.libgcc.ld-- Adding linker script /Users/super/esp/esp-idf/components/esp_rom/esp32s2/ld/esp32s2.rom.newlib-funcs.ld-- Adding linker script /Users/super/esp/esp-idf/components/esp_rom/esp32s2/ld/esp32s2.rom.spiflash.ld-- Adding linker script /Users/super/esp/esp-idf/components/bootloader/subproject/main/ld/esp32s2/bootloader.ld-- Adding linker script /Users/super/esp/esp-idf/components/bootloader/subproject/main/ld/esp32s2/bootloader.rom.ld-- Components: bootloader bootloader_support efuse esp32s2 esp_common esp_hw_support esp_rom esp_system esptool_py hal log main micro-ecc newlib partition_table soc spi_flash xtensa-- Component paths: /Users/super/esp/esp-idf/components/bootloader /Users/super/esp/esp-idf/components/bootloader_support /Users/super/esp/esp-idf/components/efuse /Users/super/esp/esp-idf/components/esp32s2 /Users/super/esp/esp-idf/components/esp_common /Users/super/esp/esp-idf/components/esp_hw_support /Users/super/esp/esp-idf/components/esp_rom /Users/super/esp/esp-idf/components/esp_system /Users/super/esp/esp-idf/components/esptool_py /Users/super/esp/esp-idf/components/hal /Users/super/esp/esp-idf/components/log /Users/super/esp/esp-idf/components/bootloader/subproject/main /Users/super/esp/esp-idf/components/bootloader/subproject/components/micro-ecc /Users/super/esp/esp-idf/components/newlib /Users/super/esp/esp-idf/components/partition_table /Users/super/esp/esp-idf/components/soc /Users/super/esp/esp-idf/components/spi_flash /Users/super/esp/esp-idf/components/xtensa-- Configuring done-- Generating done-- Build files have been written to: /Users/super/esp/esp-dev-kits/esp32-s2-hmi-devkit-1/examples/sensors/build/bootloaderninja: no work to do.[4/5] Generating binary image from built executableesptool.py v3.1-devMerged 2 ELF sectionsGenerated /Users/super/esp/esp-dev-kits/esp32-s2-hmi-devkit-1/examples/sensors/build/sensor.bin[4/5] cd /Users/super/esp/esp-idf/comp...nents/esptool_py/run_serial_tool.cmakeesptool.py esp32s2 -p /dev/cu.usbserial-1410 -b 460800 --before=default_reset --after=hard_reset write_flash --flash_mode dio --flash_freq 80m --flash_size 4MB 0x8000 partition_table/partition-table.bin 0x1000 bootloader/bootloader.bin 0x10000 sensor.binesptool.py v3.1-devSerial port /dev/cu.usbserial-1410Connecting....Chip is ESP32-S2Features: WiFi, ADC and temperature sensor calibration in BLK2 of efuseCrystal is 40MHzMAC: 7c:df:a1:0e:41:eeUploading stub...Running stub...Stub running...Changing baud rate to 460800Changed.Configuring flash size...Flash will be erased from 0x00008000 to 0x00008fff...Flash will be erased from 0x00001000 to 0x00006fff...Flash will be erased from 0x00010000 to 0x000a9fff...Compressed 3072 bytes to 106...Writing at 0x00008000... (100 %)Wrote 3072 bytes (106 compressed) at 0x00008000 in 0.1 seconds (effective 417.2 kbit/s)...Hash of data verified.Compressed 21744 bytes to 13230...Writing at 0x00001000... (100 %)Wrote 21744 bytes (13230 compressed) at 0x00001000 in 0.6 seconds (effective 291.5 kbit/s)...Hash of data verified.Compressed 627792 bytes to 303042...Writing at 0x00010000... (5 %)Writing at 0x0001d038... (10 %)Writing at 0x000254a5... (15 %)Writing at 0x0002ed85... (21 %)Writing at 0x0003b541... (26 %)Writing at 0x0004521c... (31 %)Writing at 0x0004e775... (36 %)Writing at 0x0005b6b1... (42 %)Writing at 0x00063c58... (47 %)Writing at 0x00069c67... (52 %)Writing at 0x0006f88f... (57 %)Writing at 0x000757b1... (63 %)Writing at 0x0007d3f4... (68 %)Writing at 0x00082e82... (73 %)Writing at 0x00089492... (78 %)Writing at 0x0008fb8d... (84 %)Writing at 0x0009a03c... (89 %)Writing at 0x0009fffa... (94 %)Writing at 0x000a6189... (100 %)Wrote 627792 bytes (303042 compressed) at 0x00010000 in 8.1 seconds (effective 619.4 kbit/s)...Hash of data verified.Leaving...Hard resetting via RTS pin...Executing action: monitorRunning idf_monitor in directory /Users/super/esp/esp-dev-kits/esp32-s2-hmi-devkit-1/examples/sensorsExecuting "/Users/super/.espressif/python_env/idf4.3_py3.9_env/bin/python /Users/super/esp/esp-idf/tools/idf_monitor.py -p /dev/cu.usbserial-1410 -b 2000000 --toolchain-prefix xtensa-esp32s2-elf- /Users/super/esp/esp-dev-kits/esp32-s2-hmi-devkit-1/examples/sensors/build/sensor.elf -m '/Users/super/.espressif/python_env/idf4.3_py3.9_env/bin/python' '/Users/super/esp/esp-idf/tools/idf.py' '-p' '/dev/cu.usbserial-1410'"...--- idf_monitor on /dev/cu.usbserial-1410 2000000 ------ Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---I (21) boot: ESP-IDF v4.3.1-dirty 2nd stage bootloaderI (21) boot: compile time 01:54:51I (21) boot: chip revision: 0I (22) qio_mode: Enabling default flash chip QIOI (22) boot.esp32s2: SPI Speed : 80MHzI (22) boot.esp32s2: SPI Mode : QIOI (22) boot.esp32s2: SPI Flash Size : 4MBI (23) boot: Enabling RNG early entropy source...I (23) boot: Partition Table:I (23) boot: ## Label Usage Type ST Offset LengthI (23) boot: 0 nvs WiFi data 01 02 00009000 00006000I (24) boot: 1 phy_init RF data 01 01 0000f000 00001000I (24) boot: 2 factory factory app 00 00 00010000 003cf000I (25) boot: End of partition tableI (25) esp_image: segment 0: paddr=00010020 vaddr=3f000020 size=4d080h (315520) mapI (80) esp_image: segment 1: paddr=0005d0a8 vaddr=3ffc1b40 size=02aach ( 10924) loadI (82) esp_image: segment 2: paddr=0005fb5c vaddr=40024000 size=004bch ( 1212) loadI (83) esp_image: segment 3: paddr=00060020 vaddr=40080020 size=3bd6ch (245100) mapI (125) esp_image: segment 4: paddr=0009bd94 vaddr=400244bc size=0d678h ( 54904) loadI (137) esp_image: segment 5: paddr=000a9414 vaddr=50000000 size=00010h ( 16) loadI (145) boot: Loaded app from partition at offset 0x10000I (145) boot: Disabling RNG early entropy source...I (145) cache: Instruction cache : size 8KB, 4Ways, cache line size 32ByteI (145) cache: Data cache : size 8KB, 4Ways, cache line size 32ByteI (146) spiram: Found 16MBit SPI RAM deviceI (146) spiram: SPI RAM mode: sram 80mI (146) spiram: PSRAM initialized, cache is in normal (1-core) mode.I (146) cpu_start: Pro cpu up.I (365) spiram: SPI SRAM memory test OKI (374) cpu_start: Pro cpu start user codeI (374) cpu_start: cpu freq: 240000000I (375) cpu_start: Application information:I (375) cpu_start: Project name: sensorI (375) cpu_start: App version: ec03a13I (375) cpu_start: Compile time: Oct 12 2021 01:54:41I (376) cpu_start: ELF file SHA256: 52e52dc39b98cdab...I (376) cpu_start: ESP-IDF: v4.3.1-dirtyI (376) heap_init: Initializing. RAM available for dynamic allocation:I (377) heap_init: At 3FF9E000 len 00002000 (8 KiB): RTCRAMI (377) heap_init: At 3FFC59B8 len 00036648 (217 KiB): DRAMI (377) heap_init: At 3FFFC000 len 00003A10 (14 KiB): DRAMI (378) spiram: Adding pool of 2048K of external SPI memory to heap allocatorI (378) spi_flash: detected chip: genericI (379) spi_flash: flash io: qioI (379) cpu_start: Starting scheduler on PRO CPU.I (379) spiram: Reserving pool of 32K of internal memory for DMA/internal allocationsI (379) i2c_bus: i2c0 bus initedI (442) mpu6050: mpu6050 device address is: 0x72I (464) ESP32S2_I2S_LCD: lcd_buffer_size: 32000, lcd_dma_size: 4000, lcd_dma_node_cnt: 8I (464) ESP32S2_I2S_LCD: lcd init okI (685) lcd rm68120: MADCTL=0x60I (685) bsp_lcd: Screen name : [RM68120] | width : [800] | height : [480] [size=120%]问题2:通过screen /dev/cu.usbserial-1410 460800命令查看有乱码 尝试将波特率换成日志里面看到的波特率,2000000还是乱码(我们还有一个官方的DevC Kit开发模块,默认就不是乱码),只有通过idf.py -p /dev/cu.usbserial-1410 flash monitor命令刷入并查看监视器内容才不乱码,所以如何实现通过screen查看不是乱码? 麻烦知道的朋友帮忙看看,非常感谢! |
|
相关推荐
1个回答
|
|
1. 检查硬件连接:首先,请确保您的开发板与电脑之间的连接正确。您提到没有连接任何附赠的线,但请确保USB UART接口连接正常。
2. 检查电源:请检查开发板是否有足够的电源供应。如果电源不足,可能导致屏幕无法正常显示。 3. 检查屏幕连接:请检查屏幕与开发板之间的连接是否牢固。如果连接松动,可能导致屏幕无法正常显示。 4. 检查开发环境:您提到使用的是macOS 11.5.2和idf v4.3.1。请确保您的开发环境已正确设置,包括安装所需的软件和驱动程序。 5. 检查代码:请确保您编写的代码是正确的,并且已针对ESP32-S2-HMI-DevKit-1进行了优化。如果代码存在问题,可能导致屏幕无法正常显示。 6. 检查快递损坏:您提到收到的开发板外包装已经损坏。虽然您没有提到开发板本身是否受损,但请仔细检查开发板是否有任何损坏,如屏幕破裂或元件脱落。 7. 尝试重置开发板:您可以尝试对开发板进行硬重置,看看是否能解决问题。通常,这可以通过按住开发板上的RESET按钮几秒钟来实现。 |
|
|
|
只有小组成员才能发言,加入小组>>
968 浏览 1 评论
553浏览 6评论
463浏览 5评论
有没有办法在不使用混杂模式的情况下实现Wifi驱动程序接收缓冲区访问中断呢?
447浏览 5评论
448浏览 4评论
418浏览 4评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2024-11-27 09:21 , Processed in 0.722342 second(s), Total 81, Slave 63 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号