MicroPython
Replies: 10 comments 11 replies
-
|
Curious where did you get: Does this tiny board have the transistor pair and a boot button? Are you using rshell on a Linux platform or an IDE? |
Beta Was this translation helpful? Give feedback.
-
|
Hmm, I thought unicore would be for the new RISC-based variants. I am using the D0WDQ6 but rev 1 chips. Which rev are yours?
|
Beta Was this translation helpful? Give feedback.
-
|
If I found the correct doc, the one of the first that Express has made for wroom and is Now not recommended for New Designs, so I guess That is rev 0 About unicore I thought that would be the version for single core variants, the chips which start with S, but I may be mistaken |
Beta Was this translation helpful? Give feedback.
-
|
I take it back, I have rev.1. esptool says that when connecting (didn't notice before):
even if it cites a different chip... I am a little puzzled here |
Beta Was this translation helpful? Give feedback.
-
|
So you can try the basic dual core firmware. Using the wrong firmware does not damage anything, since the boot loader is in ROM. |
Beta Was this translation helpful? Give feedback.
-
|
we replied at the same time ;) |
Beta Was this translation helpful? Give feedback.
-
|
The picture is good. I see two transistors, and there is output after booting, so the boot logic is there and works. But the ESP32-WROOM is AFAIK the standard two core ESP32. So the basic firmware, should work, e.g. https://micropython.org/resources/firmware/esp32-20230310-unstable-v1.19.1-962-g4376c969f.bin Edit: @davefes There are single core variants of the ESP32, but rarely used. And the RISC version is the ESP32-C3. |
Beta Was this translation helpful? Give feedback.
-
|
No luck, still bootloop
|
Beta Was this translation helpful? Give feedback.
-
|
Was not aware of single core variants of the ESP32.
|
Beta Was this translation helpful? Give feedback.
-
|
I would try now different flash modes. That was required for ESP8266 and I never heard that it was required for an ESP32, but .... |
Beta Was this translation helpful? Give feedback.
-
|
I hate the layout of discussions. Answers pop up at different places. |
Beta Was this translation helpful? Give feedback.
-
|
Let's try to go in sequence. (I mean with the order of the replies) flash modes: I am not sure if I understand you correctly. As I tried verify and it did work, I assumed flashing is ok, is this correct? I guess we can always go back right? |
Beta Was this translation helpful? Give feedback.
-
import network
ap = network.WLAN(network.AP_IF)All my boards I put a 1000uF cap on the 3V3. If the WiFi is really trying to boot-up at this point you can get "dips" on the 3V3 line. |
Beta Was this translation helpful? Give feedback.
-
ok, I'll try that later at work |
Beta Was this translation helpful? Give feedback.
-
|
There are four flash modes. You tried already DIO, so the next would be DOUT, then QIO and QOUT. The the other options are --flash_freq. AFAIK, the default is 80Mhz. You can try 40Mhz. |
Beta Was this translation helpful? Give feedback.
-
I have one cheap ESP32 board purchased recently to check the error with a 5x5 mm ESP32. I got the wrong one, but that required a capacitor between EN and GND, when starting WiFi. But it booted fine. |
Beta Was this translation helpful? Give feedback.
-
|
Summary of my attempts:
If I will find the time tomorrow I will try to monitor the power line with an oscilloscope and see if I detect any glitches. Let me paste the
|
Beta Was this translation helpful? Give feedback.
-
|
I always put a 1uF from EN to ground. Also, I don't know what your wifi connect script looks like. I would suggest trying this example: I haven't used idf-monitor so maybe watch things bootup from rshell. |
Beta Was this translation helpful? Give feedback.
-
|
I registered just to say I was able to fix by selecting DIO. Default was QIO. |
Beta Was this translation helpful? Give feedback.
-
|
I may be way off course here but I am able to get mine (v3 not v1) to work without any mods. esptool.py erase_flash esptool.py write_flash 0x1000 esp32-20230426-v1.20.0.bin Leaving... then: then using ESP MPY-JAMA ide no errors Hope this helps someone |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all,
I have some previous experience with ESP32 and python, but I am pretty new to micropython. So I'd like to double check that I am running the correct firmware first.
I have a cheap board integrating ESP32-WROOM-32 (there is a XXSR69 code on the module, if this helps), which as far as I understand integrates chip ESP32-D0WDQ6.
As this is a dual core chip I first tried downloading the ESP32 port with this command
esptool.py --chip esp32 --port /dev/ttyUSB0 write_flash -z 0x1000 ~/shared/esp32-20220618-v1.19.1.binThis results in a bootloop
The 'CORRUPTED' message suggest some flashing issue, however
esptool verify_flashreturnsSo I assumed this is not the correct FW and went for the UNICORE version.
Loading
esptool.py --chip esp32 --port /dev/ttyUSB0 write_flash -z 0x1000 ~/shared/esp32-unicore-20230313-unstable-v1.19.1-966-g05bb26010.binseems to work, I can connect with a terminal and I was even able to connect jupyter notebook and upload files with ampy.However I get a guru meditation if I try to configure wifi with
import networkap = network.WLAN(network.AP_IF)What am I doing wrong?
NOTE I found some notes about adding a cap between EN and GND, but as far as I understand (also from previous experience) this should be only related to instability in switching to the bootloader. I am not having download errors, just runtime, so I assume this is not the problem.
Beta Was this translation helpful? Give feedback.
All reactions