|
Nr |
Type |
Shop |
Datum |
Opmerkingen |
|
1 |
ESP-01 |
MiniInTheBox 1511281222354851 |
01-12-‘15 |
Apr 2019: 1ste test HeRo domotica met 1
relay en een HenkLIN command interface. In gebruik Relais Test. Nog geen vast
IP, Hostname HeRoESP2 MacAdres: 5c:cf:7f:0b:8f:be |
|
2 |
ESP-01 |
AliExpress 900089233911447 JSSD Technology |
29-03-’19 |
Tnkmo |
|
3 |
ESP-01S |
AliExpress 095638779681447 All goods are Freeshipping
store |
30-10-’18 |
Jan ’23: Gebruikt voor WiFi POCs. Werkt wel, maar
nadeel is dat je steeds de switch moet schakelen en uit/in de USB port moet
doen, verder op ESP Nr 7 MacAdres: 80:7D:3A:3E:E3:74 |
|
4 |
ESP-01S |
AliExpress 900089233901447 Hailangniao A+A+A+
store |
29-03-’19 |
|
|
5 |
NodeMCU V3 ESP8266 CP2102 driver |
AliExpress 095638779721447 HESAI 3C |
30-10-’18 |
Jan 2019: MacAdres: cc:50:e3:4a:55:37.Geen box voor gemaakt. Eerst HenkLIN SOP, Hostname HeRoESP1,
test met 32 SMD LEDs aan HenkLIN SOP PCB. Aug 2020: In Servo test project box
met PCA9685, is afbouw van ESP Nr 11. IP adress: 192.168.178.99 (op modem static DNS), |
|
6 |
NodeMCU V1.0 Update Industry V4.0 V2.0 Lua/amica ESP8266MOD ESP12E |
AliExpress 900089233921447 Advanced Tech |
29-03-’19 |
Mei 2019:Geen opbergdoosje. Wordt 2de test
(ESP-01 was 1ste) domotica met relay en LCD. Hostname: HeRoDomo01 IP adres: 192.168.178.98 /
MacAdres: 3c:71:bf:3a:4d:cc Jul ’19: IP Adres is static gezet in ESP Code van
HeRoDomo01. |
|
7 |
WeMOS D1 Lua |
AliExpress 900089233921447 Advanced Tech |
29-03-’19 |
MacAdres: EC:FA:BC:26:CA:BE Jan ’23: Test met HeRoTimeUtils. Was eerst op ESP Nr
3, maar hierop moet je steeds de switch zetten. Wemos is makkelijker. Apr
’23: In HeRoWiFiClock |
|
8 |
NodeMCU V3 Lua ESP8266EX CH340 + 32MB extra |
AliExpress 900089233951447 Mega Semiconductor |
29-03-’19 |
Mei
‘20: Geen opbergdoosje voor gemaakt. Wordt
test met RFID RC522. Vast
IP adres: 192.168.178.100,
MacAdres: cc:50:e3:2e:77:10 |
|
9 |
NodeMCU ESP32 |
AliExpress 900089233861447 XM (Shenzhen) elec |
29-03-’19 |
Dec 2023:NTC 3950 TempSensor, maar dit project is
mislukt (zie code). |
|
10 |
NodeMCU V3 ESP8266 Not soldered |
AliExpress 900089233861447 XM (Shenzhen) elec |
29-03-’19 |
|
|
11 |
NodeMCU V3 ESP8266 CH340G driver |
AliExpress 900276514121447 JIAQISHENG Store |
16-07-’19 |
Okt 19: MacAdres: 2e:f4:32:20:b9:8b . In plexiglasboard. Feb ’20: PCA9685 servo test (zie ESP Nr 5). Nov ’23:Power Control (zie ESP Nr 12). Jan ’24:LAN Jan24:Reset btn lijkt stuk, kan komen doordat hij in
NodeMCU base board zit. |
|
12 |
NodeMCU V3 ESP8266
CP2102 driver 4MB |
AliExpress 900276514121447 JIAQISHENG Store |
16-07-’19 |
Apr ‘20:Geen opbergdoosje. Start met ESP_cdfe30.
Eerst POC PowerControl. Sinds Jan ’21 SIP/SOP_Control. In Jul ‘21 gebruikt
voor testen bipolair 28-BYJ-48 motor met L293D IC. Daarna weer
SIP/SOP_control. Nov 23:PowerControl |
|
13 |
ESP32 WROOM |
AliExpress 900276514121447 HESAI 3C
Electronic Store |
16-07-’19 |
|
|
14 |
ESP32-WROOM-32U |
AliExpress
3004622125301447 S Robot Official Store |
28-07-‘20 |
Geen opbergdoosje voor gemaakt. In test/demo
gaatjesprint met gLCD, HeRoTempControl test. Nu in gebruik CncOfZo project. |
|
15 |
ESP32-WROOM-32U |
AliExpress 3006707149861447 Electricology
Store |
31-10-‘20 |
1ste device (van 15-09-20) is vanaf begin
stuk, wordt heet als je ‘m aansluit. Is door een nieuwe vervangen. De oude heeft plakker
espNr 15 (stuk), de nieuwe heeft plakker espNr 15 (new). MacAdres: 30:ae:a4:9d:4c:81 |
|
16 |
ESP32-WROOM-32D |
AliExpress 3005810052641447 S Robot Official Store |
15-09-‘20 |
Geen out-of-the-box output.Vanaf jan 2021 vervangt deze
ESP Nr 18 in 3D Printerkast (HeRoTempControl). MacAdres: ??,IP adres: |
|
17 |
ESP32-WROOM-32D |
AliExpress 3006444251601447 Electricology
Store |
14-10-‘20 |
In test/demo gaatjesprint met gLCD, HeRoTempControl
test (als vervanger van ESP Nr 14). MacAdres:7c:9e:bd:07:59:41 |
|
18 |
ESP32-WROOM-32D |
AliExpress 3008326637591447 All goods are free
shipping store |
02-01-21 |
Out of the box geen
output. In gebruik HeRoTempControl in 3D
printerkast. Dec ‘20:AMS1117 verbrand, in 3D printerkast zit nu ESP Nr 16. Jan
2021 nieuwe op AliExpress, dit is nu dus ESPNr 18. MacAdres 7c:9e:bd:38:8c:84 (Zie 22 jan ‘21).
Nog geen bestemming, HeRoTempControl blijft ESPNr 16 |
|
19 |
ESP32-WROOM-32U |
AliExpress 3006707149631447 Yikeshu Store |
31-10-‘20 |
Voor out-of-the-box
output, zie verderop. MacAdres: 30:ae:a4:96:c3:89 |
|
20 |
NodeMCU V3 ESP8266 CP2102 driver 4MB |
AliExpress 3009633739261447 ElectronicFans |
25-02-’21 |
Mar ‘21: Start op met WiFi FaryLink_472943. Met
baudrate 74880 in ArduinoIDE geeft hij output, net als andere firmwares.
sketch-Blink-LED werkt en daarna ook sketch-WiFi-Scan. MacAdres: 43:29:47:1F:9C:9C Is SOP_Control Server, hostname HeRoESP1, IP adress
.99 (in code) |
|
21 |
ESP32-CAM |
AliExpress
3010317256741447 Wanzai Store.
Besteld met base board. |
25-03-’21 |
Apr ‘21: Start met WiFi netwerk+webserver (volgens
chinese logging op COM poort). Onbekend IPadres. Niet geprobeerd connectie
naar IP adres te maken (netwerk=CAM9. MacAdres: 9C:9C:1F:EA:65:39. Arduino Voorbeeld webcamserver werkt (device op
WRoom, met Huge memory map). Vast IPadres 192.168.178.105.Horizontale
streepjes op beeld, kan power zijn. |
|
22 |
ESP32-CAM |
AliExpress 3009972877531447
All goods are free shipping. |
07-03-’21 |
Apr ‘21: Start op met WiFi netwerk+webserver (volgens
chinese logging op COM poort). Niet geprobeerd connectie naar IP adres te
maken (netwerk=CAM39…). MacAdres: 9C:9C:1F:CA:54:31. Nog niks mee gedaan. |
|
23 |
NodeMCU V3 ESP8266MOD CH340G |
AliExpress 3012665344201447 All goods are free
shipping store |
13-08-‘21 |
Zie onder Sep ’21. Is hetzelfde type als ESPNr 11.
Met PlatformIO,windows11 lukt proggen niet (vanwege CH340?), MacAdres: aa:48:fa:cd:2f:46 |
|
24 |
NodeMCU V3 ESP8266MOD CH9102X |
AliExpress 3012665344201447 All goods are free
shipping store |
13-08-‘21 |
ESP-12F. Zie onder,Sep ’21. MacAdres 98:c8:ac:3f:aa:a2 |
|
25 |
NodeMCU V3 ESP8266
ESP12 Not Soldered |
AliExpress 3012665344181447 SZ Aitexm Store |
13-08-‘21 |
Zie onder,Sep ’21. Lijkt hetzelfde type als ESPNr 10,
maar heeft opschrift Wemos. |
|
26 |
ESP32-WROOM-32D |
AliExpress 3012756420751447 All goods are free
shipping store |
23-08-‘21 |
Zie onder, Sep ’21. MacAdres:
94:b9:7e:e4:69:c1. Gebruikt als POC voor
A3967EasyDriver steppermotor, Aug 22. Is weer terug in box |
|
27 |
ESP32-WROOM-32U |
AliExpress 3012756420751447 All goods are free
shipping store |
23-08-‘21 |
Zie onder, Sep ’21. MacAdres:
94:b9:7e:e4:77:01. Is in gebruik in
‘DeurOpener’ project. |
|
28 |
Wemos D1 Mini
V4.0.0 USB-C |
AliExpress 3021075453921447 TZT teng Offical
Store |
01-02-‘23 |
Is met JST-SH
1.0mm pitch 4pin Power&I2C connector c6:5b:be:e5:33:80 (mbv AT+CIPAPMAC?) |
|
29 |
Wemos D1 Mini
V4.0.0 USB-C |
AliExpress 3021683012561447 TZT teng Offical
Store |
01-03-‘23 |
Is met JST-SH
1.0mm pitch 4pin Power&I2C connector 26:62:ab:03:bc:5c (mbv AT+CIPAPMAC?) |
|
30 |
NodeMCU D1 Mini MODULE
CH340 |
AliExpress 3021683012621447 Advanced Tech |
01-03-‘23 |
Factory output niet bekeken, gebruikt voor
TestHeRoSettings, Apr ‘23 MacAdres:E0:98:06:8A:94:BC |
|
31 |
ESP32-S2 Mini0 |
AliExpress 3021683012581447 ModuleFans |
01-03-‘23 |
MacAdres:48:27:E2:51:6A:0A (met HelloWorld VS Code). Heeft een USB Serial driver, geeft problems, zie
onder (24 sep 23). |
|
32 |
ESP-12E Wemos D1
Board. CH340 driver |
AliExpress 3025193680961447 ModuleFans |
25-08-‘23 |
Zie onder, Sep ’23 MacAdres:0a:3a:8d:d1:e6:b2 (mbv AT+CIPAPMAC?) CH340 driver doet raar, zie onder |
|
33 |
ESP32-S3 N16R8 DevKitC-1 CH343p driver |
AliExpress 3025193681021447 Great IT
electronics components |
25-08-‘23 |
MacAdres:f4:12:fa:ce:d7:38. Met micropython ondervraagd, zie onder. Heeft een NeoPixel
LED op board (aan pin 8, GPIO_8) |
|
34 |
ESP32-C3 Mini
USB-C ??? driver |
AliExpress 3028090177061447 All great store |
04-12-‘23 |
MacAdres:??. Nog nieuw |
|
35 |
ESP32-WROOM-32 CH9102X driver |
AliExpress 3028090177101447 SAMIORE Store |
04-12-‘23 |
MacAdres:??. Nog nieuw |
|
36 |
NodeMCU V3 ESP8266
CP2102 driver |
AliExpress 3028779223401447 TZT Choice Store |
01-01-‘24 |
MacAdres:??. Nog nieuw |
|
37 |
NodeMCU V3 ESP8266
CP2102 driver |
AliExpress 3028779223401447 TZT Choice Store |
02-01-‘24 |
MacAdres:??. Nog nieuw |
|
38 |
NodeMCU V3 ESP826 CH340G driver |
AliExpress 3028779223421447 LongCheng Micro
Store |
02-01-‘24 |
MacAdres:??. Nog nieuw |
Overzicht:
Eerste ervaringen met NodeMCU,
besteld 25 okt ’18. Dit wordt HeRoESP1, mac adres cc:50:e3:4a:55:37,
vast IP adres werkt.
Default
maakt ESP een AccessPoint ESPxxyyzz met laatste 3 nibbels van mac adres. ESP01
besteld bij MiniInTheBox, is in april ’19 gebruikt met relay module voor
domotica. In maart + april ’19 nieuwe bestelling AliExpres gedaan, zie tabel
hieronder. mDNS werkt, voor vast IP adres, dit met WiFi.config (Zie
HenkLIN_SOP_Server) of in Ziggo modem DNS reservering op MacAddress, bijv voor IP
adress 192.168.178.99, werkt.
ESP32-WRoom-32u
of 32d heeft meer (io) pins dan een gewone W-ROOM. Laatste nieuwste is ESP32-S3.
Misschien ooit nog een Witty ESP bestellen?
Samenvatting
Sep
23:Veel geleerd bij testen ESP Nr 32. Dit is een ESP-12E en bij booten kwam er
een ‘standaard’ output zoals bij meerdere ESP. Dit begint met:
ets
Jun 8 2016 00:22:57 en dan rst:0x1 (POWERON_RESET),boot:0x13
(SPI_FAST_FLASH_BOOT) etc.
Daarna
nog meer tekst en aan het eind strooi (troep) karakters. Dit had ik wel vaker
gezien maar na uitzoeken blijkt dat de tekst ‘est Jun’ etc van de ESP boootloader is en dat de ‘strooi’
karakters aan het eind, van het echte ‘interne’ programma is. De ESP bootloader
heeft een andere baudrate dan het echte programma. Dit heeft iets te maken met
het kristal op de print. De bootloader heeft een baudrate van 74880 en het
programma werkt op 115200. Met 74880 zie je dus de bootloader tekst en met
115200 de firmware output. Output bekeken met ReadCom.ps1, een zelf gemaakt
Powershell script. Let op dat deze niet in de Powershell ISE kan draaien, er is
dan geen console. Je moet een Powershell window maken.
ESP
Nr 33, is een ESP32-C3 N16-R8 en heeft micropython als firmware en een NeoPixel
LED op board aan pin 48 (GPIO_48).
ESP
Nr 32 heeft een CH340 driver, de laatste versie (3.8) werkt niet, geeft
permission errors. Versie 3.5.2019 doet ’t wel goed, zie CH441SER.exe, heb ik
gedownload.
Verdere info:
NodeMCU
ESP8266 van AliExpress, 30 okt ’18 (espNr 5), is experiment board met CP2101
serial converter, kost Euries 2,45.
NodeMCU
is standaard met LUA, een interpreter. Algemene indruk op Internet is dat LUA
interpreter wel makkelijk is, maar ‘traag’en instabiel.
Arduino
IDE en bijbehorende taal is alternatief, meer low-level, in C(++) en met goede
libraries.
In
LUA doe je iets als: gpio.mode(0,gpio.OUTPUT);
gpio.write(0,0)
In arduino: int LED_Pin = D0; void setup() { pinMode(LED_Pin, OUTPUT); }
void loop() { digitalWrite(LED_Pin, LOW); delay(3000); digitalWrite(LED_Pin,
HIGH); delay(1000); }
NodeMCU
ESP8266 heeft 80MHz cpu, 2 spi poorten,
1 ervan is voor spi flash system, andere SPI poort is wel vrij.
Opvolger
ESP8266 is ESP32, deze heeft snellere 160MHz cpu, 150Mbps WiFI, bluetooth +
hall sensor en touch sensitive pins en 4 SPI channels.
ESP32 types: DOIT ESP DEVKIT,
Xiuxin ESP32 Dev board, Adafruit feather, Sparkfun ESP32 thing, WEMOS EPS32 met
battery holder, ESP32 met OLED, ESP32 SX1278 met LoRa. ESP32S heeft 38 IO Pins, is dit hetzelfde als de
DEVKITC?
NodeMCU/ESP identificatie:
Open
gitbash shell op C:\ESP8266\ESPlorer en doe ./ESPlorer. Laatste
selectie is COM8, 115200 baud. Kies rechts Open, daarna links bij AT kies je
GMR (is at identificatie). Dan links onderin bij WiFi Station kies je
CIPSTAMAC? en dan zie je macAddress.
Eerste ervaringen met NodeMCU HeRoESP1:
Op
breadboard gezet, micro-usb kabel aangesloten, apparaatbeheer zegt dat de
drivers missen. Drivers als zip gedownload van https://www.silabs.com/products/development-tools/software/usb-to-uart-bridge-vcp-drivers.
Zip
uitgepakt in download en in apparaatbeheer de drivers geinstalleerd.
Met
putty geconnect (serial com3, 9600 baud) en het werkt! Output van putty is:
NodeMCU
custom build by frightanic.com ↵ branch: master ↵ commit:
c8037568571edb5c568c2f8231e4f8ce0683b883
SSL: false
↵ modules: cjson,file,gpio,net,node,pwm,tmr,uart,wifi
build built on: 2016-03-14 02:10
↵ powered by Lua 5.1.4 on SDK 1.4.0
↵ lua: cannot open init.lua
↵ >
Is
niet de allernieuwste waarschijnlijk (en is ook een custom build uit git, nog uitzoeken).
ESPlorer
gedownload, doet t soms wel, soms niet, starten met bat, niet met jar.
Nieuwe
flash build gemaakt, en met NodeMCU-PyFlasher-4.0-64.exe geflasht. Jammer, json
vergeten, kan later nog.
Command: esptool.py --port COM3 --baud 9600 --after no_reset write_flash
--flash_mode dio 0x00000
C:\ESP8266\Flashes\nodemcu-master-10-modules-2019-03-01-19-47-49-integer.bin
esptool.py v2.6 ↵ Serial
port COM3 ↵ Connecting.... ↵
Detecting chip type... ESP8266 ↵
Chip is ESP8266EX ↵
Features: WiFi ↵
MAC: cc:50:e3:4a:55:37 ↵ Uploading stub... ↵ Running stub... ↵ Stub running... ↵
Configuring flash size... ↵ Auto-detected Flash size: 4MB ↵ Flash params set to 0x0240 ↵
Compressed 438272 bytes to 284920... ↵
Writing at 0x00000000... (5 %)
Verder
dan dit kwam het niet…
ESP8266Flasher
van nodemcu gedownload, deze deed ’t wel, duurde een minuut of 10. Nu is de output van
putty, bij 115200 baud:
NodeMCU custom build by frightanic.com
↵ branch: master
↵ commit: 11592951b90707cdcb6d751876170bf4da82850d
SSL: false
↵ modules:
file,gpio,http,mqtt,net,node,spi,tmr,uart,wifi
build created on 2019-03-01 19:46
↵ powered by Lua 5.1.4 on SDK 2.2.1(6ab97e9)
↵ lua: cannot open init.lua
↵ >
In
ESPlorer snippet gemaakt, deze laat de LED op het board branden met: gpio.mode(0,gpio.OUTPUT); gpio.write(0,0)
Dan
met Arduino IDE gedaan. Is andere taal (Arduino C++) maar werkt ook. Default baudrate
is 9600, 256000 gaat ook, alleen mis je soms chars in Serial monitor, 115200 is
optimaal. Projectjes maken gaat redelijk simpel. HenkLIN SIP Met SPI gebruikt
als SOP (Output) met 32 LEDs, gaat goed. ESP maakt default een WiFi AP genaamd ESP4a5537, dus laatste 3 bytes van mac adres. Is uit te zetten
door alleen station mode bij wifi.begin te zetten. Zelf HeRoESP1 AP gemaakt met wachtwoord I3d3r33n. Ook begonnen met Arduino library voor MCP23S17 SPI
controle.
ESP01
gebruikt voor Relay module test. ESP01 van MiniInThebox, besteld 1 dec 2015. Mac address 5c:cf:7f:0b:8f:be, nog geen vast IP address.
ESP01
moet in ‘programming mode’staan om te kunnen proggen. Dit doe je door Pin5
(GPIO0) en Pin 1 (Gnd) met elkaar te verbinden.
GPIO1
niet gebruiken voor LED blink, want deze is TX dus zie je geen serial output. Baudrate 115200 is
OK.
Pin 1=GND, Pin 2=GPIO1/TXD,
Pin3=GPIO2, Pin4=CH_PD (Enable), Pin5=GPIO0, Pin6=Reset, Pin7= GPIO3/RX, Pin8=Vcc
ESP
NodeMCU connecties (zie randomnerdtutorials:
https://randomnerdtutorials.com/esp8266-pinout-reference-gpios/ ):.
Excerpt uit randomnerds website voor
ESP NodeMCU pin gebruik:
Best
Pins to Use – ESP8266
One important thing to notice
about ESP8266 is that the GPIO number doesn’t match the label on the board
silkscreen. For example, D0 corresponds to GPIO16 and D1 corresponds to GPIO5.
The following table shows the correspondence between the labels on the
silkscreen and the GPIO number as well as what pins are the best to use in your
projects, and which ones you need to be cautious.
The pins highlighted in green
are OK to use. The ones highlighted in yellow are OK to use, but you need to
pay attention because they may have unexpected behavior mainly at boot. The
pins highlighted in red are not recommended to use as inputs or outputs.
|
Label |
GPIO |
Input |
Output |
Notes |
|
D0 |
GPIO16 |
no
interrupt |
no PWM or I2C support |
HIGH at boot, used to wake up
from deep sleep |
|
D1 |
GPIO5 |
OK |
OK |
often used as SCL (I2C) |
|
D2 |
GPIO4 |
OK |
OK |
often used as SDA (I2C) |
|
D3 |
GPIO0 |
pulled
up |
OK |
connected to FLASH button,
boot fails if pulled LOW |
|
D4 |
GPIO2 |
pulled
up |
OK |
HIGH at boot, connected to
on-board LED, boot fails if pulled LOW |
|
D5 |
GPIO14 |
OK |
OK |
SPI
(SCLK) |
|
D6 |
GPIO12 |
OK |
OK |
SPI
(MISO) |
|
D7 |
GPIO13 |
OK |
OK |
SPI
(MOSI) |
|
D8 |
GPIO15 |
pulled
to GND |
OK |
SPI (CS), Boot fails if pulled HIGH |
|
RX |
GPIO3 |
OK |
RX pin |
HIGH at boot |
|
TX |
GPIO1 |
TX pin |
OK |
HIGH at boot, debug output at
boot, boot fails if pulled LOW |
|
A0 |
ADC0 |
Analog Input |
X |
GPIOs
connected to the Flash Chip: GPIO6 to GPIO11 are usually connected to the
flash chip in ESP8266 boards. So, these pins are not recommended to use.
Pins
used during Boot: The ESP8266 can be prevented from booting if some pins
are pulled LOW or HIGH. Pin states on BOOT:
·
GPIO16: pin is high at BOOT ; GPIO0: boot failure
if pulled LOW; GPIO2: pin is high on BOOT, boot failure if pulled LOW
·
GPIO15: boot failure if pulled HIGH; GPIO3: pin
is high at BOOT; GPIO1: pin is high at BOOT, boot failure if pulled LOW
·
GPIO10: pin is high at BOOT; GPIO9: pin is high
at BOOT
Pins
HIGH at Boot: There are certain pins that output a 3.3V signal when
the ESP8266 boots. This may be problematic if you have relays or other
peripherals connected to those GPIOs. The
following GPIOs output a HIGH signal on boot:
·
GPIO16 + GPIO3 + GPIO1 + GPIO10 + GPIO9
Additionally, the other GPIOs,
except GPIO5 and GPIO4, can output a low-voltage signal at boot, which can be
problematic if these are connected to transistors or relays. You can read this
article that investigates the state and behavior of each GPIO on boot.
GPIO4 and GPIO5 are the most
safe to use GPIOs if you want to operate relays.
Analog
Input: The ESP8266 only supports analog reading in one GPIO. That GPIO is
called ADC0 and it is usually marked on the silkscreen as A0.
The maximum input voltage of
the ADC0 pin is 0 to 1V if you’re using the ESP8266 bare chip. If you’re using
a development board like the ESP8266 12-E NodeMCU kit, the voltage input range
is 0 to 3.3V because these boards contain an internal voltage divider.
On-board
LED: Most of the ESP8266 development boards have a built-in LED. This LED is
usually connected to GPIO2.
The LED is connected to a
pull-down resistor, so when you send a HIGH signal the LED turns off.
RST
Pin: When the RST pin is pulled LOW, the ESP8266 resets. This is the same as
pressing the on-board RESET button.
GPIO0:
When
GPIO0 is pulled LOW, it sets the ESP8266 into bootloader mode. This is the same
as pressing the on-board FLASH/BOOT button.
GPIO16:
GPIO16
can be used to wake up the ESP8266 from deep sleep. To use this wake up ,
GPIO16 should be connected to the RST pin.
I2C:
The
ESP8266 doens’t have hardware I2C pins, but it can be implemented in software. So
you can use any GPIOs
as I2C. Usually, the following GPIOs are used as I2C pins:
·
GPIO5: SCL + GPIO4: SDA
SPI:
The
pins used as SPI in the ESP8266 are:
·
GPIO12: MISO + GPIO13: MOSI + GPIO14:
SCLK + GPIO15: CS
PWM
Pins: ESP8266 allows software PWM in all I/O pins: GPIO0 to GPIO16. PWM
signals on ESP8266 have 10-bit resolution.
Interrupt
Pins: The ESP8266 supports interrupts in any GPIO, except GPIO16.
Eenzelfde overzicht met PinOuts, tips
en ervaringen voor ESP32 DevKitC,ook van randomnerds: Best Pins to Use – ESP32
Versie met 36 Pins (met een antenne
recht tegenover de USB zijde):
ESP32 Peripherals, they include:
The ADC (analog to digital
converter) and DAC (digital to analog converter) features are assigned to
specific static pins. However, you can decide which pins are UART, I2C, SPI,
PWM, etc – you just need to assign them in the code. This is possible due to
the ESP32 chip’s multiplexing feature.
Although you can define the
pins properties on the software, there are pins assigned by default as shown in
the following figure (this is an example for the ESP32 DEVKIT V1 DOIT board
with 36 pins – the pin location can change depending on the manufacturer).
Additionally, there are pins
with specific features that make them suitable or not for a specific project.
The following table shows what pins are best to use as inputs, outputs and
which ones you need to be cautious.
Input
only pins
GPIOs 34 to 39 are GPIO–input
only. They don’t have internal pull-ups or pull-down resistors. They can’t be
used as outputs:
GPIO 34
GPIO 35
GPIO 36
GPIO 39
SPI
flash integrated on the ESP-WROOM-32
GPIO 6 to GPIO 11 are exposed
in some ESP32 development boards. However, these pins are connected to the
integrated SPI flash on the ESP-WROOM-32 chip and are not recommended for other
uses. So, don’t use these pins in your projects:
GPIO 6 (SCK/CLK)
GPIO 7 (SDO/SD0)
GPIO 8 (SDI/SD1)
GPIO 9 (SHD/SD2)
GPIO 10 (SWP/SD3)
GPIO 11 (CSC/CMD)
The pins marked OK are ok to
use. The ones highlighted in yellow are OK to use, but you need to pay
attention because they may have unexpected behavior mainly at boot. The pins
highlighted in red are not recommended to use as inputs or outputs.
|
GPIO |
Input |
Output |
Notes |
Toepassing in project |
|
0 |
pulled up |
OK |
Don’t
use, outputs PWM signal at boot |
|
|
1 |
TX pin |
OK |
Don’t
use as input, debug output at boot |
|
|
2 |
OK |
OK |
connected
to on-board LED |
|
|
3 |
OK |
RX pin |
Don’t
use as output,HIGH at boot |
|
|
4 |
OK |
OK |
|
|
|
5 |
OK |
OK |
outputs
PWM signal at boot |
|
|
6 |
x |
x |
connected
to the integrated SPI flash |
|
|
7 |
x |
x |
connected
to the integrated SPI flash |
|
|
8 |
x |
x |
connected
to the integrated SPI flash |
|
|
9 |
x |
x |
connected
to the integrated SPI flash |
|
|
10 |
x |
x |
connected
to the integrated SPI flash |
|
|
11 |
x |
x |
connected
to the integrated SPI flash |
|
|
12 |
OK |
OK |
Take
care if used as input, boot fail if pulled high |
|
|
13 |
OK |
OK |
|
|
|
14 |
OK |
OK |
outputs
PWM signal at boot |
|
|
15 |
OK |
OK |
outputs
PWM signal at boot |
|
|
16 |
OK |
OK |
|
|
|
17 |
OK |
OK |
|
|
|
18 |
OK |
OK |
|
|
|
19 |
OK |
OK |
|
|
|
21 |
OK |
OK |
|
|
|
22 |
OK |
OK |
|
|
|
23 |
OK |
OK |
|
|
|
25 |
OK |
OK |
|
|
|
26 |
OK |
OK |
|
|
|
27 |
OK |
OK |
|
|
|
32 |
OK |
OK |
|
|
|
33 |
OK |
OK |
|
|
|
34 |
OK |
Input
only, heeft geen internal pull-ups |
|
|
|
35 |
OK |
Input
only, heeft geen internal pull-ups |
Lijkt niet te werken, ook
niet met weerstand |
|
|
36 |
OK |
input only . Niet
gebruiken: is ESP enable, dus disablet de ESP als hij laag wordt |
|
|
|
39 |
OK |
input only. Lijkt ook geen
pull-ups te hebben. Niet geschikt voor input (misschien met een 10K pullup) |
Bij gebruik als input
(Z-As stopper in CNCOfZo), begon hij te denderen. Niet geprobeerd met een
pullup weerstand |
Continue reading for a more
detail and in-depth analysis of the ESP32 GPIOs and its functions.
Capacitive
touch GPIOs
The ESP32 has 10 internal capacitive
touch sensors. These can sense variations in anything that holds an electrical
charge, like the human skin. So they can detect variations induced when
touching the GPIOs with a finger. These pins can be easily integrated into
capacitive pads, and replace mechanical buttons. The capacitive touch pins can
also be used to wake up the ESP32 from deep sleep.
Those internal touch sensors
are connected to these GPIOs:
T0 (GPIO 4)
T1 (GPIO 0)
T2 (GPIO 2)
T3 (GPIO 15)
T4 (GPIO 13)
T5 (GPIO 12)
T6 (GPIO 14)
T7 (GPIO 27)
T8 (GPIO 33)
T9 (GPIO 32)
Learn how
to use the touch pins with Arduino IDE: ESP32 Touch Pins with Arduino IDE
Analog
to Digital Converter (ADC)
The ESP32 has 18 x 12 bits ADC
input channels (while the ESP8266 only has 1x 10 bits ADC). These are the
GPIOs that can be used as ADC and respective channels:
ADC1_CH0 (GPIO 36)
ADC1_CH1 (GPIO 37)
ADC1_CH2 (GPIO 38)
ADC1_CH3 (GPIO 39)
ADC1_CH4 (GPIO 32)
ADC1_CH5 (GPIO 33)
ADC1_CH6 (GPIO 34)
ADC1_CH7 (GPIO 35)
ADC2_CH0 (GPIO 4)
ADC2_CH1 (GPIO 0)
ADC2_CH2 (GPIO 2)
ADC2_CH3 (GPIO 15)
ADC2_CH4 (GPIO 13)
ADC2_CH5 (GPIO 12)
ADC2_CH6 (GPIO 14)
ADC2_CH7 (GPIO 27)
ADC2_CH8 (GPIO 25)
ADC2_CH9 (GPIO 26)
Note: ADC2 pins cannot be
used when Wi-Fi is used. So, if you’re using Wi-Fi and you’re having trouble
getting the value from an ADC2 GPIO, you may consider using an ADC1 GPIO
instead, that should solve your problem.
The ADC input channels have a
12 bit resolution. This means that you can get analog readings ranging from 0
to 4095, in which 0 corresponds to 0V and 4095 to 3.3V. You also have the
ability to set the resolution of your channels on the code, as well as the ADC
range.
The ESP32 ADC pins don’t have a
linear behavior. You’ll probably won’t be able to distinguish between 0 and
0.1V, or between 3.2 and 3.3V. You need to keep that in mind when using the ADC
pins. You’ll get a behavior similar to the one shown in the following figure.
Digital to
Analog Converter (DAC)
There are 2 x 8 bits DAC
channels on the ESP32 to convert digital signals into analog voltage signal
outputs. These are the DAC channels:
RTC GPIOs
There is RTC GPIO support on
the ESP32. The GPIOs routed to the RTC low-power subsystem can be used when the
ESP32 is in deep sleep. These RTC GPIOs can be used to wake up the ESP32 from
deep sleep when the Ultra Low Power (ULP) co-processor is running. The
following GPIOs can be used as an external wake up source.
RTC_GPIO0 (GPIO36)
RTC_GPIO3 (GPIO39)
RTC_GPIO4 (GPIO34)
RTC_GPIO5 (GPIO35)
RTC_GPIO6 (GPIO25)
RTC_GPIO7 (GPIO26)
RTC_GPIO8 (GPIO33)
RTC_GPIO9 (GPIO32)
RTC_GPIO10 (GPIO4)
RTC_GPIO11 (GPIO0)
RTC_GPIO12 (GPIO2)
RTC_GPIO13 (GPIO15)
RTC_GPIO14 (GPIO13)
RTC_GPIO15 (GPIO12)
RTC_GPIO16 (GPIO14)
RTC_GPIO17 (GPIO27)
Learn how to use the RTC GPIOs
to wake up the ESP32 from deep sleep: ESP32 Deep Sleep with Arduino
IDE and Wake Up Sources
PWM
The ESP32 LED PWM controller
has 16 independent channels that can be configured to generate PWM signals with
different properties. All pins that can act as outputs can be used as PWM pins (GPIOs
34 to 39 can’t generate PWM).
To set a PWM signal, you need
to define these parameters in the code:
Learn how to use ESP32 PWM with
Arduino IDE: ESP32 PWM with Arduino IDE
I2C
The ESP32 has two I2C channels
and any pin can be set as SDA or SCL. When using the ESP32 with the Arduino
IDE, the default I2C pins are:
If you want to use other pins,
when using the wire library, you just need to call:Wire.begin(SDA, SCL);
Learn more about I2C
communication protocol with the ESP32 using Arduino IDE: ESP32 I2C
Communication (Set Pins, Multiple Bus Interfaces and Peripherals)
SPI
By default, the pin mapping for
SPI is:
|
SPI |
MOSI |
MISO |
CLK |
CS |
|
VSPI |
GPIO 23 |
GPIO 19 |
GPIO 18 |
GPIO 5 |
|
HSPI |
GPIO 13 |
GPIO 12 |
GPIO 14 |
GPIO 15 |
Interrupts
All GPIOs can be configured as
interrupts.
Learn how to use interrupts
with the ESP32:
Strapping Pins
The ESP32 chip has the
following strapping pins:
These are used to put the ESP32
into bootloader or flashing mode. On most development boards with built-in
USB/Serial, you don’t need to worry about the state of these pins. The board
puts the pins in the right state for flashing or boot mode. More information on
the ESP32 Boot Mode Selection can be found here.
However, if you have
peripherals connected to those pins, you may have trouble trying to upload new
code, flashing the ESP32 with new firmware or resetting the board. If you have
some peripherals connected to the strapping pins and you are getting trouble
uploading code or flashing the ESP32, it may be because those peripherals are
preventing the ESP32 to enter the right mode. Read the Boot Mode Selection
documentation to guide you in the right direction. After resetting, flashing,
or booting, those pins work as expected.
Pins
HIGH at Boot
Some GPIOs change its state to
HIGH or output PWM signals at boot or reset. This means that if you have
outputs connected to these GPIOs you may get unexpected results when the ESP32
resets or boots.
Enable (EN)
Enable (EN) is the 3.3V
regulator’s enable pin. It’s pulled up, so connect to ground to disable the
3.3V regulator. This means that you can use this pin connected to a pushbutton
to restart your ESP32, for example.
GPIO
current drawn
The absolute maximum current
drawn per GPIO is 40mA according to the “Recommended Operating Conditions”
section in the ESP32 datasheet.
ESP32
Built-In Hall Effect Sensor
The ESP32 also features a
built-in hall effect sensor that detects changes in the magnetic field in its
surroundings.
19 mei 2019, experimenten met ESP8266 NodeMCU
NodeMCU
doet het niet in testboard, wel zonder.
Putty
connect kan maar commando’s intikken lukt niet. Met ESplorer, baudrate 115200,
AT Commando’s via knoppen:
AT ↵ OK ↵
AT+GMR ↵ AT version:1.1.0.0(May 11 2016 18:09:56) ↵SDK version:1.5.4(baaeaebb)
compile time:May 20 2016 15:08:19 ↵
OK ↵ AT+CWMODE=? ↵ +CWMODE:(1-3)
↵ OK ↵
AT+CWLAP ↵ ERROR ↵ AT+CWJAP?
↵
No AP ↵ OK ↵
AT+CIPSTAMAC? ↵
+CIPSTAMAC:"3c:71:bf:3a:4d:cc" ↵
OK ↵ AT+CIPSTA? ↵ +CIPSTA:ip:"0.0.0.0"
↵
+CIPSTA:gateway:"0.0.0.0" ↵
+CIPSTA:netmask:"0.0.0.0" ↵
OK ↵ AT+CIPMODE? ↵ +CIPMODE:0
↵ OK ↵
AT+CWSAP? ↵ +CWSAP:"ESP_3A4DCC","",1,0,4,0
↵ OK ↵
AT+CWLIF ↵ 192.168.4.2,2c:61:f6:7c:c9:c6 ↵ OK
Connectie
maken met IPad lukt niet, zit waarschijnlijk geen webserver op
Geflasht met ESP8266 flasher,
deze zegt: AP Mac: 3E-71-BF-3A-4D-0A & STA Mac: 3C-71-BF-3A-4D-0A
Na
reset nodemcu kwam output in putty:
brl{ ↵ Formatting file
system. Please wait... ↵ NodeMCU custom build by frightanic.com
↵ branch: master
commit:
11592951b90707cdcb6d751876170bf4da82850d
↵ SSL: false ↵
modules:
file,gpio,http,mqtt,net,node,spi,tmr,uart,wifi
build created on 2019-03-01 19:46
↵ powered by Lua 5.1.4 on SDK 2.2.1(6ab97e9)
↵ lua: cannot open init.lua
↵ >
20 mei 2019: Nieuwe flash gemaakt op https://nodemcu-build.com/index.php , met meer opties. Zie mail ou81288 en deze geflasht
(integer): Geflasht met ESP8266 flasher, deze zegt: AP Mac: 3E-71-BF-3A-4D-08
& STA Mac: 3C-71-BF-3A-4D-08
Na
reset nodemcu kwam output in putty:
#{lr ↵ NodeMCU custom build
by frightanic.com ↵ branch:
master ↵ commit:
4905381c004bdeaf744a60bb940c1906c2e052d4
SSL: false
modules:
adc,file,gpio,http,i2c,mdns,mqtt,net,node,ow,pcm,pwm,spi,tmr,uart,wifi,ws2801,ws2812,ws2812_effects
build created on 2019-05-20 18:35
↵ powered by Lua 5.1.4 on SDK 2.2.1(6ab97e9)
↵ lua: cannot open init.lua
In
ESPlorer snippet gemaakt, deze laat de LED op het board branden met: gpio.mode(0,gpio.OUTPUT); gpio.write(0,0)
en
weer uit met gpio.mode(0,gpio.OUTPUT);
gpio.write(0,1)
20 mei 2019: NodeMCU is nu klaar om met Arduino IDE te proggen.
Okt 2019: ESP Nr 11,
NodeMCU CH340G Gebruiken voor Power Startup module. Met ESPlorer.bat connect naar
COM5, 115200 baud en bekeken:
AT+GMR ↵ AT version:1.1.0.0(May 11
2016 18:09:56) ↵ SDK version:1.5.4(baaeaebb) ↵
compile time:May 20 2016 15:08:19 ↵
AT+CIPAPMAC? ↵ +CIPAPMAC:"2e:f4:32:20:b9:8b"
Met tablet WiFi bekeken, SSID=ESP_20B98B, password theisnospoon. Verbonden maar verder kan je niet veel.
Met
ESPFlasher firmware van 20 mei 2019 (integer) erop (je moet de bin filename
intikken), output is dan:
23:08:37.048 -> NodeMCU custom build by
frightanic.com
23:08:37.048 -> branch: master
23:08:37.048 -> commit: 4905381c004bdeaf744a60bb940c1906c2e052d4
23:08:37.048 -> SSL: false
23:08:37.048 -> modules:
adc,file,gpio,http,i2c,mdns,mqtt,net,node,ow,pcm,pwm,spi,tmr,uart,wifi,ws2801,ws2812,ws2812_effects
23:08:37.082 -> build created on 2019-05-20 18:35
23:08:37.082 -> powered by Lua 5.1.4 on SDK 2.2.1(6ab97e9)
23:08:37.150 -> lua: cannot open init.lua
23:08:37.150 -> >
Heeft ook SSID ESP20B98B, Is nu dus klaar om te
proggen.
Mei 20: ESP Nr 8, NodeMCU
CH340G, met 32 MB extra gebruiken voor RFID project. RFID met LCD in een
zelfgeprinte behuizing heeft een eigen document, ESP RFID LCD.doc, zie hierin
voor verdere vorderingen. Ik had IDE al een tijdje niet gebruikt, veel
libraries moeten ge-update, ook ntpclient en daardoor was dezae weer
verschreven en dus geen getformattedDateTime. Goede ntpclient van “taranais”
opgehaald en geinstalleerd.
SPI
FFS is deprecated, vervangen door LittleFS.
7 jun ’20: nieuwe flash
gemaakt (zie RFID doc voor de reden), 16MB gekozen, met opties: adc, file, gpio, http, i2c,
mdns, mqtt, net, node, ow, pcm, pwm, spi, tmr, uart, wifi.
28 okt ’20: ESP Nr 15 lijkt stuk,
wordt warm als je m aansluit. Nooit eerder getest. ESP Nr 17 test=ESP32-WROOM-32D.
Out of the box output:
14:28:37.901 -> ets Jun 8 2016 00:22:57
14:28:37.901 ->
14:28:37.901 -> rst:0x1
(POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
14:28:37.901 -> configsip: 0, SPIWP:0x00
14:28:37.901 -> clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
14:28:37.934 -> mode:DIO, clock div:2
14:28:37.934 -> load:0x3fff0008,len:8
14:28:37.934 -> load:0x3fff0010,len:3480
14:28:37.934 -> load:0x40078000,len:7804
14:28:37.934 -> ho 0 tail 12 room 4
14:28:37.934 -> load:0x40080000,len:252
14:28:37.934 -> entry 0x40080034
14:28:37.934 -> [0;32mI (47) boot: ESP-IDF
v2.0-3-gbef9896 2nd stage bootloader[0m
14:28:37.934 -> [0;32mI (47) boot: compile
time 05:59:45[0m
14:28:37.934 -> [0;32mI (47) boot: Enabling
RNG early entropy source...[0m
14:28:37.967 -> [0;32mI (66) boot: SPI
Speed : 40MHz[0m
14:28:37.967 -> [0;32mI (78) boot: SPI
Mode : DIO[0m
14:28:37.967 -> [0;32mI (91) boot: SPI
Flash Size : 4MB[0m
14:28:37.967 -> [0;32mI (103) boot:
Partition Table:[0m
14:28:37.967 -> [0;32mI (115) boot: ##
Label Usage Type ST Offset Length[0m
14:28:37.967 -> [0;32mI (137) boot: 0 phy_init RF data 01 01 0000f000 00001000[0m
14:28:37.967 -> [0;32mI (160) boot: 1 otadata OTA data 01 00 00010000 00002000[0m
14:28:38.001 -> [0;32mI (184) boot: 2 nvs WiFi data 01 02 00012000 0000e000[0m
14:28:38.001 -> [0;32mI (207) boot: 3 at_customize unknown 40 00 00020000 000e0000[0m
14:28:38.001
-> [0;32mI (230) boot: 4 ota_0 OTA app 00 10 00100000 00180000[0m
14:28:38.001
-> [0;32mI (253) boot: 5 ota_1 OTA app 00 11 00280000 00180000[0m
14:28:38.035 -> [0;32mI (277) boot: End of
partition table[0m
14:28:38.035 -> [0;32mI (290) boot:
Disabling RNG early entropy source...[0m
14:28:38.035 -> [0;32mI (307) boot: Loading
app partition at offset 00100000[0m
14:28:38.405 -> [0;32mI (1482) boot:
segment 0: paddr=0x00100018 vaddr=0x00000000 size=0x0ffe8 ( 65512) [0m
14:28:38.405 -> [0;32mI (1483) boot:
segment 1: paddr=0x00110008 vaddr=0x3f400010 size=0x1c5f0 (116208) map[0m
14:28:38.405 -> [0;32mI (1500) boot:
segment 2: paddr=0x0012c600 vaddr=0x3ffb0000 size=0x0215c ( 8540) load[0m
14:28:38.439 -> [0;32mI (1530) boot:
segment 3: paddr=0x0012e764 vaddr=0x40080000 size=0x00400 ( 1024) load[0m
14:28:38.439 -> [0;32mI (1553) boot:
segment 4: paddr=0x0012eb6c vaddr=0x40080400 size=0x1b028 (110632) load[0m
14:28:38.439 -> [0;32mI (1632) boot:
segment 5: paddr=0x00149b9c vaddr=0x400c0000 size=0x00034 ( 52) load[0m
14:28:38.472 -> [0;32mI (1633) boot:
segment 6: paddr=0x00149bd8 vaddr=0x00000000 size=0x06430 ( 25648) [0m
14:28:38.472 -> [0;32mI (1649) boot:
segment 7: paddr=0x00150010 vaddr=0x400d0018 size=0x7a56c (501100) map[0m
14:28:38.472 -> [0;32mI (1677)
heap_alloc_caps: Initializing. RAM available for dynamic allocation:[0m
14:28:38.472 -> [0;32mI (1699)
heap_alloc_caps: At 3FFBA6B8 len 00025948 (150 KiB): DRAM[0m
14:28:38.507 -> [0;32mI (1720)
heap_alloc_caps: At 3FFE8000 len 00018000 (96 KiB): D/IRAM[0m
14:28:38.507 -> [0;32mI (1742)
heap_alloc_caps: At 4009B428 len 00004BD8 (18 KiB): IRAM[0m
14:28:38.507 -> [0;32mI (1763) cpu_start:
Pro cpu up.[0m
14:28:38.507 -> [0;32mI (1774) cpu_start:
Single core mode[0m
14:28:38.507 -> [0;32mI (1787) cpu_start:
Pro cpu start user code[0m
14:28:38.507 -> [0;32mI (1848) cpu_start:
Starting scheduler on PRO CPU.[0m
14:28:38.540 -> [0;32mI (2087) uart: queue
free spaces: 10[0m
14:28:38.540 -> Bin version:0.10.0
14:28:38.540 -> I (2089) wifi: wifi
firmware version: c604573
14:28:38.540 -> I (2089) wifi: config NVS
flash: enabled
14:28:38.540 -> I (2090) wifi: config nano
formating: disabled
14:28:38.574 -> I (2098) wifi: Init dynamic
tx buffer num: 32
14:28:38.574 -> I (2099) wifi: wifi driver
task: 3ffc4eac, prio:23, stack:3584
14:28:38.574 -> I (2104) wifi: Init static
rx buffer num: 10
14:28:38.574 -> I (2108) wifi: Init dynamic
rx buffer num: 0
14:28:38.574 -> I (2112) wifi: Init rx
ampdu len mblock:7
14:28:38.574 -> I (2116) wifi: Init lldesc
rx ampdu entry mblock:4
14:28:38.574 -> I (2121) wifi: wifi power
manager task: 0x3ffca254 prio: 21 stack: 2560
14:28:38.607 -> I (2127) wifi: wifi timer
task: 3ffcb2d4, prio:22, stack:3584
14:28:38.607 -> [0;31mE (2132) phy_init:
PHY data partition validated[0m
14:28:38.607 -> [0;32mI (2161) phy:
phy_version: 329, Feb 22 2017, 15:58:07, 0, 0[0m
14:28:38.607 -> I (2161) wifi: mode :
softAP (7c:9e:bd:07:59:41)
14:28:38.640 -> I (2164) wifi: mode : sta
(7c:9e:bd:07:59:40) + softAP (7c:9e:bd:07:59:41)
14:28:38.640 -> I (2168) wifi: mode :
softAP (7c:9e:bd:07:59:41)
19 nov 20: ESP Nr 19 nieuw van
AliExpress, is een ESP32 devkitc 4, WROOM-32U. Out of the box output::
19:25:02.209 -> ets Jun 8 2016 00:22:57
19:25:02.209 ->
19:25:02.209 -> rst:0x1
(POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
19:25:02.209 -> configsip: 0, SPIWP:0xee
19:25:02.209 ->
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
19:25:02.244 -> mode:DIO, clock div:2
19:25:02.244 -> load:0x3fff0018,len:4
19:25:02.244 -> load:0x3fff001c,len:5656
19:25:02.244 -> load:0x40078000,len:0
19:25:02.244 -> ho 12 tail 0 room 4
19:25:02.244 -> load:0x40078000,len:13844
19:25:02.244 -> entry 0x40078fc4
19:25:02.244 -> [0;32mI (30) boot: ESP-IDF
v3.0.7 2nd stage bootloader[0m
19:25:02.244 -> [0;32mI (31) boot: compile
time 09:04:31[0m
19:25:02.244 -> [0;32mI (31) boot: Enabling
RNG early entropy source...[0m
19:25:02.277 -> [0;32mI (35) boot: SPI
Speed : 40MHz[0m
19:25:02.277 -> [0;32mI (39) boot: SPI
Mode : DIO[0m
19:25:02.277 -> [0;32mI (43) boot: SPI
Flash Size : 4MB[0m
19:25:02.277 -> [0;32mI (47) boot:
Partition Table:[0m
19:25:02.277 -> [0;32mI (51) boot: ##
Label Usage Type ST Offset Length[0m
19:25:02.277 -> [0;32mI (58) boot: 0 phy_init RF data 01 01 0000f000 00001000[0m
19:25:02.277 -> [0;32mI (66) boot: 1 otadata OTA data 01 00 00010000 00002000[0m
19:25:02.311 -> [0;32mI (73) boot: 2 nvs WiFi data 01 02 00012000 0000e000[0m
19:25:02.311 -> [0;32mI (81) boot: 3 at_customize unknown 40 00 00020000 000e0000[0m
19:25:02.311
-> [0;32mI (88) boot: 4 ota_0 OTA app 00 10 00100000 00180000[0m
19:25:02.311
-> [0;32mI (96) boot: 5 ota_1 OTA app 00 11 00280000 00180000[0m
19:25:02.344 -> [0;32mI (103) boot: End of
partition table[0m
19:25:02.344 -> [0;32mI (107) boot: No
factory image, trying OTA 0[0m
19:25:02.344 -> [0;32mI (112) esp_image:
segment 0: paddr=0x00100020 vaddr=0x3f400020 size=0x20614 (132628) map[0m
19:25:02.377 -> [0;32mI (168) esp_image:
segment 1: paddr=0x0012063c vaddr=0x3ffc0000 size=0x02d7c ( 11644) load[0m
19:25:02.377 -> [0;32mI (173) esp_image:
segment 2: paddr=0x001233c0 vaddr=0x40080000 size=0x00400 ( 1024) load[0m
19:25:02.411 -> [0;32mI (175) esp_image:
segment 3: paddr=0x001237c8 vaddr=0x40080400 size=0x0c848 ( 51272) load[0m
19:25:02.411 -> [0;32mI (205) esp_image:
segment 4: paddr=0x00130018 vaddr=0x400d0018 size=0xdfc80 (916608) map[0m
19:25:02.748 -> [0;32mI (526) esp_image:
segment 5: paddr=0x0020fca0 vaddr=0x4008cc48 size=0x02504 ( 9476) load[0m
19:25:02.748 -> [0;32mI (530) esp_image:
segment 6: paddr=0x002121ac vaddr=0x400c0000 size=0x00064 ( 100) load[0m
19:25:02.748 -> [0;32mI (542) boot: Loaded
app from partition at offset 0x100000[0m
19:25:02.748 -> [0;32mI (542) boot:
Disabling RNG early entropy source...[0m
19:25:02.816 -> 1.1.3
19:25:02.816 -> I (662) wifi: wifi firmware
version: 703e53b
19:25:02.816 -> I (663) wifi: config NVS
flash: enabled
19:25:02.850 -> I (663) wifi: config nano
formating: disabled
19:25:02.850 -> I (672) wifi: Init dynamic
tx buffer num: 32
19:25:02.850 -> I (673) wifi: Init data
frame dynamic rx buffer num: 32
19:25:02.850 -> I (673) wifi: Init
management frame dynamic rx buffer num: 32
19:25:02.850 -> I (679) wifi: wifi driver
task: 3ffdee34, prio:23, stack:3584
19:25:02.850 -> I (684) wifi: Init static
rx buffer num: 10
19:25:02.850 -> I (687) wifi: Init dynamic
rx buffer num: 32
19:25:02.850 -> I (692) wifi: wifi power
manager task: 0x3ffe369c prio: 21 stack: 2560
19:25:02.916 -> I (740) wifi: mode : softAP
(30:ae:a4:96:c3:89)
19:25:02.916 -> I (748) wifi: mode : sta
(30:ae:a4:96:c3:88) + softAP (30:ae:a4:96:c3:89)
19:25:02.916 -> I (751) wifi: mode : softAP
(30:ae:a4:96:c3:89)
19:25:02.916 -> I (755) wifi: set country:
cc=CN
23 Nov 2020, nieuwe NodeMCU WROOM-32U,
AliExpress, wordt espNr 15 (new)
Met Arduino IDE gebeurde niks,
esplorer ook niet, COM poort kwam wel (COM3, 115200 baud). In ESPlorer DTR en
RTS aan, output verscheen (zie onder), in Arduino IDE later ook, maar dan moet
je m eerst aansluiten en dan op de Reset button drukken. Device werkt dus goed,
gaat ESP Nr 15 vervangen, deze is stuk
rst:0x1 (POWERON_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:5656
load:0x40078000,len:0
ho 12 tail 0 room 4
load:0x40078000,len:13844
entry 0x40078fc4
[0;32mI (30) boot: ESP-IDF v3.0.7 2nd stage
bootloader[0m
[0;32mI (30) boot: compile time 09:04:31[0m
[0;32mI (30) boot: Enabling RNG early entropy
source...[0m
[0;32mI (35) boot: SPI Speed : 40MHz[0m
[0;32mI (39) boot: SPI Mode : DIO[0m
[0;32mI (43) boot: SPI Flash Size : 4MB[0m
[0;32mI (47) boot: Partition Table:[0m
[0;32mI (51) boot: ## Label Usage Type ST Offset Length[0m
[0;32mI (58) boot: 0 phy_init RF data 01 01 0000f000 00001000[0m
[0;32mI (65) boot: 1 otadata OTA data 01 00 00010000 00002000[0m
[0;32mI (73) boot: 2 nvs WiFi data 01 02 00012000 0000e000[0m
[0;32mI (80) boot: 3 at_customize unknown 40 00 00020000 000e0000[0m
[0;32mI
(88) boot: 4 ota_0 OTA app 00 10 00100000 00180000[0m
[0;32mI
(95) boot: 5 ota_1 OTA app 00 11 00280000 00180000[0m
[0;32mI (103) boot: End of partition table[0m
[0;32mI (107) boot: No factory image, trying
OTA 0[0m
[0;32mI (112) esp_image: segment 0:
paddr=0x00100020 vaddr=0x3f400020 size=0x20614 (132628) map[0m
[0;32mI (167) esp_image: segment 1:
paddr=0x0012063c vaddr=0x3ffc0000 size=0x02d7c ( 11644) load[0m
[0;32mI (172) esp_image: segment 2:
paddr=0x001233c0 vaddr=0x40080000 size=0x00400 ( 1024) load[0m
[0;32mI (175) esp_image: segment 3:
paddr=0x001237c8 vaddr=0x40080400 size=0x0c848 ( 51272) load[0m
[0;32mI (204) esp_image: segment 4:
paddr=0x00130018 vaddr=0x400d0018 size=0xdfc80 (916608) map[0m
[0;32mI (526) esp_image: segment 5:
paddr=0x0020fca0 vaddr=0x4008cc48 size=0x02504 ( 9476) load[0m
[0;32mI (530) esp_image: segment 6:
paddr=0x002121ac vaddr=0x400c0000 size=0x00064 ( 100) load[0m
[0;32mI (541) boot: Loaded app from partition
at offset 0x100000[0m
[0;32mI (541) boot: Disabling RNG early entropy
source...[0m
1.1.3
I (662) wifi: wifi firmware version: 703e53b
I (663) wifi: config NVS flash: enabled
I (663) wifi: config nano formating: disabled
I (673) wifi: Init dynamic tx buffer num: 32
I (673) wifi: Init data frame dynamic rx
buffer num: 32
I (673) wifi: Init management frame dynamic rx
buffer num: 32
I (679) wifi: wifi driver task: 3ffdee34,
prio:23, stack:3584
I (684) wifi: Init static rx buffer num: 10
I (687) wifi: Init dynamic rx buffer num: 32
I (692) wifi: wifi power manager task:
0x3ffe369c prio: 21 stack: 2560
I (735) wifi: mode : softAP
(30:ae:a4:9d:4c:81)
I (743) wifi: mode : sta (30:ae:a4:9d:4c:80) +
softAP (30:ae:a4:9d:4c:81)
I (747) wifi: mode : softAP
(30:ae:a4:9d:4c:81)
I (750) wifi: set country: cc=CN
Begin januari 2021:ESP Nr 18 was stuk (in 3D
printerkast,HeRoTempControl) vervangen door ESP Nr 16. Deze gaf out-of-the-box
USB error meldingen en halve opstartmeldingen. Toch geprogged met
HeRoTempControl V0.11, ging goed.
22 jan 2021, Vervanger van ESP Nr 18
ontvangen. Aan USB gehangen en met Seriele Monitor in Arduino IDE bekeken.Na
Reset knop, kwam:
ets Jun
8 2016 00:22:57
rst:0x1 (POWERON_RESET),boot:0x13
(SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0x00
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0008,len:8
load:0x3fff0010,len:3480
load:0x40078000,len:7804
ho 0 tail 12 room 4
load:0x40080000,len:252
entry 0x40080034
[0;32mI (46) boot: ESP-IDF v2.0-3-gbef9896 2nd
stage bootloader[0m
[0;32mI (47) boot: compile time 05:59:45[0m
[0;32mI (47) boot: Enabling RNG early entropy
source...[0m
[0;32mI (65) boot: SPI Speed : 40MHz[0m
[0;32mI (78) boot: SPI Mode : DIO[0m
[0;32mI (90) boot: SPI Flash Size : 4MB[0m
[0;32mI (103) boot: Partition Table:[0m
[0;32mI (114) boot: ## Label Usage Type ST Offset Length[0m
[0;32mI (137) boot: 0 phy_init RF data 01 01 0000f000 00001000[0m
[0;32mI (160) boot: 1 otadata OTA data 01 00 00010000 00002000[0m
[0;32mI (183) boot: 2 nvs WiFi data 01 02 00012000 0000e000[0m
[0;32mI (207) boot: 3 at_customize unknown 40 00 00020000 000e0000[0m
[0;32mI
(230) boot: 4 ota_0 OTA app 00 10 00100000 00180000[0m
[0;32mI
(253) boot: 5 ota_1 OTA app 00 11 00280000 00180000[0m
[0;32mI (277) boot: End of partition table[0m
[0;32mI (290) boot: Disabling RNG early
entropy source...[0m
[0;32mI (307) boot: Loading app partition at
offset 00100000[0m
[0;32mI (1482) boot: segment 0:
paddr=0x00100018 vaddr=0x00000000 size=0x0ffe8 ( 65512) [0m
[0;32mI (1483) boot: segment 1:
paddr=0x00110008 vaddr=0x3f400010 size=0x1c5f0 (116208) map[0m
[0;32mI (1499) boot: segment 2:
paddr=0x0012c600 vaddr=0x3ffb0000 size=0x0215c ( 8540) load[0m
[0;32mI (1529) boot: segment 3:
paddr=0x0012e764 vaddr=0x40080000 size=0x00400 ( 1024) load[0m
[0;32mI (1553) boot: segment 4:
paddr=0x0012eb6c vaddr=0x40080400 size=0x1b028 (110632) load[0m
[0;32mI (1631) boot: segment 5:
paddr=0x00149b9c vaddr=0x400c0000 size=0x00034 ( 52) load[0m
[0;32mI (1633) boot: segment 6:
paddr=0x00149bd8 vaddr=0x00000000 size=0x06430 ( 25648) [0m
[0;32mI (1649) boot: segment 7:
paddr=0x00150010 vaddr=0x400d0018 size=0x7a56c (501100) map[0m
[0;32mI (1676) heap_alloc_caps: Initializing.
RAM available for dynamic allocation:[0m
[0;32mI (1699) heap_alloc_caps: At 3FFBA6B8
len 00025948 (150 KiB): DRAM[0m
[0;32mI (1720) heap_alloc_caps: At 3FFE8000
len 00018000 (96 KiB): D/IRAM[0m
[0;32mI (1741) heap_alloc_caps: At 4009B428
len 00004BD8 (18 KiB): IRAM[0m
[0;32mI (1762) cpu_start: Pro cpu up.[0m
[0;32mI (1774) cpu_start: Single core mode[0m
[0;32mI (1787) cpu_start: Pro cpu start user
code[0m
[0;32mI (1847) cpu_start: Starting scheduler
on PRO CPU.[0m
[0;32mI (2087) uart: queue free spaces: 10[0m
Bin version:0.10.0
I (2089) wifi: wifi firmware version: c604573
I (2089) wifi: config NVS flash: enabled
I (2090) wifi: config nano formating: disabled
I (2098) wifi: Init dynamic tx buffer num: 32
I (2099) wifi: wifi driver task: 3ffc4eac,
prio:23, stack:3584
I (2104) wifi: Init static rx buffer num: 10
I (2108) wifi: Init dynamic rx buffer num: 0
I (2112) wifi: Init rx ampdu len mblock:7
I (2116) wifi: Init lldesc rx ampdu entry
mblock:4
I (2121) wifi: wifi power manager task:
0x3ffca254 prio: 21 stack: 2560
I (2127) wifi: wifi timer task: 3ffcb2d4,
prio:22, stack:3584
[0;31mE (2132) phy_init: PHY data partition
validated[0m
[0;32mI (2155) phy: phy_version: 329, Feb 22
2017, 15:58:07, 0, 0[0m
I (2155) wifi: mode : softAP
(7c:9e:bd:38:8c:85)
I (2158) wifi: mode : sta (7c:9e:bd:38:8c:84)
+ softAP (7c:9e:bd:38:8c:85)
I (2162) wifi: mode : softAP
(7c:9e:bd:38:8c:85)
Deze (nieuwe ESPNr 18) geprogged met
HeRoTempControl,voor test of hij het deed, ging goed. Ging filesystem
formatteren en daarna was ’t OK. Later kijken waarvoor we deze gaan gebruiken.
Sep ‘21: ESP Nr 23 nieuw van
AliExpress, is een ESP8266 MOD, zelfde als ESP Nr 11. Geen out of the box
output in Arduino IDE en ook niet in ESPlorer. ESPlorer AT commands ging wel, COM
Poort op 57600 ESPlorer met 115200 baudrate: AT Commands ging wel (verder
uitzoeken door ‘m met arduino ide te proggen):
ets Jan
8 2013,rst cause:2, boot mode:(3,6)
load 0x40100000, len 2408, room 16
tail 8
chksum 0xe5
load 0x3ffe8000, len 776, room 0
tail 8
chksum 0x84
load 0x3ffe8310, len 632, room 0
tail 8
chksum 0xd8
csum 0xd8
2nd boot version : 1.6
SPI
Speed : 40MHz
SPI
Mode : QIO
SPI
Flash Size & Map: 32Mbit(512KB+512KB)
jump to run user1 @ 1000
<troep characters>
ready
AT+GMR
AT version:1.3.0.0(Jul 14 2016 18:54:01)
SDK version:2.0.0(5a875ba)
v1.0.0.3
Mar 13 2018 09:37:06
OK
AT+CIPAPMAC?
+CIPAPMAC:"aa:48:fa:cd:2f:46"
Sep ‘21: ESP Nr 24 nieuw van
AliExpress, is een ESP8266 ESP 12. Geen/troep out of the box output in Arduino
IDE en ook niet in ESPlorer. Nog uitzoeken (misschien proggen met Arduino IDE)
Sep ‘21: ESP Nr 25 nieuw van
AliExpress, is een ESP8266 ESP 12. Geen/troep out of the box output in Arduino
IDE en ook niet in ESPlorer. Nog uitzoeken (misschien proggen met Arduino IDE)
Sep ‘21: ESP Nr 26 nieuw van
AliExpress, is een ESP32 devkitc 4, WROOM-32D. Out of the box output in Arduino IDE:
16:18:08.634 -> ets Jun 8 2016 00:22:57
16:18:08.634 ->
16:18:08.634 -> rst:0x1
(POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
16:18:08.634 -> configsip: 0, SPIWP:0x00
16:18:08.634 -> clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
16:18:08.634 -> mode:DIO, clock div:2
16:18:08.634 -> load:0x3fff0008,len:8
16:18:08.634 -> load:0x3fff0010,len:3480
16:18:08.634 -> load:0x40078000,len:7804
16:18:08.634 -> ho 0 tail 12 room 4
16:18:08.634 -> load:0x40080000,len:252
16:18:08.634 -> entry 0x40080034
16:18:08.634 -> [0;32mI (46) boot: ESP-IDF
v2.0-3-gbef9896 2nd stage bootloader[0m
16:18:08.682 -> [0;32mI (47) boot: compile
time 05:59:45[0m
16:18:08.682 -> [0;32mI (47) boot: Enabling
RNG early entropy source...[0m
16:18:08.682 -> [0;32mI (66) boot: SPI
Speed : 40MHz[0m
16:18:08.682 -> [0;32mI (78) boot: SPI
Mode : DIO[0m
16:18:08.682 -> [0;32mI (91) boot: SPI
Flash Size : 4MB[0m
16:18:08.682 -> [0;32mI (103) boot:
Partition Table:[0m
16:18:08.682 -> [0;32mI (114) boot: ##
Label Usage Type ST Offset Length[0m
16:18:08.682 -> [0;32mI (137) boot: 0 phy_init RF data 01 01 0000f000 00001000[0m
16:18:08.682 -> [0;32mI (160) boot: 1 otadata OTA data 01 00 00010000 00002000[0m
16:18:08.728 -> [0;32mI (183) boot: 2 nvs WiFi data 01 02 00012000 0000e000[0m
16:18:08.728 -> [0;32mI (207) boot: 3 at_customize unknown 40 00 00020000 000e0000[0m
16:18:08.728
-> [0;32mI (230) boot: 4 ota_0 OTA app 00 10 00100000 00180000[0m
16:18:08.728
-> [0;32mI (253) boot: 5 ota_1 OTA app 00 11 00280000 00180000[0m
16:18:08.728 -> [0;32mI (277) boot: End of
partition table[0m
16:18:08.728 -> [0;32mI (290) boot:
Disabling RNG early entropy source...[0m
16:18:08.728 -> [0;32mI (307) boot: Loading
app partition at offset 00100000[0m
16:18:09.103 -> [0;32mI (1482) boot:
segment 0: paddr=0x00100018 vaddr=0x00000000 size=0x0ffe8 ( 65512) [0m
16:18:09.103 -> [0;32mI (1483) boot:
segment 1: paddr=0x00110008 vaddr=0x3f400010 size=0x1c5f0 (116208) map[0m
16:18:09.152 -> [0;32mI (1499) boot:
segment 2: paddr=0x0012c600 vaddr=0x3ffb0000 size=0x0215c ( 8540) load[0m
16:18:09.152 -> [0;32mI (1529) boot:
segment 3: paddr=0x0012e764 vaddr=0x40080000 size=0x00400 ( 1024) load[0m
16:18:09.152 -> [0;32mI (1553) boot:
segment 4: paddr=0x0012eb6c vaddr=0x40080400 size=0x1b028 (110632) load[0m
16:18:09.152 -> [0;32mI (1632) boot:
segment 5: paddr=0x00149b9c vaddr=0x400c0000 size=0x00034 ( 52) load[0m
16:18:09.152 -> [0;32mI (1633) boot:
segment 6: paddr=0x00149bd8 vaddr=0x00000000 size=0x06430 ( 25648) [0m
16:18:09.200 -> [0;32mI (1649) boot:
segment 7: paddr=0x00150010 vaddr=0x400d0018 size=0x7a56c (501100) map[0m
16:18:09.200 -> [0;32mI (1676)
heap_alloc_caps: Initializing. RAM available for dynamic allocation:[0m
16:18:09.200 -> [0;32mI (1699)
heap_alloc_caps: At 3FFBA6B8 len 00025948 (150 KiB): DRAM[0m
16:18:09.200 -> [0;32mI (1720)
heap_alloc_caps: At 3FFE8000 len 00018000 (96 KiB): D/IRAM[0m
16:18:09.200 -> [0;32mI (1741)
heap_alloc_caps: At 4009B428 len 00004BD8 (18 KiB): IRAM[0m
16:18:09.200 -> [0;32mI (1762) cpu_start:
Pro cpu up.[0m
16:18:09.246 -> [0;32mI (1774) cpu_start:
Single core mode[0m
16:18:09.246 -> [0;32mI (1787) cpu_start:
Pro cpu start user code[0m
16:18:09.246 -> [0;32mI (1848) cpu_start:
Starting scheduler on PRO CPU.[0m
16:18:09.246 -> [0;32mI (2087) uart: queue
free spaces: 10[0m
16:18:09.246 -> Bin version:0.10.0
16:18:09.246 -> I (2089) wifi: wifi
firmware version: c604573
16:18:09.292 -> I (2089) wifi: config NVS
flash: enabled
16:18:09.292 -> I (2090) wifi: config nano
formating: disabled
16:18:09.292 -> I (2098) wifi: Init dynamic
tx buffer num: 32
16:18:09.292 -> I (2099) wifi: wifi driver
task: 3ffc4eac, prio:23, stack:3584
16:18:09.292 -> I (2104) wifi: Init static
rx buffer num: 10
16:18:09.292 -> I (2108) wifi: Init dynamic
rx buffer num: 0
16:18:09.292 -> I (2112) wifi: Init rx
ampdu len mblock:7
16:18:09.292 -> I (2116) wifi: Init lldesc
rx ampdu entry mblock:4
16:18:09.292 -> I (2121) wifi: wifi power
manager task: 0x3ffca254 prio: 21 stack: 2560
16:18:09.292 -> I (2127) wifi: wifi timer
task: 3ffcb2d4, prio:22, stack:3584
16:18:09.292 -> [0;31mE (2132) phy_init:
PHY data partition validated[0m
16:18:09.340 -> [0;32mI (2151) phy:
phy_version: 329, Feb 22 2017, 15:58:07, 0, 0[0m
16:18:09.340 -> I (2152) wifi: mode :
softAP (94:b9:7e:e4:69:c1)
16:18:09.340 -> I (2155) wifi: mode : sta
(94:b9:7e:e4:69:c0) + softAP (94:b9:7e:e4:69:c1)
16:18:09.340 -> I (2158) wifi: mode :
softAP (94:b9:7e:e4:69:c1)
Sep ‘21: ESP Nr 27 nieuw van
AliExpress, is een ESP32 devkitc 4, WROOM-32U. Out of the box output in Arduino IDE:
16:07:46.137 -> ets Jun 8 2016 00:22:57
16:07:46.137 ->
16:07:46.137 -> rst:0x1
(POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
16:07:46.137 -> configsip: 0, SPIWP:0x00
16:07:46.137 ->
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
16:07:46.183 -> mode:DIO, clock div:2
16:07:46.183 -> load:0x3fff0008,len:8
16:07:46.183 -> load:0x3fff0010,len:3480
16:07:46.183 -> load:0x40078000,len:7804
16:07:46.183 -> ho 0 tail 12 room 4
16:07:46.183 -> load:0x40080000,len:252
16:07:46.183 -> entry 0x40080034
16:07:46.183 -> [0;32mI (46) boot: ESP-IDF
v2.0-3-gbef9896 2nd stage bootloader[0m
16:07:46.183 -> [0;32mI (46) boot: compile
time 05:59:45[0m
16:07:46.183 -> [0;32mI (47) boot: Enabling
RNG early entropy source...[0m
16:07:46.183 -> [0;32mI (65) boot: SPI
Speed : 40MHz[0m
16:07:46.183 -> [0;32mI (78) boot: SPI
Mode : DIO[0m
16:07:46.183 -> [0;32mI (90) boot: SPI
Flash Size : 4MB[0m
16:07:46.183 -> [0;32mI (103) boot:
Partition Table:[0m
16:07:46.230 -> [0;32mI (114) boot: ##
Label Usage Type ST Offset Length[0m
16:07:46.230 -> [0;32mI (137) boot: 0 phy_init RF data 01 01 0000f000 00001000[0m
16:07:46.230 -> [0;32mI (160) boot: 1 otadata OTA data 01 00 00010000 00002000[0m
16:07:46.230 -> [0;32mI (183) boot: 2 nvs WiFi data 01 02 00012000 0000e000[0m
16:07:46.230 -> [0;32mI (206) boot: 3 at_customize unknown 40 00 00020000 000e0000[0m
16:07:46.230
-> [0;32mI (230) boot: 4 ota_0 OTA app 00 10 00100000 00180000[0m
16:07:46.230
-> [0;32mI (253) boot: 5 ota_1 OTA app 00 11 00280000 00180000[0m
16:07:46.277 -> [0;32mI (276) boot: End of
partition table[0m
16:07:46.277 -> [0;32mI (289) boot:
Disabling RNG early entropy source...[0m
16:07:46.277 -> [0;32mI (306) boot: Loading
app partition at offset 00100000[0m
16:07:46.652 -> [0;32mI (1482) boot:
segment 0: paddr=0x00100018 vaddr=0x00000000 size=0x0ffe8 ( 65512) [0m
16:07:46.652 -> [0;32mI (1482) boot:
segment 1: paddr=0x00110008 vaddr=0x3f400010 size=0x1c5f0 (116208) map[0m
16:07:46.652 -> [0;32mI (1499) boot:
segment 2: paddr=0x0012c600 vaddr=0x3ffb0000 size=0x0215c ( 8540) load[0m
16:07:46.652 -> [0;32mI (1529) boot:
segment 3: paddr=0x0012e764 vaddr=0x40080000 size=0x00400 ( 1024) load[0m
16:07:46.652 -> [0;32mI (1553) boot:
segment 4: paddr=0x0012eb6c vaddr=0x40080400 size=0x1b028 (110632) load[0m
16:07:46.699 -> [0;32mI (1631) boot:
segment 5: paddr=0x00149b9c vaddr=0x400c0000 size=0x00034 ( 52) load[0m
16:07:46.699 -> [0;32mI (1632) boot:
segment 6: paddr=0x00149bd8 vaddr=0x00000000 size=0x06430 ( 25648) [0m
16:07:46.699 -> [0;32mI (1649) boot:
segment 7: paddr=0x00150010 vaddr=0x400d0018 size=0x7a56c (501100) map[0m
16:07:46.699 -> [0;32mI (1676)
heap_alloc_caps: Initializing. RAM available for dynamic allocation:[0m
16:07:46.699 -> [0;32mI (1699)
heap_alloc_caps: At 3FFBA6B8 len 00025948 (150 KiB): DRAM[0m
16:07:46.747 -> [0;32mI (1720)
heap_alloc_caps: At 3FFE8000 len 00018000 (96 KiB): D/IRAM[0m
16:07:46.747 -> [0;32mI (1741)
heap_alloc_caps: At 4009B428 len 00004BD8 (18 KiB): IRAM[0m
16:07:46.747 -> [0;32mI (1762) cpu_start:
Pro cpu up.[0m
16:07:46.747 -> [0;32mI (1774) cpu_start:
Single core mode[0m
16:07:46.747 -> [0;32mI (1787) cpu_start:
Pro cpu start user code[0m
16:07:46.747 -> [0;32mI (1847) cpu_start:
Starting scheduler on PRO CPU.[0m
16:07:46.793 -> [0;32mI (2086) uart: queue
free spaces: 10[0m
16:07:46.793 -> Bin version:0.10.0
16:07:46.793 -> I (2088) wifi: wifi
firmware version: c604573
16:07:46.793 -> I (2088) wifi: config NVS
flash: enabled
16:07:46.793 -> I (2089) wifi: config nano
formating: disabled
16:07:46.793 -> I (2097) wifi: Init dynamic
tx buffer num: 32
16:07:46.793 -> I (2098) wifi: wifi driver
task: 3ffc4eac, prio:23, stack:3584
16:07:46.793 -> I (2103) wifi: Init static
rx buffer num: 10
16:07:46.793 -> I (2107) wifi: Init dynamic
rx buffer num: 0
16:07:46.840 -> I (2111) wifi: Init rx
ampdu len mblock:7
16:07:46.840 -> I (2115) wifi: Init lldesc
rx ampdu entry mblock:4
16:07:46.840 -> I (2120) wifi: wifi power
manager task: 0x3ffca254 prio: 21 stack: 2560
16:07:46.840 -> I (2126) wifi: wifi timer
task: 3ffcb2d4, prio:22, stack:3584
16:07:46.840 -> [0;31mE (2131) phy_init:
PHY data partition validated[0m
16:07:46.840 -> [0;32mI (2153) phy:
phy_version: 329, Feb 22 2017, 15:58:07, 0, 0[0m
16:07:46.840 -> I (2154) wifi: mode :
softAP (94:b9:7e:e4:77:01)
16:07:46.840 -> I (2157) wifi: mode : sta (94:b9:7e:e4:77:00)
+ softAP (94:b9:7e:e4:77:01)
16:07:46.887 -> I (2161) wifi: mode :
softAP (94:b9:7e:e4:77:01)
Mei 2022: ESP Nr 27 geprobeerd met
RaspBerry WiFi AP maar hij wilde sowieso niet wifi connecten, ook niet met
onsnetwerk en ziggo-apxx. Ook niet met een antenne. Nieuwe firmware geflashed,
output=
09:48:36.141
-> ets Jun 8 2016 00:22:57
09:48:36.141 ->
09:48:36.141 -> rst:0x1
(POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
09:48:36.141 -> configsip: 0, SPIWP:0xee
09:48:36.141 ->
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
09:48:36.141 -> mode:DIO, clock div:2
09:48:36.141 -> load:0x3fff0030,len:7672
09:48:36.141 -> load:0x40078000,len:16432
09:48:36.141 -> load:0x40080400,len:3704
09:48:36.141 -> entry 0x4008067c
09:48:36.141 -> [0;32mI (27) boot: ESP-IDF
qa-test-v4.3.3-20220423 2nd stage bootloader[0m
09:48:36.187 -> [0;32mI (27) boot: compile
time 11:11:52[0m
09:48:36.187 -> [0;32mI (27) boot: chip
revision: 1[0m
09:48:36.187 -> [0;32mI (31) boot_comm:
chip revision: 1, min. bootloader chip revision: 0[0m
09:48:36.187 -> [0;32mI (38) boot.esp32:
SPI Speed : 40MHz[0m
09:48:36.187 -> [0;32mI (42) boot.esp32:
SPI Mode : DIO[0m
09:48:36.187 -> [0;32mI (47) boot.esp32:
SPI Flash Size : 4MB[0m
09:48:36.187 -> [0;32mI (52) boot: Enabling
RNG early entropy source...[0m
09:48:36.187 -> [0;32mI (57) boot:
Partition Table:[0m
09:48:36.187 -> [0;32mI (61) boot: ##
Label Usage Type ST Offset Length[0m
09:48:36.234 -> [0;32mI (68) boot: 0 phy_init RF data 01 01 0000f000 00001000[0m
09:48:36.234 -> [0;32mI (75) boot: 1 otadata OTA data 01 00 00010000 00002000[0m
09:48:36.234 -> [0;32mI (83) boot: 2 nvs WiFi data 01 02 00012000 0000e000[0m
09:48:36.234 -> [0;32mI (90) boot: 3 at_customize unknown 40 00 00020000 000e0000[0m
09:48:36.234
-> [0;32mI (98) boot: 4 ota_0 OTA app 00 10 00100000 00180000[0m
09:48:36.234
-> [0;32mI (105) boot: 5 ota_1 OTA app 00 11 00280000 00180000[0m
09:48:36.282 -> [0;32mI (113) boot: End of
partition table[0m
09:48:36.282 -> [0;32mI (117) boot: No
factory image, trying OTA 0[0m
09:48:36.282 -> [0;32mI (122) boot_comm:
chip revision: 1, min. application chip revision: 0[0m
09:48:36.282 -> [0;32mI (129) esp_image:
segment 0: paddr=00100020 vaddr=3f400020 size=295d8h (169432) map[0m
09:48:36.328 -> [0;32mI (199) esp_image:
segment 1: paddr=00129600 vaddr=3ffbdb60 size=04474h ( 17524) load[0m
09:48:36.328 -> [0;32mI (206) esp_image:
segment 2: paddr=0012da7c vaddr=40080000 size=0259ch ( 9628) load[0m
09:48:36.328 -> [0;32mI (210) esp_image:
segment 3: paddr=00130020 vaddr=400d0020 size=111630h (1119792) map[0m
09:48:36.752 -> [0;32mI (619) esp_image:
segment 4: paddr=00241658 vaddr=4008259c size=1b568h (111976) load[0m
09:48:36.799 -> [0;32mI (665) esp_image:
segment 5: paddr=0025cbc8 vaddr=400c0000 size=00064h ( 100) load[0m
09:48:36.799 -> [0;32mI (665) esp_image:
segment 6: paddr=0025cc34 vaddr=50000000 size=00010h ( 16) load[0m
09:48:36.799 -> [0;32mI (685) boot: Loaded
app from partition at offset 0x100000[0m
09:48:36.846 -> [0;32mI (710) boot: Set
actual ota_seq=1 in otadata[0][0m
09:48:36.846 -> [0;32mI (710) boot: Disabling
RNG early entropy source...[0m
09:48:37.218 -> module_name:WROOM-32
09:48:37.218 -> max tx power=78,ret=0
09:48:37.218
-> 2.4.0
20 sep ‘23: ESP Nr 32 (NodeMCU ESP-12 board
met voeding connector en headers). Zie samenvatting bovenin, bootloader en
firmware output:
Bootloader (74880):
ets
Jan 8 2013,rst cause:2, boot mode:(3,6)
load
0x40100000, len 2408, room 16
tail
8
chksum
0xe5
load 0x3ffe8000, len 776, room 0
tail 8
chksum 0x84
load 0x3ffe8310, len 632, room 0
tail 8
chksum 0xd8
csum 0xd8
2nd boot version : 1.6
SPI
Speed : 40MHz
SPI
Mode : QIO
SPI
Flash Size & Map: 32Mbit(512KB+512KB)
jump to run user1 @ 1000
rf cal sector: 1017
rf[112] : 00
rf[113] : 00
rf[114] : 01
SDK ver: 2.0.0(5a875ba) compiled @ Aug 9 2016 15:12:27
phy
ver: 1055, pp ver: 10.2
en dan troep
en op 115200 zie je dan troep en daaarna ready. Commands met Powershell script ReadCom.ps1 gestuurd:
AT+GMR
AT version:1.3.0.0(Jul 14 2016 18:54:01)
SDK version:2.0.0(5a875ba)
v1.0.0.3
Mar
13 2018 09:37:06
OK
En ook:
AT+CIPAPMAC?
+CIPAPMAC:"0a:3a:8d:d1:e6:b2"
OK
20 sep 23, ESP Nr 33, is een ESP32-C3
N16-R8 heeft micropython als firmware en een NeoPixel LED op board aan pin 48
(GPIO_48)
Met baudrate 115200 zie je (met ReadCom.ps1) :
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x8 (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fcd0108,len:0xf24
load:0x403b6000,len:0xc2c
load:0x403ba000,len:0x2d60
entry 0x403b61f4
MicroPython v1.19.1 on 2022-06-18; ESP32S3
module with ESP32S3
Type "help()" for more information.
>>>
help() sturen geeft:
Welcome to MicroPython on the ESP32!
For generic online docs please visit
http://docs.micropython.org/
For access to the hardware use the 'machine'
module:
import machine
pin12 = machine.Pin(12, machine.Pin.OUT)
pin12.value(1)
pin13 = machine.Pin(13, machine.Pin.IN,
machine.Pin.PULL_UP)
print(pin13.value())
i2c = machine.I2C(scl=machine.Pin(21),
sda=machine.Pin(22))
i2c.scan()
i2c.writeto(addr, b'1234')
i2c.readfrom(addr, 4)
Basic WiFi configuration:
import network
sta_if = network.WLAN(network.STA_IF);
sta_if.active(True)
sta_if.scan() # Scan for
available access points
sta_if.connect("<AP_name>",
"<password>") # Connect to an AP
sta_if.isconnected() # Check for successful
connection
Control commands:
CTRL-A -- on a blank line,
enter raw REPL mode
CTRL-B -- on a blank line,
enter normal REPL mode
CTRL-C -- interrupt a
running program
CTRL-D -- on a blank line,
do a soft reset of the board
CTRL-E -- on a blank line,
enter paste mode
For further help on a specific object, type
help(obj)
For a list of available modules, type
help('modules')
>>>
Met micropython script het mac adress opgehaald (zie
script ESP32MicroPythonGetMac.ps1, in documenten/pc stuff):
$Script:port.WriteLine("import
network`r")
$Script:port.WriteLine("import
ubinascii`r")
$Script:port.WriteLine("mac=ubinascii.hexlify(network.WLAN().config('mac'),':').decode()`r")
$Script:port.WriteLine("mac`r")
Output is dan: 'f4:12:fa:ce:d7:38'
Powershell
script ESP32MicroPythonGetMac.ps1
23 sep 23, ESP Nr 28, een Wemos D1
Mini V4.0 met USB-C, net als ESP Nr 29. Bootloader
output (74480 baud), dan AT cmds met 115200 baud:
ets
Jan 8 2013,rst cause:2, boot mode:(3,7)
load 0x40100000, len 2408, room 16
tail 8
chksum 0xe5
load 0x3ffe8000, len 776, room 0
tail 8
chksum 0x84
load 0x3ffe8310, len 632, room 0
tail 8
chksum 0xd8
csum 0xd8
2nd boot version : 1.6
SPI
Speed : 40MHz
SPI
Mode : QIO
SPI
Flash Size & Map: 32Mbit(512KB+512KB)
jump to run user1 @ 1000
rf cal sector: 1017
rf[112] : 00
rf[113] : 00
rf[114] : 01
SDK ver: 2.0.0(5a875ba) compiled @ Aug 9 2016 15:12:27
phy ver: 1055, pp ver: 10.2
`j?)--> End
Dan met 115200 AT Commands:
--> Writtten AT+GMR
AT+GMR
AT version:1.3.0.0(Jul 14 2016 18:54:01)
SDK version:2.0.0(5a875ba)
v1.0.0.3
Mar 13 2018 09:37:06
OK
AT+CIPAPMAC?
+CIPAPMAC:"c6:5b:be:e5:33:80"
23 sep 23, ESP Nr 29, een Wemos D1
Mini V4.0 met USB-C, net als ESP Nr 28. Bootloader
output zie ESPNr 28, dan AT cmds met 115200 baud:
--> Writtten AT+GMR
AT+GMR
AT version:1.3.0.0(Jul 14 2016 18:54:01)
SDK version:2.0.0(5a875ba)
v1.0.0.3
Mar 13 2018 09:37:06
OK
--> Writtten AT+CIPAPMAC?
AT+CIPAPMAC?
+CIPAPMAC:"26:62:ab:03:bc:5c"
24 sep 23, ESP Nr 31, een Lolin Wemos
ESP32 S2 mini met USB-C. Werkt raar, het flash en reset btn.
Reset
btn laat com poort verdwijnen en weer komen, dus als je bij boot output print,
mis je de eerste output. Dus geen firmware bootloader output kunnen zien.
HelloWorld mbv VSCode geflasht, werkt wel maar omdat de COM poort steeds
verdwijnt is output moeilijk te catchen. Daarom laat HelloWorld nu om de 10
seconden output zien.
Links:
https://github.com/nodemcu
https://nodemcu-build.com/index.php
- Hier kan je een nieuwe firmware build samenstellen. Nog kijken naar SD-Card
support en SSL
https://github.com/nodemcu/nodemcu-firmware
https://github.com/nodemcu/nodemcu-flasher/blob/master/Win64/Release/ESP8266Flasher.exe
https://esp8266.ru/esplorer/
https://github.com/marcelstoer/nodemcu-pyflasher/releases/tag/v4.0
https://github.com/espressif/esptool/releases/tag/v2.6
https://github.com/topics/espressif
https://nodemcu-build.com/
https://nodemcu.readthedocs.io/en/master/en/getting-started/
https://nodemcu.readthedocs.io/en/master
https://www.esp8266.com
https://www.silabs.com/products/development-tools/software/usb-to-uart-bridge-vcp-drivers
Arduino
IDE ESP 32 bij preferences, zijn 2 versies:
https://dl.espressif.com/dl/package_esp32_index.json
en
https://raw.githubusercontent.com/espressif/arduino-esp32/gh-pages/package_esp32_index.json