Would make this useable straight out of the box, using available phone - tab apps ....short dev time for real world simple applications.
Be competition for the amw006 for example.
Pretty close now, just a few more steps ........
- VoIP Phone demo, especially one that can connect to Google Talk, Skype, or other such popular services
- A complete port of the latest FreeRTOS - and versions of IOT and other demos adapted to use FreeRTOS
- IOT demo providing bidirectional control and event monitoring (i.e. both a client and server) using UBJSON / BSON / Smile
These protocols are much more compact so even less bandwidth, but the main advantage is much easier to handle on a tiny 8-bit host processor for the lowest-cost category of devices.
- Example of I2S usage
- *Complete* IC datasheet and user manual documentation: for an example of what level of detail and completeness is typically needed to support product designers with a minimum of direct support calls,
check out the user manuals and datasheets of any NXP, Freescale, or ST Cortex-based microcontrollers.
- some documentation on I2S usage, registers etc.
- Do next version of the ESP8266 (ESP8266MX? ) with a Cortex M-series microcontroller core, (such as CortexM3 or M4 ) now the industry standard and well known to all serious developers.
this will make developing products around your IC *much* easier and quicker for everyone and reduce your support overhead tremendously.
- connect IO pins to all digital peripheral functions via an internal cross-bar switch, which allows any function to be mapped to any IO pin in software, and dynamically changed in real time if necessary.
this is extremely useful in such pin-limited devices; for examples how to do this, see the NXP LPC1500 or LPC824 microcontrollers (Cortex)
- upgrade flash interface to Quad SPI Flash Interface (SPIFI)
- true hardware I2C port(s)
- 2 or more UARTS, with 9-bit support and auto-direction control for RS-485 drivers, and high baud rates
- fix the RTC
- include a basic audio codec: stereo 16-bit DAC and telephony grade ADC would be sufficient.
- make I/O pins 5V-tolerant
- hotspot function with accounting
- mobile hotspot & *) tethering to the UART ( HSPI .. )
- ap mode, adhoc mode, infrastructure
- wifi bridge transparent ( 192.168.4.1 < - > 192.168.4.254 ... ping, etc )
- port forwarding
- IPV4 & IPV6
- firewall & rules & mac black/white list
*) hot function!
love it, change it or leave it.
Raw (ethernet) sockets or access.
Route packets, e.g. have a PC connected to the internet be able to share that connection to the chip, and from the chip to other devices.
More/easier SPI with DMA (add SPI RAM or NVRAM, talk to SD card, etc.).
Second UART, maybe deeper FIFOs.
PPP over the UART.
"Input Capture" timers (AVR/Arduino - an edge will grab a high speed timer value so you can measure pulses with microsecond accuracy and at high frequencies).
5GHz band - 802.11a / ac.
Maybe the ability to link 2 chips together (maybe via PPP pr something like that over SPI) so that one can be and AP and another a STA like a travel router, or enhance the wifi so it can do multiple roles at the same time (on one channel, see OpenWRT on most SoC routers).
WPS (I know it is hard to secure, but it is a lot easier to just push a button).
Because in many products like rgb-light, if esp8266 has hardware-reset, the light will be flicker, the user may be averse.
If esp just soft-reset,and the gpio remain unchanged,I think that will be very nice!!!
- SW tools (compiler, assembler, debugger etc.) running under Windows (MS-DevStudio plugin?)
- J-tag debugger for debugging firmware
Who is online
Users browsing this forum: No registered users and 5 guests
Newbies Start Here
Are you new to ESP8266?
Unsure what to do?
Dunno where to start?
Start right here!
We also have a RTOS version and a MESH version too!
Complete listing of the official ESP8266 related documentation release by ESPRESSIF!
Must read here!