USB descriptor

[MaximLiadov]

Have no idea, sorry. I don't use --noinq --target-file. Just --factory-version 15.0 --upgrade -o works fine for me. I would add sudo to every command or switch to Windows if such a bad luck with Linux.

[markp]

I just tried with sw_usb_audio-_sw_9_0_0.zip and XTC 15.3.0:

Ubuntu 24
$ xflash –noinq –factory-version 15.0 –upgrade 0x0530 ./sw_usb_audio/app_usb_aud_xk_316_mc/bin/2AMi8o8xxxxxx/app_usb_aud_xk_316_mc_2AMi8o8xxxxxx.xe -o ~/tmp/x.bin

Win10
>xflash –noinq –factory-version 15.0 –upgrade 0x0530 ./sw_usb_audio/app_usb_aud_xk_316_mc/bin/2AMi8o8xxxxxx/app_usb_aud_xk_316_mc_2AMi8o8xxxxxx.xe -o c:\Users\abc\tmp\x.bin

No issues.

Can you make sure you are running xflash from within a write-able directory - it needs to create temporary files?

[markp]

And make sure on Linux you have followed XTC Linux installation instructions and in the shell, done the step:

source SetEnv

[ratin3@gmail.com]

I dont know where the SetEnv file came from but it had issues - the PATH was not set as absolute, causing some problems (the XTC version in the path was missing). Also I looked up documentation and added XCC_TARGET_PATH=$XMOS_TOOL_PATH/targets and re-built the binaries. WIth that its working as expected, except right now its recognizing the target as XU316-1024-FB265-C32 when I have the XK-316-MC-AB eval board. Not sure if this is right or wrong, cause I think it should be using XS3-UnA-1024-FB265 package (not 100% sure)

[Lucjano0]

I dont know where the SetEnv file came from but it had issues - the PATH was not set as absolute, causing some problems (the XTC version in the path was missing). Also I looked up documentation and added XCC_TARGET_PATH=$XMOS_TOOL_PATH/targets and re-built the binaries. WIth that its working as expected, except right now its recognizing the target as XU316-1024-FB265-C32 when I have the XK-316-MC-AB eval board. Not sure if this is right or wrong, cause I think it should be using XS3-UnA-1024-FB265 package (not 100% sure)

Sounds like you're on the right track with fixing the PATH issue! As for the target, the XU316-1024-FB265-C32 is likely a similar or compatible part, but you're probably correct that it should be using the XS3-UnA-1024-FB265 package for your eval board. It’s worth double-checking the target configuration in your toolchain or verifying the exact part number in the board’s documentation to be sure. Sometimes toolchains default to a close match if the exact target isn’t specified.