ESP32 goes on a continuous printing loop after firmware for ESP32 is uploaded.

[surajkumarpandey]

Hi all, I was trying to upload the micropython TFlite firmware provided for ESP32 provided in the link "https://github.com/mocleiri/tensorflow-micropython-examples/actions/runs/2968453830" (first one named as "microlite-esp32-firmware") but after uploading it, my thonny terminal goes into a non-stop loop printing following statements:

**"rst:0x10 (RTCWDT_RTC_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:0x3f400020,len:267148 ets Jun 8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_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:0x3f400020,len:267148 ets Jun 8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_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:0x3f400020,len:267148 ets Jun 8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_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:0x3f400020,len:267148 ets Jun 8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_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:0x3f400020,len:267148 ets Jun 8 2016 00:22:57"**

I cannot save any file as it says 'Device is busy' nor can I make any other changes. Please aide over the matter.

[uraich]

Which esp32 board are you using? Does it have PSRAM?

[surajkumarpandey]

Thank you for responding. I have tried it with ESP EYE (8MB PSRAM) and ESP32-WROOM-32.

[uraich]

Ok, Can you try to download and flash: firmware.bin and tell me if that works any better?

[surajkumarpandey]

Thank you for the file but uploading this also yields a continuous loop with following statements:

"ELF file SHA256: fc359ed41e6490b2

Rebooting... ets Jun 8 2016 00:22:57

rst:0xc (SW_CPU_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:0x3fff0030,len:4344 load:0x40078000,len:13824 load:0x40080400,len:3340 entry 0x40080618 E (751) psram: PSRAM ID read error: 0xffffffff E (751) cpu_start: Failed to init external RAM!

abort() was called at PC 0x400813c8 on core 0

Backtrace:0x40081ef1:0x3ffe3bb00x4008f679:0x3ffe3bd0 0x40095321:0x3ffe3bf0 0x400813c8:0x3ffe3c60 0x4007935e:0x3ffe3c90 |<-CORRUPTED

"

However, the original micropython firmware available at "https://micropython.org/download/esp32/" works fine and does not go into loop. I am able to program basic python with that.

[uraich]

This looks to me that MicroPython cannot access the PSRAM. How do you build standard MicroPython. Do you specify a BOARD? What happens if you build standard MicroPython with make BOARD=GENERIC_SPIRAM ?

[surajkumarpandey]

No. I just use the update firmware option in Thonny to burn it as a new firmware.

[surajkumarpandey]

Do we need to upload the bootloader and partioion-table together with the "micropython.bin" given. I am first uploading just the micropython file. Could that be an issue?

[uraich]

No. The boot loader is already included in firmware.bin In fact I am using an esp32-cam (much cheaper and less powerful than your board) Yours uses an esp32s3 chip while mine uses a standard esp32. As far as I can see, there is MICROLITE_S3_SPIRAM in tflite-micropython, but that does not include the camera driver. Therefore tflte-micropython should be compiled for the esp32s3 and the camera driver must be added. Since I don't have such a board, I can try to build an esp32s3 version but you would not be able ti use the camera.

[surajkumarpandey]

I am for now experimenting with ESP32 WROOM which is a generic ESP32 chip without camera. I have kept ESP-EYE aside for now. But even on ESP32 WROOM the issue persists, which has the generic ESP32 chip.

[uraich]

Does this board have PSRAM?

[uraich]

Hmmm, I saw that there are different esp32-eye versions. There is the one with the esp32s3 and an older version with the esp32. Which one do you have?

[surajkumarpandey]

No it doesn't have PSRAM.

[surajkumarpandey]

My ESP-EYE has esp32 chip only.

[surajkumarpandey]

May I know how you uploaded the firmware?

[uraich]

The image needs PSRAM. I added two shell scripts to the github repository scripts One of them erases the esp32 flash, the second one flashes firmware.bin. After flashing I access the esp32 with minicom:

[surajkumarpandey]

Ok. It seems you did not use the partition-table and the bootloader as well. i will try to look out for more options. Still, thank you for your responses!

[uraich]

I am using the makeimg.py from the esp32 micropython port to build firmware.bin from micropython.bin and that includes partition table and bootloader into the final firmware image. I do not flash micropython.bin but firmware.bin which is generated by makeimg.py. On my esp32-cam this works without any problems. Normally I just compile the image with idf.py build and then flash it with idf.py flash. However, this you can only do when you build the image yourself. In order to produce an image that can just be downloaded and flashed, I used the above procedure and in fact I tried it on my esp32-cam as you can see above.

[surajkumarpandey]

It seems you are using ESP-IDF IDE.

[surajkumarpandey]

It worked in windows so I am switching to windows for now. Thanks for the discussion!

[uraich]

Well, micropython uses ESP-IDF. Normally it is just hidden in the makefile.. Looks like it was a problem when flashing then. Which system did you use before?

[surajkumarpandey]

Ok. I was using Ubuntu before. in windows I directly used the command given for uploading the firmware.

[uraich]

I am using Ubuntu 22.04 myself. Did you try the shell scripts I gave you on Ubuntu? These should work, if you have a fairly new version of esp_tool installed. Good luck with your further explorations.

[surajkumarpandey]

Yes I flashed the esp32 using those scripts in Ubuntu. Unfortunately I ran into the same loop as earlier. Thank you for the discussion.

[surajkumarpandey]

Is there a documentation for the functions/objects used in the Hello_world example? I am trying to build a custom network that requires different configuration for running. For instance I wanted to know about the second parameter of "microlite.interpreter()" as to whose size is it and are callbacks optional for interpreter.

[mocleiri]

@surajkumarpandey can you post the command you used to flash the firmware?

The firmware zip is not directly flash able.

The instructions on the readme show from the unzipped file how to flash the various parts: https://github.com/mocleiri/tensorflow-micropython-examples#flash-from-windows

[uraich]

Hi Michael, I copied makeimg.py from the micropython sources to the boards directory of the board I am using (MICROLITE_SPIRAM_CAM) Then I created a simple shell script to call this

!/bin/sh

python3 makeimg.py \ build/sdkconfig \ build/bootloader/bootloader.bin \ build/partition_table/partition-table.bin \ build/micropython.bin \ build/firmware.bin \ build/micropython.uf2

This creates firmware.bin which you can easily flash

[mocleiri]

@uraich thanks.

I'll incorporate that into the automatic builds to simplify flashing.

[surajkumarpandey]

@mocleiri Thank you for asking. I flashed the firmware directly using thonny interpreter's 'update firmware functionality' in ubuntu (as I could not find any other available option). However, as I mentioned, I moved to windows later where it could be uploaded. But I wanted some help over the documentation of the functions used to be able to run a custom model.

[mocleiri]

@surajkumarpandey thanks.

I want to use this issue for changing the ESP32 builds to build a unified image suitable for direct flashing.

I'll move your other question about the API over to another issue where hopefully we can get you setup and improve the documentation for others in the future.

[surajkumarpandey]

@mocleiri Sure! Thank you.

[mocleiri]

Closing as the changes to create a single firmware.bin file using the upstream makeimg.py script has been merged into the main branch. Merge commit is here: 2df65a06c2e27a38b3636eef497a4cdd04d7f964