[{"data":1,"prerenderedAt":594},["ShallowReactive",2],{"post-esp32-failed-to-connect-no-serial-data-received-en":3,"related-posts-esp32-failed-to-connect-no-serial-data-received-en":546,"related-categories-esp32-failed-to-connect-no-serial-data-received-en":575},{"id":4,"title":5,"author":6,"authorImageUrl":7,"authorUrl":8,"body":9,"categorySlug":510,"categoryText":511,"dateModified":512,"datePublished":512,"description":513,"extension":514,"faqs":515,"image":531,"imageAlt":532,"language":533,"meta":534,"navigation":535,"path":536,"seo":537,"sitemap":538,"stem":539,"summary":540,"tags":541,"__hash__":545},"blog\u002Fblog\u002Fesp32-failed-to-connect-no-serial-data-received.md","Failed to Connect to ESP32: No Serial Data Received","Mauro Brambilla","\u002Fimages\u002Fauthors\u002Fbruma.jpg","\u002Fabout",{"type":10,"value":11,"toc":494},"minimark",[12,20,36,41,47,50,61,72,81,88,94,98,107,134,137,141,155,158,185,190,194,210,216,222,227,244,252,260,264,289,293,306,310,317,353,370,378,389,393,405,413,417,420,452,458,469,473,476],[13,14,15,19],"p",{},[16,17,18],"strong",{},"Failed to connect to ESP32: No serial data received"," means esptool opened the serial port but heard nothing back from the chip's ROM bootloader. Espressif ties it to the hardware side: a dead board, unconnected RX\u002FTX lines, or a failed reset into download mode. In practice that usually comes down to a charge-only USB cable, the wrong or busy port, a board that never entered download mode, or a weak power supply. We'll go through them in that order, cheapest fix first.",[13,21,22,23,30,31,35],{},"This guide covers classic ESP32 dev boards, native-USB chips (ESP32-S3, C3, C6), the XIAO ESP32-S3 and the ESP32-CAM-MB board. The error text and causes come from ",[24,25,29],"a",{"href":26,"rel":27},"https:\u002F\u002Fdocs.espressif.com\u002Fprojects\u002Fesptool\u002Fen\u002Flatest\u002Fesp32\u002Ftroubleshooting.html",[28],"nofollow","Espressif's esptool troubleshooting page",", and the board sequences are the ones the ",[24,32,34],{"href":33},"\u002Fblog\u002Fwhat-is-opengizmo","OpenGizmo projects"," use to flash their firmware from the browser.",[37,38,40],"h2",{"id":39},"what-does-no-serial-data-received-mean","What does \"No serial data received\" mean?",[13,42,43,46],{},[16,44,45],{},"Download mode"," is the state where the ESP32's ROM bootloader waits for esptool over the serial port. The chip enters it when GPIO0 is held low at reset (the \"BOOT\" button does exactly that). Esptool sends sync packets, and the error appears when not one byte comes back. Espressif's docs say it \"usually implies some kind of a hardware issue\": a board that isn't working at all, RX\u002FTX lines that aren't connected, or a problem resetting into download mode.",[13,48,49],{},"Current esptool (I checked the 5.1.0 and 4.8.1 sources) prints it like this:",[51,52,58],"pre",{"className":53,"code":55,"language":56,"meta":57},[54],"language-text","A fatal error occurred: Failed to connect to ESP32: No serial data received.\nFor troubleshooting steps visit: https:\u002F\u002Fdocs.espressif.com\u002Fprojects\u002Fesptool\u002Fen\u002Flatest\u002Ftroubleshooting.html\n","text","",[59,60,55],"code",{"__ignoreMap":57},[13,62,63,64,67,68,71],{},"The chip name changes with your target (",[59,65,66],{},"ESP32-S3",", ",[59,69,70],{},"ESP32-C3","). Older posts may quote a different message for the same situation, such as \"Timed out waiting for packet header\". I couldn't find that string in the esptool 3.3.2, 4.8.1 or 5.1.0 sources, so I can't say which release printed it. If you see it, the fixes below still apply.",[13,73,74,75,80],{},"The browser flasher on the project pages is built on ",[24,76,79],{"href":77,"rel":78},"https:\u002F\u002Fgithub.com\u002Fespressif\u002Fesptool-js",[28],"esptool-js"," 0.7.1, and when it can't reach the chip it shows \"Failed to connect with the device\". Same problem, shorter sentence, same fixes.",[13,82,83],{},[84,85],"img",{"alt":86,"src":87},"Three symptoms of a failed ESP32 connection and their first fix: no port, port without connection, and a failure in the middle of flashing","\u002Fimages\u002Fblog\u002Fesp32-failed-to-connect-no-serial-data-received-symptoms.webp",[89,90],"blog-table",{":headers":91,":highlightCol":92,":rows":93},"[\"What you see\",\"Most likely cause\",\"First thing to try\"]","0","[[\"No new serial port when you plug the board in\",\"Charge-only cable, missing driver, dead port\",\"Swap the cable, change the USB port\"],[\"Port appears, 'No serial data received'\",\"Chip not in download mode, or another program holds the port\",\"Close other terminals, then BOOT held + RESET\"],[\"'Wrong boot mode detected (0xXX)!'\",\"Chip answers, but the auto-reset didn't work\",\"Enter download mode by hand\"],[\"'Invalid head of packet (0xXX)'\",\"Bad cable, breadboard shorts, brownout\",\"Different cable, lower baud rate\"],[\"Fails partway through flashing\",\"Unstable power or baud rate too high\",\"Retry at a lower baud rate\"]]",[37,95,97],{"id":96},"_1-is-it-the-cable-how-do-you-spot-a-charge-only-cable","1. Is it the cable? How do you spot a charge-only cable?",[13,99,100,101,106],{},"A charge-only cable has the power wires but not the data pair, so the board lights up and your computer sees nothing. Espressif's pages don't describe this case and I have no figure for how common it is, but the ",[24,102,105],{"href":103,"rel":104},"https:\u002F\u002Fgithub.com\u002Fopen-gizmo\u002Fgizmo-camera",[28],"Gizmo Camera README"," lists \"try another USB cable (some only charge)\" among its first checks, and it costs nothing to try.",[108,109,110,128,131],"ol",{},[111,112,113,114,117,118,121,122,127],"li",{},"Unplug the board and plug it back in. Look at the port list: ",[59,115,116],{},"ls \u002Fdev\u002Ftty*"," on Linux, ",[59,119,120],{},"ls \u002Fdev\u002Fcu.*"," on macOS, Device Manager on Windows (",[24,123,126],{"href":124,"rel":125},"https:\u002F\u002Fdocs.espressif.com\u002Fprojects\u002Fesp-idf\u002Fen\u002Fstable\u002Fesp32s3\u002Fget-started\u002Festablish-serial-connection.html",[28],"Espressif's serial connection guide"," uses the same method: compare the list with and without the board).",[111,129,130],{},"If nothing new appears, try a cable that you know carries data, for example the one from a phone you sync with a computer.",[111,132,133],{},"Plug it directly into the computer, not into a hub or a monitor's USB port.",[13,135,136],{},"You should now see a new entry. If you do, move on. If you don't, test the board with a second computer before blaming it.",[37,138,140],{"id":139},"_2-is-it-the-driver-or-a-permission-problem","2. Is it the driver or a permission problem?",[13,142,143,144,149,150,154],{},"Boards with a USB-to-UART bridge need the bridge chip's driver. Espressif's ",[24,145,148],{"href":146,"rel":147},"https:\u002F\u002Fdocs.espressif.com\u002Fprojects\u002Fesptool\u002Fen\u002Flatest\u002Fesp32s3\u002Fadvanced-topics\u002Fboot-mode-selection.html",[28],"boot mode page"," names FTDI, CP210x and CH340x as the common converter chips, and its ",[24,151,153],{"href":124,"rel":152},[28],"serial connection guide"," says the drivers are normally bundled with the operating system. If the port shows up in Device Manager with a warning icon, install the driver for the chip printed on your board.",[13,156,157],{},"Two more things hide a working board:",[159,160,161,171],"ul",{},[111,162,163,166,167,170],{},[16,164,165],{},"Another program holds the port."," A serial monitor left open in another window is the classic one, and on Linux ",[59,168,169],{},"modem-manager"," can interfere too. Close them and retry.",[111,172,173,176,177,180,181,184],{},[16,174,175],{},"Linux permissions."," esptool needs read and write access to the port. Add your user to the ",[59,178,179],{},"dialout"," group (or ",[59,182,183],{},"uucp"," on some distributions), then log out and back in:",[186,187],"terminal",{":commands":188,"title":189},"[\"sudo usermod -a -G dialout $USER\"]","Give your user access to the serial port",[37,191,193],{"id":192},"_3-how-do-you-enter-download-mode-by-hand","3. How do you enter download mode by hand?",[13,195,196,197,201,202,205,206,209],{},"Most dev boards reset themselves into download mode: esptool toggles the DTR and RTS lines of the USB bridge, wired to GPIO0 and EN. When that circuit is missing, slow, or unreliable, you do it yourself. ",[24,198,200],{"href":146,"rel":199},[28],"Espressif's boot mode page"," puts it as: hold the ",[16,203,204],{},"Boot"," button (GPIO0) and press ",[16,207,208],{},"EN",". GPIO0 low at reset selects the ROM serial bootloader, and GPIO0 high (or floating, thanks to the internal pull-up) selects normal execution.",[13,211,212],{},[84,213],{"alt":214,"src":215},"A maker holds the BOOT button of a tiny XIAO board while plugging in its USB-C cable, a laptop terminal waiting beside it","\u002Fimages\u002Fblog\u002Fesp32-failed-to-connect-no-serial-data-received-illustration.webp",[13,217,218],{},[84,219],{"alt":220,"src":221},"Hold-and-tap button sequences for the XIAO ESP32-S3, the ESP32-CAM-MB board and a generic ESP32 dev board","\u002Fimages\u002Fblog\u002Fesp32-failed-to-connect-no-serial-data-received-download-mode.webp",[223,224,226],"h3",{"id":225},"xiao-esp32-s3","XIAO ESP32-S3",[13,228,229,230,235,236,239,240,243],{},"Seeed's ",[24,231,234],{"href":232,"rel":233},"https:\u002F\u002Fwiki.seeedstudio.com\u002Fxiao_esp32s3_getting_started\u002F",[28],"getting started page"," documents two ways into bootloader mode, both with the ",[16,237,238],{},"BOOT"," and ",[16,241,242],{},"Reset"," buttons:",[108,245,246,249],{},[111,247,248],{},"Hold BOOT, connect the USB cable while holding it, then release BOOT.",[111,250,251],{},"Or hold BOOT while powering up and press Reset once.",[13,253,254,255,259],{},"Seeed also says to try pressing Reset on its own first if the port is missing or the upload fails. Both buttons sit on top of the board, so with the enclosure of a XIAO-based device such as ",[24,256,258],{"href":257},"\u002Fprojects\u002Fgizmo-ticker","Gizmo Ticker"," closed, you can't reach them. My notes for the XIAO say the same: once it's closed, flash and reset it over USB. For a stubborn port, open the box and use the BOOT sequence on the bench.",[223,261,263],{"id":262},"esp32-cam-on-the-esp32-cam-mb","ESP32-CAM on the ESP32-CAM-MB",[13,265,266,267,239,270,273,274,278,279,283,284,288],{},"The AI Thinker ESP32-CAM has no USB port: it sits on the ESP32-CAM-MB, a small USB adapter with ",[16,268,269],{},"IO0",[16,271,272],{},"RST"," buttons. ",[24,275,277],{"href":276},"\u002Fprojects\u002Fgizmo-camera","Gizmo Camera"," documents the manual sequence in its ",[24,280,282],{"href":103,"rel":281},[28],"README",": hold IO0, press and release RST, then release IO0 and flash again. IO0 is GPIO0, the same pin as BOOT. In the printed enclosure you press them with a paperclip through the pinholes in the long sides. The full walkthrough is in ",[24,285,287],{"href":286},"\u002Fblog\u002Fesp32-cam-mb-usb-programmer-guide","the ESP32-CAM-MB programming guide",".",[223,290,292],{"id":291},"generic-dev-board","Generic dev board",[13,294,295,296,300,301,305],{},"Hold BOOT, press and release EN (often labeled RESET), release BOOT, and start the upload. Pins other than GPIO0 also matter for some chips: on the ESP32-S3, ",[24,297,299],{"href":146,"rel":298},[28],"GPIO46 must be floating or low to enter the serial bootloader",". The ",[24,302,304],{"href":303},"\u002Fblog\u002Fesp32-strapping-pins-by-chip","strapping pins by chip"," guide covers the rest.",[37,307,309],{"id":308},"_4-why-does-it-fail-on-native-usb-chips-esp32-s3-c3-c6","4. Why does it fail on native-USB chips (ESP32-S3, C3, C6)?",[13,311,312,313,316],{},"Chips such as the ESP32-S3, ESP32-C3 and ESP32-C6 have a built-in ",[16,314,315],{},"USB Serial\u002FJTAG controller",", so there is no bridge chip between the computer and the ESP. Espressif says it \"is able to put\" the chip \"into download mode automatically\", so the bridge-related causes above mostly don't apply. A few others do:",[159,318,319,337,343],{},[111,320,321,324,325,330,331,336],{},[16,322,323],{},"The firmware took the USB pins."," The controller is fixed-function: it can't be reconfigured for anything except a serial port and JTAG. But if the application reconfigures or disables the USB pins (on the ESP32-S3 they are GPIO19 for D- and GPIO20 for D+, per ",[24,326,329],{"href":327,"rel":328},"https:\u002F\u002Fdocs.espressif.com\u002Fprojects\u002Fesp-idf\u002Fen\u002Fstable\u002Fesp32s3\u002Fapi-guides\u002Fusb-serial-jtag-console.html",[28],"Espressif's console guide","), the device disappears from the computer. The fix is the manual sequence: pull the boot pin low (GPIO0 on the ESP32-S3, ",[24,332,335],{"href":333,"rel":334},"https:\u002F\u002Fdocs.espressif.com\u002Fprojects\u002Fesp-idf\u002Fen\u002Fstable\u002Fesp32c6\u002Fapi-guides\u002Fusb-serial-jtag-console.html",[28],"GPIO9 on the ESP32-C6",") and reset the chip, then flash a sketch that leaves USB alone.",[111,338,339,342],{},[16,340,341],{},"Deep sleep."," On the ESP32-S3, the USB Serial\u002FJTAG device appears disconnected while the chip is in deep sleep and reconnects when it wakes. A sketch that sleeps almost all the time is hard to catch: use the BOOT sequence.",[111,344,345,348,349,352],{},[16,346,347],{},"The board won't restart after a manual download."," If you entered download mode with BOOT and EN, esptool can't leave it with the default reset, because USB Serial\u002FJTAG triggers only a core reset that doesn't re-read the boot pin. Add ",[59,350,351],{},"--after watchdog-reset",", or just press EN or replug the board.",[13,354,355,356,359,360,363,364,239,367,288],{},"The commands use the esptool 5 syntax (",[59,357,358],{},"esptool",", hyphenated ",[59,361,362],{},"write-flash","); older 4.x releases spell it ",[59,365,366],{},"esptool.py",[59,368,369],{},"write_flash",[51,371,376],{"className":372,"code":374,"language":375,"meta":57},[373],"language-bash","esptool --port \u002Fdev\u002FttyACM0 --after watchdog-reset write-flash 0x0 merged.bin\n","bash",[59,377,374],{"__ignoreMap":57},[13,379,380,381,384,385,388],{},"Replace the port and the file with yours. On Linux, native-USB boards usually show up as ",[59,382,383],{},"\u002Fdev\u002FttyACM*"," and bridge boards as ",[59,386,387],{},"\u002Fdev\u002FttyUSB*",", though I haven't verified that for every board.",[37,390,392],{"id":391},"_5-power-problems-that-look-like-flash-errors","5. Power problems that look like flash errors",[13,394,395,396,399,400,404],{},"If the connection works but flashing dies halfway, or you see ",[16,397,398],{},"Invalid head of packet",", suspect power and the cable. Espressif says the 3.3 V supply has to deliver up to 70 mA continuous with 200 to 300 mA peaks, and needs enough capacitance to ride out those spikes (",[24,401,403],{"href":26,"rel":402},[28],"esptool troubleshooting","). It also warns that the 3.3 V output of FTDI FT232R adapters and Arduino boards does not supply enough current, and that very simple pin breakout modules don't integrate enough capacitance to work reliably without extra components.",[13,406,407,408,412],{},"Try, one at a time: a shorter or better cable, a different port, removing the board from the breadboard (breadboards can short the SPI flash pins), and unplugging anything on the GPIO pins. A brownout during flashing is the same story as the ",[24,409,411],{"href":410},"\u002Fblog\u002Fesp32-brownout-detector-was-triggered","brownout detector reset",", only earlier in the boot.",[37,414,416],{"id":415},"_6-last-resorts-baud-rate-chip-flag-and-a-trace","6. Last resorts: baud rate, chip flag and a trace",[13,418,419],{},"Still stuck? Change one thing at a time:",[108,421,422,432,442],{},[111,423,424,427,428,431],{},[16,425,426],{},"Lower the baud rate."," Espressif suggests ",[59,429,430],{},"-b 9600"," as a very slow value to rule out a baud problem. Esptool's default is 115200, and the initial connection is limited to that.",[111,433,434,437,438,441],{},[16,435,436],{},"Name the chip."," Skipping autodetection with ",[59,439,440],{},"--chip esp32s3"," removes one variable.",[111,443,444,447,448,451],{},[16,445,446],{},"Trace the conversation."," ",[59,449,450],{},"esptool --trace"," dumps every serial exchange, which tells you whether anything comes back at all.",[51,453,456],{"className":454,"code":455,"language":375,"meta":57},[373],"esptool --chip esp32s3 --port \u002Fdev\u002FttyACM0 --baud 9600 --trace flash-id\n",[59,457,455],{"__ignoreMap":57},[13,459,460,463,464,468],{},[59,461,462],{},"flash-id"," reads the flash chip's ID without writing anything, so it's a safe test. If it answers, your connection is fine and the problem was in the flash step. If the connection works but you are unsure where the image lands in flash, ",[24,465,467],{"href":466},"\u002Fblog\u002Fesp32-partition-table-explained","the ESP32 partition table explained"," shows the layout.",[37,470,472],{"id":471},"what-to-remember","What to remember",[13,474,475],{},"\"No serial data received\" is a communication failure, not a verdict on the firmware. Work down the list: data cable, port and permissions, download mode by hand (BOOT held, then RESET), then power and baud rate. The cable and the manual BOOT sequence are the first two things to rule out, but Espressif gives no statistics on which cause is most common, and a dead board or a damaged USB-UART chip is possible when everything else fails.",[13,477,478,479,483,484,488,489,493],{},"I didn't test the sequences on every board in this post. The XIAO and the ESP32-CAM-MB steps come from Seeed's wiki and the Gizmo Camera README, the rest from Espressif's documentation. Behavior can differ by board revision, bridge chip and operating system. Once the connection works, ",[24,480,482],{"href":481},"\u002Fblog\u002Fesp-web-tools-flash-esp32-from-browser","flashing from the browser"," is the quickest way to put a project on the board, and ",[24,485,487],{"href":486},"\u002Fblog\u002Fwhat-is-the-esp32","what an ESP32 is"," gives the background on the chips mentioned here. If you're on a XIAO ESP32-S3 and your sketch needs spare pins, the ",[24,490,492],{"href":491},"\u002Fblog\u002Fxiao-esp32s3-pinout-safe-pins","XIAO ESP32-S3 pinout guide"," shows which ones are safe.",{"title":57,"searchDepth":495,"depth":495,"links":496},2,[497,498,499,500,506,507,508,509],{"id":39,"depth":495,"text":40},{"id":96,"depth":495,"text":97},{"id":139,"depth":495,"text":140},{"id":192,"depth":495,"text":193,"children":501},[502,504,505],{"id":225,"depth":503,"text":226},3,{"id":262,"depth":503,"text":263},{"id":291,"depth":503,"text":292},{"id":308,"depth":495,"text":309},{"id":391,"depth":495,"text":392},{"id":415,"depth":495,"text":416},{"id":471,"depth":495,"text":472},"troubleshooting","Troubleshooting","2026-11-14T00:00:00Z","Fix 'Failed to connect to ESP32: No serial data received' step by step: data cable, drivers, ports, download mode on S3, C3 and XIAO, and the ESP32-CAM-MB.","md",[516,519,522,525,528],{"question":517,"answer":518},"What does 'Failed to connect to ESP32: No serial data received' mean?","It means esptool opened the serial port but received no bytes back from the ESP32's ROM bootloader. Espressif's troubleshooting page says this usually points to a hardware problem: a charge-only cable, unconnected RX\u002FTX lines, a dead board, or a failed reset into download mode.",{"question":520,"answer":521},"How do I put an ESP32 into download mode manually?","Hold the BOOT button, which pulls GPIO0 low, press and release the EN (RESET) button, then release BOOT and start the upload. On a XIAO ESP32-S3, Seeed also documents holding BOOT while plugging in the USB cable, then releasing it.",{"question":523,"answer":524},"Why does my ESP32-S3 or ESP32-C3 stop showing up as a serial port?","These chips use their built-in USB Serial\u002FJTAG controller. If the running firmware reconfigures or disables the USB pins, the device disappears from the computer. Put the chip into download mode by pulling its boot pin low (GPIO0 on the ESP32-S3) and resetting, then flash a working sketch.",{"question":526,"answer":527},"Can a bad USB cable cause this error?","Yes. A charge-only cable powers the board but carries no data, so no port appears and esptool reports no serial data. A poor cable can also corrupt data mid-flash and cause 'Invalid head of packet'. Swap in a cable you know carries data, and plug it straight into the computer.",{"question":529,"answer":530},"Does lowering the baud rate fix the ESP32 failed to connect error?","Sometimes. Espressif suggests a very slow rate such as 9600 baud to rule out a baud-rate problem, and a lower rate also helps when flashing fails partway or with 'Invalid head of packet'. It will not help if the chip never enters download mode, so check the cable and BOOT sequence first.","\u002Fimages\u002Fblog\u002Fesp32-failed-to-connect-no-serial-data-received.jpg","A maker with a puzzled look at a laptop showing a red 'Failed to connect' message while pressing the BOOT button on a small ESP32 board plugged in by USB.","en",{},true,"\u002Fblog\u002Fesp32-failed-to-connect-no-serial-data-received",{"title":5,"description":513},{"loc":536},"blog\u002Fesp32-failed-to-connect-no-serial-data-received","The error means esptool got no reply from the chip's ROM bootloader. Check the data cable and port first, then force download mode by hand: hold BOOT (GPIO0), tap RESET, and retry.",[542,511,543,226,544],"ESP32","Firmware","ESP32-CAM","Qezi_IXjprxcEAVUWt4re0VTc8w5RBkPFR8Nw6WqU78",[547,555,561,567],{"title":548,"description":549,"image":550,"categoryText":511,"categorySlug":510,"tags":551,"path":554},"ESP32 .local Not Working on Android: mDNS Explained","Why an ESP32 .local hostname like gizmo-ticker.local fails on Android or a router, how to find the cause, and how to use the IP address with a reservation.","\u002Fimages\u002Fblog\u002Fesp32-mdns-local-hostname-not-working.jpg",[542,552,511,543,553],"Wi-Fi","OpenGizmo","\u002Fblog\u002Fesp32-mdns-local-hostname-not-working",{"title":556,"description":557,"image":558,"categoryText":511,"categorySlug":510,"tags":559,"path":410},"ESP32 Brownout Detector Was Triggered: Causes and Fixes","Why the ESP32 resets with 'Brownout detector was triggered', how to find the weak link in the power path, and the fixes that work on dev boards and ESP32-CAM.","\u002Fimages\u002Fblog\u002Fesp32-brownout-detector-was-triggered.jpg",[542,544,560,511,552],"Power",{"title":562,"description":563,"image":564,"categoryText":511,"categorySlug":510,"tags":565,"path":566},"ESP32 Captive Portal Not Working? Fix the Wi-Fi Popup","Why the ESP32 captive portal popup doesn't open on Android, iPhone or Windows: DNS, probe URLs, 302 redirects and the checks that fix it, with working code.","\u002Fimages\u002Fblog\u002Fesp32-captive-portal-not-working-fix.jpg",[542,552,511,543,553],"\u002Fblog\u002Fesp32-captive-portal-not-working-fix",{"title":568,"description":569,"image":570,"categoryText":511,"categorySlug":510,"tags":571,"path":574},"ESP32 I2C LCD 16x2 Not Working: Address, 5 V, Contrast","ESP32 I2C LCD 16x2 blank or showing blocks? Scan for the 0x27 or 0x3F address, turn the contrast trimmer, and check the 5 V backpack on 3.3 V pins.","\u002Fimages\u002Fblog\u002Fesp32-lcd-i2c-not-working-fix.jpg",[542,572,226,573,511,553],"Displays","Electronics","\u002Fblog\u002Fesp32-lcd-i2c-not-working-fix",[576,582,588],{"name":577,"slug":578,"path":579,"count":580,"image":581},"Comparisons","comparisons","\u002Fblog\u002Fcategories\u002Fcomparisons",8,"\u002Fimages\u002Fblog\u002Fesp32-ota-update-methods-compared.jpg",{"name":583,"slug":584,"path":585,"count":586,"image":587},"Guides","guides","\u002Fblog\u002Fcategories\u002Fguides",11,"\u002Fimages\u002Fblog\u002Fcoingecko-api-esp32-rate-limits.jpg",{"name":589,"slug":590,"path":591,"count":592,"image":593},"Builds","builds","\u002Fblog\u002Fcategories\u002Fbuilds",6,"\u002Fimages\u002Fblog\u002F3d-printed-esp32-enclosure-design-guide.jpg",1795018236264]