Page 1 of 1

Trying to use EspRFTestTool_v3.6_Manual with ESP32-C3-MINI-1U-N4

Posted: Mon Jul 29, 2024 10:28 pm
by jlmiramo
We're an OEM and we're trying to perform BLE DTM testing on the :
ESP32-C3-MINI-1U-N4

Note that we've attached screenshots in an attached PDF file.

We're using:
EspRFTestTool_v3.6_Manual

We're trying to load these files:

\\sharebear\sq\sqwork\technical\reference\Datasheets\Espressif\RF-Test\ESP_RF_Test_EN_0\ESP_RF_Test_EN\EspRFTestTool_v3.6_Manual\Bin\BQB_BIN\ESP32-C3\ESP32-C3_DTM_HCI_20220915
- bootloader.bin @ 0x1000
- partition-table.bin @ 0x8000
- ssc.bin @ 0x10000

We've tried using both the RF Test Tool download page and also the "EPS32C3 FLASH DOWNLOAD TOOL V3.97"

The result after flashing is 'FINISHED' not "SUCCESS"...(?)

What we see after rebooting on the TXDO / RXDO pins is this:
----------------------------------------------------------------
ESP-ROM:esp32c3-api1-20210207
Build:Feb 7 2021
rst:0x7 (TG0WDT_SYS_RST),boot:0xc (SPI_FAST_FLASH_BOOT)
Saved PC:0x40047ed2
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fcd5820,len:0x11c0
load:0x00000000,len:0x3b305b1b
Invalid image block, can't boot.
ets_main.c 333
----------------------------------------------------------------

Is there a newer or older version of EspRFTestTool we should use/try?

Some people claim to have had success with v2.8, but I don't know if that works with the -C3 (?)

Where can we find the v2.8 version to try?

Or what do you recommend?

Thanks!
RF-Test-Tool-Flashing-Issue.drawio.pdf
Screen Shots
(264.3 KiB) Downloaded 64 times

Re: Trying to use EspRFTestTool_v3.6_Manual with ESP32-C3-MINI-1U-N4

Posted: Tue Jul 30, 2024 2:50 am
by ESP_Sprite
Note you can also try emailing support at sales@espressif.com, they have more experience with RF test stuff.

Re: Trying to use EspRFTestTool_v3.6_Manual with ESP32-C3-MINI-1U-N4

Posted: Tue Jul 30, 2024 9:17 pm
by jlmiramo
We received a very helpful replay from the Espressif RF Support group.

Basically, for the ESP32-C3 you should burnt the bootloader.bin @ 0x0 not 0x1000 as shown in the documentation

Problem solved!

Thanks very much!