Search found 157 matches

by eriksl
Fri Jul 08, 2016 12:58 am
Forum: ESP8266 SDK
Topic: NON-OS 1.5.4 (16_05_20) PWM bug
Replies: 13
Views: 13634

Re: NON-OS 1.5.4 (16_05_20) PWM bug

This is not "production" stuff, and for the moment it's not a problem because I can fall back to the older SDK version.

But in future SDK versions, I really hope this will get fixed, so I can make use of new features.
by eriksl
Wed Jul 06, 2016 2:21 am
Forum: ESP8266 SDK
Topic: NON-OS 1.5.4 (16_05_20) PWM bug
Replies: 13
Views: 13634

Re: NON-OS 1.5.4 (16_05_20) PWM bug

Hello Pradik. I have configured IO 14 and IO 15 for PWM but in practise only IO 14 is used. So both IO 14 and IO 15 are in the gpio_info_t struct array, but only IO 14 has a duty cycle > 0 normally. I can reconfigure, so IO 15 isn't included into the struct array at all, so the struct array only has...
by eriksl
Sun Jul 03, 2016 3:22 pm
Forum: ESP8266 SDK
Topic: NON-OS 1.5.4 (16_05_20) PWM bug
Replies: 13
Views: 13634

Re: NON-OS 1.5.4 (16_05_20) PWM bug

It shouldn't be too hard to reproduce. Connect PWM channels to io 14 and io 15, activate one of them (or both) and wait.
by eriksl
Fri Jul 01, 2016 10:12 pm
Forum: ESP8266 SDK
Topic: NON-OS 1.5.4 (16_05_20) PWM bug
Replies: 13
Views: 13634

Re: NON-OS 1.5.4 (16_05_20) PWM bug

That's a bit difficult, because it's part of a huge project (image is > 256 kbytes, mostly actual code). It also includes an alternative boot loader (rboot) which makes OTA actually possible in this case. It's here if you still want to try: http://github.com/eriksl/esp8266-universal-io-bridge But, t...
by eriksl
Sun Jun 19, 2016 6:24 pm
Forum: ESP8266 SDK
Topic: NON-OS 1.5.4 (16_05_20) PWM bug
Replies: 13
Views: 13634

NON-OS 1.5.4 (16_05_20) PWM bug

If you use PWM on this version, the ESP will restart in about 15 minutes (exact time will vary) due to "hardware watchdog timeout". If you switch to one version earlier (ESP8266_NONOS_SDK_V1.5.3_16_04_18) the problem is gone. I am very grateful for the IRAM cleanup btw. Gained about 4 Kbyt...
by eriksl
Sun Jun 19, 2016 6:20 pm
Forum: ESP8266 SDK
Topic: How to check if sntp_init() completed?
Replies: 8
Views: 7319

Re: How to check if sntp_init() completed?

The current (as of 1.5.2) implementation has a nasty quirk though. Time is only fetched ONCE. As the internal clock of the ESP8266 isn't quite "real time", your clock will be off by 1-60 minutes every 24h. The concept of NTP is that it's run periodically to care for clock drift. I had to w...
by eriksl
Tue Feb 09, 2016 4:33 pm
Forum: ESP8266 SDK
Topic: Meaning of ICACHE_FLASH_ATTR
Replies: 19
Views: 21674

Re: Meaning of ICACHE_FLASH_ATTR

Very good questions, this has been all mysterious.

But I can answer your last question: simply put ALL your code in flash (apart maybe from a few a very small functions that handle interrupts). The libs from the SDK already take up most of the IRAM so you will run out of it very quickly.
by eriksl
Fri Feb 05, 2016 4:24 pm
Forum: ESP8266 SDK
Topic: Wlan rate control acting strange
Replies: 7
Views: 4403

Re: Wlan rate control acting strange

Okay let's assume "there is something wrong" with my access point, then why don't the other (PDA) clients have no similar problems? Your remark about the rate limit being only TX makes sense to me. What I am looking for is a way to influence the negotiated speed at PHY level. So it's proba...
by eriksl
Tue Feb 02, 2016 6:09 pm
Forum: ESP8266 SDK
Topic: Wlan rate control acting strange
Replies: 7
Views: 4403

Re: Wlan rate control acting strange

Hi Faye, wifi_set_use_fixed_rate() function means ESP8266 will send every package with the fixed rate specified by this function. If the rate is not reasonable, the AP will not accept the package sent from ESP8266, so the connection maybe failed. For example of "the rate is not reasonable"...
by eriksl
Tue Feb 02, 2016 2:05 am
Forum: ESP8266 SDK
Topic: Wlan rate control acting strange
Replies: 7
Views: 4403

Re: Wlan rate control acting strange

Okay, of course. I tried all of these. The calls to the first function wifi_set_use_fixed_rate all result the connection being dropped and reconnection failing. Blue is before wifi_set_user_fixed_rate and red after. The other functions (wifi_set_user_sup_rate and wifi_set_user_rate_limit) don't have...

Go to advanced search