I would like to store some device metadata, like the unique ID or firmware version. While I could just use endpoints for that, they are stored anyway in the USB device config and read when initializing the HostClient. In the HostClient::new_raw_nusb method, I can access the DeviceInfo struct within the closure that picks a device and I use it to extract the information I want. This is a bit hacky and can only be done on startup.
I imagine this design is caused by the generic aspect of Postcard RPC? I guess the metadata would be completely different when using CDC ACM right? If so, I will close the issue as my workaround works, but having it exposed would make life easier
I would like to store some device metadata, like the unique ID or firmware version. While I could just use endpoints for that, they are stored anyway in the USB device config and read when initializing the
HostClient. In theHostClient::new_raw_nusbmethod, I can access theDeviceInfostruct within the closure that picks a device and I use it to extract the information I want. This is a bit hacky and can only be done on startup.I imagine this design is caused by the generic aspect of Postcard RPC? I guess the metadata would be completely different when using CDC ACM right? If so, I will close the issue as my workaround works, but having it exposed would make life easier