Search found 21 matches
- Sun Dec 10, 2023 7:46 pm
- Forum: ESP-IDF
- Topic: LilyGo T-Eth-Lite problems
- Replies: 1
- Views: 3785
Re: LilyGo T-Eth-Lite problems
After digging into the RTL8201 PHY implementation it seems like the problem has to do with a wrong init setting in the example code. Original is says phy_config.phy_addr = CONFIG_EXAMPLE_ETH_PHY_ADDR; // 1 This 1 seems to be wrong, so I changed it to phy_config.phy_addr = ESP_ETH_PHY_ADDR_AUTO; // -...
- Sun Dec 10, 2023 3:39 pm
- Forum: ESP-IDF
- Topic: LilyGo T-Eth-Lite problems
- Replies: 1
- Views: 3785
LilyGo T-Eth-Lite problems
Hi, I try to get LilyGo T-Eth-Lite to work with ESP-IDF 4.2, I use the ethernet-example code. At first I got E (556) emac_esp32: emac_esp32_init(308): reset timeout E (556) esp_eth: esp_eth_driver_install(198): init mac failed Which was caused by wrong CONFIG_EXAMPLE_ETH_PHY_RST_GPIO So I checked al...
- Wed Apr 12, 2023 10:12 am
- Forum: ESP-IDF
- Topic: ESP32 WROVER reboots on heap_caps_calloc(MALLOC_CAP_IRAM_8BIT)
- Replies: 2
- Views: 1621
ESP32 WROVER reboots on heap_caps_calloc(MALLOC_CAP_IRAM_8BIT)
Hi,
My application requires IRAM memory, but when I use heap_caps_calloc(1, 784, MALLOC_CAP_IRAM_8BIT) it returns 0.
This is on a WROVER.
When using heap_caps_calloc(1, 784, MALLOC_CAP_INTERNAL | MALLOC_CAP_8BIT) I get a valid return pointer.
Why the differences, what am I missing?
My application requires IRAM memory, but when I use heap_caps_calloc(1, 784, MALLOC_CAP_IRAM_8BIT) it returns 0.
This is on a WROVER.
When using heap_caps_calloc(1, 784, MALLOC_CAP_INTERNAL | MALLOC_CAP_8BIT) I get a valid return pointer.
Why the differences, what am I missing?
- Wed Jun 02, 2021 8:59 am
- Forum: ESP-IDF
- Topic: Can I write directly to flash/partition without fatfs/wear lvl etc drivers?
- Replies: 11
- Views: 12606
Re: Can I write directly to flash/partition without fatfs/wear lvl etc drivers?
Ok I have an implementation of a circular partition running, really simplistic with a signature and a monotonic block id per logical block in the partition. Quick and very resilient against power breaks. Since my data chunks are just 8 bytes (bit stuffed values) and they fit very well in the logical...
- Wed May 26, 2021 9:05 am
- Forum: ESP-IDF
- Topic: Can I write directly to flash/partition without fatfs/wear lvl etc drivers?
- Replies: 11
- Views: 12606
Re: Can I write directly to flash/partition without fatfs/wear lvl etc drivers?
What algo did you use to write directly to the partition, do you maintain begin/end pointers?
regards, Jo
regards, Jo
- Tue May 25, 2021 8:51 pm
- Forum: ESP-IDF
- Topic: Can I write directly to flash/partition without fatfs/wear lvl etc drivers?
- Replies: 11
- Views: 12606
Re: Can I write directly to flash/partition without fatfs/wear lvl etc drivers?
Hi there, I am recently facing the same issues, with 4 files forming a circular logfile. the active logfile has it's name changed to unreadable chars at random times. This with FATFS+WL. (https://www.esp32.com/viewtopic.php?f=13&t=21091) After carefully inpecting code to make sure there are no 2 dif...
- Tue May 25, 2021 1:17 pm
- Forum: ESP-IDF
- Topic: Periodic FATFS corruption
- Replies: 6
- Views: 5154
Re: Periodic FATFS corruption
Thx for your thoughts. I am now trying with a changed algo that separate the logfile writes by 10 seconds and see if this improves it. Ultimately I consider going for raw partition handling, just writing sectors as they fill up with in memory caching, such that you incrementally write real data to a...
- Tue May 25, 2021 6:49 am
- Forum: ESP-IDF
- Topic: Periodic FATFS corruption
- Replies: 6
- Views: 5154
Re: Periodic FATFS corruption
Hi, I double checked and looked for all fopen/fwrite/fclose occurences in my app and there are 2 locations found: - the httpsd (http server for reporting) - the pwrmtrd (power meter daemon for collecting) Both httpsd and pwrmtrd are running in the same worker thread, which is 1 thread with a queue t...
- Mon May 24, 2021 10:16 pm
- Forum: ESP-IDF
- Topic: Periodic FATFS corruption
- Replies: 6
- Views: 5154
Re: Periodic FATFS corruption
Maybe one more detail... power is measured every minute, but the PCNT data is immediately available and written to the logfile. Next a read command is sent to the PZEM004T and then when the reply comes in, the result is written to the logfile. This communication takes about 70ms, but could be less. ...
- Mon May 24, 2021 3:41 pm
- Forum: ESP-IDF
- Topic: How do I merge 2 codes with "app_main" and one .c and other .cpp
- Replies: 3
- Views: 3603
Re: How do I merge 2 codes with "app_main" and one .c and other .cpp
Also remember that you can have just 1 app_main() function, which is the main entry function for your application.
So just updating CMakeLists.txt is not enough, you need to merge the code if multiple app_main() functions exist.
So just updating CMakeLists.txt is not enough, you need to merge the code if multiple app_main() functions exist.