topic Re: xaf_record Example Fails with comp_setup failure in SDK_26_06_00_MIMXRT700-EVK in Other NXP Products

xaf_record Example Fails with comp_setup failure in SDK_26_06_00_MIMXRT700-EVK

suhas1503 — Fri, 31 Jul 2026 11:34:49 GMT

Board: MIMXRT700-EVK

SDK Version: SDK_26_06_00_MIMXRT700-EVK
Example: SDK_26_06_00_MIMXRT700-EVK/mcuxsdk/middleware/cadence/multicore-xaf/examples/xaf_record/cm/
Build Configuration: Default example without modifications

After starting DMIC recording using the shell command: record_dmic en

The DSP reports a component setup failure, preventing the recording pipeline from functioning correctly.

console output

******************************
DSP audio framework demo start
******************************

[CM33 Main] Configure codec

[DSP_Main] Cadence Xtensa Audio Framework
[DSP_Main] Library Name: Audio Framework (Hostless)
[DSP_Main] Library Version: 3.6
[DSP_Main] API Version: 3.4

[DSP_Main] start
[DSP_Main] established RPMsg link
[CM33 Main] DSP image copied to DSP TCM
[CM33 Main][APP_DSP_IPC_Task] start
[CM33 Main][APP_Shell_Task] start

>> record_dmic en
[CM33 CMD] Setting VIT language to en
[DSP_Main] Number of channels 1, sampling rate 16000, PCM width 32
[CM33 CMD] [APP_DSP_IPC_ Task] response from DSP, cmd: 13, error: 0
[DSP Record] Audio Device Ready
[CM33 CMD] DSP DMIC Recording started
[DSP Record] comp_setup failure: 4294967294
[CM33 CMD] To see VIT functionality say wakeword and command
[CM33 CMD] [APP_DSP_IPC_ Task] response from DSP, cmd: 13, error: 4294967295
[CM33 CMD] DSP DMIC Recording started
[CM33 CMD] To see VIT functionality say wakeword and command

Expected Behavior

After executing:

record_dmic en

The DMIC recording pipeline should initialise successfully, allowing audio capture and VIT wake-word detection without any component setup errors.

Actual Behavior

The DSP reports:

[DSP Record] comp_setup failure: 4294967294

followed by an IPC response with:

error: 4294967295

As a result, the recording pipeline does not function as expected.

Request
Could you please help identify the following?

What causes the comp_setup failure, 4294967294, in the default xaf_record example?
Does this indicate a missing DSP component, codec configuration issue, or another initialisation problem?
Is there any known issue or patch for the xaf_record example in SDK 26.06.00?
Are any additional configuration steps required before using the record_dmic command?

Any guidance on debugging this issue would be appreciated.

Re: xaf_record Example Fails with comp_setup failure in SDK_26_06_00_MIMXRT700-EVK

Gavin_Jia — Mon, 03 Aug 2026 06:47:23 GMT

Hi @suhas1503 ,

Could you please provide some information about the IDE you're using? Is it MCUXpresso IDE or VS Code?

I tried to reproduce the issue in MCUXpresso IDE, but it ran fine.

I didn't find anything related to “[DSP VIT]” in your log information. I suspect this might be due to missing content in your local project rather than a software bug.

Best regards,
Gavin

Re: xaf_record Example Fails with comp_setup failure in SDK_26_06_00_MIMXRT700-EVK

suhas1503 — Mon, 03 Aug 2026 07:00:55 GMT

We have downloaded the sdk from the below link; also attaching the snap; we downloaded sdk version 26.06.00
https://mcuxpresso.nxp.com/download/c7b3a37a7e9e773a92291031541e9b58

we are compiling and flashing through command line

Build command:
west build -b mimxrt700evk middleware/cadence/multicore-xaf/examples/xaf_record/cm -d build/ -- -Dcore_id=cm33_core0 -Dtarget=flash_debug

Flash command:
LinkServer flash MIMXRT798S:MIMXRT700-EVK load dsp_xaf_record_cm33_core0.elf

Re: xaf_record Example Fails with comp_setup failure in SDK_26_06_00_MIMXRT700-EVK

suhas1503 — Mon, 03 Aug 2026 08:41:14 GMT

Please find the above reply.

Re: xaf_record Example Fails with comp_setup failure in SDK_26_06_00_MIMXRT700-EVK

Gavin_Jia — Mon, 03 Aug 2026 08:50:11 GMT

I was able to reproduce the issue using the same package.

I’ll conduct an internal investigation to see if there are any discrepancies. This may take some time. In the meantime, I recommend that you continue development based on the MCUXpresso IDE project to save the time.

Once the issues with the SDK package based on the ARM GCC toolchain have been resolved, you can port your project over.