I am running on a STM32F405 with Cube V1.23.0.I have an HID (actually PID in and out endpoints) device using interrupt transfer for both the out and in messages. This is a High Speed device using the ULPI interface.The out messages has a report type...
I have seen this with the SPI bus 6 months ago. It just just happened with the IIC bus. I am using Cube 1.12.0 and this maybe related to TKube.1 issue "Potential bug in I2C HAL layer (STM32Cube_FW_F4_V1.25.0) in I2C_MemoryTransmit_TXE_BTF() ?".I ha...
IN the function USBD_HID_setup for a class requese I added a case for send report. case HID_REQ_SET_REPORT:
Debug::Instance()->printf(Debug::ALLWAYS, (char *) "Set report %X\n", req->wValue);
Debug::Instance()->printf(Debug::ALLWAYS, ...
I am running interrupt data transfer in HS mode (with ULPI chip, and can do see interrupts at the HS rate of 8kHz). So I can get an HID report of 8 bytes, but I can get above that. I set the USB end point descriptor to 16 was 8. I added one byte to m...
Thanks Jan!That is what I figured, but before I go spend $1000s on a prototype thought I should be sure.I prefer the TIM2_CH1/TIM2_ETR. They are mutually exclusive for the timer since they are both inputs, and I saw a note to that affect somewhere i...
For some reason the picture you [Sara] posted is not showing up, but I can access it from email.I am not sure what you are trying to tell me. That picture (if I understand) says a timer can have 5 pins: _CH1, _CH2, _CH3, _CH4, _ETR. The _CHx can be e...
Could you please point me to the specific paragraph. They documentation specifically states changing from TIM2_CH1/TIM2_ETR to TIM2_CH1_ETR for PA0 and PA5, but left PA15's TIM2_CH1/TIM2_ETR alone. I can find nothing telling me how PA0 and PA5 dif...
