I guess I need a little clarification on what the problem is. Are you saying you have a MAC address that is being misidentified by the online tool? Or are you saying you need more information just "Espressif"? Or something else?

I don't think all that manual setup is necessary. The build process creates the components subfolder. You just need to run the `idf.py add-dependency` tool and it creates the necessary yml in your source folder. The build process takes care of the rest. (A full clean beforehand is recommended.)

Perhaps this? Search for manufacturer by MAC address.

Generally, we're moving things to the component registry because it allows us to decouple the code from ESP-IDF releases. It means those components and ESP-IDF can be developed and released individually, meaning that a release of either doesn't have to wait until issues in the other are resolved. M...

I'm not sure why it was moved. The documentation doesn't say. It tripped me up when I first changed to V5.0 from V4.4 as it wasn't noted in the 4.4 to 5.0 migration documentation. You don't need to manually edit the yml component configuration file. The documentation for the component gives you the ...

Have you looked at the ESP-IDF I2C example programs, and checked the documentation for your specific device for I2C address and commands, etc? It's not clear what specific kind of help you're looking for.

stnmane wrote: ↑

Tue Jan 24, 2023 12:35 am

The things that were altered was data inside a buffer that was transmitted through SPI.

Is that static data in a fixed buffer, or do you mean the code is writing different data (or a different amount of data) to a buffer?

In response to ESP_Sprite, both of the above. My OS is windows 10, I have not installed an IDE (do I need to?" No, you don't have to install an IDE. I go to this page https://dl.espressif.com/dl/esp-idf/ and attempt to install using this package "Universal Online Installer 2.18, Windows 10, 11, Siz...

The semaphores are implemented an working, I just omit those pieces of code just to keep it clean. So they don't allocate any dynamic resources? The solution you say is to add a 'free(write_buf);' in the partition_linux.c function? I'm not quite saying that. What I noticed is that there is one erro...

You have comments that give/take a semaphore but no code that does anything with semaphores. Did you just omit that code in your post, or is there really no code there that is being executed in your memory leak scenario? Is `write_value_to_flash` the only thing you are commenting out when you have t...