Search found 305 matches
- Fri Mar 23, 2018 5:17 pm
- Forum: ESP-IDF
- Topic: RMT - simplest receive example working, but idle_threshold problem
- Replies: 18
- Views: 18813
Re: RMT - simplest receive example working, but idle_threshold problem
Without a ring buffer enabled, there is no problem, but I need to do some work to get an example going to obtain the data without the ring buffer. It seems that a receive end interrupt with a zero period will not be suitable as that would be an error condition in my situation where I want to continu...
- Fri Mar 23, 2018 3:41 pm
- Forum: ESP-IDF
- Topic: RMT - simplest receive example working, but idle_threshold problem
- Replies: 18
- Views: 18813
Re: RMT - simplest receive example working, but idle_threshold problem
Also tried: different GPIO, different RMT channel, different CPU speed, different FreeRTOS tick rates, enabled verbose logging and checked the register is being written correctly by reading it back. The error with idle_threshold over a value between 11000 and 12000 only occurs when an input with a p...
- Fri Mar 23, 2018 3:24 pm
- Forum: General Discussion
- Topic: Urgent Need for Pulse Width Measurement, Register/Hardware Descriptions Would Work
- Replies: 13
- Views: 25842
Re: Urgent Need for Pulse Width Measurement, Register/Hardware Descriptions Would Work
Was this fixed? Think I might be having the same issue here: https://www.esp32.com/viewtopic.php?f=13&t=5122 When I increase the idle_threshold to 12000 or beyond (including 65535), I get an error. I am trying to understand the error code. I get similar error codes by putting in frequencies that sho...
- Fri Mar 23, 2018 12:20 pm
- Forum: ESP-IDF
- Topic: RMT - simplest receive example working, but idle_threshold problem
- Replies: 18
- Views: 18813
RMT - simplest receive example working, but idle_threshold problem
#include "freertos/FreeRTOS.h" #include "freertos/task.h" #include "freertos/queue.h" #include "driver/rmt.h" #include "driver/periph_ctrl.h" #include "soc/rmt_reg.h" void app_main() { rmt_config_t rmt_rx = { .channel = 0, .gpio_num = 17, .clk_div = 80, //1MHz .mem_block_num = 1, .rmt_mode = RMT_MO...
- Sat Mar 17, 2018 8:19 am
- Forum: Hardware
- Topic: ESP-WROVER-KIT SCH-3: IO2 pulled up and down for SD card
- Replies: 2
- Views: 4358
- Fri Mar 16, 2018 11:51 pm
- Forum: Hardware
- Topic: ESP-WROVER-KIT SCH-3: IO2 pulled up and down for SD card
- Replies: 2
- Views: 4358
ESP-WROVER-KIT SCH-3: IO2 pulled up and down for SD card
https://dl.espressif.com/dl/schematics/ESP-WROVER-KIT_SCH-3.pdf IO2 has 5K to ground and 10K to 3V3 near the SD card. I thought that IO2 is to be pulled up for SD card operation whereas this would sit at about 1.1V. IO2 uses a third transistor in the auto program circuit. Is this so that IO0 and IO2...
- Wed Mar 07, 2018 1:02 pm
- Forum: Hardware
- Topic: About the CAN controller.
- Replies: 175
- Views: 308745
Re: About the CAN controller.
It might be because you are using an RTOS queue to receive. I had a similar problem on page 8 and Thomas suggested replying in an interrupt. When I did this the latency went from multiple milliseconds to less than 10 microseconds which is the clock of the Kvaser tool.
- Sat Apr 15, 2017 7:30 pm
- Forum: Hardware
- Topic: About the CAN controller.
- Replies: 175
- Views: 308745
Re: About the CAN controller.
First eight packets are with a FreeRTOS task replying with an echo of packets received, so four are sent, four received. Second eight packets are with the reply in an ISR. Moving from FreeRTOS to an ISR drops the latency 20 times from average of 5.3ms to 260us.
- Wed Apr 05, 2017 12:36 pm
- Forum: Hardware
- Topic: About the CAN controller.
- Replies: 175
- Views: 308745
Re: About the CAN controller.
It is working with MCP2551. Kvaser log, I sent 8 zeros in the first three packets, then 0, 52 then six zeroes in the subsequent packets and the ESP32 echoes them. The 2018 is the CAN ID, 8 is the DLC, then the payload, then the timestamp and Transmit or Receive. 0 2018 8 0 0 0 0 0 0 0 0 66.129150 T ...
- Thu Mar 30, 2017 11:14 am
- Forum: Hardware
- Topic: About the CAN controller.
- Replies: 175
- Views: 308745
Re: About the CAN controller.
Connecting the D pin of the tranceiver to 3.3V, I read -1.1mV between CAN H and CAN L with the bus disconnected but with 120R termination. Connecting the D pin of the tranceiver to 0V I read 0mV between CAN H and CAN L. I should be getting a positive voltage between CAN H and CAN L in this situation...