Search found 151 matches
- Mon Jan 28, 2019 10:54 am
- Forum: ESP-IDF
- Topic: esp_log_level_set() with tag provided as variable has no effect
- Replies: 3
- Views: 5005
Re: esp_log_level_set() with tag provided as variable has no effect
I'm not 100% sure why it works with literal tags (new_entry->tag is not set to tag anywhere I can see) however I've tested my fix and posted it as a pull request here: https://github.com/espressif/esp-idf/pull/2996
- Mon Jan 28, 2019 10:38 am
- Forum: ESP-IDF
- Topic: esp_log_level_set() with tag provided as variable has no effect
- Replies: 3
- Views: 5005
Re: esp_log_level_set() with tag provided as variable has no effect
I think I've found the problem - around line 168 in components/log/log.c (in my head of ESP-IDF) there's the following code: //search in the cache and update it if exist for (int i = 0; i < s_log_cache_entry_count; ++i) { #ifdef LOG_BUILTIN_CHECKS assert(i == 0 || s_log_cache[(i - 1) / 2].generation...
- Mon Jan 28, 2019 10:17 am
- Forum: ESP-IDF
- Topic: esp_log_level_set() with tag provided as variable has no effect
- Replies: 3
- Views: 5005
esp_log_level_set() with tag provided as variable has no effect
For many months I have used code such as: esp_log_level_set("mytag", ESP_LOG_DEBUG); However I'd like to programmatically enable debugging for certain tags in response to certain events. The tag I wish to set is stored in a char *, such that I wish to call: void set_debug(char * tag) { esp_log_level...
- Fri Oct 19, 2018 11:09 am
- Forum: ESP-IDF
- Topic: i2c bug in 3.0, works with older idf
- Replies: 9
- Views: 11448
Re: i2c bug in 3.0, works with older idf
I thought we'd been through all of this with 2.x? I spent countless hours debugging the i2c driver, investigating with brushing wires together, debugging the interrupt handler, finally concluding with a workaround for a hardware bug. Are we now saying that the 3.x driver is broken again? I haven't u...
- Wed Jun 27, 2018 5:27 am
- Forum: ESP-IDF
- Topic: Debugging ESP32 programs on Linux using an "ESP32 Emulator Library"
- Replies: 14
- Views: 38369
Re: Debugging ESP32 programs on Linux using an "ESP32 Emulator Library"
The Ebiroll QEMU project is really interesting in my opinion, because it's relatively easy to write device drivers "on the other side" of the emulation, then develop ESP32 code against those, allowing the exact same code to run on the target hardware or inside QEMU. What would be super-useful is if ...
- Sat Jun 09, 2018 7:24 am
- Forum: ESP-IDF
- Topic: Getting the uptime
- Replies: 9
- Views: 41075
Re: Getting the uptime
As ESP_Sprite said, you've got your math wrong. It will overflow after 292,000 years. Should be long enough for most IoT apps and even some enterprise applications.shelladdicted wrote: esp_timer_get_time() returns an int64_t so [-2³²,+2³²] is the max.
- Fri Apr 27, 2018 2:47 am
- Forum: ESP-IDF
- Topic: OpenOCD ESP32 - Erase
- Replies: 8
- Views: 13307
Re: OpenOCD ESP32 - Erase
I've also had JTAG debug/flash programming success on the ESP32 with this one:
http://www.ftdichip.com/Support/Documen ... _CABLE.PDF
It's based on the FTDI FT232H device.
http://www.ftdichip.com/Support/Documen ... _CABLE.PDF
It's based on the FTDI FT232H device.
- Mon Apr 16, 2018 8:15 pm
- Forum: General Discussion
- Topic: multi-thread I2C synchronization
- Replies: 11
- Views: 17638
Re: multi-thread I2C synchronization
No, I'm not sure now - I hadn't seen that warning before. I thought I'd looked at the source in the past and seen a lock. Sorry for sowing confusion. I'll edit my comment. Incidentally I am using a mutex for my own project, as I needed to ensure that tasks had exclusive use of individual slaves.
- Mon Apr 16, 2018 7:01 am
- Forum: General Discussion
- Topic: ESP_LOG(I/W/E) vs printf for debug
- Replies: 6
- Views: 20568
Re: ESP_LOG(I/W/E) vs printf for debug
I like the ESP_LOGx macros because you can enable/disable them at runtime. For example, hook up some appropriate MQTT topics and you've got yourself a run-time selectable debug log.
- Mon Apr 16, 2018 6:56 am
- Forum: General Discussion
- Topic: multi-thread I2C synchronization
- Replies: 11
- Views: 17638
Re: multi-thread I2C synchronization
I should be using a single I2C controller(I2C 0 OR I2C 1) for both I2C slaves, since I have access to a single I2C bus on the hardware? You can use a single I2C master controller for both of your I2C slaves provided they will work at the same SCK rate. EDIT: My comment here is most likely wrong - i...