In the MSP430F5152 datasheet's BSL section it lists Data Transmit for the 40-pin QFN RSB package as P3.5 - 34 and P3.7 - 36.  It eludes that a register setting would allow transmit to happen on either pin.  I'm not seeing anything in the SYSCTL or SYSBSLC registers that would set this.  In SLAU319 it says "TX and RX pins are noted in the device data sheet" and doesn't elaborate.

My schematic is wired with Pin 34 connected yet I'm seeing data presented on Pin 36.  Am I correctly understanding the datasheet that the transmit can come out of either pin?  If so, how do I set that?

I want debugger/emulator for MSP430F5324 custom board.

Can I use spyby wire connection from launchpad MSP430F5529

Hello, 

I am a teaching assistant for a course in which we use the TI MSP432P401R LaunchPad at the Georgia Institute of Technology, Atlanta GA. Back in January 2016, when I took the course, we used CCS version 6.1.2.00015 and MSPWare version 2_20_00_19 which has driverlib.h version 2_20_00_08 

The problem with using this version of CCS was that it was not MacOS compatible and students with Mac laptops had to use lab computers. Therefore, we have decided to use CCS version 6.1.3.00033 as it is both MacOS compatible and it supports MSP432 platform.

However, my code does not compile when I use CCS version 6.1.3.00033 and MSPWare version 2_20_00_19 which has driverlib.h version 2_20_00_08. The reason I am using the older version of driverlib is because the MACROS have changed in recent versions as compared to what I had learnt in Spring.

We would like to stick with the old MACROS but use a MacOS compatible version of CCS. Please guide me if there is a solution for that. 

I get the following error messages in my console, when I try to flash a program onto the MSP432 launchpad:-

**** Build of configuration Debug for project test2 ****

"C:\\ti\\ccsv6\\utils\\bin\\gmake" -k all
'Building file: ../main.c'
'Invoking: MSP432 Compiler'
"C:/ti/ccsv6/tools/compiler/ti-cgt-arm_15.12.1.LTS/bin/armcl" -mv7M4 --code_state=16 --float_support=FPv4SPD16 -me --include_path="C:/ti/ccsv6/ccs_base/arm/include" --include_path="C:/ti/ccsv6/ccs_base/arm/include/CMSIS" --include_path="C:/Users/Marcus/workspace_v6_1_3/test2/driverlib/MSP432P4xx" --include_path="C:/ti/ccsv6/tools/compiler/ti-cgt-arm_15.12.1.LTS/include" --advice:power=all -g --gcc --define=__MSP432P401R__ --define=TARGET_IS_MSP432P4XX --define=ccs --diag_wrap=off --diag_warning=225 --display_error_number --abi=eabi --preproc_with_compile --preproc_dependency="main.d" "../main.c"

>> Compilation failure
subdir_rules.mk:7: recipe for target 'main.obj' failed
"C:\Users\Marcus\workspace_v6_1_3\test2\driverlib\MSP432P4xx\pmap.h", line 76: warning #48-D: incompatible redefinition of macro "P1MAP" (declared at line 1286 of "C:\ti\ccsv6\ccs_base\arm\include\msp432p401r.h")
"C:\Users\Marcus\workspace_v6_1_3\test2\driverlib\MSP432P4xx\pmap.h", line 77: warning #48-D: incompatible redefinition of macro "P2MAP" (declared at line 1287 of "C:\ti\ccsv6\ccs_base\arm\include\msp432p401r.h")
"C:\Users\Marcus\workspace_v6_1_3\test2\driverlib\MSP432P4xx\pmap.h", line 78: warning #48-D: incompatible redefinition of macro "P3MAP" (declared at line 1288 of "C:\ti\ccsv6\ccs_base\arm\include\msp432p401r.h")
"C:\Users\Marcus\workspace_v6_1_3\test2\driverlib\MSP432P4xx\pmap.h", line 79: warning #48-D: incompatible redefinition of macro "P4MAP" (declared at line 1289 of "C:\ti\ccsv6\ccs_base\arm\include\msp432p401r.h")
"C:\Users\Marcus\workspace_v6_1_3\test2\driverlib\MSP432P4xx\pmap.h", line 80: warning #48-D: incompatible redefinition of macro "P5MAP" (declared at line 1290 of "C:\ti\ccsv6\ccs_base\arm\include\msp432p401r.h")
"C:\Users\Marcus\workspace_v6_1_3\test2\driverlib\MSP432P4xx\pmap.h", line 81: warning #48-D: incompatible redefinition of macro "P6MAP" (declared at line 1291 of "C:\ti\ccsv6\ccs_base\arm\include\msp432p401r.h")
"C:\Users\Marcus\workspace_v6_1_3\test2\driverlib\MSP432P4xx\pmap.h", line 82: warning #48-D: incompatible redefinition of macro "P7MAP" (declared at line 1292 of "C:\ti\ccsv6\ccs_base\arm\include\msp432p401r.h")
"../main.c", line 47: error #20: identifier "SMCLK_EN" is undefined
"../main.c", line 47: error #20: identifier "SELM_3" is undefined
"../main.c", line 47: error #20: identifier "DIVS_0" is undefined
"../main.c", line 66: error #20: identifier "EUSCI_A0_MODULE" is undefined
"../main.c", line 72: error #20: identifier "TIMER_A0_MODULE" is undefined
"../main.c", line 74: error #20: identifier "INT_TA0_0" is undefined
"../main.c", line 80: error #20: identifier "ADC14RES_1" is undefined
"../main.c", line 81: error #20: identifier "ADC14SSEL_4" is undefined
"../main.c", line 81: error #20: identifier "ADC14PDIV_0" is undefined
"../main.c", line 81: error #20: identifier "ADC14DIV_0" is undefined
"../main.c", line 83: error #20: identifier "ADC14VRSEL_0" is undefined
"../main.c", line 83: error #20: identifier "ADC14INCH_0" is undefined
"../main.c", line 130: remark #1528-D: (ULP 3.1) Detected flag polling using UCA0IFG. Recommend using an interrupt combined with enter LPMx and ISR
"../main.c", line 113: remark #2623-D: (ULP 5.4) Detected an assignment to a type with size less than int. To avoid unnecessary sign extension, use int-sized types for local varaibles and convert to smaller types for static storage.
"../main.c", line 113: remark #1532-D: (ULP 5.3) Detected sprintf() operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"../main.c", line 115: remark #2623-D: (ULP 5.4) Detected an assignment to a type with size less than int. To avoid unnecessary sign extension, use int-sized types for local varaibles and convert to smaller types for static storage.
"../main.c", line 110: remark #2623-D: (ULP 5.4) Detected an assignment to a type with size less than int. To avoid unnecessary sign extension, use int-sized types for local varaibles and convert to smaller types for static storage.
"../main.c", line 113: remark #2623-D: (ULP 5.4) Detected an assignment to a type with size less than int. To avoid unnecessary sign extension, use int-sized types for local varaibles and convert to smaller types for static storage.
"../main.c", line 115: remark #2623-D: (ULP 5.4) Detected an assignment to a type with size less than int. To avoid unnecessary sign extension, use int-sized types for local varaibles and convert to smaller types for static storage.
"../main.c", line 110: remark #2623-D: (ULP 5.4) Detected an assignment to a type with size less than int. To avoid unnecessary sign extension, use int-sized types for local varaibles and convert to smaller types for static storage.
"../main.c", line 183: error #20: identifier "TIMER_A0_MODULE" is undefined
"../main.c", line 175: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
13 errors detected in the compilation of "../main.c".
gmake: *** [main.obj] Error 1
gmake: Target 'all' not remade because of errors.

**** Build Finished ****

Thanks, 
Marcus Pereira 

email: mpereira30@gatech.edu 

hi all,

I've been trying to use the getting started with wlan station code for a couple of weeks now. I have an MSP430FR6989 and a CC3100 wifi booster pack.  Is there a board.h and board.c file available for each board or is it a case of coding one? at the minute, using one of the examples I have errors such as undefined "CSCTL0_H" is undefined and CSCTL0_L is undefined.

Any help or pointer would be great,

Thanks,

Ciaran

Hi,

Ive got a launchpad with a g2553, ive just received 2 nrf24l01 transceivers, is there a simple code sample that just sets up the device to constantly transmit like a hello world message or something similar. the reason is that Ive got an arduino listening on the other side. Ive managed to get two arduino uno's talking but am having difficulty with the msp430. the code samples seems a bit much to start off with. I have downloaded the libraries too.

