2 new importants requirements in AT firmware
2 new importants requirements in AT firmware
Postby phil31 » Thu Nov 13, 2014 9:07 pm
Hello
I would like to request some new and important features in the AT firmware :
- possibility to set up an STATIC IP (and all required others parameters, like gateway .. ).
the DHCP solution is not possible in every situation. some customer don't provide a DHCP server.
- an possibility to enable/disable an hardware handshake feature : RTS/CTS can be mapped on GPIO0/GPIO2 (which are almost available on all modules)
this is really important for some applications which can't parse quickly all data lines, from the ESP8266 chip. without such solution, I lose many message from the chip.
thanks, regards
I would like to request some new and important features in the AT firmware :
- possibility to set up an STATIC IP (and all required others parameters, like gateway .. ).
the DHCP solution is not possible in every situation. some customer don't provide a DHCP server.
- an possibility to enable/disable an hardware handshake feature : RTS/CTS can be mapped on GPIO0/GPIO2 (which are almost available on all modules)
this is really important for some applications which can't parse quickly all data lines, from the ESP8266 chip. without such solution, I lose many message from the chip.
thanks, regards
Re: 2 new importants requirements in AT firmware
Postby phil31 » Sat Nov 29, 2014 8:56 pm
Hi Espressif team,
please, do you plan to add hardware Handshake feature soon, in the official AT commands firmware ?
using GPIO 13 & 15 as RTS / CTS pins ?
thanks
Phil
please, do you plan to add hardware Handshake feature soon, in the official AT commands firmware ?
using GPIO 13 & 15 as RTS / CTS pins ?
thanks
Phil
Re: 2 new importants requirements in AT firmware
Postby phil31 » Tue Dec 02, 2014 4:57 pm
Hi,
please may i expect an answer ?
Is it that I'm the only one who need this feature?
i don't expect so !?? all HOST cpu don't have plenty of SRAM to manage a big buffer (by example to store the full HTML header when a socket is open) before parse all the lines !
so without hardware handshake, we can't use this famous chip to play a web server role...
thanks, regards
please may i expect an answer ?
Is it that I'm the only one who need this feature?
i don't expect so !?? all HOST cpu don't have plenty of SRAM to manage a big buffer (by example to store the full HTML header when a socket is open) before parse all the lines !
so without hardware handshake, we can't use this famous chip to play a web server role...
thanks, regards
-
- Posts: 140
- Joined: Mon Oct 27, 2014 10:40 am
Re: 2 new importants requirements in AT firmware
Postby Espressif_Kelly » Mon Dec 15, 2014 3:20 pm
Dear Sir,
The current SDK supports hardware flow control by default. Please make a try.
Only MTCK(GPIO13) can be reused as UART0 CTS and MTDO(GPIO15) can be reused as UART0 RTS. CTS/RTS can not be swapped to GPIO0/GPIO2.
Please be noted.
Thanks.
The current SDK supports hardware flow control by default. Please make a try.
Only MTCK(GPIO13) can be reused as UART0 CTS and MTDO(GPIO15) can be reused as UART0 RTS. CTS/RTS can not be swapped to GPIO0/GPIO2.
Please be noted.
Thanks.
Re: 2 new importants requirements in AT firmware
Postby bjpirt » Tue Mar 24, 2015 1:10 am
Following up on the first part of the original question; I too would like to be able to disable the DHCP client on the STATION interface and supply a static IP address. It doesn't look like this information gets saved anywhere because when I call wifi_station_dhcpc_stop(), when I restart the DHCP client is back in place.
It would be great if wifi_station_dhcpc_stop() was made persistent and that the ip_info struct was also stored in persistent memory so that it is possible to set up a static IP address
What do the Espressif folks think about this? Am I understanding things correctly?
Cheers,
Ben
It would be great if wifi_station_dhcpc_stop() was made persistent and that the ip_info struct was also stored in persistent memory so that it is possible to set up a static IP address
What do the Espressif folks think about this? Am I understanding things correctly?
Cheers,
Ben
Who is online
Users browsing this forum: No registered users and 188 guests
Login
Newbies Start Here
Are you new to ESP8266?
Unsure what to do?
Dunno where to start?
Start right here!
Latest SDK
Documentation
Complete listing of the official ESP8266 related documentation release by ESPRESSIF!
Must read here!
- All times are UTC+08:00
- Top
- Delete all board cookies
About Us
Espressif Systems is a fabless semiconductor company providing cutting-edge low power WiFi SoCs and wireless solutions for wireless communications and Internet of Things applications. We are the manufacturer of ESP8266EX.