[SOLVED] WiPy firmware to a standard WROOM-32?
-
@BetterAuto Alternative boards are "sparkfun esp32 thing", "Huzzah32" or "wemos lolin32". While the first one is a custom layout, the Wemos and Huzzah devices just use the wroom-32 as module, and as always, the Wemos device is unbeatable in price. But it looks as if the first batch was sold out immediately. I tried the sparkfun device, and waiting for the wemos device to be delivered. That may take a while with the slow boat from china.
-
@jmarcelino The Pycom board is powered from 3.3V. The breadboard power supply is an MB102 variant like this which claims to do 700mA. I'm using a bare WROOM-32 which uses even less than the Pycom board so if anything the Pycom should not work. I suspect a dead chip and will be able to confirm that tomorrow with the arrival of the Espressif-built dev board.
@robert-hh I started to buy a Sparkfun but then saw it does not have a WROOM-32 on it as you noted. Went direct to the manufacturer for their dev board. If that doesn't work then I don't know what to do :-D
-
@BetterAuto I see that the Wemos Lolin32 is available at aliexpress:
https://www.aliexpress.com/item/WEMOS-LOLIN32-V1-0-0-wifi-bluetooth-board-based-ESP-32-4MB-FLASH/32808551116.html?spm=2114.01010208.3.2.DXyahW&ws_ab_test=searchweb0_0,searchweb201602_1_10152_10065_10151_10068_436_10136_10157_10137_10060_10138_10155_10062_10156_10154_10056_10055_10054_10059_100032_100033_100031_10099_10103_10102_10101_10096_10147_10052_10053_10050_10107_10142_10051_10084_10083_10080_10082_10081_10177_10110_10111_10112_10113_10114_10181_10180_10183_10182_10185_10184_10078_10079_10073_10186_10123,searchweb201603_2,ppcSwitch_5&btsid=f83eac71-efb8-450c-9b60-df678e0e9263&algo_expid=b986c6e2-8366-45d3-87e4-a86052471d35-0&algo_pvid=b986c6e2-8366-45d3-87e4-a86052471d35 -
Same error on the Espressif-built dev board. It flashes just fine but loops this on boot.
rst:0x10 (RTCWDT_RTC_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:QIO, clock div:2
load:0x3fff9010,len:8
load:0xffffffff,len:-1
ets Jun 8 2016 00:22:57rst:0x10 (RTCWDT_RTC_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:QIO, clock div:2
load:0x3fff9010,len:8
load:0xffffffff,len:-1
ets Jun 8 2016 00:22:57rst:0x10 (RTCWDT_RTC_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:QIO, clock div:2
load:0x3fff9010,len:8
load:0xffffffff,len:-1 -
A comment in the IRC chat is I should try flashing in DIO mode. Since the flasher tool does not include the binary firmware is there somewhere I can just download it?
-
@BetterAuto You can fimnd them here.
https://software.pycom.io/downloads/WiPy-1.6.13.b1.tar.gz
For the other versions, just change the version number in the link.
See also https://forum.pycom.io/topic/517/downgrading-firmware-advanced-users -
Thank you!
Found that I can do it with the standard firmware updater. I edited C:\Program Files (x86)\Pycom\Pycom Firmware Update\Upgrader\bin\updater.py, changed qio to dio.
-
Several pins are unusable on the ESP-WROOM-32. GPIO16, 7, 32, 33, 25, 26, 27, and 13.
Anyone know of a way to remap the pins? Probably have to recompile the firmware is my guess.
-
@BetterAuto
Change pins.csv https://github.com/pycom/pycom-micropython-sigfox/blob/master/esp32/boards/WIPY/pins.csv perhaps? -
-
Hi;
This thread is marked as solved, but there does not appear to be a solution ?
I have flashed the firmware to an esp32-wroom, however I get the RTCWDT_RTC_RESET reboot.
I have seen this before with the micropython port and the cause was related to the flash size, type and speed which is now included in the application (wipy) binary file.
If there is a solution, would someone mind sharing it as the esp-32 port looks like it is constrained by lack of resources and is moving extremely slowly.
Many Thanks
-
@crankshaft I'm the one who marked my own thread solved because except for the pinouts still needing to be modified, I can boot successfully on an ESP-WROOM-32 from Espressif. Both the individual module and on the Espressif breakout board. I had to modify the flasher program as stated above but that's what I needed to do. I didn't get the error you're getting, so I marked it as solved.
Sorry that I don't know the answer to your question, but perhaps someone else does. Perhaps try exactly the same modules I tried?
https://smile.amazon.com/gp/product/B01MU8LL47/ref=oh_aui_detailpage_o07_s00?ie=UTF8&psc=1
https://smile.amazon.com/gp/product/B01N0SB08Q/ref=oh_aui_detailpage_o05_s00?ie=UTF8&psc=1
-
@BetterAuto - thanks, can you elaborate on what you mean by modify the flasher ?
Is it possible you canalso let me know what you modified in the pins to save me re-inventing the wheel !
-
@BetterAuto - Thanks for the help, as this post has so many threads, I thought I would create a new one which shows the steps I took.
-
@BetterAuto Once you have the environment set up to build the firmware yourself, you can simply flash the firmware to any esp32 module with "make TARGET=WIPY flash". I tried that with the Wemos Lolin, which has an WROOM32-module, and and Sparkfun esp32 thing. Since these board have the logic implemented to switch GPIO0, you do not even have to care for strapping it to GND manually. The Huzzah esp32 should work the same way.
-
While Im waiting for Wipy 2.o modules.
Have tried to flash Wipy 2.0 firmware on new board from Wemos Lolin 32 Lite without success.
Has anyone else tried new Lolin 32 lite boards?
-
@easyrider I tried it and it fails. @damien's explanation: The Lolin32 Lite uses esp32 revision 1. The Pycom software decides by revision, whether the device has external SPI RAM, and this tries to use SPI-RAM on the LOLIN32 Lite. The ESP32 firmware of micropython.org (http://micropython.org/download/) or loboris' branch of it (https://github.com/loboris/MicroPython_ESP32_psRAM_LoBo/tree/master/MicroPython_BUILD/firmware/esp32) work both.
-
Thanks Robert.
Have uploaded 1.9.2 version using command line and esptool, individually bootloader then partitioner and then wipy firmware. With limited testing board boots ok and runs simple scripts.
Not sure if esp32 revision check is done by uploader.py for all firmware verions or only new 1.10 that supports external 4MB Ram and 8MB flash?
-
@easyrider The older revisions of the pycom firmware before 1.10.0 run fine on the Lolin 32 lite.
-
@easyrider The revision check is done at many places in the code. I managed to create a version of the 1.10.1b1 firmware for the LOLIN32 lite with a rough hack. I changed the function esp_get_revision() in system_api.c of the esp_idf to always return 0, so the code believes it runs on a revision 0 chip. That is not a clean way and maybe has other side effects.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login