Custom firmware user_main.c required code
Posted: Mon Jul 27, 2015 10:55 pm
I have been through a LOT of material on the ESP8266.
What I have not been able to find is a clear description of what is required when writing custom firmware in C.
Specifically,
What includes are required in user_main? I see ets_sys.h, uart.h, and others in a lot custom code on the web, but no description of what they do, and why they are needed.
What functions are required in user_main? user_init is, and is where user code starts.
What other files are required?
I feel like the whole ESP8266 community grew so fast that the people who started with it in the beginning assume others know a lot more than they think. I have yet to find a comprehensive beginning guide, or any tutorial/example that does not skip directly to inserting code into user_init.
I can program an ESP8266 in C just fine, but I can't help but feel like I'm a cave man who learned to drive a car. Gas, brake, steering wheel. I know the result of using them, just not how they accomplish that result. (excuse the terrible analogy )
Does anyone know of any resources? Can anyone explain it (or some?)
Thanks, Ygneh
What I have not been able to find is a clear description of what is required when writing custom firmware in C.
Specifically,
What includes are required in user_main? I see ets_sys.h, uart.h, and others in a lot custom code on the web, but no description of what they do, and why they are needed.
What functions are required in user_main? user_init is, and is where user code starts.
What other files are required?
I feel like the whole ESP8266 community grew so fast that the people who started with it in the beginning assume others know a lot more than they think. I have yet to find a comprehensive beginning guide, or any tutorial/example that does not skip directly to inserting code into user_init.
I can program an ESP8266 in C just fine, but I can't help but feel like I'm a cave man who learned to drive a car. Gas, brake, steering wheel. I know the result of using them, just not how they accomplish that result. (excuse the terrible analogy )
Does anyone know of any resources? Can anyone explain it (or some?)
Thanks, Ygneh