New FEATURES gathering

[MikeBolton]

A 'built-in' Bonjour / Zeroconf' capability. This is essential if the ESP is ever to be used as a standalone service provider. This seems a very obvious requirement for any IoT device but a glaring omission on the ESP?

[derekh]

Overall so far we feel good about ESP8266 and it's s/w. But few things come to mind:

HW:

- can we have 64 bit timer for deep sleep? current 32-bit usec timer is only slight over 1 hour sleep time.

SW:

- please open up source code for your lib. especially those seems (?) to be somehow connected to severs at ESPRESSIF. E.g. OTA functions and IoT functions. Those lib should be made such that users can configure their own servers.

- for smartconfig, there are some security concern discussions on how TI does it. Again, it would be better if source code is available so users can see how it's implemented here.

- we are using setup similar to NodeMCU where there is an external push button to reset/wake up the chip. But it share the same reset pin with deep sleep. When it wakes up from deep sleep, s/w does not seem to tell if it's awaken by push button or timer expires. Can the s/w be modified to read the timer to see if it's really expired and add a new "External_Wakeup" reset code so user can tell exactly why it's awaken?


Thanks!!



-

[javed]

Hi Espressif team,

Great job, I do appreciate the work done so far!
Some suggestions and observations;

3V3 LDO could be integrated into the chip with at least 300mA capability and wide input voltage range
just like TOREX XC6206
http://www.torexsemi.com/products/detail.php?id=368
All IOs should be 5V tolerant for better IOP with other hardware

and

finally, more ADC channels with 12 bit or higher resolution

Thanks,

Keep up the good work

[eriksl]

I vote against 5V tolerance. 5V is hopelessly outdated and obsolete. Just run everything on 3.3V and you're fine.

[rudi]

Hi espressif stuff,

i append my wishes :

real, unchangeable, permanent Chip uid -

txs

best wishes
rudi

[idragoev]

Hi,
how about real time clock?

[MikeBolton]

I know it has been mentioned before (many times) but could I ask again for an alternative to the (very outdated) AT command set.
If the ESP is to be interfaced with any reasonable microcontroller, it needs a simple, fast, binary scheme, preferably via the SPI as this can be faster with a MCU than a USART. Instead of the long winded AT commands, can we have single byte instructions (255 possibles) and no ASCII except for 'strings'. Also I see no point in having a very fast WiFi if you can only get the info in and out very slowly !

Clearly the links into the SDK must be there so a 'simple' data transfer scheme should be fairly easy.

Mike Bolton

[geo.espressif]

An snprintf implementation would help a lot.

[chaeplin]

- a api to prevent connecting to OPEN AP
- a api to get the encryption type of the current network

[eriksl]

I know it has been mentioned before (many times) but could I ask again for an alternative to the (very outdated) AT command set.
If the ESP is to be interfaced with any reasonable microcontroller, it needs a simple, fast, binary scheme, preferably via the SPI as this can be faster with a MCU than a USART. Instead of the long winded AT commands, can we have single byte instructions (255 possibles) and no ASCII except for 'strings'. Also I see no point in having a very fast WiFi if you can only get the info in and out very slowly !

Agreed.

But even better, just dump the whole standard software and create your own binary interface