RTOS/TDA2P-ACD: issue about modifying SYSTEM_BUFFER_ALIGNMENT

rooney.hu

Part Number: TDA2P-ACD

Tool/software: TI-RTOS

Hi all,

Due to reusing a lib which is built in VSDK 2.9 and whose SYSTEM_BUFFER_ALIGNMENT is 16. But SYSTEM_BUFFER_ALIGNMENT in VSDK 3.3 is 32. If I roughly modify it to 16, an assertion could happen in SYS/BIOS. what else should I modify? and why does TI change it from 16 to 32 ?

log as below:

[IPU2 ] 524047.820533 s: ### XDC ASSERT - ERROR CALLBACK START ###
[IPU2 ] 524047.820624 s:
[IPU2 ] 524047.820685 s:
[IPU2 ] 524047.820746 s: ### XDC ASSERT - ERROR CALLBACK START ###
[IPU2 ] 524047.820807 s:
[IPU2 ] 524047.820929 s: assertion failure: A_badContext: bad calling context. See GateMutex API doc for details.
[IPU2 ] 524047.821051 s:
[IPU2 ] 524047.821082 s: ### XDC ASSERT - ERROR CALLBACK END ###

over 7 years ago

0 Anuj Gupta over 7 years ago

TI__Genius 15985 points

Hi,

In the new releases some algorithm needs the SYSTEM_BUFFER_ALIGNMENT as 32.

Regards,
Anuj

0 rooney.hu over 7 years ago in reply to Anuj Gupta

Intellectual 700 points

Hi Anuj,
could you tell us for which algorithms it is a must to set SYSTEM_BUFFER_ALIGNMENT as 32 ? what do you suggest to do if SYSTEM_BUFFER_ALIGNMENT is 16 for the algorithm in our third party library, which cannot be modify anymore?
look forward to you reply.
Thanks.

0 Anuj Gupta over 7 years ago in reply to rooney.hu

TI__Genius 15985 points

Hi,

In the VSDK 3.3 the SYSTEM_BUFFER_ALIGNMENT is 32. So it will be 32 bit aligned as well as 16 bit aligned.
So if you use keppt the SYSTEM_BUFFER_ALIGNMENT as 32 then the vsdk will also match its requirement as well as your library since it is both 16 and 32 aligned.

The reason behind moving this to 32 from 16 was to have same buffer alignment for all modules.
As capture related modules needs a buffer of 16 alighned and IVA related modules needs a32 alighned buffer.
So in order to simplify this the above change in buffer alighment is done. So that it will unique across all modules.

I hope this will help to solve your issue and as well to clear your doubt about the change of SYSTEM_BUFFER_ALIGNMENT .

Regards,
Anuj

0 rooney.hu over 7 years ago in reply to Anuj Gupta

Intellectual 700 points

Hi Anuj,
so for this assertion in the log, how can I fix this ?
Thanks.

0 Anuj Gupta over 7 years ago in reply to rooney.hu

TI__Genius 15985 points

Hi,

You have modified the SYSTEM_BUFFER_ALIGHMENT to 16 from 32 and because of this you are getting assertion error.

So you have to make it 32 then try to build.

Regards,

Anuj

0 rooney.hu over 7 years ago in reply to Anuj Gupta

Intellectual 700 points

Hi,
if I set SYSTEM_BUFFER_ALIGNMENT to 32, the link gets blocked in the create phase, and I'm not able to debug further. I can only find that it's blocked in the function "ti_systios_knl_Idle_run_E()" on CCS.

0 Anuj Gupta over 7 years ago in reply to rooney.hu

TI__Genius 15985 points

Hi,

1st try to find which link is failing at the create phase.
Then try to add breakpoint at the create function of that link and then find which piece of code is getting block inside that link file.

Regards,
Anuj

0 Anuj Gupta over 7 years ago in reply to Anuj Gupta

TI__Genius 15985 points

Hi,

Did you able to resolve this issue.

Regards,
Anuj

Processors

Processors forum

RTOS/TDA2P-ACD: issue about modifying SYSTEM_BUFFER_ALIGNMENT