AM5708: SDK tune options

stef boerrigter

Part Number: AM5708

Hi TI Team,

We noticed that for the AM57xx EVM the following TUNE options are configured for the SDK (06 latest):

TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard"

Since the AM5708 uses a single Cortex-A15 (http://www.ti.com/processors/sitara-arm/am5x-cortex-a15/overview.html) we thought in order of performance to use cortex-a15 tune options which resolve for Yocto/open-embedded into:

TUNE_FEATURES = "arm armv7ve vfp neon callconvention-hard cortexa15"

The problem is that with these TUNE features Valgrind doens't work (output doesn't make sense), further we don't notice any difference.

Question:
Why do you use the generic armv7 tune options in the SDK rather than the cortex-a15 tune options?

have you considered cortex-a15 tune options or tested with it?

over 6 years ago

0 RonB over 6 years ago

TI__Mastermind 30506 points

Thanks for your question.

Better code re-use between all the platforms we support in our SDK - Cortex-A8, Cortex-A9, Cortex-A15. It is an optimization to further tune the options and is left to the system developer. In our experience, the performance benefit was minimal and not worth the extra work.

No, we do not test with this option.

I hope this answers your question.

0 stef boerrigter over 6 years ago in reply to RonB

Expert 1050 points

Thanks for your answer, since you mention you did not test i could guess the answer to my next question: Did/do you expect issues with Valgrind when using cortex-a15 flags iso armv7-a generic?

0 RonB over 6 years ago in reply to stef boerrigter

TI__Mastermind 30506 points

I believe your guess is accurate. Since we don't test with it, we have no idea why it may cause issues with Valgrind.

Processors

Processors forum

AM5708: SDK tune options