MCHPFSUSB v2.5 Released

I was pretty excited when I read this post...
 
...  Until I looked at the release notes.
 
How come only 3 of the 11 USB host examples are supported on the PIC32 USB Starter Kit?
 
Are these coming, or is PIC32 not really the way to go for USB Host applications?
When I went looking for a USB Host platform a few months back it seemed like PIC32 was the direction Microchip was going.
 
ps: If you are looking for a killer example to code for PIC32, consider a USB HOST that can read a PSP or Logitech game controller.
 
Thanks.
Phil.

Thanks for the info.
 
Although the USB Starter board is short on hardware, it does have a pretty capable USB debugger which is good for basic diagnostics and testing.
 
I wanted to see what it would take to get a USB host up and running (as a bare minimum), but I really don't need a fancy display. 
I can just use printfs to verify functionality.  The odd LED would also help.
 
I don't find it easy to adapt the code from different platforms, so having a canned HOST application TARGETED for the Starter board is where I needed to start.
 
Some of the Starter Kit applications seem to be ported from the Pic24, with the intent to switch between either uart2 or USB debug, but it's not quite there yet....  It took some creative juggling.
 
I was hoping that would be more turnkey on the latest release.
 
Bottom line....
 
If you're going to sell a product and call it the PIC32 Starter Board...
   expect that people will buy it, with the expectation of  being able to "get started" with it :)
 
I'll keep plugging away....   
 
 
 
 
 
 

A few very basic questions: Does the audio Midi sample code supports real-time audio input from USB? If not, is there any existing microchip pic18 sample codes that support real-time audio input from USB? I am thinking along the line of building a USB microphone...

Thank you
sj

Sorry, missed that Phillbot had asked specifically about the PIC32 Starter Kit Support

I'm seeing exactly the same situation here with attaching a flash drive.  From the debugging I have done, I can see that interrupts are turned off right before it tells me Host Reset complete (expected behavior) in _USB1Interrupt with this line

             numTimerInterrupts--;
             if (numTimerInterrupts == 0)
             {
                 // Turn off the timer interrupt.
                 U1OTGIEbits.T1MSECIE = 0;
 
                 // Advance to the next state.  We can do this here, because the only time
                 // we'll get a time interrupt is while we are in one of the holding states.
                 _USB_SetNextSubSubState();
             }
 

So far so good.  Now subsequently it calls USBHostMSDInitialize when it recognizes that it has the drive and in that code when it goes to request the LUN you see this code:

                             // Initiate the request to get the max LUN.  If we can't initiate the request,
                             // then we can't enumerate the device.
                             errorCode = USBHostIssueDeviceRequest( deviceInfoMSD[device].deviceAddress,
                                     USB_SETUP_DEVICE_TO_HOST | USB_SETUP_TYPE_CLASS | USB_SETUP_RECIPIENT_INTERFACE,
                                     USB_MSD_GET_MAX_LUN, 0, deviceInfoMSD[device].interface, 1, deviceInfoMSD[device].blockData,
                                     USB_DEVICE_REQUEST_GET, deviceInfoMSD[i].clientDriverID );
 

So this code looks to be reasonable, BUT if you pay attention to the last parameter, you will notice that it uses i instead of device to index the deviceInfoMSD array.  So if you change that code to be:

                              // Initiate the request to get the max LUN.  If we can't initiate the request,
                              // then we can't enumerate the device.
                              errorCode = USBHostIssueDeviceRequest( deviceInfoMSD[device].deviceAddress,
                                      USB_SETUP_DEVICE_TO_HOST | USB_SETUP_TYPE_CLASS | USB_SETUP_RECIPIENT_INTERFACE,
                                      USB_MSD_GET_MAX_LUN, 0, deviceInfoMSD[device].interface, 1, deviceInfoMSD[device].blockData,
                                      USB_DEVICE_REQUEST_GET, deviceInfoMSD[device].clientDriverID );
  

you should get better behavior

Hi all,
I'm trying to compile the USB MSD on SDCard for a PIC18F4550.
I'm using the "USB Device - Mass Storage - SD Card reader" example (found with "Microchip Application Libraries v2009-08-31") configured for a FSUSB PICDEM board, but I'm not able to compile it(I'm using mcc18 v3.34).

The first error was that the define of GetInstructionClock() and GetSystemClock() was not present in "HardwareProfile.h" nor "HardwareProfile - PICDEM FSUSB.h".

Once fixed this issue (added the defines in "HardwareProfile - PICDEM FSUSB.h") the problem was that all the define for SPI was not present (eg: SD_CS, SPICON1 etc.).

I added the defines to "HardwareProfile - PICDEM FSUSB.h" but the project still don't buil because of sintax error on "usb_ch9.h" (mcc18 compiler don't recognize __attribute__ ((packed)) on typedef struct definition). I removed every __attribute__ ((packed)) from the include file and still don't compile because of syntax error in the following line code:

extern CLIENT_DRIVER_TABLE usbMediaInterfaceTable;  // This table contains the initialization

in "usb_host_msd.c" source file

Before I spend other hours trying to compile I would like to know if there's anybody compiled the project and if I'm wrong in anything.

The sad thing is that previous version of MCHPUSB Framework (v2.3) worked fine on PIC18F4550 (both on Proteus simulator and phisical board).

My question is: Microchip don't debug new libraries any more?

Years ago I did choise Microchip because of tons of free example code and application library found on Microchip homepage, but some of the last releases (both software and silicon) are really bugged. I hope Microchip fix early most of the bugs present on library and silicon devices because I would not to learn about another brand of microcontroller (compiler, libraries and devices).

Hi Hopefully in right place I am posting this issue

