Search found 31 matches

by Pato
Wed Aug 29, 2018 1:09 am
Forum: ESP8266 SDK
Topic: PWM, SSL and FOTA: ill-compiled libraries or conflicts ?
Replies: 1
Views: 192

Re: PWM, SSL and FOTA: ill-compiled libraries or conflicts ?

Okay, I reworked my test and could narrow the situation a little more. The simple code below runs as expected when compiled for non-FOTA. But when compiled for FOTA: - If linked with gc-section option, works only if pwm_start() is commented out. - If linked without gc-section option, works only if p...
by Pato
Tue Aug 28, 2018 6:39 pm
Forum: ESP8266 SDK
Topic: PWM, SSL and FOTA: ill-compiled libraries or conflicts ?
Replies: 1
Views: 192

PWM, SSL and FOTA: ill-compiled libraries or conflicts ?

Hi all, I've got an OTA program that use and link against these libs (among others): libssl, libpwm and libdriver. But depending on if I link with the option gc-section (to remove unused code), or depending on the libraries I link against, my program crashes to Fatal Exception (0) right after boot, ...
by Pato
Tue Aug 21, 2018 4:23 pm
Forum: ESP8266 SDK
Topic: FOTA version causes FatalException (0) after boot, but non-FOTA works
Replies: 0
Views: 587

FOTA version causes FatalException (0) after boot, but non-FOTA works

Hi all, I have a NON-FOTA code that compiles and works perfectly fine on the ESP8266. However if I compile the exact same code for OTA build, with the same compiler and linker options and linking the same libraries, the bootloader jumps @01000 to run user1, but immediatly after throws a fatal except...
by Pato
Fri Aug 17, 2018 5:13 pm
Forum: General Q&A
Topic: First byte is not the magic 0xE9 for OTA binaries
Replies: 0
Views: 909

First byte is not the magic 0xE9 for OTA binaries

Hey all, I build my two applications for OTA upgrade user1.bin and user2.bin, one for each flash slot (for addresses 0x01000 and 0x81000 respectively). The documentation says that the first byte of an application built for the ESP8266 is always 0xE9. This is the "magic byte" (https://www.e...
by Pato
Tue Aug 07, 2018 3:21 pm
Forum: General Q&A
Topic: ESP8266 - two sdk applications
Replies: 3
Views: 1492

Re: ESP8266 - two sdk applications

Hey ! Yes you can, this is the "OTA" feature of the Esp. In the SDK you have different bootloaders available. The bootloaders for OTA basivally consider the flash is split in two slots (called user1 and user2 by Espressif), and they will run one of the two applications according to a flag ...
by Pato
Thu Aug 02, 2018 10:24 pm
Forum: ESP8266 SDK
Topic: Creating a Blocking Thread on espconn_gethostbyname
Replies: 4
Views: 753

Re: Creating a Blocking Thread on espconn_gethostbyname

Hey, I am also studying a way to do a kind of wait() or delay() that would block the execution of my function while letting the SDK do its background tasks like Wifi and TCP processing. I've found very intersesting things in the ESP support for Arduino IDE: their great guys have built this exact sam...
by Pato
Tue Jul 24, 2018 5:46 pm
Forum: ESP8266 SDK
Topic: UART0: Can't get FIFO length
Replies: 1
Views: 285

Re: UART0: Can't get FIFO length

Okay, my mistake. It was because I did not understand that the code in uart.c was actually already doing some custom processing of the data that arrived on the UART, like reprinting it and clearing the buffer, especially on the UART_RXFIFO_TOUT_INT interrupt event. It was not a basic UART driver to ...
by Pato
Tue Jul 24, 2018 1:40 am
Forum: ESP8266 SDK
Topic: Software Architecture
Replies: 1
Views: 375

Re: Software Architecture

Hi, Here is my basic understanding so far, certainly not accurate, but maybe it can give you some hints :) I will assume you are talking about bare C software programming (the one I play with): 1) The ESP being basically a microcontroller, you decide the sofware architecture... However, Espressif pr...
by Pato
Tue Jul 24, 2018 1:04 am
Forum: ESP8266 SDK
Topic: UART0: Can't get FIFO length
Replies: 1
Views: 285

UART0: Can't get FIFO length

Hi folks, I'm trying to receive a string on UART0, and at the most basic step to get the number of bytes available in the RX FIFO buffer. I try to use the magic formulae fifo_len = (READ_PERI_REG(UART_STATUS(UART0)) >> UART_RXFIFO_CNT_S) & UART_RXFIFO_CNT; in a callback function, and from my PC ...

Go to advanced search