Search found 9 matches
- Tue Nov 16, 2021 6:23 pm
- Forum: ESP-IDF
- Topic: esp_https_ota() fails to complete
- Replies: 1
- Views: 1987
Re: esp_https_ota() fails to complete
Solved the issue. Turned out to be an issue with the http server I was using. openssl s_server -WWW -key ca_key.pem -cert ca_cert.pem -port 8070 Using the curl command as suggested in the troubleshooting section of examples\system\ota\README.MD pointed me to the issue as the curl command would only ...
- Thu Nov 11, 2021 9:39 pm
- Forum: ESP-IDF
- Topic: esp_https_ota() fails to complete
- Replies: 1
- Views: 1987
esp_https_ota() fails to complete
Using IDF 4.3 I call esp_https_ota() and it never returns. Here is the log output. D (14171) esp_https_ota: Written image length 19652 D (14171) HTTP_CLIENT: is_data_remain=1, is_chunked=1, content_length=-1 D (14181) TRANS_SSL: remain data in cache, need to read again D (14181) HTTP_CLIENT: need_re...
- Fri Sep 24, 2021 1:58 pm
- Forum: ESP-IDF
- Topic: Will ets_delay_us() work on core 1?
- Replies: 2
- Views: 1838
Re: Will ets_delay_us() work on core 1?
I pinned my tasks to core 1 and I ran into an issue with updating ledc channels. The delay was originally inserted due to ledc updates not working if they are performed back-to-back. Once the delay was added the ledc updates worked fine when on core 0, once I moved to core 1 I ran into the issue aga...
- Thu Sep 23, 2021 3:51 pm
- Forum: ESP-IDF
- Topic: Will ets_delay_us() work on core 1?
- Replies: 2
- Views: 1838
Will ets_delay_us() work on core 1?
I have a task that was using ets_delay_us(), I was pinning this task to core 0 and have now moved the task to core 1. It appears that ets_delay_us() no longer works. esp_timer task is running on core 0. I know that ets_delay_us() is in the ROM, but I expected it to run on the core from which it is c...
- Fri Jul 23, 2021 10:31 pm
- Forum: ESP-IDF
- Topic: RS-485 half-duplex extra byte received.
- Replies: 1
- Views: 1750
RS-485 half-duplex extra byte received.
IDF4.3 Sending 7 bytes out UART2 configured as RS485 Half-duplex every 80ms at 115200 baudrate. While debugging this issue, https://www.esp32.com/viewtopic.php?f=13&t=21835 Occasionally I would see a data byte in the RX FIFO following a transmission. The byte was always 0x00. I modified the TX DONE ...
- Fri Jul 23, 2021 5:23 pm
- Forum: ESP-IDF
- Topic: RS485 Enable pin issue
- Replies: 17
- Views: 10851
Re: RS485 Enable pin issue
Your analysis matches my system. Thank you.
- Thu Jul 22, 2021 3:55 pm
- Forum: ESP-IDF
- Topic: RS485 Enable pin issue
- Replies: 17
- Views: 10851
Re: RS485 Enable pin issue
I switched to using uart_tx_chars() and I still had the failure. Since I am only sending 7 bytes at a time and not very often, at least 10ms between transmits, I modified uart_tx_chars() to move the critical section to include the call to uart_hal_write_txfifo(). The issue did not occur overnight. T...
- Wed Jul 21, 2021 7:01 pm
- Forum: ESP-IDF
- Topic: RS485 Enable pin issue
- Replies: 17
- Views: 10851
Re: RS485 Enable pin issue
No luck. Applied the changes to uart.c and moved the ISR to IRAM and it still fails.
- Tue Jul 20, 2021 9:51 pm
- Forum: ESP-IDF
- Topic: RS485 Enable pin issue
- Replies: 17
- Views: 10851
Re: RS485 Enable pin issue
I have the same issue. Using ESP-IDF 4.3.
I call uart_write_bytes() to send 7 bytes, then I wait 10ms+ (in other tasks) and never call uart_wait_tx_done().
Is uart_wait_tx_done() required even if the transmission is completed?
I call uart_write_bytes() to send 7 bytes, then I wait 10ms+ (in other tasks) and never call uart_wait_tx_done().
Is uart_wait_tx_done() required even if the transmission is completed?