thanks guys

Sir

    In UART transmission the current consumption in all LPM the multimeter shows 1.7.During sleep mode i'm unable to achieve the current mentioned in the graph.Here with I hav attached my code.

#include <msp430g2553.h>

#define LED0 BIT0
#define LED1 BIT6
#define BUTTON BIT3

void uart_init( void )
{

P1DIR = 0xFF;
P2DIR = 0xFF;
P1DIR |= LED0 + LED1; // P1.0 and P1.6 output
P1OUT &= ~(LED0 + LED1); // set P1.0 to 0 (LED OFF)
P1DIR &= ~BUTTON;
P1OUT |= BUTTON;
P1IES ^= BUTTON;
P1IE |= BUTTON; // P1.3 interrupt enabled
P1IFG &= ~BUTTON; // P1.3 IFG cleare
P1REN = BUTTON;
P1SEL |= BIT1 + BIT2; // to select transmit and receive pin
P1SEL2 |= BIT1 + BIT2;
UCA0CTL1 = UCSWRST; // USCI Clock = SMCLK,USCI_A0 disabled
UCA0CTL1 |= UCSSEL_2; // USCI Clock = SMCLK,USCI_A0 disabled
UCA0BR0 = 104; //104 From datasheet table-
UCA0BR1 = 0x00; //-selects baudrate =9600,clk = SMCLK
UCA0MCTL = UCBRS_1; // Modulation value = 1 from datasheet
UCA0STAT |= UCLISTEN; // loop back mode enabled
UCA0CTL1 &= ~UCSWRST; // Clear UCSWRST to enable USCI_A0
//IE2 |= UCA0TXIE; // Enable the Transmit interrupt
//IE2 |= UCA0RXIE; // Enable the Receive interrupt

}

int main(void)

{

WDTCTL = WDTPW + WDTHOLD; // Stop Watchdog timer

BCSCTL1 = CALBC1_1MHZ; // Set range
DCOCTL = CALDCO_1MHZ; // Set DCO step + modulation
uart_init();

__enable_interrupt(); // enable all interrupts
_BIS_SR(LPM4_bits + GIE); // Enter LPM4 w/interrupt

}

// Port 1 interrupt service routine
#pragma vector=PORT1_VECTOR
__interrupt void Port_1(void)
{

UCA0TXBUF = 'h'; //assigning data
while (!(IFG2 & UCA0TXIFG)) ;
PIFG2 &= ~UCA0RXIFG; // Clear RX flag
P1IFG &= ~BUTTON; // P1.3 IFG cleared
//__bic_SR_register_on_exit(LPM4_bits); // Exit LPM4
//P1IES ^= BUTTON; // toggle the interrupt edge

}

Dear sir,

I want to use three 3 msp430g2553 with cc110l air booster pack,in that one is Hub and other two are sensors..........then where should we need to change the in the code for transmitter and receiver...........

How can i use two sensor,is there any document ,pdf's or code regarding this type of exapmle.If so please share with me 

thank you.

I am using a MSP430F5659 for usb communication with window10.

32kHz for xt1 clock and 4MHz for xt2 clock is generated in cc2650 by pwm.

msp430 gets clock both xt1 and xt2 by using bypassmode.

 I changed descriptors.h like this.

#define USB_USE_INTERNAL_3V3LDO TRUE

#define USB_XT2_BYPASS_MODE TRUE

#define USB_PLL_XT 2 
#define USB_XT_FREQ_VALUE 4.0
#define USB_XT_FREQ USBPLL_SETCLK_4_0
#define USB_DISABLE_XT_SUSPEND 1

But, my board doesn't enumerated in device manager.

I also tried in window xp, window7, and window8.

But, i can't see the list of msp430 cdc port in device manager.

Hi,

I want interface external data flash AT25DF081A with MSP430F5529 on SPI (USCIB0). can i get some source code w.r.t to data flash interface.

Thanks

Girish S

I want to test my UART implementation on MSP430f1611.

I have connected the MSP430f1611 (Olimex development board) to a MSP-FET Flash emulation tool.

I want the UART backchannel on MSP-FET as an interface to the PC terminal so that I can send and receive data from my terminal and msp430f1611.

MSP-FET provides me 2 COM ports, COM16 for MSP430UIF and COM17 for what I assume is backchannel UART.

I am opening a serial communication on my PC on COM17 with baudrate 9600/8-N-1 (same settings as on COM17).

I have configured the MSP430f1611 to MCLK= 1MHz and baud rate 9600/8-N-1 (same settings as on COM16).

But, I do not see any communication between msp430f1611 and the terminal. I am working on IAR embedded workbench.

Kindly help me figure out the issue.

Hi,

Greetings for the day...!!!

We are using MSP430F149 Microcontroller in our all products.

In one of our product there is problem of erasing program from Microcontroller automatically after some time.

We are using same design from previous many years but from before few days we are suffering this issue...

Hi,

I've restarted some development on MSP430F2274 (chip revision E populated on my board) and I'm facing some strange data corruption when programming trough MSP-FETU430IF (HW V1.4A, FW upgraded to 3.08.00.000).

I've tested latest MSP flasher command line tool (Exit: 60, Error: Verification error) and also FET-Pro430 programing tool (verification error). Both are returning verification error occasionally.

I'm flashing main memory only.

I've tested two physical MSP-FETU430IF programmers, both behaves the same.

I've tested FlashPro430 programming HW and it works perfectly fine, no errors.

For information here is snapshot comparison from FET-Pro430 tool (it seems there is some shift in data):

: ============ Data Result Comparation. =============
: == Only data from the code file that does not match==
: == with the Flash Memory data is displayed. ==
: == Extra data from the Flash Memory is ignored. ==

: First Line - Data from the Code File.
: Second Line - Data from the Flash Memory.

0x93B0: .. .. .. .. .. .. .. .. 58 02 1C 41 02 00 .. 4C | ........X..A...L
0x93B0: .. .. .. .. .. .. .. .. EF BE 58 02 1C 41 .. 00 | ..........X..A..

0x93C0: 03 43 0C 42 81 4C 00 00 03 43 31 50 06 00 30 41 | .C.B.L...C1P..0A
0x93C0: 02 4C 03 43 0C 42 81 4C 00 00 03 43 31 50 06 00 | .L.C.B.L...C1P..

0x93D0: 5C 42 58 02 5C 93 3B 20 5C 42 19 00 7C F0 7F 00 | \BX.\.; \B..|..
0x93D0: 30 41 5C 42 58 02 5C 93 3B 20 5C 42 19 00 7C F0 | 0A\BX.\.; \B..|.

0x93E0: 3C F0 FF 00 C2 4C 19 00 03 43 5C 42 18 00 6C F2 | <....L...C\B..l.
0x93E0: 7F 00 3C F0 FF 00 C2 4C 19 00 03 43 5C 42 18 00 | .<....L...C\B..

0x93F0: 0C 93 FB 23 5C 42 19 00 7C D0 80 FF 3C F0 FF 00 | ...#\B..|...<...
0x93F0: 6C F2 0C 93 FB 23 5C 42 19 00 7C D0 80 FF 3C F0 | l....#\B..|...<.

0x9400: C2 4C 19 00 7D 40 88 FF 7C 40 2C 00 B0 12 34 99 | .L..}@..|@,...4.
0x9400: FF 00 C2 4C C2 4C 7D 40 88 FF 7C 40 2C 00 B0 12 | ...L.L}@..|@,...

0x9410: 7D 40 31 00 7C 40 2D 00 B0 12 34 99 7D 40 09 00 | }@1.|@-...4.}@..
0x9410: 34 99 7D 40 31 00 7C 40 2D 00 B0 12 34 99 7D 40 | 4.}@1.|@-...4.}@

0x9420: 7C 40 2E 00 B0 12 34 99 E2 43 58 02 7C 40 36 00 | |@....4..CX.|@6.
0x9420: 09 00 7C 40 2E 00 B0 12 34 99 E2 43 58 02 7C 40 | ..|@....4..CX.|@

0x9430: B0 12 4A 98 03 43 7C 40 3D 00 B0 12 4A 98 3C F0 | ..J..C|@=...J.<.
0x9430: 36 00 B0 12 4A 98 03 43 EF BE 3D 00 B0 12 4A 98 | 6...J..C..=...J.

