-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
samples:mimxrt1010_evk:samples/subsys/usb/audio: build error no usbd found #25313
Comments
@galak Can we use common node label for the first usb device? diff --git a/boards/arm/mimxrt1010_evk/mimxrt1010_evk.dts b/boards/arm/mimxrt1010_evk/mimxrt1010_evk.dts
index 1f560ec26f..6443883bd7 100644
--- a/boards/arm/mimxrt1010_evk/mimxrt1010_evk.dts
+++ b/boards/arm/mimxrt1010_evk/mimxrt1010_evk.dts
@@ -63,6 +63,6 @@ arduino_serial: &lpuart1 {};
current-speed = <115200>;
};
-&usb1 {
+usbd: &usb1 {
status = "okay";
}; |
This is in line with what I proposed here: |
What is wrong with just |
Since the label is zephyr specific we need to name it as such. |
PR #25495 to address a precursor aspect of this issue (ie, sanitycheck doesn't build anything for these samples). |
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time. |
Either all dts files change name for usbd or this sample will not work. |
@galak, are you suggesting that this sample will need a board specific overlay for the rt1010 similar to nrf overlay? |
I see 2 ways of handling this:
|
I like the second option... seems cleaner (I think). Where does this generic overlay reside? Do you have an example of something like this? |
Look at something like |
Sounds good. |
We will need to add a section in the docs for these zephyr specific node labels to give the specific intent/usage. |
Dev-Review (Sept 10, 2020): No issue w/using a node label for this purpose, just needs a zephyr namespace. (And added to docs) @jfischer-phytec-iot asked about doing something similar for display. Don't see any issue, but asked to work up PR to see specific details. |
If we're going wit this solution (which I find elegant), should we add some way to filter on this for sanitycheck?
|
Since there are thoughts of supporting more than one device controller, and host support is WiP, would "zephyr_usbd0" node label be acceptable? |
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time. |
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time. |
@jfischer-no there seems to be an agreement on how to fix this, could you send a PR? |
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time. |
USB audio class samples are generic and can be built for any board that supports USB device and isochronous endpoints. Add app.overlay that uses aliases and remove board specific overlays. Note: USB audio is still experimental and even though the sample can be built for specific platform, it does not mean that it can be run on it without issues. Fixes: zephyrproject-rtos#25313 Signed-off-by: Johann Fischer <[email protected]>
USB audio class samples are generic and can be built for any board that supports USB device and isochronous endpoints. Add app.overlay that uses aliases and remove board specific overlays. Note: USB audio is still experimental and even though the sample can be built for specific platform, it does not mean that it can be run on it without issues. Fixes: #25313 Signed-off-by: Johann Fischer <[email protected]>
Describe the bug
build error report usbd not found, but usbd is supported on this platform
To Reproduce
Steps to reproduce the behavior:
Expected behavior
can build and run well
Impact
NA
Screenshots or console output
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: