Emprog. Quick Start Guide. Emprog ThunderBench MSP430 FAQ. Version 1.2. Nov Page 1

Transcription

1 Emprog ThunderBench MSP430 FAQ Version 1.2 Nov 2014 Page 1

2 TI MSP430 General FAQ This guide is a quick overview and FAQ related to the Texas Instruments MSP430. If you have any question that is not covered by this document please feel free to contact Emprog support at support@emprog.com. Known issues - Each time you change project please restart the XDS Agent, the XDS Agent (or GDBServer) does not need to restart if you are debugging the same project. If you switch project simply close it and Emprog ThunderBench will prompt you again. - Sometimes you get in the console a warning about failing to load symbol table, you can safely ignore it. - Some launchpads boards like the G2, report Already in use in the XDS Agent, this is because on some computers the driver does not load well into Windows. - Please remember when debugging that you only have two hardware breakpoints. Stopping at main() will consume one HW BP. You can resume to the next breakpoint then clear it to enable to assign a new one. FAQ Interrupts: - To declare an interrupt service routine the syntax is as follow: interrupt(timer0_a0_vector) Timer_A (void) Where TIMER0_A0_VECTOR is the interrupt vector number and Timer_A is the actual ISR Name. You can fetch the interrupt vector number from the I/O header file like the msp430f5529.h under section called Interrupt Vectors - Tip: You can start typing interr and then press ctrl-space, the editor will add the ISR for you. To convert ISRs from other tools please follow the example in any BSP or for example: #pragma vector=timer1_a0_vector interrupt void TIMER1_A0_ISR (void) Will become interrupt(timer1_a1_vector) TIMER1_A1_ISR (void) Page 2

3 Placing variables or function into upper memory in the 430X: -To place a function in the upper memory section in 430X the syntax is as follow: void attribute ((section (".upper.text "))) My_Func (void) My Func will be allocated in upper memory starting at address 0x Tip: You can start typing upper and then press ctrl-space, the editor will add the proper attribute before the function name. The auto-complete might add an extra void if you already have a return type. Placing variables or tables into flash at a certain address (method 1): -To place a variable at a certain address in flash the syntax is as follow: unsigned long HighScore attribute((section (".HighScore"))); Section HighScore should be declared in the linker map file (.ld) for example: SECTIONS {.APP_DATA : /* Section Name */ { KEEP(*(.HighScore)) } >APP_DATA /* Memory Region Name at address */ interrupt_vector_1 interrupt_vector_2 interrupt_vector_3 : { KEEP (*( interrupt_vector_1 )) } > VECT1 : { KEEP (*( interrupt_vector_2 )) } > VECT2 : { KEEP (*( interrupt_vector_3 )) } > VECT3 APP_DATA is the memory region address and also must be defined in the.ld file as follow: INFOD : ORIGIN = 0x1800, LENGTH = 0x0080 /* END=0x187F, size 128 */ ROM (rx) : ORIGIN = 0x4400, LENGTH = 0xB778 /* END=0xB778, size */ APP_DATA : ORIGIN = 0xFB78, LENGTH = 0x08 APP_FRAM_SPEED : ORIGIN = 0xFB80, LENGTH = 0x0400 HighScore will be allocated in section APP_DATA at address 0xFB78 and its length is )x08 bytes. Placing variables or tables into flash at a certain address (method 2): -To place a variable at a certain address in flash the syntax is as follow: unsiogned dataarray[1000] attribute((section(".dataarray"))); Section.dataArray should be declared in the linker map file (.ld) for example: SECTIONS {.dataarray 0x9000: /* section name at address */ { KEEP(*(.dataArray)) } >ROM /* Memory Region */ interrupt_vector_1 : { KEEP (*( interrupt_vector_1 )) } > VECT1 dataarray[1000] will be allocated in memory region ROM start address 0x9000. Page 3

4 Helpful intrinsic functions : - You can check all helpful intrinsic function in in430.h, which is always included in the main msp430.h. You can find in430.h in directory 430\include. Some helpful frequently used intrinsic functions: * starts with single _ or double no_operation() _disable_interrupts() _enable_interrupts() _get_interrupt_state() _set_interrupt_state(x) _bic_sr_register(x) _bis_sr_register(x) _get_sr_register() _bic_sr_register_on_exit(x) _bis_sr_register_on_exit(x) _get_sp_register() _set_sp_register(x) _data16_write_addr(addr,src) _data16_read_addr(addr) _data20_write_char(addr,src) _data20_read_char(addr) // Enter Low Power Mode 0 with Global Interrupts Enabled bis_sr_register(lpm0_bits+gie); // Enter LPM3.5 mode with interrupts enabled. Note that this function will // not return, but rather the device will go through a RESET-like sequence. bis_sr_register(lpm3_bits GIE); // Sleep in LPM3 bis_sr_register(lpm3_bits + GIE); // Exit LPM3 bic_sr_register_on_exit(lpm3_bits); #define no_init attribute ((section (".noinit"))) #define interrupt(vec) void attribute ((interrupt(vec))) Page 4

5 General Notes : - Make sure you have msp430.h included in all your projects, can be included in main. - Make sure you always have a preprocessor define in your project, please check properties>settings>compiler>preprocessor >>> MSP430G2553 (name of device). This will help pick up the proper I/O file from msp430.h that must be included in all your projects. - At the time of this document, the user must manually place functions in the upper memory to make room in the lower memory. The process is easy, when you exceed the space in the lower memory, please pick the biggest functions and place them in upper memory. With manual memory managment the user can make use of every byte in lower and upper memory. This is applicable only for devices with msp430x architecture. Page 5

6 Page 6

7 Page 7

8 Page 8

9 Page 9

10 Page 10

11 Page 11

12 Page 12

13 Page 13

14 Page 14

15 Page 15

16 Page 16

17 Page 17

18 Page 18

19 Page 19

20 Page 20

21 Page 21