eFuse burned

User avatar
urbanze
Posts: 295
Joined: Sat Jun 10, 2017 9:55 pm
Location: Brazil

eFuse burned

Postby urbanze » Fri Dec 15, 2017 8:36 pm

I was testing FLASH TOOL and when I clicked start (to get the information from the chip), it appeared on the console that the "CONSOLE_DEBUG_DISABLE eFuse" was burned.

I went to the Datasheet and apparently it does not seem to be anything serious, just that it will not drop LOG's from the bootROM. What can this fuse, now burned, possibly influence my plate? What is it for? And what is this "bootROM" for?

eFuse CONSOLE_DEBUG_DISABLE: disables serial output from the BootROM when set 1.
Image

WiFive
Posts: 3529
Joined: Tue Dec 01, 2015 7:35 am

Re: eFuse burned

Postby WiFive » Fri Dec 15, 2017 8:51 pm

It disable the rom basic console. No effect on firmware.

User avatar
urbanze
Posts: 295
Joined: Sat Jun 10, 2017 9:55 pm
Location: Brazil

Re: eFuse burned

Postby urbanze » Fri Dec 15, 2017 9:22 pm

WiFive wrote:It disable the rom basic console. No effect on firmware.
Where can I find more information about this bootrom? In the Datasheet there are not many things.

Can I use all features of esp32 yet? Even secure / flash boot?

ESP_Sprite
Posts: 9016
Joined: Thu Nov 26, 2015 4:08 am

Re: eFuse burned

Postby ESP_Sprite » Sat Dec 16, 2017 3:18 am

Yes. The ESP32 has a feature that when it doesn't see any flash, it drops you into a Basic console. We had some issues with it interrupting customers boot sequences, so I think nowadays we disable it in the ATE process. It was half an internal debugging tool, half an easter egg anyway, so it won't affect your ESP32 experience in any way.

Who is online

Users browsing this forum: Baidu [Spider] and 117 guests