Search found 171 matches

by AgentSmithers
Wed Feb 06, 2019 1:51 am
Forum: ESP8266 SDK
Topic: HTTP File Upload
Replies: 1
Views: 805

Re: HTTP File Upload

I finished this, After getting to the last 3000 bytes I start scanning for the Mime Border at the footer and then I chop it off. Works perfectly for when someone is transferring one file.
by AgentSmithers
Mon Feb 04, 2019 9:06 pm
Forum: ESP8266 SDK
Topic: dev 1153 ?
Replies: 8
Views: 2502

Re: dev 1153 ?

alex323qp wrote:I uploaded a mcve to the issue tracker a week ago. No one from espressif seems to care about this though. I'm leaving the link here in case anyone wishes to confirm:

https://github.com/espressif/ESP8266_NO ... /issues/90

A.


Thank you for coming back and leaving a trail.
by AgentSmithers
Sun Feb 03, 2019 12:16 pm
Forum: ESP8266 SDK
Topic: SPI Push / Pop Variables
Replies: 2
Views: 824

Re: SPI Push / Pop Variables

Update: Got it.. I had to flip my bits so Flash writes correctly then after I read the type, shift the bits over by 3 then pull the actual value acordingly. Start -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Address now at: 70000 Buffer00 00 00 00 00 00 00 00 FF FF FF FF FF FF FF FF Writing: FD FF FF FF FF FF FF ...
by AgentSmithers
Sun Feb 03, 2019 10:37 am
Forum: ESP8266 SDK
Topic: SPI Push / Pop Variables
Replies: 2
Views: 824

Re: SPI Push / Pop Variables

I resolved it. It was because erase_sector takes a 2 digit sector number vs. an actual address.. If you want include upgrade.h and take the address and divide it by SPI_FLASH_SEC_SIZE. spi_flash_erase_sector(0x60000/SPI_FLASH_SEC_SIZE); =====>>>>> spi_flash_erase_sector(0x60); Thanks anyways! =] Aft...
by AgentSmithers
Sun Feb 03, 2019 9:18 am
Forum: ESP8266 SDK
Topic: SPI Push / Pop Variables
Replies: 2
Views: 824

SPI Push / Pop Variables

Hi Everyone!! I believe I have a simple error and wanted to reach out to see what it may be. It appears after the write spi_flash_write it returns success but does not return the correct values. The whole idea of this function is to allow me to push and pop variables like booleans and char arrays. A...
by AgentSmithers
Fri Feb 01, 2019 4:57 am
Forum: ESP8266 SDK
Topic: Firmware burns and Works on one Wemos d1 mini pro but not the other?
Replies: 1
Views: 687

Re: Firmware burns and Works on one Wemos d1 mini pro but not the other?

Hi everyone! I'll tell you. This whole ESP stuff has been quite an expereice.. Long story short... The two chips look physically the same but only one supports QIO and QOUT and BOTH support DIO and DOUT... DIO is faster so use that! I resolved it by setting osboxes@osboxes Main]$ esptool.py --baud 1...
by AgentSmithers
Fri Feb 01, 2019 2:37 am
Forum: ESP8266 SDK
Topic: mac 985 ?
Replies: 6
Views: 1688

Re: mac 985 ?

Migrating the code is not an option at this stage, would take months. Dude, No shit.. I feel you on that one :( I have a bunch I have to convert myself to move to ESP32 to the point where I almost never want to. I don't know if this will help your situation but are you debugging with that Breakpoin...
by AgentSmithers
Thu Jan 31, 2019 5:26 am
Forum: ESP8266 SDK
Topic: Firmware burns and Works on one Wemos d1 mini pro but not the other?
Replies: 1
Views: 687

Firmware burns and Works on one Wemos d1 mini pro but not the other?

Hi Everyone! Recently I purchased another set of 5 devices of my Wemos D1 Mini Pro and continued development on my project. For the last 2 years I've been using the same 5 chips and they all have been working perfectly fine with both FOTA and standard Firmware Images. Now after I opened my first one...
by AgentSmithers
Tue Jan 29, 2019 6:02 am
Forum: ESP8266 SDK
Topic: mac 985 ?
Replies: 6
Views: 1688

Re: mac 985 ?

How are you implementing these functions? Are they from including a header then calling an init function to the respective TCP or UDP setup you have? This is the way I do it and one of the landmines I landed on was that the headers sometimes shared variables with the same name so when I called funct...
by AgentSmithers
Sat Jan 26, 2019 12:26 am
Forum: ESP8266 SDK
Topic: dev 1153 ?
Replies: 8
Views: 2502

Re: dev 1153 ?

So I think the 1153 means your WDT triggered. This is due to an amount of time passing in a BLOCKING USERLEVEL thread. So if one of your functions take a full Human second to clear this is where you start to get into trouble.. If the 1153 is your WDT then there is a WDT Feed function that can reset ...

Go to advanced search