1. 29 Sep, 2014 1 commit
  2. 28 Sep, 2014 1 commit
    • Dave Hylands's avatar
      Fix timer overflow code. · 39296b40
      Dave Hylands authored
      Teensy doesn't need to worry about overflows since all of
      its timers are only 16-bit.
      
      For PWM, the pulse width needs to be able to vary from 0..period+1
      (pulse-width == period+1 corresponds to 100% PWM)
      
      I couldn't test the 0xffffffff cases since we can't currently get a
      period that big in python. With a prescaler of 0, that corresponds
      to a freq of 0.039 (i.e. cycle every 25.56 seconds), and we can't
      set that using freq or period.
      
      I also tested both stmhal and teensy with floats disabled, which
      required a few other code changes to compile.
      39296b40
  3. 25 Sep, 2014 1 commit
  4. 24 Sep, 2014 1 commit
    • Dave Hylands's avatar
      Add pulse_width_percent to teensy. · 53d5fa64
      Dave Hylands authored
      Fix stmhal and teensy print routines to report actual prescaler an period.
      Fix teensy build to use soft-float
      Add USE_ARDUINO_TOOLCHAIN option to teensy build
      53d5fa64
  5. 21 Sep, 2014 1 commit
    • Damien George's avatar
      stmhal: Add pulse_width_ratio to timer channel object. · 0e58c581
      Damien George authored
      This allows to set the pulse width (for PWM mode) as a ratio relative to
      the period of the timer.  Eg, 0.5 is a 50% duty cycle.  You can set the
      ratio in the channel init, or using channel.pulse_width_ratio; the
      latter can also read the pulse width as a ratio.
      0e58c581
  6. 19 Sep, 2014 1 commit
  7. 29 Aug, 2014 1 commit
  8. 13 Aug, 2014 1 commit
  9. 03 Jul, 2014 1 commit
  10. 02 Jul, 2014 1 commit
  11. 30 Jun, 2014 1 commit
  12. 19 Jun, 2014 1 commit
  13. 03 May, 2014 2 commits
  14. 02 May, 2014 1 commit
  15. 26 Apr, 2014 2 commits
  16. 21 Apr, 2014 2 commits
  17. 16 Apr, 2014 1 commit
    • Damien George's avatar
      stmhal: Improve flash storage cache management. · 6d983539
      Damien George authored
      Internal flash used for the filesystem is now written (from the cache)
      only after a 5s delay, or when a file is closed, or when the drive is
      unmounted from the host.  This delay means that multiple writes can
      accumulate in the cache, and leads to less writes to the flash, making
      it last longer.
      
      It's implemented by a high-priority interrupt that takes care of flash
      erase and write, and flushing the cache.
      
      This is still only an interim solution for the flash filesystem.  It
      eventually needs to be replaced with something that uses less RAM for
      the cache, something that can use more of the flash, and something that
      does proper wear levelling.
      6d983539
  18. 15 Apr, 2014 1 commit
  19. 05 Apr, 2014 1 commit
  20. 02 Apr, 2014 1 commit