Thomas Roell

It is a tad compicated. You are supposed to get a IEEE EUI64 for your devices. Then the DevEUI is unique. On the other hand, the "DevEUI" needs to be...

I am still pondering that one. Is it good enough to add 2 APIs: USBDevice.enableHotPlug() USBDevice.disableHotPlug() Idea being that at reset the code detects whether USB is connected or not....

Still toying with that. Key questions: - do you just need a way to say "please keep USB_VBUS detection in STOP mode" - do you need a way to detect...

Mind checking out the code I dropped this evening on github ? USBDevice: bool begin(); void end(); bool attach(); bool detach(); void wakeup(); bool attached(); bool connected(); bool configured(); bool...

A) Yes. If USB_VBUS is present at startup everything works like before. The USB stack is running. Depending upon the timing you might call the USBDevice.onConnect before the USB_VBUS logic...

An alternative scheme would be that "setup()" gets called via "USBDevice.begin()" not not with "USBDevice.attach()". Only when SerialUSB.begin() is called USBDevice.attach() is called from there. This would allow you then...

I need to recheck the code here. I ran into something similar yesterday where the code went throu a suspend/resume sequence, but did not properly restart up SerialUSB (and/or USB/MSC)....

Give me a day or 2. Need to rework some other parts of USB first.

> * It seems that [bdd33df](https://github.com/GrumpyOldPizza/ArduinoCore-stm32l0/commit/bdd33dfcb0bf205eddd3374375f4a42db841e780) removed support for not having an VBUS pin? Was that intentional? I'm working with a board that has no way to detect VBUS (which,...

> Thanks for your quick and detailed response :-) > > > That was intentional. A USB_VBUS pin is required going forward (or for STM32L4/L4+/WB detection via PVM1). > >...