Just use a timer interrupt
That's what I ended up on doing, Only issue is I need three of these triggering at different times (with an interrupt triggering the respective timer and switching the others off)
Although this code works perfectly to start the timer:
gpio_set_level(32, 0);
gpio ...
Search found 21 matches
- Sat Jul 27, 2019 11:49 pm
- Forum: Hardware
- Topic: very very slow pwm singal generation
- Replies: 4
- Views: 6225
- Tue Jul 23, 2019 6:59 am
- Forum: Hardware
- Topic: very very slow pwm singal generation
- Replies: 4
- Views: 6225
Re: very very slow pwm singal generation
Hi WiFive,
This was the other option I was thinking of doing.
I was hoping that maybe the ledc module could do this.
I'd say if the timer has a period of 20 mins with a 10% duty, then a variation of 5% or less would be preferred.
I'm not too familiar with the esp32's timers. How would I go about ...
This was the other option I was thinking of doing.
I was hoping that maybe the ledc module could do this.
I'd say if the timer has a period of 20 mins with a 10% duty, then a variation of 5% or less would be preferred.
I'm not too familiar with the esp32's timers. How would I go about ...
- Tue Jul 23, 2019 6:25 am
- Forum: Hardware
- Topic: very very slow pwm singal generation
- Replies: 4
- Views: 6225
very very slow pwm singal generation
Hey everyone,
I'm starting to dig around and have been fooling with the ledc module, but I don't think it will fulfill my requirements completely. I need to generate a very slow pwm signal, somewhere in the order of having a period of 10 to 20 minutes. The duty will be fixed
Is there anyone I can ...
I'm starting to dig around and have been fooling with the ledc module, but I don't think it will fulfill my requirements completely. I need to generate a very slow pwm signal, somewhere in the order of having a period of 10 to 20 minutes. The duty will be fixed
Is there anyone I can ...
- Wed Jun 12, 2019 7:09 pm
- Forum: ESP-IDF
- Topic: resync NTP
- Replies: 0
- Views: 2387
resync NTP
Hey everyone,
In my code upon wake up I want to have the esp retrieve time using sntp. The sync works perfectly the first time as it updates from 1970 to 2019, althought I have no idea what to make the condition for subsequent sync's to allow it to resync.
time_t now = 0;
struct tm timeinfo ...
In my code upon wake up I want to have the esp retrieve time using sntp. The sync works perfectly the first time as it updates from 1970 to 2019, althought I have no idea what to make the condition for subsequent sync's to allow it to resync.
time_t now = 0;
struct tm timeinfo ...
- Wed May 22, 2019 8:42 pm
- Forum: ESP-IDF
- Topic: CoreDump not providing enough info
- Replies: 4
- Views: 6852
Re: CoreDump not providing enough info
HI Ritesh Prajapati,
Sorry I completely forgot to reply and have still not gotten this working.
Here's the output of the core dump:
python ~/esp/esp-idf/components/espcoredump/espcoredump.py info_corefile -d 3 -t b64 -c ~/Desktop/dump1.txt ~/Desktop/esp-idf-template/build/app-template.elf ...
Sorry I completely forgot to reply and have still not gotten this working.
Here's the output of the core dump:
python ~/esp/esp-idf/components/espcoredump/espcoredump.py info_corefile -d 3 -t b64 -c ~/Desktop/dump1.txt ~/Desktop/esp-idf-template/build/app-template.elf ...
- Mon Apr 29, 2019 10:14 am
- Forum: Hardware
- Topic: SPI pull down CS
- Replies: 3
- Views: 6015
Re: SPI pull down CS
Hey everyone,
I've got my SPI init code defined as the following:
#define GPIO_MOSI 21
#define GPIO_MISO 14
#define GPIO_SCLK 12
#define GPIO_CS 22
ESP_LOGI(TAG1,"Started master SPI");
esp_err_t ret;
spi_device_handle_t handle;
//Configuration for the SPI bus
spi_bus_config_t buscfg ...
- Fri Apr 26, 2019 2:58 pm
- Forum: Hardware
- Topic: SPI pull down CS
- Replies: 3
- Views: 6015
SPI pull down CS
Hey everyone,
I've got my SPI init code defined as the following:
#define GPIO_MOSI 21
#define GPIO_MISO 14
#define GPIO_SCLK 12
#define GPIO_CS 22
ESP_LOGI(TAG1,"Started master SPI");
esp_err_t ret;
spi_device_handle_t handle;
//Configuration for the SPI bus
spi_bus_config_t buscfg ...
I've got my SPI init code defined as the following:
#define GPIO_MOSI 21
#define GPIO_MISO 14
#define GPIO_SCLK 12
#define GPIO_CS 22
ESP_LOGI(TAG1,"Started master SPI");
esp_err_t ret;
spi_device_handle_t handle;
//Configuration for the SPI bus
spi_bus_config_t buscfg ...
- Mon Apr 22, 2019 5:56 pm
- Forum: ESP-IDF
- Topic: CoreDump not providing enough info
- Replies: 4
- Views: 6852
Re: CoreDump not providing enough info
hey everyone,
For some reason the coredump utility is providing me with nearly no info.
It either just says that a brownout procured or that it couldn't access some memory region or some other random info.
I had a look at kolbans book and in it he gets the exact line at which the error ...
- Fri Apr 19, 2019 2:36 pm
- Forum: ESP-IDF
- Topic: SPI slave long wait period panicks system
- Replies: 2
- Views: 4167
Re: SPI slave long wait period panicks system
Can you post the contents of the panic (and if possible, the backtrace)?
Hi! Here's the coredump:
espcoredump.py v0.3-dev
INFO:Read TCB 356 bytes @ 0x3ffbb9b4
INFO:Read stack 1148 bytes @ 0x3ffbb530
INFO:Stack start_end: 0x3ffbb530 @ 0x3ffbb9ac
INFO:Read TCB 356 bytes @ 0x3ffbc88c
INFO:Read ...
- Fri Apr 19, 2019 4:24 am
- Forum: ESP-IDF
- Topic: SPI slave long wait period panicks system
- Replies: 2
- Views: 4167
SPI slave long wait period panicks system
Hey everyone,
I have a multi_master spi going.
When the one master takes a long time to communicate with the esp32 the device panicks.
Essentially the spi_slave transmission call is done with the following:
ret=spi_slave_transmit(HSPI_HOST, &t, portMAX_DELAY);
I know that it is this causing ...
I have a multi_master spi going.
When the one master takes a long time to communicate with the esp32 the device panicks.
Essentially the spi_slave transmission call is done with the following:
ret=spi_slave_transmit(HSPI_HOST, &t, portMAX_DELAY);
I know that it is this causing ...