I am stuck with this task ....
I have simple programm with USB FW 1.3 and is working fine, but when I am trying to do the same using USB FW 2.5 something is rong and I can't figure it out what.
Mainly something is wrong with EP02 activation or definitions or something else.
This is my USB FW 1.3 code

/* Configuration 1 Descriptor */
 CFG01=
 {
     /* Configuration Descriptor */
     sizeof(USB_CFG_DSC),    // Size of this descriptor in bytes
     DSC_CFG,                // CONFIGURATION descriptor type
     sizeof(cfg01),          // Total length of data for this cfg
     1,                      // Number of interfaces in this cfg
     1,                      // Index value of this configuration
     0,                      // Configuration string index
     _DEFAULT,               // Attributes, see usbdefs_std_dsc.h
     50,                     // Max power consumption (2X mA)
     
     /* Interface Descriptor */
     sizeof(USB_INTF_DSC),   // Size of this descriptor in bytes
     DSC_INTF,               // INTERFACE descriptor type
     0,                      // Interface Number
     0,                      // Alternate Setting Number
     3,                      // Number of endpoints in this intf
     0x00,                   // Class code
     0x00,                   // Subclass code
     0x00,                   // Protocol code
     0,                      // Interface string index
     
     /* Endpoint Descriptors */
     sizeof(USB_EP_DSC),DSC_EP,_EP01_OUT,_INT,USBGEN_EP_SIZE,32,
     sizeof(USB_EP_DSC),DSC_EP,_EP01_IN,_INT,USBGEN_EP_SIZE,32,
 	sizeof(USB_EP_DSC),DSC_EP,_EP02_IN,_INT,USBINT_EP_SIZE,32
 };

and this is my USB FW 2.5 endpoints config

/* Configuration 1 Descriptor */
 ROM BYTE configDescriptor1[]={
     /* Configuration Descriptor */
     0x09,//sizeof(USB_CFG_DSC),    // Size of this descriptor in bytes
     USB_DESCRIPTOR_CONFIGURATION,                // CONFIGURATION descriptor type
     0x20,0x00,            // Total length of data for this cfg
     1,                      // Number of interfaces in this cfg
     1,                      // Index value of this configuration
     0,                      // Configuration string index
     _DEFAULT | _SELF,               // Attributes, see usb_device.h
     50,                     // Max power consumption (2X mA)
 							
     /* Interface Descriptor */
     0x09,//sizeof(USB_INTF_DSC),   // Size of this descriptor in bytes
     USB_DESCRIPTOR_INTERFACE,               // INTERFACE descriptor type
     0,                      // Interface Number
     0,                      // Alternate Setting Number
     4,                      // Number of endpoints in this intf
     0xFF,                   // Class code
     0xFF,                   // Subclass code
     0xFF,                   // Protocol code
     0,                      // Interface string index
     
     /* Endpoint Descriptor */
     0x07,                       /*sizeof(USB_EP_DSC)*/
     USB_DESCRIPTOR_ENDPOINT,    //Endpoint Descriptor
     _EP01_OUT,                  //EndpointAddress
     _BULK,                       //Attributes
     USBGEN_EP_SIZE,0x00,        //size
     1,                         //Interval
     
     0x07,                       /*sizeof(USB_EP_DSC)*/
     USB_DESCRIPTOR_ENDPOINT,    //Endpoint Descriptor
     _EP01_IN,                   //EndpointAddress
     _BULK,                       //Attributes
     USBGEN_EP_SIZE,0x00,        //size
     1,							//Interval
 
     0x07,                       /*sizeof(USB_EP_DSC)*/
     USB_DESCRIPTOR_ENDPOINT,    //Endpoint Descriptor
     _EP02_OUT,                   //EndpointAddress
     _INT,                       //Attributes
     USBINT_EP_SIZE,0x00,        //size
     1,                          //Interval 
     
 	0x07,                       /*sizeof(USB_EP_DSC)*/
     USB_DESCRIPTOR_ENDPOINT,    //Endpoint Descriptor
     _EP02_IN,                   //EndpointAddress
     _INT,                       //Attributes
     USBINT_EP_SIZE,0x00,        //size
     1                          //Interval                          
 };

and EP activation

void USBCBInitEP(void)
 {
     USBEnableEndpoint(USBGEN_EP_NUM,USB_OUT_ENABLED|USB_IN_ENABLED|USB_HANDSHAKE_ENABLED|USB_DISALLOW_SETUP);
     USBGenericOutHandle = USBGenRead(USBGEN_EP_NUM,(BYTE*)&OUTPacket,USBGEN_EP_SIZE);
     USBEnableEndpoint(USBINT_EP_NUM,USB_OUT_ENABLED|USB_IN_ENABLED|USB_HANDSHAKE_ENABLED|USB_DISALLOW_SETUP);
     USBGenericOutHandle = USBIntRead(USBINT_EP_NUM,(BYTE*)&OUTPacket,USBINT_EP_SIZE);    
 }

Can anybody kindly halp me where I am doing something not right, please.

Thanks
Marcin

You are not stupid!
Just download the Microchip Application Libraries installer (zip).
Install it and you'll have the MCHPFSUS v.2.6 (newest one) and all Microchip Libraries (Graphics, TCP IP .....) available.
So, it's now a kind of All-in-one!

On a related note, is there any file - anywhere - that documents what has been changed / bugs fixed in each new version of the framework? The 2.6 download has a "Migration guide" section and bullet-point list of new demos/stuff added to the download, but where is the file that tells me if the 2.6 framework fixes any of the specific bugs I've been encountering in 2.4, or whether it's worthwhile to spend all day migrating my project to the new version, or else, the specific fixes I could apply with less invasive surgery?