Hello, I've programed this board with IDE 1.8.x and now I've tryed reprogramm this one with IDE cca 2.8.6 or upgraded, but it report constant error :
Where is a problem ?? Must I use IDE 1.8.x only ?
Thank zou for your help.
PavelOu
Hello to xfpd and to all, there are no errors in the sketch, there is only classical problem with builtin-led 2 or 16, but instead of builtin-led off, the transfer from C to code fall down in all cases ..
PavelOu
Yes, I will test my simpliest code for blink of Led diode ...
I've problem with test of blinking built in led diode, so I've tried compile more used and useful schetch :
// Esp8266-mac-address
/*
Rui Santos & Sara Santos - Random Nerd Tutorials
Complete project details at https://RandomNerdTutorials.com/get-change-esp32-esp8266-mac-address-arduino/
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files.
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
*/
//Wemos D1 R1 Lolin mac address 48:55:19:17:1C:50
#include <ESP8266WiFi.h>
void setup()
{
Serial.begin(9600);
Serial.println();
Serial.print("ESP Board MAC Address: ");
Serial.println(WiFi.macAddress());
}
void loop()
{
}
MOD EDIT - moved the following text outside of the code tags
So, please, if you own this Wemos Wroom-02 Devkit with CP2102, try to compile this sketch into this board on Arduino IDE 2.3.x my x = 10 is now. Thank you.
Thak you for your help. P.
It's indicating an upload error, not a compilation error.
Have you configured the correct port?
The IDE version does not matter at all.
Looks like the most recent core, but again that does not matter.
Can you show us which board exactly you are using and whether you have anything connected anything to it ?
Please do not post screenshots, Copy the output window and paste it within <code> tags.
Please confirm that you have by unplugging it and checking to see if it disappears, and shows up again when you plug it back in.
Hi Deva,
thank you for your help. I am not sure, if there is possible to communicate my problem on e-mails ...
So I try to answer you at first.
There is my sketch for blinking led test in my language at first ... this sketch was compiled with my IDE 2.8.10 in W11 system well,
but it was rejected with com problem again.
In this board library is impossible baud rate for programming core and I am not sure, if the change of it on 115200 works ...
Best wishes, Pavel Ou
Hi Maximo,
I am not sure, if the port is set well .. it is work of my W11 OS ... my IDE is 2.8.10 ...
and I cannot prinscreen this settings, but it is Silicon Lab USB Bridge ...
Thank you for your help.
Pavel Ou
Yes, I have many problems with my com ports and they drivers on W10 .. sometime helps to reinstal them .. maybe these problems are continuing on W11 .. or my board is already destroyed ... 
For example, there is report from my previous using of this board on W10 and IDE 1.8.x :
ESP-AP-server-Wroom-02-CP-po-3 2025-05-22 (W10) from monitor
- program reducted only for AP
18:08:48.961 ->
18:08:48.961 -> Server on board ESP-Wemos-Wroom-02-CP-po-3 is ready for communication !
18:08:49.065 -> Access Point name : APwemosWroomCP
18:08:49.099 -> Its password : 12345678
18:08:49.099 -> WiFi mode : WIFI_AP
18:08:49.133 -> For start scanner type W (as WLAN) !
18:08:49.167 -> For start server type S (as server ) !
18:08:49.201 -> Client timeout: 20 in seconds !
18:08:49.234 -> For client timeout type XX (as time as nr in seconds) !
18:08:49.302 -> For end of all actions type B (as Break) !
18:08:58.926 ->
18:08:58.926 -> Typed: W
18:08:58.961 -> - - - - - - - - - -
18:08:58.961 -> Zahajeni skenovani..
18:09:01.243 -> 1 WiFi sit v okoli. Seznam:
18:09:01.278 -> Seznam:
18:09:01.278 -> 1: SSID MS175, RSSI -42, encrypted
18:09:01.312 -> - - - - - - - - - - - - - -
18:09:01.346 -> For return to menu type B !
18:09:07.061 ->
18:09:07.061 -> Typed: B
18:09:07.100 -> Break and return to basic state !
18:09:07.170 ->
18:09:07.170 -> Server on board ESP-Wemos-Wroom-02-CP-po-3 is ready for communication !
18:09:07.238 -> Access Point name : APwemosWroomCP
18:09:07.306 -> Its password : 12345678
18:09:07.306 -> WiFi mode : WIFI_AP
18:09:07.340 -> For start scanner type W (as WLAN) !
18:09:07.374 -> For start server type S (as server ) !
18:09:07.408 -> Client timeout: 20 in seconds !
18:09:07.442 -> For client timeout type XX (as time as nr in seconds) !
18:09:07.510 -> For end of all actions type B (as Break) !
18:09:20.879 ->
18:09:20.914 -> Typed: 2
18:09:20.914 ->
18:09:20.914 -> Server on board ESP-Wemos-Wroom-02-CP-po-3 is ready for communication !
18:09:20.982 -> Access Point name : APwemosWroomCP
18:09:21.016 -> Its password : 12345678
18:09:21.050 -> WiFi mode : WIFI_AP
18:09:21.084 -> For start scanner type W (as WLAN) !
18:09:21.119 -> For start server type S (as server ) !
18:09:21.160 -> Client timeout: 25 in seconds !
18:09:21.194 -> For client timeout type XX (as time as nr in seconds) !
18:09:21.262 -> For end of all actions type B (as Break) !
18:09:31.658 ->
18:09:31.658 -> Typed: S
18:09:31.658 -> ESP-AP-server-Wroom-02-CP-po-3 is on !
18:09:31.693 -> AP SSID: APwemosWroomCP
18:09:31.729 -> AP password: 12345678
18:09:32.653 -> AP IP:192.168.4.1
18:09:32.653 -> AP Gateway: 192.168.4.100
18:09:32.687 -> AP Subnet Mask: 255.255.255.0
18:09:32.721 -> MAC Address: 60:01:94:46:22:80
18:09:32.755 -> DNS 1: (IP unset)
18:09:32.789 -> DNS 2: (IP unset)
18:09:32.789 -> AP HTTP server started
18:13:59.165 ->
18:13:59.165 -> SSID: APwemosWroomCP , Psk: 12345678
18:13:59.200 -> New Client.
18:13:59.234 -> GET / HTTP/1.1
18:13:59.234 -> Host: 192.168.4.1
18:13:59.268 -> Connection: keep-alive
18:13:59.302 -> Cache-Control: max-age=0
18:13:59.302 -> Upgrade-Insecure-Requests: 1
18:13:59.336 -> User-Agent: Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.6312.118 Mobile Safari/537.36 XiaoMi/MiuiBrowser/14.32.0-gn
18:13:59.506 -> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,/;q=0.8,application/signed-exchange;v=b3;q=0.7
18:13:59.676 -> Accept-Encoding: gzip, deflate
18:13:59.710 -> Accept-Language: cs-CZ,cs;q=0.9,en-US;q=0.8,en;q=0.7
18:13:59.744 ->
18:14:02.311 -> Client disconnected.
18:14:02.311 ->
18:14:06.617 ->
18:14:06.617 -> SSID: APwemosWroomCP , Psk: 12345678
18:14:06.656 -> New Client.
18:14:06.692 -> GET /5/off HTTP/1.1
18:14:06.692 -> Host: 192.168.4.1
18:14:06.731 -> Connection: keep-alive
18:14:06.731 -> Upgrade-Insecure-Requests: 1
18:14:06.770 -> User-Agent: Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.6312.118 Mobile Safari/537.36 XiaoMi/MiuiBrowser/14.32.0-gn
18:14:06.945 -> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,/;q=0.8,application/signed-exchange;v=b3;q=0.7
18:14:07.087 -> Referer: http://192.168.4.1/
18:14:07.126 -> Accept-Encoding: gzip, deflate
18:14:07.165 -> Accept-Language: cs-CZ,cs;q=0.9,en-US;q=0.8,en;q=0.7
18:14:07.203 ->
18:14:07.203 -> Green LED GPIO 5 off
18:14:07.242 -> Client disconnected.
18:14:07.281 ->
18:14:08.829 ->
18:14:08.829 -> SSID: APwemosWroomCP , Psk: 12345678
18:14:08.863 -> New Client.
18:14:08.897 -> GET /5/on HTTP/1.1
18:14:08.897 -> Host: 192.168.4.1
18:14:08.931 -> Connection: keep-alive
18:14:08.965 -> Upgrade-Insecure-Requests: 1
18:14:08.999 -> User-Agent: Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.6312.118 Mobile Safari/537.36 XiaoMi/MiuiBrowser/14.32.0-gn
18:14:09.169 -> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,/;q=0.8,application/signed-exchange;v=b3;q=0.7
18:14:09.305 -> Referer: http://192.168.4.1/5/off
18:14:09.340 -> Accept-Encoding: gzip, deflate
18:14:09.375 -> Accept-Language: cs-CZ,cs;q=0.9,en-US;q=0.8,en;q=0.7
18:14:09.444 ->
18:14:09.444 -> Green LED GPIO 5 on
18:14:09.444 -> Client disconnected.
18:14:09.478 ->
18:14:11.087 ->
18:14:11.087 -> SSID: APwemosWroomCP , Psk: 12345678
18:14:11.121 -> New Client.
18:14:11.155 -> GET /4/on HTTP/1.1
18:14:11.155 -> Host: 192.168.4.1
18:14:11.189 -> Connection: keep-alive
18:14:11.224 -> Upgrade-Insecure-Requests: 1
18:14:11.258 -> User-Agent: Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.6312.118 Mobile Safari/537.36 XiaoMi/MiuiBrowser/14.32.0-gn
18:14:11.397 -> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,/;q=0.8,application/signed-exchange;v=b3;q=0.7
18:14:11.569 -> Referer: http://192.168.4.1/5/on
18:14:11.611 -> Accept-Encoding: gzip, deflate
18:14:11.645 -> Accept-Language: cs-CZ,cs;q=0.9,en-US;q=0.8,en;q=0.7
18:14:11.679 ->
18:14:11.679 -> Red LED GPIO 4 on
18:14:11.713 -> Client disconnected.
18:14:11.747 ->
18:14:13.049 ->
18:14:13.049 -> SSID: APwemosWroomCP , Psk: 12345678
18:14:13.083 -> New Client.
18:14:13.083 -> GET /4/off HTTP/1.1
18:14:13.119 -> Host: 192.168.4.1
18:14:13.119 -> Connection: keep-alive
18:14:13.154 -> Upgrade-Insecure-Requests: 1
18:14:13.188 -> User-Agent: Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.6312.118 Mobile Safari/537.36 XiaoMi/MiuiBrowser/14.32.0-gn
18:14:13.365 -> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,/;q=0.8,application/signed-exchange;v=b3;q=0.7
18:14:13.504 -> Referer: http://192.168.4.1/4/on
18:14:13.538 -> Accept-Encoding: gzip, deflate
18:14:13.572 -> Accept-Language: cs-CZ,cs;q=0.9,en-US;q=0.8,en;q=0.7
18:14:13.642 ->
18:14:13.642 -> Red LED GPIO 4 off
18:14:13.642 -> Client disconnected.
18:14:13.676 ->
18:14:14.909 ->
18:14:14.909 -> SSID: APwemosWroomCP , Psk: 12345678
18:14:14.943 -> New Client.
18:14:14.977 -> GET /5/off HTTP/1.1
18:14:14.977 -> Host: 192.168.4.1
18:14:15.011 -> Connection: keep-alive
18:14:15.045 -> Upgrade-Insecure-Requests: 1
18:14:15.079 -> User-Agent: Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.6312.118 Mobile Safari/537.36 XiaoMi/MiuiBrowser/14.32.0-gn
18:14:15.250 -> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,/;q=0.8,application/signed-exchange;v=b3;q=0.7
18:14:15.388 -> Referer: http://192.168.4.1/4/off
18:14:15.422 -> Accept-Encoding: gzip, deflate
18:14:15.456 -> Accept-Language: cs-CZ,cs;q=0.9,en-US;q=0.8,en;q=0.7
18:14:15.525 ->
18:14:15.525 -> Green LED GPIO 5 off
18:14:15.525 -> Client disconnected.
18:14:15.559 ->
17:00:44.042 -> Server on board ESP-Wemos-Wroom-02-CP is ready for communication !
17:00:44.142 -> Access Point name : APwemosWroomCP
17:00:44.142 -> Its password : 12345678
17:00:44.195 -> WiFi mode : WIFI_AP
17:00:44.195 -> For start scanner type W (as WLAN) !
17:00:44.242 -> For start server type S (as server ) !
17:00:44.296 -> Client timeout: 20 in seconds !
17:00:44.343 -> For client timeout type Txx (as Time and nr in seconds) !
17:00:44.396 -> For end of all actions type B (as Break) !
17:00:54.624 ->
17:00:54.624 -> Typed: W
17:00:54.624 -> - - - - - - - - - -
17:00:54.671 -> Zahajeni skenovani..
17:00:56.930 -> 1 WiFi sit v okoli. Seznam:
17:00:56.930 -> Seznam:
17:00:56.977 -> 1: SSID MS175, RSSI -47, encrypted
17:00:56.977 -> - - - - - - - - - - - - - -
17:00:57.031 -> For return to menu type B !
17:00:57.031 ->
17:00:57.078 -> Typed:
17:00:57.078 ->
17:00:57.078 -> Typed:
17:00:57.078 ->
17:01:08.315 ->
17:01:08.315 -> Typed: B
17:01:08.315 -> Break and return to basic state !
17:01:08.400 ->
17:01:08.400 -> Server on board ESP-Wemos-Wroom-02-CP is ready for communication !
17:01:08.494 -> Access Point name : APwemosWroomCP
17:01:08.531 -> Its password : 12345678
17:01:08.531 -> WiFi mode : WIFI_AP
17:01:08.578 -> For start scanner type W (as WLAN) !
17:01:08.632 -> For start server type S (as server ) !
17:01:08.632 -> Client timeout: 20 in seconds !
17:01:08.678 -> For client timeout type Txx (as Time and nr in seconds) !
17:01:08.763 -> For end of all actions type B (as Break) !
17:01:09.666 ->
17:01:09.666 -> Typed:
... etc.
Yes, I did do it yesterday and today, nothing new ..
Please edit your post and put the output text in code tags to make it easier to read and copy
So the sketch compiles, this was confirmed already, no attempt to upload will be made unless compilation is successful.
Hopefully and probably not.
a cp2012
and this doesn't work on your W11 machine ?
i was asking for the output text, but what was posted is the 'Serial monitor output'
This is the output text.
Please check in this order.
- The device (cp2102 or similar) in the device manager to see if the device is installed properly
- No other applications are using the same port, this includes the Serial monitor during upload
You can try to uninstall the cp2102 and re-install it, try another hub and try another usb cable.
Please show us a picture of the board or a link to where you got the board from.
CP2102 works with NodeMCU V3 ... the board wit this CP ...
so when you open the Serial monitor at 115200 and press reset, do you get the same (or similar) message on the monitor as you did with your W10 machine ?
Does the device manager show that the board/USB to TTL bridge is properly installed ?
Also please to exclude possible interference from other parts, disconnect all else from the board. Just a USB connection. (also one of the solder joints on the USB plug looks damaged)
Connector - Yes, I know, that on these board are connectors USB_B bad solded and one is already in my basket .. but actual one seems to hold zet normal and battery is charged .
Bauds - are set by IDE automaticly - for normal serial communication I use 9600 baud . IDE has normally no problem to choose self the more suitable rate.
Boards - can we compare reloaded board data by IDE ?
CP2102 - there is photo of board NodeMcu V3 with CP2102 what I've programmed by IDE well :
Maybe my last result - so, when I am connected on USB, battery is charded and Led light red or green.
I've had probably actual on board programmed blink test, but builtin led do not blink now.
Then I can connect to monitor from IDE, or another serial monitor, so CP2102 com is OK .
Now, when I disconnect USB and I switch power on board on, the blue built in led started blink .
So I think, there is a problem between USB and local battery powering, what can block the communication between IDE and Esp Wroom ..
But maybe I can do my last experiment to take my battery out ...
Heureka probably again, so thank you all for your patience with me .. and sorry that I am probably more and more sclerotic ..
But there is manual for all owners of this very special board .. :) .. and I am sorry, that I've lost my manual last year, sure ..
So my renewed manual:
Battery off, USB On and power swith ON !!!
Best wishes for all.
Pavel Ou
p.s. there is a question, if battery must be by programming off. I am now in doubts to test it ..
For producents - how to use this type of boards and do not shut this idea with it ... maybe some special breadboard can solve the practical problems with battery off .
p.s. Yes, battery can be on this board ... now we are ready with programming this board in IDE 2.8.x .... but with the built in Led ?? ... I open better new topic.