CCS_April

JohnStevenson:Product&ApplicationsManagerAgenda•CCSv4Overview•Availableresources•FuturedirectionofCCS•FeedbackCodeComposerStudio4•Background–ReleasedinAugust2009–CCSv4isbasedontheEclipseopensourcesoftwareframework•WhyEclipse?–Quicklybecomingastandardforembeddeddevelopmenttools–Excellentsoftwarearchitecture–EnablesTItoleveragetheworkofothers–Wideselectionof3rdpartyplug-insavailable4/16/20103KeyFeatures&Benefits•Superiorcodedevelopmentenvironmentspeedsdesignandtroubleshootingwithanadvancededitorandfeaturessuchascodecompletion,codefolding,localhistoryofsourcechanges,markersandtheabilitytoassociatetaskswithsourcelines.•AdvancedGUIframeworksimplifiesdataandprojectmanagementthroughthecreationofperspectiveswithfullcustomizationofmenus,toolbarsand'fastviews'thatenabledeveloperstodefinethefunctionalityandviewsappropriatetospecifictasks.•Extendtheenvironmentwithawideselectionofplug-insincludingstaticcodeanalysis,sourcecodecontrol,modelingandscriptingdevelopment.•Multi-processordebuggingintelligentlymanagesstatusandinformationfrommultiplecoreswithouttheconfusionthatariseswheneachcorerequiresitsownseparatedebugger.•Debugserverscriptinginterfaceenablestheautomationofcommontaskssuchascodevalidationandprofiling.•Updatemanagertoolautomaticallymanagestoolupdates.LanguageSupport•Installlanguagepacks–Mustbeinstalledtobeabletochangetextencoding–Willtranslatemanymenuitemsanddialogs–CCSshoulddetectyourOSlanguage,ifnotyoucaneditthedesktopshortcutandadd“–nlzh”forChinese–•Textencoding–Automaticallysetupifyouarerunningalanguagespecificversionofwindows–Editor•Window-Preferences.ExpandGeneral-Workspace•Set“textfileencoding”GBK/GB2312(forChinese)–Console(printfoutput)•rightclickonprojectandselectDebugProperties•Gotothecommontabandchangetheconsoleencoding•Tip:AvoidusingChinesecharactersinprogramandfilenames4/16/2010TIProprietaryInformation-StrictlyPrivate7Multi-processorEnvironment•Problem:–Manydevicestodayincludemorethanoneprocessingcoreandoftenresideinasystemwithmanyotherdevices.DisplayingdebuginformationfrommanydifferentcorestypicallyrequiresmanyIDEwindows.•Solution:–CCSv4allowsyoutohaveasingleIDEwindowandtochangethedebugcontextoftheIDEtoanyofthecoresinthesystem.–Youcanalso“pin”thecontextofadebugdisplaytoaspecificcore.–IfdesiredyoucanopenatoplevelIDEforanycore4/16/20108CCSv3.3Multi-coreEnvironmentSeparatetoplevelIDEwindowsforeachcoreCanactuallyrunoutofwindowsresourcesParalleldebugmanagertoseestatusofallcores4/16/20109CCSv4Multi-coreEnvironmentUsetheDebugviewtoselectthecontextDisplaysshowcontentforthecurrentdebugcontext4/16/201010WindowingEnvironment•Problems:–Today’sembeddedIDEsofferalargeselectionoffeatureshoweverfittingallofyourwindowsintotheIDEisachallenge–Youusedifferentwindowsatdifferenttimes•Solutions:–Acomprehensivewindowingsolutionthatallowsyoutomaximizetheavailablescreenspacebutstillhaveallfunctionalityatyourfingertips–Abilitytocreatedifferentperspectivesthathavethewindowsthatyouusemostforagivendevelopmentactivityreadilyavailable4/16/201011CCSv3.3EnvironmentLimitedspaceforwindowsOftenhavetomakewindowssmallCanonlyhaveafewwindowsopen4/16/201012CCSv4EnvironmentTabbededitorwindowsTabdatadisplaystogethertosavespaceFastviewwindowsdon’tdisplayUntilyouclickonthemPerspectivescontainseparatewindowarrangementsdependingonwhatyouaredoing.Customizetoolbars&menusAdvancedEditorFeatures•CodeCompletion–Completeword–Auto-memberinformation–Auto-parameterinformation–…•Navigation–Back/Forwardbuttons–Backtolasteditbutton–Gotodefinition–Gotodeclaration•Showlinenumbers•CodeFolding–CollapsefunctionsLocalHistory•CCSkeepsalocalhistoryofsourcechanges•Youcancompareyourcurrentsourcefileagainstanypreviousversionorreplaceitwithanypreviousversion–Double-clickonarevisiontoopenitintheeditor–Right-clickonarevisiontocomparethatrevisiontothecurrentversion‘History’viewFileComparer4/16/201015ToolIntegration&Customization•Problem:–Morethanjustanembeddeddebuggerisrequiredduringproductdevelopment•Solution:–CCSv4isbasedonEclipsewhichhasahugeselectionof3rdpartyplug-insavailable(codeanalysis,sourcecodecontrol,modelling,Perldevelopment…)•–TheEclipseplug-indevelopmentenvironmentallowsforthecreationofyourowncustomtooling•Wizardsforcreatingplug-insquickly4/16/201016Scripting•Problem:–Sometaskssuchastestingneedtorunforhoursordayswithoutuserinteraction–Needtobeabletoautomatecommontasks•Solution:–CCSv4hasacompletescriptingenvironmentallowingfortheautomationofrepetitivetaskssuchastestingandperformancebenchmarking.–TheCCSv4ScriptingConsoleallowsyoutotypecommandsortoexecutescriptswithintheIDE#1ResourceforInformation•CCSv4Mediawiki–=Category:Code_Composer_Studio_v4–Documentation–FAQs–Licenseinfo–Training–Downloads–Demonstrations•NoInternetaccess?–Offlineversion––IntegratesintoCCSv4helpGettingHelp•InadditiontoyourlocalFAEsupport•Communitysupportmodel–Collaboration–FAEs,applicatio