1. 05 Apr, 2019 1 commit
    • Natalia's avatar
      I2C sw driver with support of multiple buses, Slow, Fast, FastPlus, and... · ab61e9c0
      Natalia authored
      I2C sw driver with support of multiple buses, Slow, Fast, FastPlus, and user-defined speed selection (#2465)
      
      * I2C driver speed-up, i2c.SLOW, i2c.FAST and user-defined speed selection
      
      * - Multiple buses (up to 10) with different speeds on each bus
      - Standard(Slow, 100kHz), Fast(400kHz) and FastPlus(1MHz) modes or an 
      arbitrary clock speed
      - Sharing SDA line over multiple I²C buses to save available pins
      - GPIO16 pin can be used as SCL pin, but it does not support clock 
      stretching and selected bus will be limited to FAST speed.
      
      * Dynamic memory allocation, error checks, simplification, timing tweaks.
      
      * Separated the code of old driver for better compatibility and simplicity
      
      * Change of driver interface
      
      * Add bus status check in setup(); simplify getDC(); remove unnesessary lines in ACK read/write
      
      * Fix for moved doc file and trailing whitespaces
      ab61e9c0
  2. 16 May, 2017 1 commit
  3. 24 Apr, 2017 1 commit
  4. 22 Jul, 2016 1 commit
  5. 26 Feb, 2016 1 commit
    • TerryE's avatar
      Make the wifi.smart functions options and remove wofs and upgrade · 46ea2aa4
      TerryE authored
      AFAIK no one uses the wifi.startsmart() and wifi.stopsmart().  Removing
      them frees up an extra 20-25K of Flash to use as filesystem.  So I have
      added a new config define WIFI_SMART_ENABLE which is enabled by default
      so the default functionality is the same, but if this is commented out
      then this code is omitted.
      
      I have also removed wofs and upgrade from this build as we no longer
      support these.
      46ea2aa4
  6. 12 Dec, 2015 2 commits
    • Johny Mattsson's avatar
      d84a24fc
    • Johny Mattsson's avatar
      Cleaned up all uses of INTERNAL_FLASH_START_ADDRESS. · c4e8b04f
      Johny Mattsson authored
      There was only one genuine use of this macro, all other places were
      using it only as a necessary compensation. While this was fine as long as
      it was the first meg of flash which was mapped, it became incorrect and
      quite dangerous whenever this assumption did not hold (such as when
      running from the second slot in an OTA scenario).
      
      The flash API now uses actual addresses, not translated/mapped
      addresses, and the users of this API have been adjusted accordingly.
      This makes the flash API work correctly regardless of what flash mapping
      is in use.
      
      The old macro is still available under the new name
      INTERNAL_FLASH_MAPPED_ADDRESS, and this is used to detect flash writes
      where the source is mapped flash (and thus has to be bounced), and to
      adjust the _flash_used_end linker symbol when used with
      flassh_find_sector() by the filesystem code. The latter usage is not
      OTA-proof, but in an OTA scenario the filesystem needs a fixed location
      anyway and thus would not use this code path.
      c4e8b04f
  7. 15 Mar, 2015 2 commits
  8. 11 Feb, 2015 1 commit
  9. 16 Jan, 2015 1 commit
  10. 30 Dec, 2014 1 commit
  11. 22 Dec, 2014 1 commit