Skip to content
  1. Jun 04, 2016
  2. Jun 01, 2016
  3. May 31, 2016
  4. May 30, 2016
  5. May 29, 2016
    • Gregory Nutt's avatar
      Merged in ziggurat29/nuttx/stm32l4_i2c_lcd_mjkdz_001 (pull request #35) · 22044edd
      Gregory Nutt authored
      correct bugs and add enhancements to pcf8574 lcd backpack driver
      22044edd
    • ziggurat29's avatar
      fleshed out rest of fileops interface; read now takes into consideration... · bb7a5796
      ziggurat29 authored
      fleshed out rest of fileops interface; read now takes into consideration current file position (so the display can be read in multiple operations, and indiate EOF correctly), seek (really just to facilitate rewind), and unlink (to facilitate dropping from system at runtime).
      bb7a5796
    • Manuel Stühn's avatar
    • Gregory Nutt's avatar
      i.MX6: Update ECSPI header file · 815bea77
      Gregory Nutt authored
      815bea77
    • ziggurat29's avatar
      correct logic hazard in latch and load nybble; was transitioning control lines... · 4643fcdf
      ziggurat29 authored
      correct logic hazard in latch and load nybble; was transitioning control lines at the same time as enable, causing spurious behaviour on less-tolerant displays
      
      improve timing parameters in init sequences for better display compatibility
      
      correct (row,col) -> address calculation; affects 4-line displays
      
      update comments in header and readme
      4643fcdf
    • Gregory Nutt's avatar
      Stefan Kolb's change to the SAMV7 Oneshot Timer (commit... · fa10927d
      Gregory Nutt authored
      Stefan Kolb's change to the SAMV7 Oneshot Timer (commit d44ecbcf) should also be applied to the SAM3/4 oneshot time since the drivers are identical.  Here are the commit commits from Stefan's original change:
      
      "This is a fix to a problem in the handling of the oneshot timer. Due to a wrong assumption concerning the behavior directly after the start of the timer/counter the function sam_oneshot_cancel(…) calculates the wrong remaining time. The code assumes that the counter register is zero directly after the start of the timer, but this is not true. To start the time/counter a software trigger is invoked, this trigger starts the timer/count and sets the counter register to zero, but the reset of the counter register is not performed instantly. According to the datasheet: “The counter can be reset by a trigger. In this case, the counter value passes to zero on the next valid edge of the selected clock.” Thus the counter is set to zero between 0 and USEC_PER_TICK microseconds after the clock was started.
      
      "In my fix I use the freerun count value to determine if at least one tick passed since the start of the timer and thus if the value of the oneshot counter is correct. I also tried to use the function up_timer_gettime(…) to achieve this but, at least if compiled with no optimization the problem vanishes without using the value of the function, the function call takes too long.
      
      "Another problem treated in the fix is that if the oneshot timer/counter is canceled, we only know the remaining time with a precision of USEC_PER_TICK microseconds. This means the calculated remaining time is between 0 and USEC_PER_TICK microseconds  too long. To fix this I subtract one tick if the calculated remaining time is greater than one tick and otherwise set the remaining time to zero. By doing so the measured times are much more precise as without it."
      fa10927d
    • Gregory Nutt's avatar
      Cosmetic fix to spacing · 9071a22c
      Gregory Nutt authored
      9071a22c
  6. May 28, 2016
  7. May 27, 2016