esp-12f 라는 보드는 esp8266을 탑재하고 있는데
[링크 : https://www.devicemart.co.kr/goods/view?no=1378117] 2500원
특이하게도 ESP8089 드라이버를 올려서 wifi로 잡아버린다.
esp8266은 esp8089에 포함된 wifi를 쓰는건가?
[링크 : https://eleparts.co.kr/EPXKDNPB]
[링크 : https://hackaday.io/project/9300-esp-12f-raspberry-pi-gpio-sdio-wifi]
| esp8266 wifi at 명령어 (0) | 2023.12.12 |
|---|---|
| esp8266 nodemcu v3 기본 펌웨어 (0) | 2023.12.11 |
| esp8266 esptool.py (0) | 2023.12.11 |
| esp8266 microUSB 연결 2 (0) | 2023.12.11 |
| esp8266 arduino (0) | 2023.12.09 |
AT+RST와 리셋 버튼의 메시지가 많이 다르게 나온다.
| AT+RST OK 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 ⸮ ⸮n⸮r⸮⸮n|⸮ l l⸮$`⸮ rl⸮l⸮ l`⸮ rl⸮l⸮ l`⸮ rl $⸮ ll`rl$rl⸮bb Čb⸮b br⸮$ b⸮n'nn⸮ l⸮ l ⸮ l⸮ll⸮l⸮⸮⸮⸮$`⸮n⸮bb l l$b ⸮⸮bb l ⸮b rlrl ready |
기본은 AP 모드로 되어있는 것 같고
| AT+CWMODE? +CWMODE:2 OK |
 |
FaryLink_F81835 라는 SSID로 검색되고 접속된다.
| AT+CWSAP? +CWSAP:"FaryLink_F81835","",1,0,4,0 OK |
핸드폰이 192.168.4.2로 붙었는데 MAC이 안드로이드에서 나오는 거랑 다르다. 머지?
| AT+CWLIF 192.168.4.2,0e:f8:ff:00:00:00 OK |
핸드폰에서 붙이면 이렇게 붙는데, 저 MAC은 도대체 누구꺼냐 -ㅁ-?
노트북꺼 붙이니 제대로 뜨는데, 핸드폰은 왜 다르지?
| AT+CWLIF 192.168.4.2,0e:f8:ff:00:00:00 192.168.4.3,8c:55:4a:28:25:bc OK |
요건 노트북 MAC
| $ ifconfig wlo1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1280 inet 192.168.4.3 netmask 255.255.255.0 broadcast 192.168.4.255 inet6 fe80::9169:c7eb:3e76:3204 prefixlen 64 scopeid 0x20<link> ether 8c:55:4a:28:25:bc txqueuelen 1000 (Ethernet) RX packets 2431961 bytes 301079066 (301.0 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 205909 bytes 25249933 (25.2 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 |
status가 5는 멀 의미하는지 모르겠다. 한개 더 붙었다고 느는것도 아니고 머지?
프로토콜 문서 찾아보니 5번은 wifi에 연결되지 않았다. 머 AP 모드니까 당연한건가?
| AT+CIPSTATUS STATUS:5 OK |
 |
[링크 : https://www.espressif.com/sites/default/files/4a-esp8266_at_instruction_set_en_v1.5.4_0.pdf]
| esp8266 sdio wifi (0) | 2024.09.12 |
|---|---|
| esp8266 nodemcu v3 기본 펌웨어 (0) | 2023.12.11 |
| esp8266 esptool.py (0) | 2023.12.11 |
| esp8266 microUSB 연결 2 (0) | 2023.12.11 |
| esp8266 arduino (0) | 2023.12.09 |
minicom이나 리눅스용 putty로 쇼를 해도 안되서
결국에는 arduino 설치하고 시리얼 터미널로 테스트하니 응답한다
Both NL & CR로 해주어야 응답한다. (망할!)
[링크 : https://techposts.org/flash-nodemcu-v3-stock-firmware/]
[링크 : https://github.com/sleemanj/ESP8266_Simple/blob/master/firmware/README.md]
| v1.1.1 ai-thinker-v1.1.1.bin the default baud rate is 115200 Important Note: The AT command must be end with "\r\n". For Arduino, must type the AT command like this Serial1.print("AT+GMR\r\n"); Not like this: Serial1.println("AT+GMR"); So the hardwareSerialMonitor sketch will not work now. v0.9.5.2 ai-thinker-0.9.5.2-9600.bin The default baud rate is 9600 ai-thinker-0.9.5.2.bin The default baud rate is 115200 AT+GMR AT version:0.21.0.0 SDK version:0.9.5 v0.9.5 beta ai-thinker-0.9.5.bin AT+GMR 00200.9.5(b1) compiled @ Dec 25 2014 21:40:28 AI-THINKER Dec4 |
[링크 : https://wiki.aprbrother.com/en/Firmware_For_ESP8266.html]
어디서 받아야하나?
[링크 : https://www.espressif.com/en/support/download/at]
+
AT 명령어
[링크 : https://blog.naver.com/ssshin22/220868021464]
[링크 : https://www.espressif.com/sites/default/files/4a-esp8266_at_instruction_set_en_v1.5.4_0.pdf]
| esp8266 sdio wifi (0) | 2024.09.12 |
|---|---|
| esp8266 wifi at 명령어 (0) | 2023.12.12 |
| esp8266 esptool.py (0) | 2023.12.11 |
| esp8266 microUSB 연결 2 (0) | 2023.12.11 |
| esp8266 arduino (0) | 2023.12.09 |
ubuntu 22.04에서 brltty를 삭제하고 하라고 한다.
[링크 : https://stackoverflow.com/questions/70123431/why-would-ch341-uart-is-disconnected-from-ttyusb]
패키지 설치는 아래의 명령어를 사용하면 끝!
| $ sudo apt remove brltty $ git clone https://github.com/espressif/esptool.git $ pip install intelhex $ pip install pyserial $ cd esptool |
아따.. 읽어 보기도 힘드네 -_-
| $ ./esptool.py --port /dev/ttyUSB0 read_flash_status esptool.py v4.6.2 Serial port /dev/ttyUSB0 Connecting.... Detecting chip type... Unsupported detection protocol, switching and trying again... Connecting.... Detecting chip type... ESP8266 Chip is ESP8266EX Features: WiFi Crystal is 26MHz MAC: bc:ff:4d:f8:18:35 Uploading stub... Running stub... Stub running... Status value: 0x0000 Hard resetting via RTS pin... |
| $ ./esptool.py --port /dev/ttyUSB0 flash_id esptool.py v4.6.2 Serial port /dev/ttyUSB0 Connecting.... Detecting chip type... Unsupported detection protocol, switching and trying again... Connecting.... Detecting chip type... ESP8266 Chip is ESP8266EX Features: WiFi Crystal is 26MHz MAC: bc:ff:4d:f8:18:35 Uploading stub... Running stub... Stub running... Manufacturer: d8 Device: 4016 Detected flash size: 4MB Hard resetting via RTS pin... |
| $ ./esptool.py --port /dev/ttyUSB0 chip_id esptool.py v4.6.2 Serial port /dev/ttyUSB0 Connecting.... Detecting chip type... Unsupported detection protocol, switching and trying again... Connecting.... Detecting chip type... ESP8266 Chip is ESP8266EX Features: WiFi Crystal is 26MHz MAC: bc:ff:4d:f8:18:35 Uploading stub... Running stub... Stub running... Chip ID: 0x00f81835 Hard resetting via RTS pin... |
| $ ./esptool.py -h usage: esptool [-h] [--chip {auto,esp8266,esp32,esp32s2,esp32s3beta2,esp32s3,esp32c3,esp32c6beta,esp32h2beta1,esp32h2beta2,esp32c2,esp32c6,esp32h2,esp32p4}] [--port PORT] [--baud BAUD] [--before {default_reset,usb_reset,no_reset,no_reset_no_sync}] [--after {hard_reset,soft_reset,no_reset,no_reset_stub}] [--no-stub] [--trace] [--override-vddsdio [{1.8V,1.9V,OFF}]] [--connect-attempts CONNECT_ATTEMPTS] {load_ram,dump_mem,read_mem,write_mem,write_flash,run,image_info,make_image,elf2image,read_mac,chip_id,flash_id,read_flash_status,write_flash_status,read_flash,verify_flash,erase_flash,erase_region,merge_bin,get_security_info,version} ... esptool.py v4.6.2 - Espressif chips ROM Bootloader Utility positional arguments: {load_ram,dump_mem,read_mem,write_mem,write_flash,run,image_info,make_image,elf2image,read_mac,chip_id,flash_id,read_flash_status,write_flash_status,read_flash,verify_flash,erase_flash,erase_region,merge_bin,get_security_info,version} Run esptool.py {command} -h for additional help load_ram Download an image to RAM and execute dump_mem Dump arbitrary memory to disk read_mem Read arbitrary memory location write_mem Read-modify-write to arbitrary memory location write_flash Write a binary blob to flash run Run application code in flash image_info Dump headers from a binary file (bootloader or application) make_image Create an application image from binary files elf2image Create an application image from ELF file read_mac Read MAC address from OTP ROM chip_id Read Chip ID from OTP ROM flash_id Read SPI flash manufacturer and device ID read_flash_status Read SPI flash status register write_flash_status Write SPI flash status register read_flash Read SPI flash content verify_flash Verify a binary blob against flash erase_flash Perform Chip Erase on SPI flash erase_region Erase a region of the flash merge_bin Merge multiple raw binary files into a single file for later flashing get_security_info Get some security-related data version Print esptool version options: -h, --help show this help message and exit --chip {auto,esp8266,esp32,esp32s2,esp32s3beta2,esp32s3,esp32c3,esp32c6beta,esp32h2beta1,esp32h2beta2,esp32c2,esp32c6,esp32h2,esp32p4}, -c {auto,esp8266,esp32,esp32s2,esp32s3beta2,esp32s3,esp32c3,esp32c6beta,esp32h2beta1,esp32h2beta2,esp32c2,esp32c6,esp32h2,esp32p4} Target chip type --port PORT, -p PORT Serial port device --baud BAUD, -b BAUD Serial port baud rate used when flashing/reading --before {default_reset,usb_reset,no_reset,no_reset_no_sync} What to do before connecting to the chip --after {hard_reset,soft_reset,no_reset,no_reset_stub}, -a {hard_reset,soft_reset,no_reset,no_reset_stub} What to do after esptool.py is finished --no-stub Disable launching the flasher stub, only talk to ROM bootloader. Some features will not be available. --trace, -t Enable trace-level output of esptool.py interactions. --override-vddsdio [{1.8V,1.9V,OFF}] Override ESP32 VDDSDIO internal voltage regulator (use with care) --connect-attempts CONNECT_ATTEMPTS Number of attempts to connect, negative or 0 for infinite. Default: 7. |
| esp8266 wifi at 명령어 (0) | 2023.12.12 |
|---|---|
| esp8266 nodemcu v3 기본 펌웨어 (0) | 2023.12.11 |
| esp8266 microUSB 연결 2 (0) | 2023.12.11 |
| esp8266 arduino (0) | 2023.12.09 |
| esp8266 SDK (0) | 2023.12.04 |
115200bps 로 설정해서 reset 누르니 아래와 같이 먼가 나오긴 한데..
pcb 뒷편에는 CH340G 드라이버 설치하고 9600bps로 연결하라고 하는데 머가 맞는걸까?
봉투에서 뜯은녀석이라 다른 프로그램이 들어있는건 아닐텐데..
| �brlrl ready |
dmseg로 확인하면 아래와 같이 인식된다. CH341? CH340G 라고 한거 같은디..
| normal boot |
| [ 528.742541] usb 2-1.1: new full-speed USB device number 11 using ehci-pci [ 528.851812] usb 2-1.1: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.54 [ 528.851831] usb 2-1.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [ 528.851838] usb 2-1.1: Product: USB2.0-Ser! [ 528.852466] ch341 2-1.1:1.0: ch341-uart converter detected [ 528.854364] ch341-uart ttyUSB0: break control not supported, using simulated break [ 528.854604] usb 2-1.1: ch341-uart converter now attached to ttyUSB0 |
flash 버튼 누르고 부팅하면 아래와 같이 조금더 나온다.
그런데 BRLTTY가 머하는걸까? USB 플래시 처럼인식은 안되나보네
| flash 버튼 누르고 boot 메시지 |
| [ 455.103387] usb 2-1.1: new full-speed USB device number 10 using ehci-pci [ 455.213032] usb 2-1.1: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.54 [ 455.213052] usb 2-1.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [ 455.213059] usb 2-1.1: Product: USB2.0-Ser! [ 455.213892] ch341 2-1.1:1.0: ch341-uart converter detected [ 455.214821] ch341-uart ttyUSB0: break control not supported, using simulated break [ 455.215109] usb 2-1.1: ch341-uart converter now attached to ttyUSB0 [ 455.792404] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input27 [ 455.880634] usb 2-1.1: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1 [ 455.881356] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0 [ 455.881387] ch341 2-1.1:1.0: device disconnected |
| 일반 권한 |
| $ brltty BRLTTY 6.4 rev BRLTTY-6.4 [https://brltty.app/] brltty: can't isolate namespaces brltty: executing as the invoking user: falinux brltty: can't set supplementary groups brltty: group not joined: 0(root) brltty: group not joined: 5(tty) brltty: group not joined: 29(audio) brltty: group not joined: 107(input) brltty: group not joined: 133(pulse-access) brltty: required capability not granted: cap_sys_admin (for injecting input characters typed on a braille device) brltty: required capability not granted: cap_sys_tty_config (for playing alert tunes via the built-in PC speaker) brltty: required capability not granted: cap_mknod (for creating needed but missing special device files) |
| root 권한 |
| $ sudo brltty BRLTTY 6.4 rev BRLTTY-6.4 [https://brltty.app/] brltty: executing as the invoking user: root |
두번 실행하니 먼가 5초에 한번 주기적으로 뜬다. 멀까?
(그냥 프롬프트가 뜨길래 먼가했는데 백그라운드로 brltty가 실행되고 있어서 뜨는 메시지 였음)
| [450328.072373] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input36 [450351.379981] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input37 [450351.389760] usb 1-2.4.2: usbfs: interface 0 claimed by usbfs while 'brltty' sets config #1 [450356.391459] usb 1-2.4.2: usbfs: interface 0 claimed by usbfs while 'brltty' sets config #1 [450361.393130] usb 1-2.4.2: usbfs: interface 0 claimed by usbfs while 'brltty' sets config #1 [450366.397596] usb 1-2.4.2: usbfs: interface 0 claimed by usbfs while 'brltty' sets config #1 [450371.400305] usb 1-2.4.2: usbfs: interface 0 claimed by usbfs while 'brltty' sets config #1 [450376.389840] usb 1-2.4.2: usbfs: interface 0 claimed by usbfs while 'brltty' sets config #1 [450381.395540] usb 1-2.4.2: usbfs: interface 0 claimed by usbfs while 'brltty' sets config #1 [450386.401519] usb 1-2.4.2: usbfs: interface 0 claimed by usbfs while 'brltty' sets config #1 [450391.397008] usb 1-2.4.2: usbfs: interface 0 claimed by usbfs while 'brltty' sets config #1 [450396.389537] usb 1-2.4.2: usbfs: interface 0 claimed by usbfs while 'brltty' sets config #1 [450401.402252] usb 1-2.4.2: usbfs: interface 0 claimed by usbfs while 'brltty' sets config #1 [450406.395525] usb 1-2.4.2: usbfs: interface 0 claimed by usbfs while 'brltty' sets config #1 |
| esp8266 nodemcu v3 기본 펌웨어 (0) | 2023.12.11 |
|---|---|
| esp8266 esptool.py (0) | 2023.12.11 |
| esp8266 arduino (0) | 2023.12.09 |
| esp8266 SDK (0) | 2023.12.04 |
| esp8266 microUSB 연결 (0) | 2023.12.04 |
| https://arduino.esp8266.com/stable/package_esp8266com_index.json https://raw.githubusercontent.com/espressif/arduino-esp32/gh-pages/package_esp32_dev_index.json |
[링크 : https://github.com/esp8266/Arduino/blob/master/package/package_esp8266com_index.template.json]
[링크 : https://github.com/esp8266/Arduino]
[링크 : https://m.blog.naver.com/elepartsblog/221453102971]
| esp8266 esptool.py (0) | 2023.12.11 |
|---|---|
| esp8266 microUSB 연결 2 (0) | 2023.12.11 |
| esp8266 SDK (0) | 2023.12.04 |
| esp8266 microUSB 연결 (0) | 2023.12.04 |
| esp8266 (0) | 2023.12.03 |
[링크 : https://nodemcu.readthedocs.io/en/release/]
[링크 : https://github.com/espressif/ESP8266_NONOS_SDK]
[링크 : https://github.com/nodemcu/nodemcu-devkit-v1.0]
보드의 FLASH 버튼을 LOW로 한 채로 켜야 하는 듯.(즉, 전원 넣기 전에 누르고 있어야 한단 의미)
| Just click flash and you can burn firmware to ESP8266. Before you doing it, GPIO0 MUST LOW. |
[링크 : https://github.com/nodemcu/nodemcu-flasher] 윈도우용 플래시 퓨징 프로그램
[링크 : https://github.com/nodemcu/nodemcu-firmware]
[링크 : https://github.com/marcelstoer/nodemcu-pyflasher] pyFlasher
[링크 : https://nodemcu.readthedocs.io/en/latest/flash/]
[링크 : https://www.best-microcontroller-projects.com/nodemcu-firmware.html]
| esp8266 esptool.py (0) | 2023.12.11 |
|---|---|
| esp8266 microUSB 연결 2 (0) | 2023.12.11 |
| esp8266 arduino (0) | 2023.12.09 |
| esp8266 microUSB 연결 (0) | 2023.12.04 |
| esp8266 (0) | 2023.12.03 |
flash 버튼 누른채로 usb 연결하면 아래와 같이 먼가 나오는데
기존의 cp210x를 죽여버리고 ch341은 연결하는 느낌이다.
| $ lsusb -t -v |__ Port 3: Dev 59, If 0, Class=Vendor Specific Class, Driver=, 12M ID 1a86:7523 QinHeng Electronics CH340 serial converter |
| $ sudo dmesg [1473116.242277] usb 1-3: new full-speed USB device number 59 using xhci_hcd [1473116.391455] usb 1-3: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.54 [1473116.391473] usb 1-3: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [1473116.391479] usb 1-3: Product: USB2.0-Ser! [1473116.431662] usbcore: registered new interface driver ch341 [1473116.431675] usbserial: USB Serial support registered for ch341-uart [1473116.431693] ch341 1-3:1.0: ch341-uart converter detected [1473116.432077] ch341-uart ttyUSB2: break control not supported, using simulated break [1473116.432166] usb 1-3: ch341-uart converter now attached to ttyUSB2 [1473116.503795] input: PC Speaker as /devices/platform/pcspkr/input/input82 [1473117.030963] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input83 [1473117.156864] usb 1-3: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1 [1473117.157672] ch341-uart ttyUSB2: ch341-uart converter now disconnected from ttyUSB2 [1473117.157738] ch341 1-3:1.0: device disconnected [1473117.174250] usb 1-2.4.2: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 [1473117.178085] cp210x ttyUSB1: cp210x converter now disconnected from ttyUSB1 [1473117.178151] cp210x 1-2.4.2:1.0: device disconnected |
| esp8266 esptool.py (0) | 2023.12.11 |
|---|---|
| esp8266 microUSB 연결 2 (0) | 2023.12.11 |
| esp8266 arduino (0) | 2023.12.09 |
| esp8266 SDK (0) | 2023.12.04 |
| esp8266 (0) | 2023.12.03 |
위조부품인가 왜 마킹이 지워진 흔적이 있지?
LDO는 1117
nodeMCU v3
[링크 : https://nodemcu.readthedocs.io/en/release/]
[링크 : https://github.com/nodemcu/nodemcu-firmware]
[링크 : https://www.embedic.com/technology/details/esp32-vs-esp8266--which-is-better-and-how-to-choose]
[링크 : https://makeradvisor.com/esp32-vs-esp8266/]
cp2102칩이 좀 더 작고, ch340이라 드라이버 설치이야기가 나오는 듯
| esp8266 esptool.py (0) | 2023.12.11 |
|---|---|
| esp8266 microUSB 연결 2 (0) | 2023.12.11 |
| esp8266 arduino (0) | 2023.12.09 |
| esp8266 SDK (0) | 2023.12.04 |
| esp8266 microUSB 연결 (0) | 2023.12.04 |
|
