Skip to content
Snippets Groups Projects
  1. Mar 01, 2018
  2. Feb 28, 2018
  3. Feb 27, 2018
    • Beat Küng's avatar
      logger: fix potential semaphore counter overflow · 40675bd1
      Beat Küng authored
      When the timer callback is called at a higher rate than the logger can
      execute the main loop (which is never the case under normal conditions),
      the semaphore counter will increase unbounded, and eventually lead to
      an assertion failure in NuttX.
      The maximum semaphore counter is 0x7FFF, and when the logger runs at
      default rate (3.5ms), the logger task must be blocked for 0x7FFF*3.5/1000
      = 114 seconds continuously for an overflow to happen.
      
      I see 2 cases where that could happen:
      - the logger execution blocks somehow, or busy-loops in an inner loop
      - a higher-prio task runs busy and hogs the CPU over a long period of time
      40675bd1
    • Beat Küng's avatar
      hardfault_log: fix comment · 17cb5c4d
      Beat Küng authored
      17cb5c4d
    • Roman's avatar
      49e349c7
  4. Feb 26, 2018
  5. Feb 25, 2018
  6. Feb 24, 2018
  7. Feb 23, 2018
  8. Feb 22, 2018
Loading