Discuss here different C compiler set ups, and compiling executables for the ESP8266

User avatar
By Lawrence_jeff
#6404
Necromant wrote:Okay, folks. I'm somewhat back after a lengthy timeout. Merged all the pull requests, and have done a little bit of bugfixes, binaries updated.
  • Buildsystem now only uses esptool.py (recent esptool.py with elf2image is a must).
  • esptool.py is now a 'deployment' method consistent with the rest of antares.
  • New command baud (modify serial port(s) speed on the go).

That's part of news. The other part is I've tried running esp8266 and a serial2tcp bridge. To make the long story short - it sucks. lwip is compiled in a weird way that assembles data in big packets, so you when you send a single character via telnet you have to wait for a second or so for it to appear. Working on lwip now.


Do you look at this firmware by chance, I compiled and used it briefly and it seemed to work ok (I certainly didn't notice any delays from typing between a telnet session and a UART at 115200)
https://github.com/beckdac/ESP8266-transparent-bridge
User avatar
By Necromant
#6534
Lawrence_jeff wrote:Do you look at this firmware by chance, I compiled and used it briefly and it seemed to work ok (I certainly didn't notice any delays from typing between a telnet session and a UART at 115200)
https://github.com/beckdac/ESP8266-transparent-bridge


I did. It's unbuffered. Probably okay for 115200, but if you want to go way beyond that - problems might happen. I haven't tried. Yet. Since implementing a bridge would be a simple go when I finish reworking uart driver, it's actually a useful side effect.

Okay, meanwhile, I'm posting another update. This time quite feature-packed:
  • frankenstein now sends it's hostname to DHCP server as DHCP_OPTION_HOSTNAME.
  • A bunch of stability improvements here and there.
  • telnet console available

Yep, you can now telnet into frankenstein shell! By default it's on port 23, but you can change that with environment variables.
    telnet-autostart - Set it to '1' to fire up telnet at boot
    telnet-port - Set port telnet server will run on
    telnet-drop - Timeout (in seconds) for idle clients to get dropped. Set to '-1' to disable.

You can also start/stop the telnet server in runtime using 'telnet start' and 'telnet stop'. To disconnect from telnet server use 'telnet quit'.
telnet server handles only one client. server will drop all other clients after the first one's connected.

Binaries are updated, as usual post about all new wonderful bugs I've added.

P.S. A little bonus to this update
User avatar
By RichardS
#6545 SUGGESTION

Should we start a section in WIKI for documenting [DEV][WiP] Frankenstein firmware for ESP8266???? This is getting to be a lot of info!

Anyone want to step up?

Richard,