Search found 306 matches

by mzimmers
Fri May 17, 2019 10:01 pm
Forum: General Discussion
Topic: questions about manufacturing utility
Replies: 10
Views: 1040

Re: questions about manufacturing utility

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...
by mzimmers
Thu May 16, 2019 3:55 pm
Forum: General Discussion
Topic: questions about manufacturing utility
Replies: 10
Views: 1040

Re: questions about manufacturing utility

Hi -

Any updates on this?
by mzimmers
Mon Apr 22, 2019 2:47 pm
Forum: ESP32 IDF
Topic: (resolved) I2C call panicking system
Replies: 29
Views: 1132

Re: I2C call panicking system

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.
by mzimmers
Fri Apr 19, 2019 8:41 pm
Forum: ESP32 IDF
Topic: (resolved) I2C call panicking system
Replies: 29
Views: 1132

Re: I2C call panicking system

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...
by mzimmers
Fri Apr 19, 2019 4:45 pm
Forum: ESP32 IDF
Topic: (resolved) I2C call panicking system
Replies: 29
Views: 1132

Re: I2C call panicking system

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...
by mzimmers
Thu Apr 18, 2019 5:39 pm
Forum: ESP32 IDF
Topic: (resolved) I2C call panicking system
Replies: 29
Views: 1132

Re: I2C call panicking system

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.
by mzimmers
Thu Apr 18, 2019 4:44 pm
Forum: ESP32 IDF
Topic: (resolved) I2C call panicking system
Replies: 29
Views: 1132

Re: I2C call panicking system

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...
by mzimmers
Thu Apr 18, 2019 2:54 pm
Forum: ESP32 IDF
Topic: (resolved) I2C call panicking system
Replies: 29
Views: 1132

Re: I2C call panicking system

Also, just wanted to make sure that the function was expecting the address of a 16 bit variable instead of an int. Which function? Here's the complete code for the function that reads the registers of the external device via I2C: esp_err_t Max77818::readReg(uint8_t devAddr, uint8_t regAddr, uint16_...
by mzimmers
Thu Apr 18, 2019 2:44 pm
Forum: ESP32 IDF
Topic: (resolved) I2C call panicking system
Replies: 29
Views: 1132

Re: I2C call panicking system

Hi - yes I did: the results never moved: I (619406) memreport: memReport(): there are 114124 MALLOC_CAP_8BIT bytes free. I (619406) memreport: memReport(): there are 163988 MALLOC_CAP_32BIT bytes free. I (619406) memreport: memReport(): there are 163988 MALLOC_CAP_INTERNAL bytes free. I (619416) mem...
by mzimmers
Thu Apr 18, 2019 2:34 pm
Forum: ESP32 IDF
Topic: (resolved) I2C call panicking system
Replies: 29
Views: 1132

Re: I2C call panicking system

I left this running overnight...it's definitely more reliable than it was, but I still get an occasional error like this: E (2085053) i2c: i2c command link malloc error abort() was called at PC 0x4015c4ab on core 1 I make a series of calls to the i2c library every half second, and according to the t...

Go to advanced search