Arduino for STM32

Serial2 may already be there, trying commenting the definition and rebuild

https://github.com/stm32duino/wiki/wiki ... wareserial

what you have done is probably as 'simple' as it gets. i.e. use software / app on the host to bridge HID to Serial, converting between them. it is probably the way most apps work. for anything more, you would need custom control on the firmware (i.e. your blue pills stm32f103) and the host s/w (i.e....

HID talks to the host, i.e. your PC, it doesn't talk to the other blue pill
if Freejoy is a hid implementation, then it probably can cater for the buttons as part of its hid implementation

i'm not sure what is being done, but it is probably easier to do it as 2 separate devices / sketches. one is just HID the other Serial. 2 blue pills are required. if you are trying to mimic the custom protocol, you may need to go beyond 'simple' HID. it may involve things like using a usb sniffer / ...

i'm not too familiar with atmega328, but I'd give it a try. It seemed you are trying to detect a 'zero crossing' and using that to toggle the pins i.e. triac on or triac off. In practical terms, stm32 timers did not define that trigger point for the timer inputs, it is some voltages (between 0 - vdd...

try a blink sketch firsthand https://github.com/stm32duino/wiki/wiki and later review the API and examples for hardware timer. https://github.com/stm32duino/wiki/wiki/HardwareTimer-library playing with timers is something like MyTim->pause(); MyTim->setMode(channel, TIMER_OUTPUT_COMPARE_PWM1, pin); ...

I'd assume you have already reviewed these: https://www.stm32duino.com/viewtopic.php?f=2&t=301 https://www.stm32duino.com/viewtopic.php?f=2&t=3 and this is the 'formal' core https://github.com/stm32duino/Arduino_Core_STM32 and the wiki is here https://github.com/stm32duino/wiki/wiki first of...

those are HID report descriptors, they are not device descriptors, they are (much) more complicated than simply IN/OUT endpoints. HID works around usage pages and usage (codes), that is nested many levels deeper than just device descriptors and IN/OUT endpoints. even for a com port, i think it is po...

saw this from usb1.1 specs, this is for a keyboard - the leds https://www.usb.org/hid 95 05 Report Count (5), 75 01 Report Size (1), 05 08 Usage Page (Page# for LEDs), 19 01 Usage Minimum (1), 29 05 Usage Maximum (5), 91 02 Output (Data, Variable, Absolute), 95 01 Report Count (1), // padding 75 03 ...

i'm not the author of USB composite, and I had not used it myself. Hence, I won't really know. But lets just say you are using the 'keyboard' as an interface, normally in the 'IN' direction (to host) would be the key codes of key presses. then in the 'OUT' direction (to stm32), it would normally be ...