1. 20 Jul, 2017 1 commit
    • Paul Molloy's avatar
      Mostly handling first request from the host to get device descriptor. · da3c3a73
      Paul Molloy authored
      Couldn't figure out why the second IN packet wasn't getting sent.
      The host requests 16KBytes worth of data when it makes it's first get
      device descriptor request.  HOWEVER, it sends a STATUS packet immediately
      after receiving the first IN stage.  The stm32 ref manual recommends
      STALLing all xfrs in the opposite direction of current transfer.  But that
      breaks things preventing the host from telling the device to stop talking.
      So still need to add that fix but everything looks good for the first data
      stage when using logic analyzer.
      Current build added support for devices which require external xtals for
      USB via define statements.  Also setting flash/sram size to 32KB/6KB to
      support smaller devices.  Adding include files for other devices, guess
      030 is pretty worthless considering it doesn't have USB...
      Added "make program" support to make file.  ST-LINK_CLI.exe must be in
      path variable, only works on windows for now..
  2. 15 Jul, 2017 1 commit
  3. 13 Jul, 2017 1 commit
  4. 06 Mar, 2017 1 commit
    • Paul Molloy's avatar
      Have things finally working with switch input and LED outputs. · 22a17230
      Paul Molloy authored
      Issue was due to messed up SRAM define in linker script.  IDK what
      datasheet I was reading..  But I had the location and size completely
      wrong.  That caused any access of SRAM to cause a hardfault of course.
      First happening when popping anything to the stack.  Which also explains
      why I couldn't look at the stack to figure out the last called instruciton
      to point to where the issue was...
      copied stm32f0xx_*.h files over from STM32F0xx_StdPeriph_Driver/inc dir
  5. 23 Jan, 2017 1 commit
  6. 22 Jan, 2017 1 commit