Project:USBGroup/Resources: Difference between revisions

From London Hackspace Wiki
mNo edit summary
No edit summary
Line 2: Line 2:
==General USB Resources.==
==General USB Resources.==
* [http://lvr.com/usb.htm http://lvr.com/usb.htm] is the website of USB Complete author Jan Axelson. A great place to start for anything to do with USB.
* [http://lvr.com/usb.htm http://lvr.com/usb.htm] is the website of USB Complete author Jan Axelson. A great place to start for anything to do with USB.
*  
* [http://www.usbmadesimple.co.uk/ http://www.usbmadesimple.co.uk/] The basics of The USB Protocol.
 
 


==Microchip.==
==Microchip.==
*[http://pwc.theclarkwebsite.com/PIC18F4550usb.php http://pwc.theclarkwebsite.com/PIC18F4550usb.php] How to create a really simple circuit for a PIC18F4550 HID device.
*[http://pwc.theclarkwebsite.com/PIC18F4550usb.php http://pwc.theclarkwebsite.com/PIC18F4550usb.php] How to create a really simple circuit for a PIC18F4550 HID device.
*[http://eegeek.net/content/view/35/32 http://eegeek.net/content/view/35/32] Understanding the Microchip USB Firmware. "''The Microchip USB firmware (for the PICDEM full-speed USB demo board, but used frequently for DIY projects as well) is written and organized in a manner that it is not very easy to just take a quick look and see exactly what's going on.  Everything is arranged across 9 source files, and 15 header files.  There are enough subroutines to make your head spin.  Things are broken down into pretty logical chunks, with an ample amount of commenting accompanying each subroutine, however it's still hard to pick out what is being run, and when.  First off, you need to get an idea of the "core" execution path during normal operation, with the device already enumerated and configured and sitting there running user code and servicing requests.  This description is assuming that the device is running the 'generic' class firmware, as in the Microchip firmware I started from.'' "
*[http://eegeek.net/content/view/35/32 http://eegeek.net/content/view/35/32] Understanding the Microchip USB Firmware. "''The Microchip USB firmware (for the PICDEM full-speed USB demo board, but used frequently for DIY projects as well) is written and organized in a manner that it is not very easy to just take a quick look and see exactly what's going on.  Everything is arranged across 9 source files, and 15 header files.  There are enough subroutines to make your head spin.  Things are broken down into pretty logical chunks, with an ample amount of commenting accompanying each subroutine, however it's still hard to pick out what is being run, and when.  First off, you need to get an idea of the "core" execution path during normal operation, with the device already enumerated and configured and sitting there running user code and servicing requests.  This description is assuming that the device is running the 'generic' class firmware, as in the Microchip firmware I started from.'' "
*[http://www.waitingforfriday.com/index.php/Building_a_PIC18F_USB_device http://www.waitingforfriday.com/index.php/Building_a_PIC18F_USB_device] Building a PIC 18F device.
*[http://www.connectable.org.uk/wp2/?page_id=135 http://www.connectable.org.uk/wp2/?page_id=135] An interesting project using the PIC18F4550.


==Tools.==
==Tools.==

Revision as of 15:29, 1 May 2011

Resources.

General USB Resources.


Microchip.

  • http://pwc.theclarkwebsite.com/PIC18F4550usb.php How to create a really simple circuit for a PIC18F4550 HID device.
  • http://eegeek.net/content/view/35/32 Understanding the Microchip USB Firmware. "The Microchip USB firmware (for the PICDEM full-speed USB demo board, but used frequently for DIY projects as well) is written and organized in a manner that it is not very easy to just take a quick look and see exactly what's going on. Everything is arranged across 9 source files, and 15 header files. There are enough subroutines to make your head spin. Things are broken down into pretty logical chunks, with an ample amount of commenting accompanying each subroutine, however it's still hard to pick out what is being run, and when. First off, you need to get an idea of the "core" execution path during normal operation, with the device already enumerated and configured and sitting there running user code and servicing requests. This description is assuming that the device is running the 'generic' class firmware, as in the Microchip firmware I started from. "
  • http://www.waitingforfriday.com/index.php/Building_a_PIC18F_USB_device Building a PIC 18F device.
  • http://www.connectable.org.uk/wp2/?page_id=135 An interesting project using the PIC18F4550.


Tools.