pfalcon/yaota8266

Issues

• ota-server should have own settings for WiFi params

  #13 opened 8 years ago by pfalcon
  2

• `iram1_0_seg' overflowed after upy and sdk update

  #19 opened 7 years ago by ulno
  4

• Tutorial?!?

  #26 opened 5 years ago by jedie
  1

• Project status?!?

  #25 opened 5 years ago by jedie
  2

• Building combined firmwares (yaota8266+app) undocumented?

  #24 opened 5 years ago by dave2
  0

• Allow user app to signal need to enter an OTA bootloader

  #10 opened 8 years ago by pfalcon
  6

• How do i convert publish key to config.h format?

  #18 opened 7 years ago by p0we7
  2

• How to flash a custom ota firmware?

  #17 opened 8 years ago by riegaz
  0

• WDT Reset Issue While Flashing

  #16 opened 8 years ago by dj095
  3

• UDP datagram size issues

  #15 opened 8 years ago by pfalcon
  0

• Allow to manage bootloader params "at use time", without recompilation

  #14 opened 8 years ago by pfalcon
  1

• ota_client.py: Crypto package is unnecessarily imported

  #12 opened 8 years ago by dpgeorge
  1

• boot8266 user_config.h is missing

  #11 opened 8 years ago by dpgeorge
  1

• boot8266 should minimize any delays when waking from deep sleep

  #3 opened 8 years ago by pfalcon
  1

• Baud rate setting in boot8266 is not ideal

  #9 opened 8 years ago by pfalcon
  0

• boot8266 on power-up goes into OTA mode

  #1 opened 8 years ago by pfalcon
  7

• Hardware reliability issues

  #7 opened 8 years ago by pfalcon
  1

• boot8266, etc. use default baud rate (74880)

  #2 opened 8 years ago by pfalcon
  2

• ota-server is missing config.h file

  #4 opened 8 years ago by dpgeorge
  2

• "AES encryption" is broken

  #6 opened 8 years ago by pfalcon
  2

• Allow OTA to happen in "canned" mode

  #5 opened 8 years ago by pfalcon
  1

• Flashing yaota8266.bin to clean flash leads to bootloop

  #8 opened 8 years ago by pfalcon
  0