Henrik,

See https://github.com/espressif/esptool/wiki/espefuse -- you can try the dump command and send the results to Espressif. If your ESP32 really lost its efuses,
I think that's a warranty issue.

I ran the dump. It did not report CRC error, nor all1’s or 0’s. Is there any reason not to share the output from the dump command publicly?

The CRC check is done on the data level. The dump should not contain sensible data, but unless Mark can read it (?) there is no reason to post it here. Espressif should check it and possibly tell you what to do.

I am guessing the current rebooting issue could be an issue with my build. It is my first OVMS build, based on sources pulled Aug 4, and I may have done something wrong, have the wrong version of some tool installed, or something may have changed in the repos since the developer guide was last tested by someone.

Can I download bootloader.bin, ovms3.bin and partitions.bin from somewhere, and flash those instead of my build?

We normally only publish ovms3.bin, I created a directory with all three files for you:
https://dexters-web.de/firmware/henrik/

But I doubt that's the reason.

Henriks-MBP:OVMS.V3 henrik$ make print_flash_cmd

--flash_mode dio --flash_freq 40m --flash_size detect 0x1000 bootloader/bootloader.bin 0x10000 ovms3.bin 0x8000 partitions.bin

Is “make flash” always supposed to bring the device to a functioning state, when configured and built as described in the developer config (i.e. by cp support/sdkconfig.default.hw31 sdkconfig and then make menuconfig)?

Yes.

I seem to get errors when connecting to the device, e.g. when flashing:

Flashing binaries to serial port /dev/tty.SLAB_USBtoUART (app at offset 0x10000 )...
esptool.py v2.3.1
…
File "/Library/Python/2.7/site-packages/serial/serialposix.py", line 438, in _reconfigure_port
[iflag, oflag, cflag, lflag, ispeed, ospeed, cc])

termios.error: (22, 'Invalid argument')

make: *** [flash] Error 1

Henriks-MBP:OVMS.V3 henrik$ make flash

Flashing binaries to serial port /dev/tty.SLAB_USBtoUART (app at offset 0x10000 )...

esptool.py v2.3.1

Connecting........_____....._____....._____....._____....._____....._____....._____....._____....._____....._____

A fatal error occurred: Failed to connect to ESP32: Timed out waiting for packet header

make: *** [flash] Error 2

Henriks-MBP:OVMS.V3 henrik$

Could all of this conceivably be caused by “bad” USB hardware? I connect the device via a cheap Hama device for converting my thunderbolt port to standard USB.

Yes, but maybe you can solve that by using another speed setting for the port? (see "make menuconfig")

However, this cannot affect the efuse data.

Regards,
Michael

Best regards,

Henrik

--

Venlig hilsen / best regards
Henrik R. Scheel

Spjeldager Consult ApS
Spjeldager 9
DK-2630 Taastrup
CVR: 34491399
T: +45 2720 9828
http://www.spjeldager.dk/
_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev

-- 
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26