Hi WiFive - no, this isn't from the first run. In the first run, I programmed values into BLK3. But on subsequent runs, I'm getting this: E (109) system_api: Base MAC address from BLK3 of EFUSE version error, version = 0 when I call esp_efuse_mac_get_custom(). According to the docs, that suggests th...

BTT...anyone have any suggestions on this?

Thanks...

Hi all - I recently started working with the efuse handler. I need to store a custom MAC address in BLK3, so I wrote the following routine: esp_err_t Flash::initBaseMacAddress() { char macAddrAscii[18] = { NULL_CHAR }; esp_err_t rc = ESP_OK; ESP_FUSE3 fuse3; // see whether efuse has been programmed ...

Hi all - I've been asked to look into adding syslog functionality to our product. Part of the requirement is storing the logs on the ESP32 for some period of time (probably 24 hours). Does anyone have an idea on how best to do this? Storage space is probably going to be an issue, so using the NVS li...

Hi Shivani - Thanks for the patch; it looks like it's working properly now. Which release will this patch appear in? I'd like to propose an enhancement to this tool. We're planning on using it to create nvs files that contain factory defaults for the units we manufacture. It would be very helpful if...

Hi Shivani - If I understand you, the 2nd entry in my values file was missing a bunch of commas. So, I added them. Here are my two files now (this time I'm posting the complete files to avoid confusion): config.csv: CD_FACTORY,namespace, SERIAL_NBR,data,string MAC_ADDR,data,string NVS_LABEL,data,str...

Hi shivanit - The term "PST8PDT,M3.2.0/2,M11.1.0" is indeed supposed to be one item; that's the reason for the double quotes. I want the last line to be considered a new line. If I understand the docs, by using the REPEAT tag in my config file, I should only need two fields in my values file. But th...

Hi Roland - Thanks for the reply. I'm not sure whether it's not working, or if I'm doing something wrong. I'm trying to use the "REPEAT" tag, like so: config.csv: CD_FACTORY,namespace, SERIAL_NBR,data,string MAC_ADDR,data,string NVS_LABEL,data,string,REPEAT DEVICE_NAME,data,string,REPEAT VERSION,dat...

Hi -

Any updates on this?

It's been running 28 hours now without a problem. I'm not claiming that I don't have a heap problem somewhere, but the lesson I'm taking from this is to not permit the possible overlapping of calls into the I2C library.

Thanks to all who looked at this with me.