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.

Well, I certainly wouldn't claim that I don't any heap bugs in my code, but...since I made my code change, it's run flawlessly for almost 4 hours, which is 2 orders of magnitude better than its original behavior, and 1 order of magnitude better than when I slowed down my I2C access to .5 second inte...

That's true. I've seen a few flavors of strange behavior: - the occasional i2c malloc error - kernel panics (traceable into the i2c library) - heap poisoning (traceable into the i2c library) I did find a possible flaw in my program: the higher level functions using ReadReg were called from two tasks...

How so? I use queues for inter-task communication. But my structures are small, and every event loop has a wait at the end. Hard to see how I'd be overconsuming resources with these, especially given how much heap I seem to have available.

Essentially, yes. The program does a few other things (looks at queues for entries), but when the device is left alone, as it was in this case, not much else is really happening. I could try regressing to 3.1.3, though I remember trying that once, and it was a pretty big hassle. And as I recall, I w...