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
Describe the bug
with 2.14, this example just works
with 2.15, the device appears on usb as an audio device, and apps can play to it, but no sound
To Reproduce
try the example in 2.14 and 2.15 and listen to the headphone output.
Environment (please complete the following information):
vscode on mac m silicon, rt1170 evkb
Additional context
I did a folder compare and even pushed every difference in the .h and .c files from 2.14 onto 2.15. even all the other files (build related) were ensured to be the same aside from path differences as files were reorganized from sdk 2.14 to 2.15
Because of this, I believe the issue lies in the sdk, not in the example, not clear to me yet where.
The text was updated successfully, but these errors were encountered:
west update to 2.14 and get the mentioned example. you will hear audio in the headphone jack of the rt1170 evkb
west update to 2.15, 2.16 or main and you will not hear audio
in all cases, the device will enumerate
it doesn't matter if you delete the example and get fresh when you switch sdk, except for a spelling error issue in 2.14. the result is the same
Aside: it seems debugging the multicore RT MCU with vscode is quite awkward with vscode, is there any documentation or guidance for debugging across cores?
Describe the bug
with 2.14, this example just works
with 2.15, the device appears on usb as an audio device, and apps can play to it, but no sound
To Reproduce
try the example in 2.14 and 2.15 and listen to the headphone output.
vscode on mac m silicon, rt1170 evkb
Additional context
I did a folder compare and even pushed every difference in the .h and .c files from 2.14 onto 2.15. even all the other files (build related) were ensured to be the same aside from path differences as files were reorganized from sdk 2.14 to 2.15
Because of this, I believe the issue lies in the sdk, not in the example, not clear to me yet where.
The text was updated successfully, but these errors were encountered: