You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to see if I can use TinyUSB for my project, which is a hypervisor microkernel built from scratch that executes on bare metal consumer PCs (alongside the guest operating systems (VMs) below it). What I'm trying to do is to create a logging/debugging transport via USB that goes from the microkernel to an external device connected via a male-to-male USB cable.
Upon reading the Getting Started page for TinyUSB projects, I have found that two macro definitions are required by the tusb_config.h header which seem to be problematic. For CFG_TUSB_OS I'm aware I can specify that there is no underlying OS via OPT_OS_NONE, but for CFG_TUSB_MCU I'm uncertain what kind of option to specify. I believe this may relate to the supported devices list, along with some of the compilation options for specifying the build board; all of which is leading me to believe this type of configuration won't be possible with TinyUSB.
Would anybody more knowledgeable on the subject be willing to lend some guidance as for whether or not I should continue with TinyUSB or look elsewhere for my needs?
Thank you for your time :)
Edit:
I have retroactively found a related question from around 3 years ago which seeks out some of the same guidance here: #987
Still curious if there have been any developments in this area that would address both issues, or if one would still need to add their own board configuration to get TinyUSB working for this purpose.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello.
I'm trying to see if I can use TinyUSB for my project, which is a hypervisor microkernel built from scratch that executes on bare metal consumer PCs (alongside the guest operating systems (VMs) below it). What I'm trying to do is to create a logging/debugging transport via USB that goes from the microkernel to an external device connected via a male-to-male USB cable.
Upon reading the Getting Started page for TinyUSB projects, I have found that two macro definitions are required by the
tusb_config.h
header which seem to be problematic. ForCFG_TUSB_OS
I'm aware I can specify that there is no underlying OS viaOPT_OS_NONE
, but forCFG_TUSB_MCU
I'm uncertain what kind of option to specify. I believe this may relate to the supported devices list, along with some of the compilation options for specifying the build board; all of which is leading me to believe this type of configuration won't be possible with TinyUSB.Would anybody more knowledgeable on the subject be willing to lend some guidance as for whether or not I should continue with TinyUSB or look elsewhere for my needs?
Thank you for your time :)
Edit:
I have retroactively found a related question from around 3 years ago which seeks out some of the same guidance here: #987
Still curious if there have been any developments in this area that would address both issues, or if one would still need to add their own board configuration to get TinyUSB working for this purpose.
Beta Was this translation helpful? Give feedback.
All reactions