Hi,
I have written code some time ago that compiled fine with esp-idf 3.3. I know that for compilation, you just have to create a
components directory and in each component, you need an empty component.mk . In the project dir. you have a CMakeLists.txt with a
content like this
cmake_minimum ...
Search found 32 matches
- Sun Dec 01, 2019 8:21 am
- Forum: General Discussion
- Topic: Project structure IDF 3.3 vs IDF4.1 compilation w/ components directory
- Replies: 1
- Views: 3482
- Wed Sep 18, 2019 6:58 am
- Forum: General Discussion
- Topic: StoreProhibited when trying to set callback for BLE
- Replies: 3
- Views: 6112
Re: StoreProhibited when trying to set callback for BLE
I used the workaround now by declaring a global variable holding an instance of the MyCallbacks class. I set the callbacks in the initialization process.
- Tue Sep 17, 2019 3:16 pm
- Forum: General Discussion
- Topic: StoreProhibited when trying to set callback for BLE
- Replies: 3
- Views: 6112
Re: StoreProhibited when trying to set callback for BLE
It looks like the problem is when I am connected, I can not set the callback. It works when I set the callback in the initialization function.
- Tue Sep 17, 2019 2:08 pm
- Forum: General Discussion
- Topic: vsnprintf exception and debugging
- Replies: 5
- Views: 9847
- Tue Sep 17, 2019 2:05 pm
- Forum: General Discussion
- Topic: StoreProhibited when trying to set callback for BLE
- Replies: 3
- Views: 6112
StoreProhibited when trying to set callback for BLE
Hi,
I have been searching for some days now, but cannot seem to find my mistake. The error happens when I try to set a callback in the BLE class. I checked whether the callback is NULL, but it isn't.
Here is my stack trace:
D (13343) BLECharacteristic: >> setCallbacks: 0x3ffdba58
Guru ...
I have been searching for some days now, but cannot seem to find my mistake. The error happens when I try to set a callback in the BLE class. I checked whether the callback is NULL, but it isn't.
Here is my stack trace:
D (13343) BLECharacteristic: >> setCallbacks: 0x3ffdba58
Guru ...
- Tue Sep 03, 2019 8:12 am
- Forum: General Discussion
- Topic: Interrupt on GPIO36 triggered only once
- Replies: 3
- Views: 6246
Re: Interrupt on GPIO36 triggered only once
Oh okay thanks.
- Mon Sep 02, 2019 3:49 pm
- Forum: General Discussion
- Topic: Interrupt on GPIO36 triggered only once
- Replies: 3
- Views: 6246
Interrupt on GPIO36 triggered only once
Hi,
I have attached an interrupt on the GPIO36 following the tutorial here: https://github.com/espressif/esp-idf/tree/release/v3.3/examples/peripherals/gpio
I am using IDF 3.3, because I have dependencies on esp azure, which requires this version of the IDF.
When the interrupt is triggered, the ...
I have attached an interrupt on the GPIO36 following the tutorial here: https://github.com/espressif/esp-idf/tree/release/v3.3/examples/peripherals/gpio
I am using IDF 3.3, because I have dependencies on esp azure, which requires this version of the IDF.
When the interrupt is triggered, the ...
- Thu May 16, 2019 7:36 am
- Forum: General Discussion
- Topic: Compression using miniz
- Replies: 5
- Views: 18105
Re: Compression using miniz
That’s great news. I will check it out. I haven’t done any benchmarking yet.
- Tue May 14, 2019 9:18 am
- Forum: General Discussion
- Topic: Compression using miniz
- Replies: 5
- Views: 18105
Re: Compression using miniz
#include "compression.h"
#include "assert.h"
#include "zlib.h"
#include <string.h>
#include "stdio.h"
#include "freertos/FreeRTOS.h"
#include "freertos/task.h"
#include "stdlib.h"
#include "esp_log.h"
const char * TAG = "Chaze-Compression";
/**
* @brief When recording sensor data, multiple tasks ...
#include "assert.h"
#include "zlib.h"
#include <string.h>
#include "stdio.h"
#include "freertos/FreeRTOS.h"
#include "freertos/task.h"
#include "stdlib.h"
#include "esp_log.h"
const char * TAG = "Chaze-Compression";
/**
* @brief When recording sensor data, multiple tasks ...
- Thu Apr 25, 2019 6:29 am
- Forum: Hardware
- Topic: Discrepancy between WROOM-32 and ESP Hardware design guidelines
- Replies: 1
- Views: 4651
Discrepancy between WROOM-32 and ESP Hardware design guidelines
Hi,
There is a difference in the two reference sheets "Hardware design guidelines" and "ESP32-WROOM-32 datasheet".
Both can be found here:
https://www.espressif.com/sites/default/files/documentation/esp32-wroom-32_datasheet_en.pdf
https://www.espressif.com/sites/default/files/documentation/esp32 ...
There is a difference in the two reference sheets "Hardware design guidelines" and "ESP32-WROOM-32 datasheet".
Both can be found here:
https://www.espressif.com/sites/default/files/documentation/esp32-wroom-32_datasheet_en.pdf
https://www.espressif.com/sites/default/files/documentation/esp32 ...