1. Community Forum
  2. AWE Core
  3. defer task is not woken up .

defer task is not woken up .

9 posts / 0 new
Log in or register to post comments
Last post
Wed, 01/21/2026
11:12pm
yong.li_14167
#1
Top
#1
defer task is not woken up .

The module  generated by AWE designer version 4.3 and  now `awe_modSetDeferredSet()`function has three parameters,
 and after calling it, the defer task is not woken up. Printing `pAweInstance->instanceId` shows a very large value.
 Previously, with AWE designer version 3.1, the defer task could be woken up normally. can you help me fix this issue.

Thanks/

Thu, 01/22/2026
1:37pm
DSPC_Gary
Top

Hi Yong Li,

This is due to a mismatch between one or more components that you are using.  Can you please clarify:

AWE-Q or QAR SDK version: <e.g. AWE-Q v4.2.A or QAR SDK v4.7.C.0>AWE Designer build: <from Help->About AWE Designer, screenshot is OK>HW Target: <e.g. ADP Air v3 8255>Qualcomm Software Product Baseline: <e.g. SnapdragonAuto.HQX.5.7.7.0 r00001.3[ES0]>

AWECore Build numbers (shown in AWE Server).

Thanks,

Gary

Thu, 01/22/2026
9:32pm
yong.li_14167
Top
(Reply to #2)

Hi Gary： 

The information is as follows: 

AWE-Q: R4.3.A

AWE Designer build: 

image

 

HW Target: ADP RIDESX V2 8797

Qualcomm Software Product Baseline: Snapdragon_Auto_GEN5.HGY.5.1.7.0 ES5_r00018.2[ES5]

AWECore Build numbers: AWECore Version: 8.C.0.13  Build Number: 768

What is AWE-Q or QAR SDK?  R4.3.A is information we obtained from the Qualcomm release notes.

Thanks,

Yong

Thu, 01/22/2026
9:35pm
yong.li_14167
Top

The AWE  designer version please refer to the attachment. 

Image icon picture1.png
Fri, 01/23/2026
5:39pm
DSPC Kevin
Top

Hello Yong.li_14167,

Thank you for the information.  Are you building a custom module?  If so, could you please re-run the custom module creator wizard in the new version of AWE Designer and see if this issue resolves itself?

Thanks,

Kevin

Sun, 01/25/2026
2:53am
yong.li_14167
Top
(Reply to #5)

Hi Kevin:

I recreate a test module running  on gdsp1 with  clockDivider  set to 1A2'. I add debug and printed the "pAweInstance->instanceId". i think the correct  value is '2', but now it is currently  0. so the defer task still not be waken up . can you help me how to fix this issue or how to debug.

 _AWEInstance* pAweInstance = (struct _AWEInstance *)defTaskParam->pAwe;

  LOGD("aweControlModuleSet mask=%u, instance id : 0x%x \n", mask,   pAweInstance->instanceId);

Thanks 

Yong

Sun, 01/25/2026
10:23pm
yong.li_14167
Top
(Reply to #6)

Hi Kevin: 

00:00:25.070244|awe_bsp.c                     |awe_core_init                 |  1776 | instanceId=0x2
00:00:25.070856|awe_bsp.c                     |awe_core_init                 |  1865 | awb[0]=0xd4028e, awb[795]=0x0
00:00:25.076330|awe_bsp.c                     |audioStartCallback            |  1316 | audioStartCallback start instance id 2

From initial printing the instance id is ''2', but in awe module we get the instance id is '0'.

Sun, 01/25/2026
10:23pm
yong.li_14167
Top
(Reply to #7)

Hi Kevin: 

00:00:25.070244|awe_bsp.c                     |awe_core_init                 |  1776 | instanceId=0x2
00:00:25.070856|awe_bsp.c                     |awe_core_init                 |  1865 | awb[0]=0xd4028e, awb[795]=0x0
00:00:25.076330|awe_bsp.c                     |audioStartCallback            |  1316 | audioStartCallback start instance id 2

From initial printing the instance id is ''2', but in awe module we get the instance id is '0'.

Tue, 02/03/2026
9:09pm
DSPC Kevin
Top

Hi yong.li_14167,

Apologies for the delayed response here, but just wanted to close the loop on this forum thread for thoroughness, as the multiple inter-company troubleshooting threads regarding this issue have been consolidated to a single email thread we have both been added to.  Let's continue discussion and progress there.

Thanks,

Kevin