ESP RF Test Tool download fails.

[jesper]

I'm trying to prepare some boards for FCC/CE testing, using the RF Test SDK from Espressif.
But I have issues downloading code to the boards. It fails with "Serial data stream stopped: Possible serial noise or corruption."
This is boards that I have programmed hundreds of times with the Flash Download Tool or directly from the ESP plugin in Eclipse.
Without EVER having a similar fault.
The odd thing is that its only download to Flash that fails. Download to RAM, or the "Erase" function works just fine.
Also, trying to use the Flash Download Tool to download the RF Test binary to the specified address 0x1000, result in a printout of "mmu set" messages or nothing at all. It varies between different board designs.
All boards use the ESP32-U4WHD.
I have tried 3 different boards of very different designs and the results a similar. The RF Tools just don't download correctly.

And, I have of course tried various download speeds from 9600 to 921600. Same, same.
Normally, I download at 921600 with Flash Download tool or from Eclipse. No problem.

What the hey is going on? Why these errors when downloading to flash?
And why does the code not run when using the Flash Download Tool?

ESPRFTestTool Failed.png (237.53 KiB) Viewed 2024 times

DownloadTool Failed.png (177.36 KiB) Viewed 2024 times

DownloadTool Ok to RAM.png (146.08 KiB) Viewed 2024 times

[jesper]

Two more attachments, showing the Download Tool downloading, but resulting binary NOT working as intended.

Download with Flashtool.png (169.65 KiB) Viewed 2023 times

After download with FlashTool.png (120.2 KiB) Viewed 2023 times

[micteus127]

I have exactly the same error with the same chip. Is there already a solution to the problem?

[vsousa]

Hi. I'm facing the same problem. I'm using a ESP32-MINI-1 with the dev kit ESP32-DevKitM-1, V1.
I've tried EspRFTestTool v2.8, V3.6 and now EspRFTestTool_v4.6_Manual with the firmware ESP32_RFTest_V191_482eb73_20230724.bin.

All of then has the same fault, as mentioned above.

DEBUG:Flash
DEBUG:['C:/Users/EspRFTestTool_v4.6_Manual/Bin/RF_TEST_BIN/ESP32_RFTest_V191_482eb73_20230724.bin']
ESP32
Connecting....
DEBUG:Chip is ESP32-U4WDH (revision v3.0)
DEBUG:Features: WiFi, BT, Dual Core, 240MHz, Embedded Flash, VRef calibration in efuse, Coding Scheme None
DEBUG:Crystal is 40MHz
MAC: 54:43:b2:51:86:4c
DEBUG:MAC:54:43:b2:51:86:4c
DEBUG:Load flash...
DEBUG:Erasing flash...
DEBUG:Enabling default SPI flash mode...
Flash params set to 0x0200
Compressed 201808 bytes to 131960...
DEBUG:Serial data stream stopped: Possible serial noise or corruption.
WARNING:Load bin fail...

And the ESP keeps sending the status below:
...
Receive <-
Receive <- rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
Receive <- configsip: 188777542, SPIWP:0x00
Receive <- clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
Receive <- mode:QIO, clock div:2
Receive <- load:0x40080000,len:176052
Receive <- 1150 mmu set 00010000, pos 00010000
Receive <- 1150 mmu set 00020000, pos 00020000
Receive <- load:0xffffffff,len:-1
Receive <- ets Jul 29 2019 12:21:46
...

What am I doing wrong? Is there a solution?

Thanks.

[vsousa]

I found a way to make this work.

The Espressif tools keep writing mode = QIO, even if I select DIO.
I had to write the firmware by command line, using esptool.py and enforcing the flash mode "--flash_mode dio".

Now, it is working.