Code Composer Studio™ 6.1 for MSP432 (Rev. B)
Contents
1. blink c 24 1 of PEPPER EEE EEE EEE ESE TEESE EE EEEEE EERE EE EE EEEEE EEE SE EEEEEEEE EE EEER EE EEE EES TEESE 2 f 3 MSP432 main c template P1 port toggle 4 E i 6 7 include msp h g 5 woid main void of volatile uint32 t i WOTCTL WOTPW WDTHOLD Stop watchdog timer The following code toggles P1 port 1 2 3 4 5 A PInTR l RITA ff Confieure P1 0 as nutnut 4 E Console H MS5P432_BlinkLED CORTEX_M4_ GEL Output Memory Map Initialization Complete CORTEX_M4_ GEL Output Halting Watchdog Timer CORTEX_M4_ Flash Programmer Erasing main memory CORTEX _M4 Flash Programmer Writing 1232 bytes to flash memory x eegeGe0 A Writable Smartinsert 11 25 Foll cms LE Figure 9 Debug Session 10 Code Composer Studio 6 1 for MSP432 SLAU575B March 2015 Revised May 2015 Submit Documentation Feedback Copyright 2015 Texas Instruments Incorporated l TEXAS INSTRUMENTS www ti com EnergyTrace Technology 6 6 1 6 2 6 3 EnergyTrace Technology EnergyTrace Technology is an energy based code analysis tool that measures and displays the application s energy profile and helps to optimize it for ultra low power consumption MSP432 devices with built in EnergyTrace CPU State or in short EnergyTrace technology allow real time monitoring of many internal device states while user program code executes Energy Trace technology is supported on2. s Debug 2 a lle U0 ee oe eee E r 4 4 a TMAL_Test Code Composer Studio Device Debugging p Texas Instruments XD5100v3 USB Emulator CORTEA_M4_0 Running No Power Figure 37 CPU Core Status Display Indicating Deep Sleep Mode When halting the device the debugger will reconnect and the IDE will show the current program counter location which in this case will be the WFI assembly instruction that sent the MSP432 to sleep 28 Code Composer Studio 6 1 for MSP432 SLAU575B March 2015 Revised May 2015 Submit Documentation Feedback Copyright 2015 Texas Instruments Incorporated ld TEXAS INSTRUMENTS www ti com Frequently Asked Questions ec cpu c 3 E 302 bx 1r A 303 304 endif 305 if defined ccs 306 void CPU wfi void 307 386 i 309 t Wait for the next interrupt 310 if 311 asmi wfi n gt 3125 313 endit 314 Figure 38 Program Counter Located at WFI Instruction 9 Frequently Asked Questions Q cannot program my LaunchPad kit the IDE cannot connect to target What s wrong A Check the following e Is the JTAG switch S101 in the correct orientation Switch to left for XDS110 ET onboard debugger Switch to the right for external debugger connection e Check the debugger settings change to Serial Wire Debug SWD without SWO When the settings of Port J PUSELO and PJSEL1 bits are changed full JTAG access is prevented on these pins Changing to use SWD allows access thr
3. E Figure 12 EnergyTrace Technology Control Bar Table 1 EnergyTrace Technology Control Bar Icons Enable or disable EnergyTrace Technology When disabled icon turns gray Set capture period 5 sec 10 sec 30 sec 1 min or 5 min Data collection stops after time has elapsed However the program continues to execute until the Pause button in the debug control window is clicked Save profile to project directory When saving an EnergyTrace profile the default filename will start with 1E EnergyTrace_D followed by a timestamp When saving an EnergyTrace profile the default filename will start with EnergyTrace followed by a timestamp Load previously saved profile for comparison Restore graphs or open Preferences window Switch between EnergyTrace mode and EnergyTrace mode 6 5 EnergyTrace Mode When debugging devices with built in Energy Trace support the Energy Trace mode gives information about both energy consumption and the internal state of the target microcontroller The following windows are opened during the startup of a debug session e Profile e States e Power e Energy SLAU575B March 2015 Revised May 2015 Code Composer Studio 6 1 for MSP432 13 Submit Documentation Feedback Copyright 2015 Texas Instruments Incorporated I8 TEXAS TM EnergyTrace Technology www ti com A x lt CCS Debug lab1 _power lab1_power_solution c Code Composer t aca File Edit View Project Tools Run Sc
4. Link Emulator Support http orocessors wiki ti com index php J Link_ Emulator Support 30 Code Composer Studio 6 1 for MSP432 SLAU575B March 2015 Revised May 2015 Submit Documentation Feedback Copyright 2015 Texas Instruments Incorporated ld TEXAS INSTRUMENTS www ti com Revision History Revision History Changes from May 13 2015 to May 20 2015 Page e Added Mac OS X to introduction wcesnnviscavacerensnetacdsaten taka sebeedeoienntincsAnannieabeieaatduenevbadkaa erestwhstacdeceeeuees 1 NOTE Page numbers for previous revisions may differ from page numbers in the current version SLAU575B March 2015 Revised May 2015 Revision History 31 Submit Documentation Feedback Copyright 2015 Texas Instruments Incorporated IMPORTANT NOTICE Texas Instruments Incorporated and its subsidiaries Tl reserve the right to make corrections enhancements improvements and other changes to its semiconductor products and services per JESD46 latest issue and to discontinue any product or service per JESD48 latest issue Buyers should obtain the latest relevant information before placing orders and should verify that such information is current and complete All semiconductor products also referred to herein as components are sold subject to Tl s terms and conditions of sale supplied at the time of order acknowledgment Tl warrants performance of its components to the specifications applicable at the time of sale in accor
5. OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT INDIRECT INCIDENTAL gt msp432_startup_ccs c 26 SPECIAL EXEMPLARY OR CONSEQUENTIAL DAMAGES INCLUDING BUT NOT b gt Le msp432p401r cmd 27 LIMITED TO PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES LOSS OF USE 28 DATA OR PROFITS OR BUSINESS INTERRUPTION HOWEVER CAUSED AND ON ANY 29 THEORY OF LIABILITY WHETHER IN CONTRACT STRICT LIABILITY OR TORT 3 INCLUDING NEGLIGENCE OR OTHERWISE ARISING IN ANY WAY OUT OF THE USE 31 OF THIS SOFTWARE EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE 32 33 MSP432 main c template P1 port toggle 34 35 KEKE KEEKKKKKKKKKKKKKEE KEKKKKKKKKKHKKKEKSE KEKKKKKKKKKKKEE KEKKKKKKKKKKKKKKEKE eee 36 37 include msp432 h al uint32_t i WDTCTL WDTPW WDTHOLD Stop watchdog timer The following code toggles P1 port PIDIR BIT Configure P1 as output while 1 P1 BIT Toggle P1 0 for i 10000 i gt i Delay return Figure 5 New Project Files Now you can go on and start developing code 4 Additional MSP432 Examples and Documentation The Texas Instruments MSP team releases a software package called MSPWare that contains many software examples projects documentation as well as application notes and training for all MSP devices This includes example projects for Code Composer Studio that work with MSP432 For more information visit www ti com tool mspware SL
6. Profile Window The Profile window enables a quick overview of the resource use of the profiled application e CPU Shows information about program execution Low Power Mode Shows a summary of low power mode use Active Mode Shows which functions have been executed during active mode Functions in the run time library are listed separately under the _RTS_ subcategory If the device supports IP Encapsulation a line labeled as lt Protected gt is displayed to indicate the time executing out of IP encapsulated memory 14 Code Composer Studio 6 1 for MSP432 SLAU575B March 2015 Revised May 2015 Submit Documentation Feedback Copyright 2015 Texas Instruments Incorporated la TEXAS INSTRUMENTS www ti com EnergyTrace Technology The States window see Figure 15 shows the real time trace of the target microcontroller s internal states during the captured session State information includes the Power Modes on and off state of peripheral modules and the state of the system clocks Figure 15 shows a device going into a Low Power mode then back to Active Mode The States window allows a direct verification of whether or not the application exhibits the expected behavior for example that a peripheral is disabled after a certain activity ke States 33 A A Rr mle yo y Showing 794 records Figure 15 States Window The Power window see Figure 16 shows the dynamic power consumption of the target over time
7. Texas Instruments Incorporated la TEXAS INSTRUMENTS www ti com Device Security F Debug 2 al Ta a XDS100v2 ccxml Code Composer Studio Device Debugging 4 Non Debuggable Devices J Texas Instruments XDS100v2 USB Emulato CS DAP 0 Disconnected aS Texas Instrumem 42 Connect Target Ctrl Alt C known Disconnect Target Ctrl Alt D Enable Global Breakpoints Enable Halt On Reset Enable 05 Debugging Open GEL Files View Hide core s Show all cores Group core s Sync group core s Ungroup core s Rename Remove All Terminated Relaunch Edit XDS1LO0v2 ccuml Terminate and Remove Terminate Disconnect All Properties Figure 31 Manually Connecting to the DAP When the debugger has connected to the DAP the Debug view window changes indicating a successfully connected DAP Debug 2 ei a a XDS100v2 ccuml Code Composer Studio Device Debugging 4 ef Non Debuggable Devices Texas Instruments XDSL00v2 USB Emulator CS_DAP_O a Texas Instruments XDS1O00v2 USB Emulator CORTEX_M4_0 Disconnected Unknown Figure 32 DAP is Connected Now you need to execute a CCS script that performs triggers a reboot reset through the DAP Go to Scripts default MSP432_Factory_Reset and click on it Project Tools Rurg jj detaul MSP432_Factory_Reset File Edit View E Figure 33 Executing the Factory Reset Script As the script is executed the Console window will show tha
8. buinenrusia bie seseraue 4 Creating a New CCS Projet ssc cc Sec ccsnacndes ice scccsadehusnonccsetiecsueedecsaenecusecesdcasentseedecscauey Seatac 5 NEW IPIOICG VWIZANG prteuarnicdauucteusvacdiangreccevaeesausuieeie acess ves teadvacmadanndiackmn davasacauvemedeuaveeminesens 6 NCW IPVOIGCE FCS sconetcetuecesceus veesvencsnevineenuececsexttscseswe ceveeseut sian vovetowsecseviweecusecesauevetceaee sete 7 Projeci PFODGTIGS ia scicaccccwtuninnanaca wa casieG e E Ea a estedvesuun a E i 8 Choose Debugger COMING CHO sssrin eirinn E EE a EEEREN 9 Launch DEDUG SESSION ererasrdr risik e ar eE nE a 9 PEDUT GS O erra E E E ems enous ese eee enemeeeetoees 10 Pulse Densiy and CuUnent FIOW ccxsetesciets ceaccganed ee e e E aai 11 Energy Trace Technology Preferentes sic van tecee scien irinenn donar EEEa EEan ESEO 12 EnergyTrace Technology Control Bar assssssassnnnunnsnnnnnrnrnnnnnnnrnnnnnnrnernrnnnnrnrnnrnnnnrnennrnennrnrnnn 13 Debug Session With Energy Trace Graphie sisrsiionasrriesin iuiar AR 14 Prole WNO OW setucinneotssunietevesbirtieratacisiot eia e EET 14 AES NOON eana E E a S uses 15 OWED VuINOOWieccnidaciaeccennwenanegunaeteecusen a a denned 15 MELOY VV IMGAGW saecctad seas unwee tat wetsecsem asda vente sien E oneal u ees oaeeeeed owners us 16 Debug Session With EnergyTrace Grapns ccccce cece cece cece eee eee eee eee e nesses 16 Energy 1 race Prone WINDOW sxcons case cneutdosawenieueencnevedenienus tenner a A A a 17 ZOOM O OWE VINO OW
9. went away There might be other USB3 0 hardware and device driver combinations that will lead to the same issue If you think you might be affected contact the PC vendor or locate and install more recent versions of the USB3 0 device drivers Alternatively connect the LaunchPad to an USB2 0 port on the PC if available Q cannot get the backchannel UART to connect What s wrong A Check the following e Do the baud rate in the host s terminal application and the eUSCI settings match e Are the appropriate jumpers in place on the isolation jumper block e Probe on RXD and send data from the host If you don t see data it might be a problem on the host side e Probe on TXD while sending data from the MSP432 If you don t see data it might be a configuration problem with the eUSCI module e Consider the use of the hardware flow control lines especially for higher baud rates 10 Additional Code Composer Studio Information For more information about Code Composer Studio refer to the following links e Code Composer Studio Information http Awww ti com tool ccstudio e Code Composer Studio v6 Training http orocessors wiki ti com index php Category CCSv6_ Training e Code Composer Studio v6 Wiki http orocessors wiki ti com index php Category Code_ Composer Studio v6 e Code Composer Studio Quick Start Guide http downloads ti com ccs esd documentation CCSv6 QSG pdf 11 References 1 MSPWare www ti com tool mspware 2 J
10. 2015 Revised May 2015 Code Composer Studio 6 1 for MSP432 2 Submit Documentation Feedback Copyright 2015 Texas Instruments Incorporated 13 TEXAS INSTRUMENTS Low Power Debug www ti com a So type filter text b Resource General Device Texas Instruments ADS100v2 USB Emulator CORTEA_M4_0 4 Build a ARM Compiler Program Memory Loa O Aware Debug Options depend am Auto Run and Launch i Automatically load module symbols Optimization Misc Other Options Never 7 Include Options MISRA C 2004 i i b Advanced Options Tt Pich Settings Whenever halted in the module load unload routines you must manually t ARM Linker ARM Hex Utility Disabled KModule name list Module symboal search path When modules are loaded and unloaded intrusive on target execution anc Simulators will flush the pipeline on a halt d timestamp information to target Allow software breakpoints to be used Default directory for File 10 con added to a sync aroun F IT b D Show advanced settings Figure 36 Enabling Low Power Run When Low Power Run is enabled the MCU will go to any low power mode specified You can verify the effect by watching the CPU core status display during a debug session When the MCU goes to a low power mode equal or deeper than DSL the debugger will report a loss of connection due to the MSP432 clocks all being disabled including the clock that operates the Debug Access Port or DAP
11. 4 0 1 2 0 LPMx n 72 2 0 0 es 482 2 0 E 24 0 I 2 0 Active Mode 27 8 C 100 O 48 2 I 1 76 0 C 98 0 Figure 23 Comparing Profiles in EnergyTrace Mode In the EnergyTrace mode no States information is available to generate an exhaustive report However the overall energy consumed during the measurement is compared and with it the Min Mean and Max values of power and current Parameters that have become better are shown with a green bar and parameters that have become worse are shown with a red bar see Figure 24 SLAU575B March 2015 Revised May 2015 Code Composer Studio 6 1 for MSP432 19 Submit Documentation Feedback Copyright 2015 Texas Instruments Incorporated I TEXAS INSTRUMENTS EnergyTrace Technology www ti com D EnergyTrace 22 i Lo oz Uhl Reference MSP430_2014 01_21 103959 EnergyMonitor Profile Mame Liwe Delta Reference 4 System Time 10 sec 10 sec Energy 784 mJ 11 5 8 86 mJ 4 Power Mean O79 mW C 10 8 0 89 mW Min 0 582 mW CL 27 3 0 800 mW Max 1 938 mW 0 2 1 942 mW 4 Voltage Mean 299V 0 0 2 99 4 Current Mean 0 26 mA C 10 8 0 30 mA Min 0 195 mA OS 27 0 0 268 mA Max 0 646 mA 0 4 0 648 mA Battery Life CR2032 35 1 day est Si 13 0 CR2032 31 0 day est Figure 24 Comparing Profiles in EnergyTrace Mode The delta bars are drawn linearly from 0 to 50 Deltas larger than 50 do not result in a larger delta bar 6 8 EnergyTrace Technology FAQs Q What is
12. AU575B March 2015 Revised May 2015 Code Composer Studio 6 1 for MSP432 7 Submit Documentation Feedback Copyright 2015 Texas Instruments Incorporated I TEXAS INSTRUMENTS Debugging Your Application www ti com 5 Debugging Your Application The following debug probes have been tested successfully with CCS e Texas Instruments XDS100v2 XDS100v3 XDS200 XDS110 e Segger J Link for more information visit the TI J Link Support Emulator Wiki Page at http processors wiki ti com index php J Link_Emulator_Support After you create a project you can change the debugger used to debug the application To change the debugger right click on the project in the workspace and choose Properties see Figure 6 CCS Edit MSF File Edit View Navigate Project Run Scripts Window Help iv iB Diteri eS vif Ft Project Explorer 82 O blinke Z S MSP432 BlinkLED Active Debug g eeeeensennses New Add Files Copy Ctrl C Paste Ctrl V Delete Refactor Source Move Rename Import Export Show Build Settings Build Project Clean Project Rebuild Project Refresh Close Project Build Configurations Make Targets Index Debug As Team Compare With Restore from Local History Properties Alt Enter EI Fadl Figure 6 Project Properties In the project properties window make sure that you are in the General options pane There you can see a drop down list of target
13. CR2032 3 0 day est OF R vv Showing 120 002 records QQarve z Showing 120 002 records Figure 18 Debug Session With EnergyTrace Graphs SLAU575B March 2015 Revised May 2015 Submit Documentation Feedback Copyright 2015 Texas Instruments Incorporated la TEXAS INSTRUMENTS www ti com EnergyTrace Technology In the EnergyTrace mode the Profile window shows statistical data about the application that has been profiled see Figure 19 The following parameters are shown e Captured time e Total energy consumed by the application in mJ e Minimum mean and maximum power in mW e Mean voltage in V e Minimum mean and maximum current in mA e Estimated life time of a CR2032 battery in days for the captured energy profile NOTE The formula to calculate the battery life time assumes an ideal 3 V battery and does not account for temperature aging peak current and other factors that could negatively affect battery capacity It should also be noted that changing the target voltage for example from 3 6 V to 3 V might cause the analog circuitry to behave differently and operate in a more or less efficient state hence reducing or increasing energy consumption The value shown in the Profile window cannot substitute measurements on real hardware EnergyTrace Profile _ Name Live 4 System Time 10 sec Energy 14 61 m 4 Power Mean 1 75 mi Min 1 068 mW Mase 7943
14. Run mode is nonintrusive to the device but still uses the debug port which affects energy measurement For highest accuracy run EnergyTrace without debugging or Free Run Also note that the graphs for energy and power are printed in blue instead of green when no accurate measurement is possible 6 6 EnergyTrace Mode This mode allows a standalone use of the energy measurement feature with MSP432 microcontrollers that do not have built in EnergyTrace support It can also be used to verify the energy consumption of the application without debugger activity If the EnergyTrace mode is selected in the Preferences window the following windows open when a debug session starts see Figure 18 e Profile e Power e Energy Xs Debug 4 7 labl_power Code Composer Studio Device Debugging p Texas Instruments XDS110 USB Debug Probe CORTEX_M4_0 Running ic lab1_power c labl_power_solution c 3 cpu c 66 _ 67 int main void o8 Halting the Watchdog WDT_A_holdTimer 71 InitializeDevice 7 curPowerState 16 Code Composer Studio 6 1 for MSP432 labl_power_startup_ccs c Y A iif Registers EnergyTrace Technology 53 OlS Wa s moo EnergyTrace Profile N_ Name Live 4 System N Time 60 sec Energy 545 530 mJ a Power Mean 9 3160 mW Min 0 9408 mW Max 86 9814 mW 4 Voltage a 3 3000 V x 4 Current Mean 2 8230 mA Min 0 2851 mA Max 26 3580 mA Battery Life
15. S ae Seer ee cece E cece neuen se meaenenteenccesenaeaese se anceeeneeeccesesee ace EEE EERE EA EAEE 24 30 Listo All Cores itv Ihe MSP482 sereset 24 31 Manually Connecting to the DAP i iccsccdescccsenccaccnisueeeacieeensaveceesdescheuwen sen dwcatwieseveleddcuneews Ea 25 32 DAP IS COMME GCC ott ceases tei a cece cnet es cne donee E sree E reece acces eae ee eens ease 25 33 Executing the Factory Reset SCH t ncccesexctccennnes veces cteuennnnccdadeecmsnawanaicedeedeweccesdaeedauien sevetecesautde 25 34 Mass Erase Script Console Output cc cece cece cece eee eee nen eee eee 26 35 FP MOD eRe SNC AU wocecan aude ctexawtamiavesi eee cheenevenexaatenavdweseeoeeunenaccrdnaccuesdeeseed aeeumenndsrecaecenedesseeneene 27 36 Enabling LOW Power RUN i scccewsewcdcs eneueardewawaeswewv ee eiiwewieudenienawietweenteerddawiiaeeeseneneeceeeeseaiewed as 28 37 CPU Core Status Display Indicating Deep Sleep Mode ccc cecceceeee eee e eee e eee eeeeeeeeeeeeeenneeeeeeesenenane 28 38 Program Counter Located at WEI INSWUCIOM isis coriuidtoerniavteriveeanndelueenkseieuieranevidiaiieiualierd on 29 39 Change Debugger Settings 10 SW D siscsurcecetecseteascecedxwec e cladeccsasseweeacecwedcun EE 29 Read This First How to Use This Manual This manual describes only those CCS features that are specific to the MSP432 low power microcontrollers It does not fully describe the MSP432 microcontrollers or the complete development software and hardware systems For details
16. The current profile is plotted in light blue color while a previously recorded profile that has been reloaded for comparison is plotted in yellow color hae Power 52 gO op A ba 4 W p amp Warning Debugger activity such as breakpoint polling 9 Showing 8 621 records Figure 16 Power Window The Energy window see Figure 17 shows the accumulated energy consumption of the target over time The current profile is plotted in light blue color while a previously recorded profile that has been reloaded for comparison is plotted in yellow color SLAU575B March 2015 Revised May 2015 Code Composer Studio 6 1 for MSP432 15 Submit Documentation Feedback Copyright 2015 Texas Instruments Incorporated EnergyTrace Technology I TEXAS INSTRUMENTS www ti com Rx Energy 33 vr 4 m p amp Warning Debugger activity such as breakpoint polling 9 Showing 8 621 records Figure 17 Energy Window NOTE During the capture of the internal states the target microcontroller is constantly accessed by the JTAG or Spy Bi Wire debug logic These debug accesses consume energy therefore no absolute power numbers are shown on the Power and Energy graph vertical axis To see absolute power numbers of the application it is recommended to use the EnergyTrace mode in combination with the Free Run option In this mode the debug logic of the target microcontroller is not accessed while measuring energy consumption Free
17. back Copyright 2015 Texas Instruments Incorporated la TEXAS INSTRUMENTS www ti com Installing Code Composer Studio IDE 1 Installing Code Composer Studio IDE The Code Composer Studio IDE can be obtained from TI website under www ti com tool ccstudio Note that MSP432 low power microcontrollers are supported by Code Composer Studio 6 1 and higher versions Previous versions do not support MSP432 2 Updating Code Composer Studio IDE Use the CCS update feature to update the installation before starting to work with MSP432 low power microcontrollers To check for updates click Help Check for Updates ide Getting Started ABNER NLRB PLACA B RADARS BAPLMLIL PALA BAA M IIIB ICRA ACIS RSD Mo aa About Code Composer Studio CCS Videos and Tutorials CCS Developer Site CCS Support Help Contents Search Dynamic Help Rey Assist Ctrl Shitt L Tips and Tricks Cheat Sheets Code Composer Studio Licensing Information Eclipse Marketplace Check for Updates Install New Software Figure 1 Check for Updates CCS now automatically connects to the TI update server and retrieves information about relevant updates for the system You can still select which update to install but it is good practice to install all updates see Figure 2 SLAU575B March 2015 Revised May 2015 Submit Documentation Feedback Code Composer Studio 6 1 for MSP432 3 Copyright 2015 Texas Instru
18. baud A Certain serial terminal programs such as HTerm or the CCS built in terminal might not work with the MSP432 LaunchPad at specific baud rates resulting in the software not being able to open the virtual COM port or in the baud rate getting configured incorrectly An issue with the LaunchPad s emulator firmware has been identified and will be fixed in the next release Until the update is available use Tera Term ClearConnex or HyperTerminal instead or reduce the baud rate to speeds of 38400 baud or lower Q Problems plugging the MSP432 LaunchPad into a USB3 0 Port A It has been observed that when the MSP432 LaunchPad is connected to USB3 0 ports provided by a certain combination of USB3 0 host controller hardware and associated device drivers that the IDE is unable to establish a debug session with the LaunchPad resulting in an error message like CS_DAP_0 Error connecting to the target Error 260 0x0 An attempt to connect to the XDS110 failed in the case of Code Composer Studio In this case the CCS provided low level command line utility xdsdfu will also not be able to establish a connection with the LaunchPad Specifically this issue was observed on PCs running Windows 7 that show the Renesas Electronics USB 3 0 Host Controller and the associated Renesas Electronics USB 3 0 Root Hub in the device manager After updating the associated Windows USB drivers to more recent versions obtained from the hardware vendor the issue
19. bution Q My profile sometimes includes an lt Undetermined gt low power mode and there are gaps in the States graph Power Mode section Where does the lt Undetermined gt low power mode originate from A During transitions from active mode to low power mode internal device clocks are switched off and occasionally the state information is not updated completely This state is displayed as lt Undetermined gt in the Profile window and the States graph shows a gap during the time that the lt Undetermined gt low power mode persists The lt Undetermined gt state is an indication that the application has entered a low power mode but which mode cannot be accurately determined If the application is frequently entering low power modes the lt Undetermined gt state will probably be shown more often than if the application only rarely uses low power modes Q When capturing in EnergyTrace mode the min and max values for power and current show deviation even though my program is the same would expect absolutely the same values A The energy measurement method used on the hardware counts dc dc charge pulses over time Energy and power are calculated from the energy over time Due to statistical sampling effects and charge and discharge effects of the output voltage buffer capacitors it is possible that minimum and maximum values of currents vary by some percent even though the program is identical The captured energy however should be a
20. connections Choose the debugger from this list and click OK Code Composer Studio 6 1 for MSP432 SLAU575B March 2015 Revised May 2015 Submit Documentation Feedback Copyright 2015 Texas Instruments Incorporated la TEXAS INSTRUMENTS www ti com Debugging Your Application _ Properties for MSP432 Blink type filter text General t Resource General 4 Build Configuration Debug Active Manage Configurations a MSP432 Compiler Processor Options Optimization E Main Include Options MISR A C 2004 Device ULP Advisor Farnily MSP432 b Advanced Options gt MSP432 Linker MSP432 Hex Utility Disabled Debug Manage the project s target configuration automatically Advanced settings Compiler version TI w5 2 2 ki Output type Executable Output format Device endianness little Linker command file msp432p40Lr cmd Runtime support library lt automatic gt show advanced sting Figure 7 Choose Debugger Connection After the project has been set to the correct debugger you can begin to debug the application To launch a debug session click the icon in the top toolbar of the IDE see Figure 8 File Edit View Wavigate Project Run Scripts Window Help Ty LAMAER Project Explorer 52 ebug bank c ic blink 3 j E MSP43 BlinkLED Active Debug 1 ff PEPE ESSSSESESES SESE SELES SES b 4P B
21. dance with the warranty in Tl s terms and conditions of sale of semiconductor products Testing and other quality control techniques are used to the extent TI deems necessary to support this warranty Except where mandated by applicable law testing of all parameters of each component is not necessarily performed Tl assumes no liability for applications assistance or the design of Buyers products Buyers are responsible for their products and applications using TI components To minimize the risks associated with Buyers products and applications Buyers should provide adequate design and operating safeguards Tl does not warrant or represent that any license either express or implied is granted under any patent right copyright mask work right or other intellectual property right relating to any combination machine or process in which Tl components or services are used Information published by TI regarding third party products or services does not constitute a license to use such products or services or a warranty or endorsement thereof Use of such information may require a license from a third party under the patents or other intellectual property of the third party or a license from TI under the patents or other intellectual property of TI Reproduction of significant portions of TI information in TI data books or data sheets is permissible only if reproduction is without alteration and is accompanied by all associated warranties cond
22. e using the configuration file for an XDS100v2 debugger Code Composer Studio 6 1 for MSP432 SLAU575B March 2015 Revised May 2015 Submit Documentation Feedback Copyright 2015 Texas Instruments Incorporated la TEXAS INSTRUMENTS www ti com Device Security id Target Configurations s fey x a E type filter text 4 Projects 4 E5 MSP432_ Blink_LED 4 targetConfigs XDS100v ccxml Default User Defined Figure 26 List of Target Configurations Now right click on the target configuration and select Launch Selected Configuration Target Configurations 13 Ei x ye oO type filter text Projects 4 ES MSP432_Blink_LED 4 amp targetConfigs E User ax New Target Configuration Import Target Configuration a Delete Delete Rename F2 ae Refresh FS Set as Default Link File To Project Properties Alt Enter Figure 27 Launch Selected Target Configuration The debugger will now connect to the device which is still possible but does not try to halt the CPU write to registers or even download code which would not be possible The Debug view that is spanned shows the CPU core but marks it as disconnected s Debug E3 7 E a XDS100v2 cexml Code Composer Studio Device Debugging T Texas Instruments XDS100v2 USB Emulator CORTEX M4_0 Disconnected Unknown Figure 28 Debug View After Launching Target Configurat
23. ecom Computers and Peripherals Consumer Electronics Energy and Lighting Industrial Medical Security Space Avionics and Defense Video and Imaging TI E2E Community www ti com wirelessconnectivity Mailing Address Texas Instruments Post Office Box 655303 Dallas Texas 75265 Copyright 2015 Texas Instruments Incorporated www ti com automotive www ti com communications www ti com computers www ti com consumer apps www ti com energy www ti com industrial www ti com medical www ti com security www ti com space avionics defense www ti com video
24. ents Incorporated l TEXAS INSTRUMENTS www ti com EnergyTrace Technology Two capture modes are supported e The full featured EnergyTrace CPU State mode that delivers real time device state information together with energy measurement data e The EnergyTrace mode that delivers only energy measurement data Use the radio button to select the mode to enable when a debug session is launched If an MSP432 device does not support device state capturing the selection is ignored and Code Composer Studio starts in EnergyTrace mode While a debug session is active click the Wil icon in the Profile window to switch between the modes NOTE If the EnergyTrace Technology windows are not opened when a debug session starts verify the following items e Does the hardware debugger and device support EnergyTrace Technology To determine if the selected device supports EnergyTrace refer to the device specific data sheet the MSP432 Hardware Tools User s Guide or the user guide that came with the evaluation board e Is EnergyTrace Technology globally enabled in Window Preferences Code Composer Studio Advanced Tools EnergyTrace Technology 6 4 Controlling EnergyTrace Technology EnergyTrace Technology can be controlled using the control bar icons in the Profile window see Figure 12 Table 1 describes the function of each of these buttons EnergyTrace Technology 2 3 i H og gt Su
25. g is not applied so that detail information is not lost Another factor that affects the energy and with it the current that is consumed by the target is periodic background debug access during normal code execution either through capturing of States information or through breakpoint polling Try recording in Free Run mode to see a much smoother Power graph 20 Code Composer Studio 6 1 for MSP432 SLAU575B March 2015 Revised May 2015 Submit Documentation Feedback Copyright 2015 Texas Instruments Incorporated la TEXAS INSTRUMENTS www ti com EnergyTrace Technology Q have a code that repeatedly calls functions that have the same size would expect the function profile to show an equal distribution of the run time In reality see some functions having slightly more run time than expected and some functions slightly less A During program counter trace various factors affect the number of times a function is detected by the profiler over time The microcontroller code could benefit from the internal cache thus executing some functions faster than others Another influencing factor is memory wait states and CPU pipeline stalls which add time variance to the code execution An outside factor is the sampling frequency of the debugger itself which normally runs asynchronous to the microcontroller s code execution speed but in some cases shows overlapping behavior which also results in an unequal function run time distri
26. g the applications energy a profile and correlating with the devices CPU state and optimizing it for a ultra low power consumption This feature is available on MSP432 devices and gt Build selected debuggers Please check the CCS for MSP432 User s Guide for gt Debug details Error Reporting E a Energy Trace technology in addition supports an enhanced energy based s code and peripheral analysis tool that is useful for measuring and viewing the alii applications energy profile and correlating with the devices CPU and peripheral states and optimizing it for ultra low power consumption This feature amp gt Help available on selected MSP430 devices and selected debuggers Please check the b Install Update CCS for MSP430 User s Guide for details p RunfDebug RRR RS ee ee ee gee b Teri Enable Auto Launch on target connect 4 Code Composer Studio Energia Terminal EnergyTrace EnergyTrace CPU State Peripheral States Cell Type CR2032 Cell voltage y 3 0 Cell capacity mAh 220 Optional Peak current continuous m4 0 0 Peak current pulse mA 0 ki l Target lifetime days 0 0 Target Connection Device MSP432 Voltage trv Restore Defaults Apply Show advanced settings Figure 11 EnergyTrace Technology Preferences 12 Code Composer Studio 6 1 for MSP432 SLAU575B March 2015 Revised May 2015 Submit Documentation Feedback Copyright 2015 Texas Instrum
27. ically indicate that the device has halted The user needs to manually hit the halt icon to enable the IDE to reconnect and show where the program has halted e Auto Run after loading a program will not work The breakpoint that is set automatically by the IDE for example at main will be hit but the IDE will not switch to halt automatically When the user halts manually after program load the program counter will be at start of main e SWO trace does not work when transitioning into power modes lower than AMO_SL or AM1_SL mode To enable the feature in CCS right click on the active project in the Project Explorer and click on Properties 26 Code Composer Studio 6 1 for MSP432 SLAU575B March 2015 Revised May 2015 Submit Documentation Feedback Copyright 2015 Texas Instruments Incorporated la TEXAS INSTRUMENTS www ti com Low Power Debug New b Add Files Copy Ctrl C Faste Ctrl V Delete Delete Refactor b Source b Move Rename F2 Import Export E Show Build Settings Build Froject Clean Project Rebuild Project Refresh F5 Close Project Build Configurations Make Targets Index Debug As Team Compare With Restore from Local History Alt Enter Figure 35 Properties Menu In the Properties window select Debug then go to Misc Other Options and enable the Allow power transitions while running if supported low power running option SLAU575B March
28. iguration File DSP BIOS v5 x Configuration File RTSC Configuration File Other Ctrle Nl Figure 3 Creating a New CCS Project e Select MSP432 as the target family see Figure 4 which limits the list of devices in the device pulldown list e Select the device being used for example MSP432P401R e Select the debug connection to use In the following example a XDS110 debug probe These settings can later be modified in the Project Properties Type a unique project name e Click Finish A new project is created and along with it a number of files are copied into the workspace SLAU575B March 2015 Revised May 2015 Submit Documentation Feedback Code Composer Studio 6 1 for MSP432 5 Copyright 2015 Texas Instruments Incorporated Creating an MSP432 Project Create a new CCS Project Target MSP432 Family Connection Texas Instruments ADS110 USB Debug Probe Default ei Cortex M MSP432 Project name MSP432_BlinkLED E Use default location Location C temp t Advanced settings Project templates and examples type filter text Toggle P1 0 by xor ing P1 0 inside of a a software loop 4 Empty Projects Empty Project Empty Project with main c Ge Empty Assembly only Project Ge Empty RTSC Project 4 Basic Examples Blink The LED Ge Blink The LED CMSIS Style Next gt Figure 4 New Project Wizard The workspace now contai
29. in and change the result shown in both Energy and Power graphs To see the absolute power consumption of an application it is recommended to use the Free Run mode In Free Run mode the debug logic of the target microcontroller is not accessed See Figure 22 for an example of the effect of energy consumption coming from debug accesses The yellow profile was recorded in Resume mode and the green profile was recorded in Free Run mode Rx Energy 5 RA Rr Oo lEnergy EnergyReff A Showing 34 118 records Figure 22 Energy Profile of the Same Program in Resume Yellow Line and Free Run Green Line 18 Code Composer Studio 6 1 for MSP432 SLAU575B March 2015 Revised May 2015 Submit Documentation Feedback Copyright 2015 Texas Instruments Incorporated la TEXAS INSTRUMENTS www ti com EnergyTrace Technology 6 7 Comparing Captured Data With Reference Data The EnergyTrace Technology can be used in various ways One is to check the device s internal states over time against the expected behavior and correct any misbehavior for example due to a peripheral not being disabled after periodic usage Another way is to compare the captured data against previously captured data The previously captured data is called the reference data in the following discussion After the reference data has been loaded a yellow reference graph is plotted in the Power and Energy windows The Power window shows the power profiles of both data
30. inaries aif 5 nihile a j MSP432 main c template P gt Debug 5 eee eee eee eee t E targetConfigs 6 p ic blink c 7 include msp h b msp432_startup_ces c 8 R gt La msp432p401r cmd es mney vaLe 11 volatile uint32 t i 12 13 WOTCTL WDTPW WDTHOLD 14 Figure 8 Launch Debug Session SLAU575B March 2015 Revised May 2015 Code Composer Studio 6 1 for MSP432 9 Submit Documentation Feedback Copyright 2015 Texas Instruments Incorporated I TEXAS INSTRUMENTS Debugging Your Application www ti com After the IDE has finished compiling linking and downloading the code to the device the debug session starts and you can begin to debug the application CCS Debug MSP432_BlinkLED blink c Code uc File Edit View Project Tools Run Scripts Window Help oy Gio ET O DVe Serie BIDiDiteie Quick Access i Fe CCS Edit 4 Debug 23 Se YF A i Variables 6 Expressions J Registers H Ala na a P MSP432_BlinkLED Code Composer Studio Device Debugging Name Value 4 gf m ainakaa ADSI10 USB Debug Probe CORTEX_M4_0 Suspended AM Core Registers Ly maini at blink c10 0x000003D0 pc ox00003D0 int0O at boot asm 222 Ox0000036E _c_int00 does not contain frar Ox20010000 00000036F xPSR 051000000 Ox00000000 Fa renner a l D l Oo l o l D l o l o l i 1 ol 10 ol 10 ol 10 ol 10 ol 10 o1 10 ol 16 ria a 0 0 0 oO 0 oOo oo i828 a I 4
31. ion To access the Debugger Access Port or DAP right click on the highlighted line that shows the CPU core and select Show all cores from the drop down menu SLAU575B March 2015 Revised May 2015 Code Composer Studio 6 1 for MSP432 23 Submit Documentation Feedback Copyright 2015 Texas Instruments Incorporated 24 I8 TEXAS INSTRUMENTS Device Security www ti com Debug 2 uae 4 a XDS100v2 ccxml Code Composer Studio Device Debugging eT ca Connect Target Ctrl Alt C Disconnect Target Ctr Alt D Enable Global Breakpoints Enable Halt On Reset Enable OS Debugging Open GEL Files View Hide core s Show all cores Group core s Syne group core s Ungroup core s Rename Remove All Terminated Relaunch Edit ADSLOOv2 ccxml Terminate and Remove Terminate Disconnect All Properties Figure 29 Show All Cores The MSP432 Debug Access Port or DAP will now be listed under Non Debuggable Devices F Debug E3 4 go a Ee XDS100v2 ccxml Code Composer Studio Device Debugging 4 y2 Non Debuggable Devices ee Texas Instruments XDS100v2 USB Emulator CS DAP_O Disconnected Texas Instruments XDS1LO0v2 USB Emulator CORTEX_M4_0 Disconnected Unknown Figure 30 List of All Cores in the MSP432 Now right click on the DAP and select Connect Target Code Composer Studio 6 1 for MSP432 SLAU575B March 2015 Revised May 2015 Submit Documentation Feedback Copyright 2015
32. itions limitations and notices TI is not responsible or liable for such altered documentation Information of third parties may be subject to additional restrictions Resale of TI components or services with statements different from or beyond the parameters stated by TI for that component or service voids all express and any implied warranties for the associated Tl component or service and is an unfair and deceptive business practice TI is not responsible or liable for any such statements Buyer acknowledges and agrees that it is solely responsible for compliance with all legal regulatory and safety related requirements concerning its products and any use of TI components in its applications notwithstanding any applications related information or support that may be provided by TI Buyer represents and agrees that it has all the necessary expertise to create and implement safeguards which anticipate dangerous consequences of failures monitor failures and their consequences lessen the likelihood of failures that might cause harm and take appropriate remedial actions Buyer will fully indemnify Tl and its representatives against any damages arising out of the use of any Tl components in safety critical applications In some cases Tl components may be promoted specifically to facilitate safety related applications With such components Tl s goal is to help enable customers to design and create their own end product solutions that meet applicable f
33. l TEXAS INSTRUMENTS User s Guide SLAU575B March 2015 Revised May 2015 Code Composer Studio 6 1 for MSP432 This manual describes the use of the Tl Code Composer Studio IDE CCS version 6 1 with the MSP432 low power microcontrollers This manual describes only CCS for Windows operating systems The versions of CCS for Linux and Mac OS X operating systems are similar and therefore are not described separately OONOOOFWDND CON OOF WD 20 Contents installing Code Composer Studio IDE ecsttec tte ee vecdectanstc ys notacesacbus a vend eneek 3 Updating Code Composer Studio IDE 2 0 cccccc cece cece eeeeeeeee een eee eee eee 3 Creating an MSP432 Project earren E E Ea 5 Additional MSP432 Examples and Documentation sasasassssnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 7 Debugging Yo r AOC CAC Mxnccorsteccmatacvowsiesanwesensnteacneecnive EEEE aac vorsumseann 8 Energy Trace Technology ssicnivsovecensbutavesdaimcraesdxauaeswsanetesecsaendiwanatestniwas PEAARU NENE 11 DEVICE SO CUI eaae E E i 22 ONR Ower DEDU oeer a a EE aA 26 Frequently Asked QUESTIONS uanasnsnnsnnnnnnnnnnnnnnnnnrnnnnennnnrnnnnrnnnnnnnnnnnnnnrnnnnnnnnnnnnnnnnnnnnn nunnan 29 Additional Code Composer Studio INOrmaNON sisisrsrininiiei inoa 30 PCIe E E ETT crac crn ns TET T T A T E E T TTE A T 30 Check Tor UG G16 S irenstea E E E E 3 Avalaple UPO AIES 4 vcnutsveus tosesabueduerestat peussedeeierrsuini r EEEE te
34. lmost equal in the given accuracy range Q What are the influencing factors for the accuracy of the energy measurement A The energy measurement circuit is directly supplied from the USB bus voltage and thus it is sensitive to USB bus voltage variations During calibration the energy equivalent of a single dc dc charge pulse is defined and this energy equivalent depends on the USB voltage level To ensure a good repeatability and accuracy power the debugger directly from an active USB port and avoid using bus powered hubs and long USB cables that can lead to voltage drops especially when other consumers are connected to the USB hub Furthermore the LDO and resistors used for reference voltage generation and those in the calibration circuit come with a certain tolerance and ppm rate over temperature which also influences accuracy of the energy measurement Q am trying to capture in EnergyTrace mode or EnergyTrace mode with a MSP432 device that is externally powered but there is no data shown in the Profile Energy Power and States window A Both EnergyTrace mode and EnergyTrace mode require the target to be supplied from the debugger No data can be captured when the target microcontroller is externally powered Q cannot measure LPM currents when am capturing in EnergyTrace mode am expecting a few microamps but measure more than 150 LA A Reading digital data from the target microcontroller consumes energy in the JTAG do
35. mW 4 Voltage Mean 3 59V 4 Current Mean O49 mA Min 0 298 mA Max 2 213 mA Battery Life CR2032 18 8 day est Figure 19 EnergyTrace Profile Window The Power window see Figure 20 shows the dynamic power consumption of the target over time The current profile is plotted in light blue color while a previously recorded profile that has been reloaded for comparison is plotted in yellow color Rx Power 53 ee R Yor 4 b amp Warning Debugger activity such as breakpoint polling 9 Figure 20 Zoom Into Power Window The Energy window see Figure 21 shows the accumulated energy consumption of the target over time The current profile is plotted in light blue color while a previously recorded profile that has been reloaded for comparison is plotted in yellow color SLAU575B March 2015 Revised May 2015 Code Composer Studio 6 1 for MSP432 17 Submit Documentation Feedback Copyright 2015 Texas Instruments Incorporated ld TEXAS INSTRUMENTS EnergyTrace Technology www ti com Rx Energy 53 QQQ Y OB 4 ala amp Warning Debugger activity such as breakpoint polling 9 Figure 21 Current Profile Blue With Recorded Profile Yellow NOTE During program execution through the debugger s view Resume button the target microcontroller is constantly accessed by the JTAG or Spy Bi Wire protocol to detect when a breakpoint has been hit Inevitably these debug accesses consume energy in the target doma
36. main of the microcontroller Hence an average current of approximately 150 WA is measured when connecting an ampere meter to the device power supply pins If you want to eliminate energy consumption through debug communication switch to EnergyTrace mode and let the target microcontroller execute in Free Run mode Q My LPM currents seem to be wrong am expecting a few microamps but measure more even in Free Run mode or when letting the device execute without debug control from an independent power supply A The most likely cause of this extra current is improper GPIO termination as floating pins can lead to extra current flow Also check the JTAG pins again especially when the debugger is still connected but idle as the debugger output signal levels in idle state might not match how the JTAG pins have been configured by the application code This could also lead to extra current flow SLAU575B March 2015 Revised May 2015 Code Composer Studio 6 1 for MSP432 21 Submit Documentation Feedback Copyright 2015 Texas Instruments Incorporated Ze I TEXAS INSTRUMENTS Device Security www ti com Q When start the EnergyTrace windows through View Other EnergyTrace before launching the debug session data capture sometimes does not start A Enable EnergyTrace through Window Preferences Code Composer Studio Advanced Tools gt EnergyTrace Technology When launching a debug session the Energy Trace
37. ments Incorporated I TEXAS INSTRUMENTS www ti com Updating Code Composer Studio IDE Available Updates Check the updates that you wish to install com ticgt dmed win32 feature group com ticgt msp430 4 2 wins2 feature gr com tLocstudio msp430 emu win32 tea com sd ccstudic emulation wins2 feate com t emulation pack win32 feature gi uh Compiler Tools On line Documentation Wit MSP430 Compiler Tools it MSP430 Emulators Lah Spectrum Digital Emulators lank TI Emulators 4 lt Back Figure 2 Available Updates 4 Code Composer Studio 6 1 for MSP432 SLAU575B March 2015 Revised May 2015 Submit Documentation Feedback Copyright 2015 Texas Instruments Incorporated la TEXAS INSTRUMENTS www ti com 3 Creating an MSP432 Project Creating an MSP432 Project CCS organizes its projects in workspaces A new workspace is generated automatically when you start CCS the first time This workspace is blank To create a new project in that workspace e Click File New CCS Project CCS Edit Code Composer Studio I File Edit View Navigate Project Scripts Run Window Help Open File Close Close All Save Save As Save All Revert Move Rename 21 Refresh Alt Shift N f i Ctrl W Ctrl Shitt W Ctrl 5 Ctrl Shitt S F2 i a R D wi CCS Project Project Source File Header File Class File from Template Folder Target Conf
38. ns a newly created project including e A basic main c file l TEXAS INSTRUMENTS www ti com e The interrupt vector file msp432_startup_ccs c where all interrupt handlers are predefined e The linker command file msp432p401r cmd e The target configuration MSP432P401R ccxml file including a link to the XDS 110 debug probe 6 Code Composer Studio 6 1 for MSP432 SLAU575B March 2015 Revised May 2015 Submit Documentation Feedback Copyright 2015 Texas Instruments Incorporated la TEXAS INSTRUMENTS www ti com Additional MSP432 Examples and Documentation CCS Edit MSP432_BlinkLED mainc Code Composer Studio iI T tt ae File Edit View Navigate Project Run Scripts Window Help t RVIDiB VID VIE Project Explorer 52 BS YT GB E maine amp MSP432_BlinkLED Active Debug 17 Neither the name oT Texas Instruments Incorporated nor the names ot gt ie Includes 18 its contributors may be used to endorse or promote products derived 19 from this software without specific prior written permission Debug 20 4 targetConfigs 21 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS MSP432P401R ccxml Active Default 22 AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES INCLUDING BUT NOT readme idt 23 LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR z 24 A PARTICULAR PURPOSE ARE DISCLAIMED IN NO EVENT SHALL THE COPYRIGHT gt main c 25 OWNER
39. on these items see the appropriate TI documents listed in Important MSP432 Documents on the Web Important MSP432 Documents on the Web The primary sources of MSP432 information are the device specific data sheets and user s guides The MSP432 web site www ti com msp432 contains the most recent version of these documents Documents describing the Code Composer Studio tools Code Composer Studio IDE assembler C compiler linker and librarian can be found at www ti com tool ccstudio A CCS specific Wiki page FAQ is available at processors wiki ti com index php Category CCS and the Texas Instruments E2E Community support forums at e2e ti com provide additional help Documentation for third party tools such as IAR Embedded Workbench for ARM or the Segger J Link debug probe can be found on the respective company s website If You Need Assistance 2 Support for the MSP482 devices and the hardware development tools is provided by the Texas Instruments Product Information Center PIC Contact information for the PIC can be found on the TI web site at www ti com support The Texas Instruments E2E Community support forums for the MSP432 at e2e ti com provide open interaction with peer engineers Tl engineers and other experts Additional device specific information can be found on the MSP432 web site at www ti com msp432 Code Composer Studio 6 1 for MSP432 SLAU575B March 2015 Revised May 2015 Submit Documentation Feed
40. oscovecegenssocneveceume E r vase aruesnesescerers cca ece Fi Code Composer Studio MSP432 E2E LaunchPad are trademarks of Texas Instruments ARM is a registered trademark of ARM Ltd OS X is a registered trademark of Apple Inc IAR Embedded Workbench is a trademark of IAR Systems Linux is a registered trademark of Linus Torvalds Windows is a registered trademark of Microsoft Corporation SLAU575B March 2015 Revised May 2015 Code Composer Studio 6 1 for MSP432 1 Submit Documentation Feedback Copyright 2015 Texas Instruments Incorporated I TEXAS INSTRUMENTS www ti com 21 Current Profile Blue With Recorded Profile YelOW 0 ccccecceeee ee eeeeeeeeeeeeeeeeneeeesseeenenesseaannnees 18 22 Energy Profile of the Same Program in Resume Yellow Line and Free Run Green Line 0sse0eees 18 23 Gomparng Profiles im Energy Tracer MOQUE scccsncecectesteceneetecensvemescmeedseetesunuexddedereneeeiandeeevssezances 19 24 Comparing Profiles in Energy Trace Mod src cenccissnrecexaeeveteerccdvcutcaneedeest R EEEE EE 20 25 Show Target Configuration VieW cccccccccc cece eee eee eee a n a a aaa aE 22 26 GCO Ta ek an Ut aulOMe iais ieee teers eel ere te eeeeee sec oaar eave eves A A EEA 23 27 Launch Selected Target COMIGuIrallOM cvececennssctncnteaceieasnccse teens e EEEa 23 28 Debug View After Launching Target Configuration ccccceeeeee eee e ee eeee eee e eee ee nee eeeeeneneeneeeaneneeneees 23 29 BOW FS Ol C
41. ough the dedicated debug pins only Figure 39 shows how to configure the debugger to use SWD instead of JTAG by modifying the MSP432P401R ccxml file Project Explorer 3 E 7 G E mspaz2paoir ceaml 3 tS blink Active Deb E aan ee Target Configuration amp Debug All Connections Connection Properties Set th rties of the selected ction 4 T Texas Instruments XDS110 USB Debug Probe Import i ha a SORT 4 gt MSP432P401R Board Data File auto generate X i New A blink c a amp CS DAPO Debug Probe Selection Only on A msp432_startup_ccs c a R subpath_0 Add f msp432p401r cmd 4 CORTEX_M4_0 M SWD Mode Settings Use 1149 1JTAG_SWD Mode is disabled Delete Use 1149 1 JTAG SWD Mode is disabled Use SWD Mode with SWO Trace disabled N Up Use SWD Mode with SWO Trace enabled Test Connection Basic Source Figure 39 Change Debugger Settings to SWD e If even this cannot connect reset the device to factory settings Review Section 7 for information on how to perform a factory reset on the device SLAU575B March 2015 Revised May 2015 Code Composer Studio 6 1 for MSP432 29 Submit Documentation Feedback Copyright 2015 Texas Instruments Incorporated I TEXAS INSTRUMENTS Additional Code Composer Studio Information www ti com Q Why doesn t the back channel UART on the MSP432 LaunchPad work with my serial terminal program at speeds faster than 56000
42. ripts Window Help Or Oi Wao OP De Seria mG Oita Quccicces af ccsese CSOD 4f Debug 5 Y A Wilf Registers EnergyTrace Technology 5 6 i States X QAR hh b labl_power Code Composer Studio Device Debugging Og HS Ds gt i a p Texas Instruments XDS110 USB Debug Probe CORTEX_M4_0 Free Running E a B nergyTrace Profile E E Name Runtime Energy System 100 100 a CPU Active Mode Ess 83 0 993 a Low Power Mode G3 17 0 07 LPMx 17 0 07 ce labl_power c labl_power_solution c 3 A cpu c labl_power_startup_ccs c m 66 _ 67 int main void Halting the Watchdog WDT_A_holdTimer InitializeDevice curPowerState i Showing 118 810 records Console Rx Power 33 QA R a A e Showing 794 records RI l Full License LE Showing 118 810 records Figure 13 Debug Session With EnergyTrace Graphs The Profile window see Figure 14 is the control interface for EnergyTrace It can be used to set the capturing time or to save the captured data for later reference The Profile window also displays a compressed view of the captured data and allows comparison with previous data bint Registers 4 EnergyTrace Technology 3 A O S He E M EnergyTrace Profile 5 Mame Runtime 7 Energy 7a System 100 100 a CPU Active Mode SSS 83 0 Eee 99 3 a Low Power Mode IE 17 0 0 7 LP Mx C 17 0 0 7 Figure 14
43. selected MSP432 devices and debuggers EnergyTrace mode without the is the base of EnergyTrace Technology and enables analog energy measurement to determine the energy consumption of an application but does not correlate it to internal device information The EnergyTrace mode is available for all MSP432 devices with selected debuggers including CCS Energy Measurement Debuggers with EnergyTrace Technology support include a new and unique way of continuously measuring the energy supplied to a target microcontroller that differs considerably from the well known method of amplifying and sampling the voltage drop over a shunt resistor at discrete times A software controlled dc dc converter is used to generate the target power supply The time density of the dc dc converter charge pulses equals the energy consumption of the target microcontroller A built in on the fly calibration circuit defines the energy equivalent of a single dc dc charge pulse Figure 10 shows the energy measurement principle Periods with a small number of charge pulses per time unit indicate low energy consumption and thus low current flow Periods with a high number of charge pulses per time unit indicate high energy consumption and also a high current consumption Each charge pulse leads to a rise of the output voltage Voy which results in an unavoidable voltage ripple common to all dc dc converters Current Vout Pulse Figure 10 Pulse Density and Current Flo
44. sets over time and is useful to determine any changes in static power consumption for example due to use of a deeper low power mode or disabling of unused peripherals It also shows how the dynamic power consumption has changed from one measurement to the other for example due to ULP Advisor hints being implemented The Energy window shows the accumulated energy consumption over time and gives an indication which profile is more energy efficient In the EnergyTrace mode the condensed view of both captured and reference data is displayed in the Profile window see Figure 23 You can quickly see how the overall energy consumption and use of power modes peripherals and clocks changed between both capture sessions In general parameters that have become better are shown with a green bar and parameters that have become worse are shown with a red bar For example time spent in Active Mode is generally seen as negative Hence if a code change makes the application spend less time in active mode the negative delta is shown as a green bar and the additional time spent in a low power mode is shown as a green bar EnergyTrace Technology 52 i lal S pE i H Reference EnergyTrace_D_2015_01_15_120933 EnergyTrace Profile Name Runtime Energy Delta Runtime Delta Energy Reference Runtime Reference Energy System 100 231397 8 O es 497 8 100 100 4 CPU 4 Low Power Mode Ga 72 2 0 0 ess 482 0 2 0 E 2
45. t the mass erase has been executed Now you can terminate the debug connection After you have power cycled the device it is accessible in a normal way again SLAU575B March 2015 Revised May 2015 Code Composer Studio 6 1 for MSP432 25 Submit Documentation Feedback Copyright 2015 Texas Instruments Incorporated I TEXAS INSTRUMENTS Low Power Debug www ti com El Console 52 ADSLOOV2 ccxml CS DAP GEL Output Executing mass erase to remove all device protection CS DAP GEL Output Mass erase executed Please terminate and restart debug session Figure 34 Mass Erase Script Console Output 8 Low Power Debug Under normal debug control MSP432 microcontrollers will not transition into low power modes deeper than LPMO mode i e into either LPMO_VCOREO or LPMO_VCORE1 mode This behavior is a consequence of the standardized Cortex M debug architecture Subsequently especially current consumption and IRQ wake up timing will be different from a free running application If users want to verify the current consumption and timing of their application while still being under basic debug control MSP432 offers the Low Power Run feature When enabled the MCU will transition into exactly the low power mode the user has specified with internal clocks being disabled and the power management module shutting down internal power domains This has some implications e Previously set breakpoints will be hit but the IDE will not automat
46. the sampling frequency of EnergyTrace technology A The sampling frequency depends on the debugger and the selected debug protocol and its speed setting It typically ranges from 1 kHz for example when using the Spy Bi Wire interface set to SLOW up to 3 2 kHz for example when using the JTAG interface set to FAST The debugger polls the state information of Energy Trace from the device status information Depending on the sampling frequency a short or fast duty cycle active peripheral state may not be captured on the State graph In addition the higher sampling frequency affects the device energy consumption under EnergyTrace Q What is the sampling frequency of EnergyTrace technology A The sampling frequency to measure the energy consumption is the same independent of which debug protocol or speed and is approximately 4 2 kHz in Free Run mode Q My Power graph seems to include noise Is my board defective A The power values shown in the Power graph are derived that is calculated from the accumulated energy counted by the measurement system When the target is consuming little energy a small number of energy packets over time are supplied to the target and the software needs to accumulate the dc dc charge pulses over time before a new current value can be calculated For currents under 1 uA this can take up to one second while for currents in the milliamp range a current can be calculated every millisecond Additional filterin
47. unctional safety standards and requirements Nonetheless such components are subject to these terms No Tl components are authorized for use in FDA Class III or similar life critical medical equipment unless authorized officers of the parties have executed a special agreement specifically governing such use Only those Tl components which TI has specifically designated as military grade or enhanced plastic are designed and intended for use in military aerospace applications or environments Buyer acknowledges and agrees that any military or aerospace use of Tl components which have not been so designated is solely at the Buyer s risk and that Buyer is solely responsible for compliance with all legal and regulatory requirements in connection with such use Tl has specifically designated certain components as meeting ISO TS16949 requirements mainly for automotive use In any case of use of non designated products TI will not be responsible for any failure to meet ISO TS16949 Products Audio Amplifiers Data Converters DLP Products DSP Clocks and Timers Interface Logic Power Mgmt Microcontrollers RFID OMAP Applications Processors Wireless Connectivity www ti com audio amplifier ti com dataconverter ti com www dip com www ti com clocks interface ti com logic ti com power ti com microcontroller ti com www ti rfid com www ti com omap Applications Automotive and Transportation Communications and Tel
48. w The benefit of sampling continuously is evident even the shortest device activity that consumes energy contributes to the overall recorded energy No shunt based measurement system can achieve this Code Composer Studio Integration EnergyTrace Technology is available as part of Texas Instrument s Code Composer Studio IDE for MSP432 microcontrollers During debugging of an application additional windows are available if the hardware supports EnergyTrace Technology Enabling EnergyTrace Technology and Selecting the Default Mode By default the EnergyTrace Technology feature is disabled in the Code Composer Studio Preferences To enable it go to Window Preferences gt Code Composer Studio Advanced Tools EnergyTrace Technology see Figure 11 SLAU575B March 2015 Revised May 2015 Code Composer Studio 6 1 for MSP432 11 Submit Documentation Feedback Copyright 2015 Texas Instruments Incorporated I TEXAS INSTRUMENTS EnergyTrace Technology www ti com EnergyTrace Technology n type filter text Aa Energy Trace technology enables analog energy measurement to determine the energy consumption of an application This feature is available for all 4 Advanced Tools devices with selected debuggers Disk Usage EnergyTrace Technology EnergyTrace technology in addition supports an energy based code ee ye ee analysis tool that is useful for measuring and viewin
49. windows automatically open and data capture starts when the device executes If you accidentally close all Energy Trace windows during a debug session you can reopen them through View Other EnergyTrace Device Security If you have disabled JTAG access on the device or are working on an application where you need to unlock a secure IP zone the lock can be only be removed by erasing all Flash memory including USER and INFO memory through a debugger invoked reboot cycle To unlock a device the following steps are required e Select a Target Configuration that matches the current debugger type e Execute a script that triggers a reboot erase These steps will be explained in detail next Go to View Target Configurations to see the available debugger configurations View Navigate Project Scripts Run Window yg TI Resource Explorer a Grace Snippets 4 Project Explorer Outline Alt Shift Q O Advice Problems Alt Shift Q X l Console Alt Shift Q C Optimizer Assistant i s G Debug Memory Browser 5 T Registers oo ich Expressions Variables Alt Shit Q V Disassembly Breakpoints Alt Shift Q B Modules lI i a EE Other Alt Shitt Q Figure 25 Show Target Configuration View CCS will open a view showing the target configurations it can identify in the current workspace Pick the one that works for the device and debugger In our example we ar
Download Pdf Manuals
Related Search