DFRobot / uPyCraft

287 stars 80 forks source link

cp210x serial port problem #26

Open nedoskiv opened 5 years ago

nedoskiv commented 5 years ago

Hello, First I want to thank you for creating this tool and make our python programming easier.

I started to use esp32 (lolin32 lite) it works fine with upycraft, today I reveived 2 other esp32 boards, but their com ports (usb 2 uart ) use different chip - cp210X (old board is ch34X, here is what happen, when I execute sciript it do not catch some of the output (like os error) etc (here I got a script that import machine and perform reset using machine.reset(). Output in upycraft is cut and it still thinking that program is running and need to be interrupted with control - C :

`exec(open('./reset.py').read(),globals())` e I (434) cpu_start: Pro cpu start user code I (5) cpu_start: Starting scheduler on PRO CPU. Oprogram is running,do anything with stop it!1 program is running,do anything with stop it!1 program is running,do anything with stop it!1 This is the same stuff using putty to open serial port:

``exec(open('./reset.py').read(),globals()) ets Jun 8 2016 00:22:57

rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) configsip: 0, SPIWP:0xee clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 mode:DIO, clock div:2 load:0x3fff0018,len:4 load:0x3fff001c,len:4732 load:0x40078000,len:7496 load:0x40080400,len:5512 entry 0x4008114c I (399) cpu_start: Pro cpu up. I (399) cpu_start: Single core mode I (399) heap_init: Initializing. RAM available for dynamic allocation: I (403) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM I (409) heap_init: At 3FFC4F68 len 0001B098 (108 KiB): DRAM I (415) heap_init: At 3FFE0440 len 00003BC0 (14 KiB): D/IRAM I (422) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM I (428) heap_init: At 40091604 len 0000E9FC (58 KiB): IRAM I (434) cpu_start: Pro cpu start user code I (5) cpu_start: Starting scheduler on PRO CPU. OSError: [Errno 2] ENOENT MicroPython v1.9.4-684-g51482ba92 on 2018-11-20; ESP32 module with ESP32 Type "help()" for more information. ``

guess since putty catch out all of the board output that is not a serial driver problem.

nedoskiv commented 5 years ago

i decided to check that on another windows computer, same story.