1. 06 May, 2017 1 commit
  2. 02 Mar, 2017 2 commits
  3. 06 Feb, 2017 1 commit
    • Damien George's avatar
      stmhal: Add pyb.fault_debug() function, to control hard-fault behaviour. · 27c149ef
      Damien George authored
      This new function controls what happens on a hard-fault:
      - debugging disabled: board will do a reset
      - debugging enabled: board will print registers and stack and flash LEDs
      
      The default is disabled, ie to do a reset.  This is different to previous
      behaviour which flashed the LEDs and waited indefinitely.
      27c149ef
  4. 27 Jan, 2017 1 commit
    • Damien George's avatar
      stmhal: Convert to use VFS sub-system and new ooFatFs component. · 84c614e7
      Damien George authored
      This patch makes the following configuration changes:
      - MICROPY_FSUSERMOUNT is disabled, removing old mounting infrastructure
      - MICROPY_VFS is enabled, giving new VFS sub-system
      - MICROPY_VFS_FAT is enabled, giving uos.VfsFat type
      - MICROPY_FATFS_OO is enabled, to use new ooFatFs lib, R0.12b
      
      User facing API should be almost unchanged.  Most notable changes are
      removal of os.mkfs (use os.VfsFat.mkfs instead) and pyb.mount doesn't
      allow unmounting by passing None as the device.
      84c614e7
  5. 21 Oct, 2016 1 commit
    • Damien George's avatar
      py: Be more specific with MP_DECLARE_CONST_FUN_OBJ macros. · 4ebdb1f2
      Damien George authored
      In order to have more fine-grained control over how builtin functions are
      constructed, the MP_DECLARE_CONST_FUN_OBJ macros are made more specific,
      with suffix of _0, _1, _2, _3, _VAR, _VAR_BETEEN or _KW.  These names now
      match the MP_DEFINE_CONST_FUN_OBJ macros.
      4ebdb1f2
  6. 14 Oct, 2016 1 commit
  7. 21 Sep, 2016 1 commit
  8. 10 Feb, 2016 1 commit
  9. 09 Feb, 2016 1 commit
  10. 22 Dec, 2015 1 commit
    • Damien George's avatar
      stmhal: Add pyb.irq_stats() to get statistics about IRQ calls. · 401af50d
      Damien George authored
      Adds a lot of code, makes IRQs a bit less efficient, but is very useful
      for debugging.  Usage: pyb.irq_stats() returns a memory view that can be
      read and written, eg:
      
          list(pyb.irq_stats())
          pyb.irq_stats()[0]
          pyb.irq_stats()[0] = 0
      
      The patch provides general IRQ_ENTER() and IRQ_EXIT() macros that can be
      modified to provide further IRQ statistics if desired.
      401af50d
  11. 25 Nov, 2015 1 commit
  12. 09 Nov, 2015 1 commit
  13. 19 Oct, 2015 3 commits
  14. 07 Aug, 2015 1 commit
  15. 05 Aug, 2015 2 commits
  16. 29 Jul, 2015 2 commits
  17. 22 Mar, 2015 2 commits
  18. 04 Mar, 2015 2 commits
  19. 13 Feb, 2015 2 commits
  20. 21 Jan, 2015 1 commit
  21. 07 Jan, 2015 1 commit
  22. 01 Jan, 2015 1 commit
  23. 27 Dec, 2014 1 commit
  24. 08 Dec, 2014 1 commit
  25. 30 Nov, 2014 1 commit
  26. 29 Nov, 2014 1 commit
  27. 02 Nov, 2014 1 commit
  28. 22 Oct, 2014 1 commit
  29. 09 Oct, 2014 1 commit
  30. 05 Oct, 2014 2 commits
  31. 04 Oct, 2014 1 commit
    • Damien George's avatar
      stmhal: Allow pyb.freq() function to change SYSCLK frequency. · 24119176
      Damien George authored
      Eg pyb.freq(120000000) sets the CPU to 120MHz.  The frequency can be set
      at any point in the code, and can be changed as many times as you like.
      Note that any active timers will need to be reconfigured after a freq
      change.
      
      Valid range is 24MHz to 168MHz (but not all freqs are supported).  The
      code maintains a 48MHz clock for the USB at all times and it's possible
      to change the frequency at a USB REPL and keep the REPL alive (well,
      most of the time it stays, sometimes it resets the USB for some reason).
      Note that USB does not work with pyb.freq of 24MHz.
      24119176