Search found 481 matches
- Wed Jun 26, 2013 1:36 am
- Forum: V-USB
- Topic: USB_CFG_HAVE_INTRIN_ENDPOINT3 set to 0 gives errors
- Replies: 1
- Views: 3789
USB_CFG_HAVE_INTRIN_ENDPOINT3 set to 0 gives errors
Can anyone tell me why setting USB_CFG_HAVE_INTRIN_ENDPOINT3 to 0 gives the below warnings? I'm also told the compile failed but I have no errors? I do not use a 3rd but it had to be set to 1 to ovoid this crazy what not. is it needed because I use an out pipe? note: some warnings do not apply. Warn...
- Tue Jun 25, 2013 4:53 pm
- Forum: V-USB
- Topic: Endless loop. usbInterruptIsReady3() usbSetInterrupt3()
- Replies: 17
- Views: 14492
Re: Endless loop. usbInterruptIsReady3() usbSetInterrupt3()
ok well this is how I would do it but yes you would loose 8 ms here. EDIT : ( ok I see you are doing this here gamepad_report_1.report_id=1; ) then see comment below. usbSendHidReport((void *)&gamepad_report_1, sizeof(gamepad_report_1), 1); usbSendHidReport((void *)&gamepad_report_1, sizeof(...
- Tue Jun 25, 2013 4:43 pm
- Forum: V-USB
- Topic: Endless loop. usbInterruptIsReady3() usbSetInterrupt3()
- Replies: 17
- Views: 14492
Re: Endless loop. usbInterruptIsReady3() usbSetInterrupt3()
Ok well I downloaded you files and you didnt have the set to 1? Update your zip file so we can help you better. btw: you dont see to use ENDPOINT3 to do this? All you need to do is change the report id in your out going packets. Is there a reason you are trying to do this on its own pipe? Speed mayb...
- Tue Jun 25, 2013 4:36 pm
- Forum: V-USB
- Topic: Endless loop. usbInterruptIsReady3() usbSetInterrupt3()
- Replies: 17
- Views: 14492
Re: Endless loop. usbInterruptIsReady3() usbSetInterrupt3()
You didnt set the 3rd enpoint in config? #define USB_CFG_HAVE_INTRIN_ENDPOINT3 0 /* Define this to 1 if you want to compile a version with three endpoints: The * default control endpoint 0, an interrupt-in endpoint 3 (or the number * configured below) and a catch-all default interrupt-in endpoint as...
- Tue Jun 25, 2013 4:22 pm
- Forum: V-USB
- Topic: Endless loop. usbInterruptIsReady3() usbSetInterrupt3()
- Replies: 17
- Views: 14492
Re: Endless loop. usbInterruptIsReady3() usbSetInterrupt3()
I'm confused by "Code is compiling without errors." do you mean the suggestion fixed the issue, or just that it compiles and you still have the endless loop?
- Tue Jun 25, 2013 3:58 pm
- Forum: V-USB
- Topic: Not understanding usbFunctionInterrupt()
- Replies: 1
- Views: 3333
Re: Not understanding usbFunctionInterrupt()
If you have one endpoint and the default use usbSetInterrupt()
If you have two endpoint and the default use usbSetInterrupt3()
sorry I dont recall what usbFunctionInterrupt was for i'll report back if I recall.
If you have two endpoint and the default use usbSetInterrupt3()
sorry I dont recall what usbFunctionInterrupt was for i'll report back if I recall.
- Tue Jun 25, 2013 3:56 pm
- Forum: V-USB
- Topic: Endless loop. usbInterruptIsReady3() usbSetInterrupt3()
- Replies: 17
- Views: 14492
Re: Endless loop. usbInterruptIsReady3() usbSetInterrupt3()
your not polling? while (!usbInterruptIsReady()) usbPoll(); usbSendHidReport((void *)&gamepad_report_1, sizeof(gamepad_report_1)); while (!usbInterrup3tIsReady()) usbPoll(); //just a guess on the name here usbInterrup3tIsReady may not be the right name. usbSendHidReport3((void *)&gamepad_rep...
- Tue Jun 25, 2013 3:51 pm
- Forum: V-USB
- Topic: HID keys port problem
- Replies: 1
- Views: 3541
Re: HID keys port problem
I think d+ needs to go to an int pin. Other then that they should work on any pin. see in code Please note that D+ must also be connected * to interrupt pin INT0! # define USB_CFG_IOPORTNAME D /* This is the port where the USB bus is connected. When you configure it to * "B", the registers...
- Tue Jun 25, 2013 3:43 pm
- Forum: V-USB
- Topic: HID Faster Transfer Rate
- Replies: 2
- Views: 7090
Re: HID Faster Transfer Rate
I'm after the same thing http://forums.obdev.at/viewtopic.php?f=8&t=8493 From the SO page I think he is claiming that he stole more bandwidth from one of the pipes. I will look in to that but I dont think its possible with v-usb. I think his reference to set_report is just setting the report typ...
- Tue Jun 25, 2013 3:38 pm
- Forum: V-USB
- Topic: timer polling
- Replies: 1
- Views: 3571
Re: timer polling
I think v-usb just uses the interrupts for timing and the poll depends strictly on the function usbInterruptIsReady.
Code: Select all
while ( !usbInterruptIsReady() ) //when not ready you must poll
{
usbPoll();
}
//pulling has stopped tiuem to send
usbSetInterrupt( reportBuffer, 8);- Tue Jun 25, 2013 3:31 pm
- Forum: V-USB
- Topic: HID Report for custom hardware
- Replies: 1
- Views: 3162
Re: HID Report for custom hardware
1) guessing the buttons and Encoder are input you want to send to the host and you need the host to turn on your device leds? Normally to commune from host to device you need to use the vender specific feature. I never used that before but it requires a driver. For the descriptor I'd use the HID gam...
- Mon Jun 24, 2013 7:07 pm
- Forum: V-USB
- Topic: poll timing
- Replies: 1
- Views: 3167
Re: poll timing
Ok just saw something in my code I didnt see the first go. I'm set to 10 in config but I my descriptor I have this USBDESCR_ENDPOINT, /* descriptor type = endpoint */ //0x81, /* IN endpoint number 1 */ 0x81, // bulk IN endpoint number 1 0x03, /* attrib: Interrupt endpoint */ 8, 0, /* maximum packet ...
- Sun Jun 16, 2013 1:10 am
- Forum: V-USB
- Topic: poll timing
- Replies: 1
- Views: 3167
poll timing
Trying to tweak poll timing a bit here. I'm set to 10ms in config So I normally do this while (!usbInterruptIsReady()){usbPoll(); } usbSetInterrupt((void *)&reportBuffer + 0, ; while (!usbInterruptIsReady()){usbPoll(); } usbSetInterrupt((void *)&reportBuffer + 8, 5); If I do it one like whil...
- Thu Jun 13, 2013 1:45 pm
- Forum: V-USB
- Topic: clocking my usb pulls
- Replies: 2
- Views: 3802
Re: clocking my usb pulls
I was looking for a software solution using a watchdog or something.
- Wed Jun 12, 2013 10:29 pm
- Forum: V-USB
- Topic: multiple ADC channels
- Replies: 8
- Views: 8619
Re: multiple ADC channels
yeah that is because your data reader needs calibrating.
example
reportBuffer[1]= (read_adc(0)/3 + 200);//pc0 : this is some extreme math
You have to now do your own math. Maybe just - 50 from the result ( only a guess ) you'll get it.
example
reportBuffer[1]= (read_adc(0)/3 + 200);//pc0 : this is some extreme math
You have to now do your own math. Maybe just - 50 from the result ( only a guess ) you'll get it.