Search found 51 matches
- Tue Feb 28, 2017 10:08 pm
- Forum: General Discussion
- Topic: Documentation for esp_err_t values?
- Replies: 2
- Views: 10223
Documentation for esp_err_t values?
Hi, this might be a silly question, but where can I find documentation for what the different values for esp_err_t means? I'm playing around with I2C, and when I do this; portBASE_TYPE timeout = 500 / portTICK_PERIOD_MS; error = i2c_master_cmd_begin(I2C_NUM_0, cmd, timeout); if (error == 0) //Device...
- Tue Feb 28, 2017 9:12 pm
- Forum: ESP-IDF
- Topic: Issues with I2C? Only 1 of 4 devices found by i2cscanner.c
- Replies: 14
- Views: 23149
Re: Issues with I2C? Only 1 of 4 devices found by i2cscanner.c
Got it working! In Kolban's i2c scanner I changed this line from espRc = i2c_master_cmd_begin(I2C_NUM_0, cmd, 10/portTICK_PERIOD_MS); to espRc = i2c_master_cmd_begin(I2C_NUM_0, cmd, 100/portTICK_PERIOD_MS); With that change all the four devices were detected. As I understand it the last parameter of...
- Tue Feb 28, 2017 8:54 pm
- Forum: ESP-IDF
- Topic: Issues with I2C? Only 1 of 4 devices found by i2cscanner.c
- Replies: 14
- Views: 23149
Re: Issues with I2C? Only 1 of 4 devices found by i2cscanner.c
Hi guys, so I tried the same tests, but this time using a Teensy 3.2. It was able to detect all four devices! So ESP32 was able to find device at 0x21, while Teensy found devices at 0x21, 0x48, 0x53 and 0x60. Regarding the external pull-up resistors; yes, those are important, and all the breakout bo...
- Mon Feb 27, 2017 9:14 pm
- Forum: ESP-IDF
- Topic: Issues with I2C? Only 1 of 4 devices found by i2cscanner.c
- Replies: 14
- Views: 23149
Re: Issues with I2C? Only 1 of 4 devices found by i2cscanner.c
Tomorrow I can try to hook up a Teensy 3.2 instead of the ESP32, and run an Arduino-based I2C scanner on the Teensy to see if that gives different result.
- Mon Feb 27, 2017 9:11 pm
- Forum: ESP-IDF
- Topic: Issues with I2C? Only 1 of 4 devices found by i2cscanner.c
- Replies: 14
- Views: 23149
Re: Issues with I2C? Only 1 of 4 devices found by i2cscanner.c
Yes, I have a Saleae Logic 4. I hooked it up earlier, and in the I2C analyzer section it listed a hole lot of NAK's, and a single ACK (for 0x21). I'm unsure as what more info I should look for in the analyzer, and what logiclevels I'm supposed to see.
- Mon Feb 27, 2017 8:55 pm
- Forum: ESP-IDF
- Topic: Issues with I2C? Only 1 of 4 devices found by i2cscanner.c
- Replies: 14
- Views: 23149
Issues with I2C? Only 1 of 4 devices found by i2cscanner.c
Hi, I'm playing around with I2C using a Sparkfun ESP32 Thing and Kolbans code for i2cscanning (https://github.com/nkolban/esp32-snippets/blob/master/i2c/scanner/i2cscanner.c) I've got a TMP102 (temperature), HMC6352 (compass), MPL3115A5 (altitude) and a ADXL345 (accelerometer). I've tried hooking up...
- Mon Feb 27, 2017 11:33 am
- Forum: ESP-IDF
- Topic: Questions about basic button-toggle-led program
- Replies: 5
- Views: 17934
Re: Questions about basic button-toggle-led program
Thanks for an execellent reply! Would it make sense to do something like this in the last loop of a task to detect when things are about to fail? (At work, so I haven't been able to test). while (1) { vTaskDelay(1000 / portTICK_PERIOD_MS); if (uxTaskGetStackHighWaterMark(NULL) < 10) ESP_LOGW("Close ...
- Sun Feb 26, 2017 5:17 pm
- Forum: ESP-IDF
- Topic: Questions about basic button-toggle-led program
- Replies: 5
- Views: 17934
Re: Questions about basic button-toggle-led program
Thank you very much for an excellent reply. I got it working now. In addition to your observations I also changed the definitions from #define LED_GPIO GPIO_SEL_5 #define BUTTON_GPIO GPIO_SEL_0 to #define LED_GPIO GPIO_NUM_5 #define BUTTON_GPIO GPIO_NUM_0 For the next newbie to come along, here is t...
- Sun Feb 26, 2017 2:30 pm
- Forum: ESP-IDF
- Topic: Using pins 6-11 on ESP-WROOM-32?
- Replies: 3
- Views: 11135
Re: Using pins 6-11 on ESP-WROOM-32?
Hi,
I'm referring to physical pads on the ESP-WROOM-32.
Pad 6 (IO34), pad 7 (IO35) and pad 8 (IO32).
But you're saying that the unusable pins are IO6, IO7, IO8, IO9, IO10 and IO11? As far as I can tell none of those are broken out to physical pads, which would make my PCB design OK.
I'm referring to physical pads on the ESP-WROOM-32.
Pad 6 (IO34), pad 7 (IO35) and pad 8 (IO32).
But you're saying that the unusable pins are IO6, IO7, IO8, IO9, IO10 and IO11? As far as I can tell none of those are broken out to physical pads, which would make my PCB design OK.
- Sun Feb 26, 2017 11:55 am
- Forum: ESP-IDF
- Topic: Using pins 6-11 on ESP-WROOM-32?
- Replies: 3
- Views: 11135
Using pins 6-11 on ESP-WROOM-32?
Hi, I'm just getting started with ESP32, and have designed a PCB for the ESP-WROOM-32 that I've just delivered for production. While waiting for the PCB to be shipped I read in Kolbans book that: Note that GPIO_NUM_34 – GPIO_NUM_39 are input mode only. You can not use these pins for signal output. A...