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/
1:37pm
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
9:32pm
Hi Gary:
The information is as follows:
AWE-Q: R4.3.A
AWE Designer build:
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
9:35pm
The AWE designer version please refer to the attachment.
5:39pm
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