Objective Development Forums 2006-12-05T23:37:04+02:00 https://forums.obdev.at/app.php/feed/topic/64 2006-12-05T23:37:04+02:00 2006-12-05T23:37:04+02:00 https://forums.obdev.at/viewtopic.php?t=64&p=303#p303 <![CDATA[Problems getting usbFunctionRead() called]]>
christian wrote:This one is tricky :-)

10: c0 01 00 00 00 00 00 04


The last two bytes here indicate a length of 0x400 = 1024 bytes. That's more than the maximum of 254 which is allowed by AVR-USB.

The driver evaluates only the low byte of the length (since 254 can be expressed in one byte). And the low byte of 0x400 is 0, which indicates a zero sized read.

Simply change the host code to

Code: 

usb_control_msg(hDev,USB_TYPE_VENDOR|USB_RECIP_DEVICE|USB_ENDPOINT_IN,RTEST, 0, 0, buf, 254, 1000);


(assuming that the buffer is always at least 254 bytes in size).

Statistics: Posted by Guest — Tue Dec 05, 2006 11:37 pm

]]> 2006-11-21T19:27:52+02:00 2006-11-21T19:27:52+02:00 https://forums.obdev.at/viewtopic.php?t=64&p=165#p165 <![CDATA[Problems getting usbFunctionRead() called]]>


Code: 

10: c0 01 00 00 00 00 fe 00
sr20: 4b 00 00

So now it works ;-)

Thankyou very much!

Best regards,
Tobias

Statistics: Posted by Guest — Tue Nov 21, 2006 7:27 pm

]]> 2006-11-21T18:59:06+02:00 2006-11-21T18:59:06+02:00 https://forums.obdev.at/viewtopic.php?t=64&p=164#p164 <![CDATA[Problems getting usbFunctionRead() called]]>

10: c0 01 00 00 00 00 00 04


The last two bytes here indicate a length of 0x400 = 1024 bytes. That's more than the maximum of 254 which is allowed by AVR-USB.

The driver evaluates only the low byte of the length (since 254 can be expressed in one byte). And the low byte of 0x400 is 0, which indicates a zero sized read.

Simply change the host code to

Code: 

usb_control_msg(hDev,USB_TYPE_VENDOR|USB_RECIP_DEVICE|USB_ENDPOINT_IN,RTEST, 0, 0, buf, 254, 1000);


(assuming that the buffer is always at least 254 bytes in size).

Statistics: Posted by christian — Tue Nov 21, 2006 6:59 pm

]]> 2006-11-21T18:31:21+02:00 2006-11-21T18:31:21+02:00 https://forums.obdev.at/viewtopic.php?t=64&p=163#p163 <![CDATA[Problems getting usbFunctionRead() called]]>

Code: 

usb_control_msg(hDev,USB_TYPE_VENDOR|USB_RECIP_DEVICE|USB_ENDPOINT_IN,RTEST, 0, 0, buf, sizeof(buffer), 1000);

yields

Code: 

10: c0 01 00 00 00 00 00 04
s20: 4b 00 00

on the serial console with debuglevel=2.

The 's' marks the entry to usbFunctionSetup();

Below is the trace of sending "asdasdasdasd\0".

Code: 

10: 40 02 00 00 00 00 13 00
s13: 61 73 64 61 73 64 61 73
w20: 4b 00 00
13: 64 61 73 64 61 73 64 61
w20: 4b 00 00
13: 73 64 0a
w20: 4b 00 00


Is there more information i should provide?

I get the linker-error about missing the usbFunctionRead() symbol as i should.

Statistics: Posted by Guest — Tue Nov 21, 2006 6:31 pm

]]> 2006-11-21T10:54:43+02:00 2006-11-21T10:54:43+02:00 https://forums.obdev.at/viewtopic.php?t=64&p=156#p156 <![CDATA[Problems getting usbFunctionRead() called]]>
You can verify that usbFunctionRead() is actually linked by changing the name of your function. You should get a linker error when linking.

If that's all OK, please enable debugging by adding -DDEBUG_LEVEL=2 to the compiler command line. This will give more information about data received and actions taken.

Statistics: Posted by christian — Tue Nov 21, 2006 10:54 am

]]> 2006-11-20T17:32:06+02:00 2006-11-20T17:32:06+02:00 https://forums.obdev.at/viewtopic.php?t=64&p=148#p148 <![CDATA[Problems getting usbFunctionRead() called]]>
USB_CFG_IMPLEMENT_FN_READ and USB_CFG_IMPLEMENT_FN_WRITE
are both defined to 1.

The device gets detected without problems.

The codesnippet below is the content of the
callbacks

Code: 

uchar usbFunctionSetup(uchar data[8])
{
 uart_putc('s');
 switch(data[1]){
    case STEST:{
        buffer[0]=1;
        usbMsgPtr=buffer;
        return 1;
    }break;  
    case RTEST:{
        return 0xff; // get usbFunctionRead called;
    }break;
    case WTEST:{
        return 0xff; // get usbFunctionWrite called;
    }break;
 }
}

uchar usbFunctionWrite(uchar* data,uchar len)
{
  uart_putc('w');
  return 1;
}

uchar usbFunctionRead(uchar* data,uchar len)
{
  uart_putc('r');
  return 1;
}




On the client side:

Performing

Code: 

usb_control_msg(hDev,USB_TYPE_VENDOR|USB_RECIP_DEVICE|USB_ENDPOINT_OUT,WTEST, 0, 0, buf, strlen(buffer), 1000);

Results in "sw" in the terminal app and usbFunctionWrite getting called.

Performing

Code: 

usb_control_msg(hDev,USB_TYPE_VENDOR|USB_RECIP_DEVICE|USB_ENDPOINT_IN,STEST, 0, 0, buf, sizeof(buffer), 1000);

Results in "s" in the terminal app and correct data getting returned
to the client app.

Performing

Code: 

usb_control_msg(hDev,USB_TYPE_VENDOR|USB_RECIP_DEVICE|USB_ENDPOINT_IN,RTEST, 0, 0, buf, sizeof(buffer), 1000);

Results in "s" in the terminal app and no usbFunctionRead getting called.
Thus no data is supplied to the client application.

I'm using AVR-USB on an mega8515 with 8kb of external sram.
I thought of usbFunctionRead as a Way to conveniently read the
xmem in larger chunks than 254.
The firmware code contains atm just the xmem initialization, since i am trying to understand where the problem lies.

The usbdriver is from the latest PowerSwitcher zipfile.

Best Regards,
Tobias

Statistics: Posted by Guest — Mon Nov 20, 2006 5:32 pm

]]>