Part Number: MSP430FR5872
I am developing a product that is based on the part number: MSP430FR5872IPMR. I intend to implement a firmware update system that relies on UART BSL and enters the BSL mode through software. The user guides and datasheets so…
Part Number: MSP430FR5872 Hi Team MSP,
I see we have some FRAM utilities like "Compute Thru Power Loss" in dev.ti.com/tirex.
Do we have a simple/sample code/project for using some of FRAM as RAM/Variables? Maybe w/ sample changes to Linker File, etc…
Part Number: MSP430FR5872 Other Parts Discussed in Thread: MSP430FR2675 , ENERGIA , MSP-EXP430FR6989 , I have a question about the MSP430FR5872, it says that all pins can be used for capacitive sensing. Does this mean they are all self capacitance or…
Part Number: MSP430FR5872 The chip will essentially act as a UART to I2C buffer. It's designed to be as low power as possible, with a supply of 3.3V. Any improvements, tips, or corrections, please let me know!
Part Number: MSP430FR5872 Hi Expert.
In mostly MSP430 example code I am seeing this line in starting of the main loop "WDTCTL = WDTPW | WDTHOLD;
Can you explain the reason behind this and if we exclude this statement then what could be the consequences…
Part Number: MSP430FR5872 Hi Experts,
I am using LPM4.5 in my application and I am able to get proper LPM4.5 wakeup .
As per TI manual after wake-up from LPM4.5, the state of the I/Os are locked and remain unchanged until the application clears…
Thanks JD,
That did the trick ! I am now writing 0 to SYSRSTIV after reading it in order to clear any pending interrupt flags.
The system now behaves as per expectation.
Regards,
Aman
Hi
1.Yes , you can refer to the datasheet: www.ti.com/.../msp430fr5872.pdf Table 6-17
2Temperaturecalibration values are available for use in the TLV descriptors (see the device-specific data sheet for locations) for more information you can refer to…
Part Number: MSP430FR5872
Tool/software: Code Composer Studio
Hopefully the formatting on this comes out decently.
I have modified the linker command script to create a data section and a code section for doing self programming on my controller…
Hello Salvatore,
From a coding standpoint, you are toggling the GPIOs correctly; however, with our FRAM devices, after POR you need to add the following line to unlock the GPIOs after you configure them.
PM5CTL0 &= ~LOCKLPM5; // Disable the GPIO…