0x9440: FF 00 7C F0 F0 00 0C 93 F6 23 30 40 50 94 03 43 | ..|......#0@P..C
0x9440: 3C F0 FF 00 7C F0 F0 00 0C 93 F6 23 30 40 50 94 | <...|......#0@P.

0x9450: 30 41 5C 42 25 00 6C F2 0C 93 0E 24 5C 42 23 00 | 0A\B%.l....$\B#.
0x9450: 03 43 30 41 5C 42 25 00 6C F2 0C 93 0E 24 5C 42 | .C0A\B%.l....$\B

Any idea what could be wrong? 

Thanks.

If some code is written using bdm commands at the lowest layer, is there any way to modify it so that i can implement the code for a JTAG interface?

In the past few days,it is normal to build this project,but the errors happen again.PS:already have updated the mspware,use projects  of examples also normal.

Customer is shipping in volumes with MSP430F6736A.

Previously, the meter was only subjected to 20th harmonic, and TI's design proved to effectively maintain Class 1 under such circumstances.

Moving forward, the meter will be tested up to the 50th harmonic. Will E-meters based on MSP430F6736A be capable of maintaining Class 1 under 50th harmonic (40% Voltage, 15% current)?

Hello,

We are currently developping a board with a MSP430FR2311IPW20R and are having difficulties for the debuger to recgonize this chip. We are using the FET DEBUGGER UIF. We have tested this debugger with a MSP430G2 Launchpad already and it work properly.

After building the project and trying to connect to the target with our MSP430FR2311IPW20R we get the following: 

This is how CCS6  project looks like :

Hence, I suppose we have a hardware issue. The system is powered by a battery which voltage goes from 2V to 3V in running mode but we have used normal power supply which we set to 3.3V for target connection. We have tested that power is supplied properly to the MSP430FR2311IPW20R with 3.3V for loading firmward and testing the connection between the JTAG pin and the pin of the component with a continuity test. 

We have difficulties to identify where we are getting wrong. We would appreciate to get a second pair of eyes to review our schematic and our PCB layout if possible. 

I can also provide PCB layout in PM for review if necessary

Your help is well appreciated

While (!(UCB0IFG & UCTXIFG));

UCB0TXBUF=0X01;

.

.

Plz explain in detail. It is used for spi communication between msp430f5438a and an transceiver ic.

I am horrible at assembly language, so I am trying to eliminate BSL430_Low_Level_Init.asm and replace it with C.  Unfortunately I do not understand the contents of the asm file.  Is it possible to write the Low_Level_Init.asm contents in C?

If it is, in the image below, my understanding is that the logic outlined in red is the BSL430_Low_Level_Init.asm.  Is that correct?

My custom BSL can be seen here: https://github.com/sittim/msp430-OTP/tree/master/otp

When I try to compile the code with GCC, I get the following error:

makefile:223: recipe for target 'hw_1_5.out' failed
msp430-elf-gcc: error: ./otp/BSL430_Low_Level_Init.o: No such file or directory
gmake: *** [hw_1_5.out] Error 1
gmake: Target 'all' not remade because of errors.

Are there any recommended solutions for that?  The contents of the asm file can be viewed here:

github.com/.../BSL430_Low_Level_Init.asm

I am having issues after the firmware update on my MSP-FET. Previously, when I entered the following command, the flasher would update the device with the code. Now, it gives me the following error. Any suggestions?

C:\ti\MSPFlasher_1.3.10\MSP430Flasher.exe -w C:\ti\MSPFlasher_1.3.10\mega.txt
* -----/|-------------------------------------------------------------------- *
* / |__ *
* /_ / MSP Flasher v1.3.10 *
* | / *
* -----|/-------------------------------------------------------------------- *
*
* Evaluating triggers...done
* Checking for available FET debuggers:
* Found USB FET @ COM4 <- Selected
* Initializing interface @ COM4...done
* Checking firmware compatibility:
* FET firmware is up to date.
* Reading FW version...done
* Setting VCC to 3000 mV...done
* Accessing device...
# Exit: 16
# ERROR: Unknown device
* Powering down...done
* Disconnecting from device...done
*
* ----------------------------------------------------------------------------
* Driver : closed (Internal error)
* -----------------------------------------