Filter
Top Products
www.ti.com
3.3Packaging
3.3.1ObjectCode
Packaging
Rule13
EachoftheIALGmethodsimplementedbyanalgorithmmustbeindependentlyrelocatable.
Inpractice,thissimplymeansthateachmethodshouldeitherbeimplementedinaseparatefileorplaced
inaseparateCOFFoutputsection.Byplacingeachofthesemethodsinaseparatefileoroutputsection,
thelinkercanbeusedtoeliminatethosemethodsthatareunnecessaryinsystemsthatdonotrequire
run-timeobjectcreation.
Insomecases,itisawkwardtoplaceeachfunctioninaseparatefile.Forexample,doingsomayrequire
makingsomeidentifiersgloballyvisibleorrequiresignificantchangestoanexistingCodebase.TheTIC
compilersupportsapragmadirectivethatallowsyoutoplacespecifiedfunctionsindistinctCOFFoutput
sections.Thispragmadirectivemaybeusedinlieuofplacingfunctionsinseparatefiles.Thetablebelow
summarizesrecommendedsectionnamesandtheirpurpose
SectionNamePurpose
.text:algActivateImplementationoftheIALGalgActivatemethod
.text:algAllocImplementationoftheIALGalgAllocmethod
.text:<name>ImplementationoftheIALG<name>method
Inotherwords,analgorithm'simplementationoftheIALGmethod<name>shouldbeplacedinaCOFF
sectionnamed".text:<name>".
SincetheIALGinterfacedoesnotdefinemethodsthatcanbeusedtoactuallyrunanalgorithm,itis
importantthateachabstractalgorithminterfaceextend(or"derive")fromtheIALGinterface.Thus,every
algorithmhasconsiderableflexibilitytodefinethemethodsthatareappropriateforthealgorithm.By
derivingfromIALG,wecanensurethatallimplementationsofanyalgorithmimplementtheIALG
interface.
Rule14
AllabstractalgorithminterfacesmustderivefromtheIALGinterface.
Inthissection,wecoverthedetailsnecessaryforadevelopertobundleamoduleintoaformthatcanbe
deliveredintoanyTMS320DSPAlgorithmStandarddevelopmentsystem.Itisimportanttorecallthata
module'simplementationmayconsistofmanyobjectfilesandatleastoneCheaderfile.Byfollowing
theseconventions,algorithmdeveloperscanbesurethattheircomponentscanbeseamlesslyintegrated
intoanyTMS320DSPAlgorithmStandarddevelopmentenvironment.Moreover,theseconventionsare
designedtoenableTMS320DSPAlgorithmStandarddevelopmentenvironmentstoeasilymanagean
arbitrarycollectionofeXpressDSP-compliantcomponents.
Inmanycases,theTMS320DSPAlgorithmStandardrequirementssimplyamounttofilenaming
conventions.InordertoensurethatasinglecomponentcanbeusedinbothUNIXandWindows
developmentenvironments,itisnecessaryto
•nevercreatetwofileswhosenamesonlydifferincase,and
•alwaystreatfilenamesasbeingcase-sensitive.
Rule15
EacheXpressDSP-compliantalgorithmmustbepackagedinanarchivewhichhasanamethatfollows
auniformnamingconvention.
AlloftheobjectCodefilesforamoduleshouldbearchivedintoalibrarywiththefollowingname:
<module><vers>_<vendor>.l<arch>
where
AlgorithmComponentModel 34SPRU352G–June2005–RevisedFebruary2007
SubmitDocumentationFeedback