HID_Write limitations

[HardWareMan]

Is there any limitations of use HID_Write() procedure when USB_INTERRUPT set to 1?
If I call this procedure inside another interrupt handler, it's hangs somewhere inside (around L_HID_Write500):

[Pelikan]

Здравствуйте HardWareMan,


this is exactly why I use only units of which the source is present.
Please review with my unit.

Peter

[HardWareMan]

this is exactly why I use only units of which the source is present.
Please review with my unit.
Peter

I completely forgot about your module. It is necessary to bring it to working condition and try to use. Thank you for reminding me.

[HardWareMan]

Please review with my unit.
Peter

OK, your unit seems to be working. I call HID_Tx() from interrupt handler and controller didn't hangs. But something wrong with it. Packets reaches the PC host software with lag by one-two calling the HID_Tx(). For example: I call HID_Tx() first time no data appears on PC terminal. Then I call HID_Tx() again and previous sended data appears on PC terminal. What can be wrong with it?

Attach detection, enumeration and all system stuff seems to work excellent.

[filip]

Hi,

Did you try the default UAB Polling example from the compiler, setting the USB_INTERRUPT to 1, and the code got stuck ?
Which MCU are you using ?

Regards,
Filip.

[Pelikan]

Hi HardWareMan

the problem I do not understand.
Can you please give a graphical representation?
( also to my email )

Regards,
Peter