Part Number: MSP430FR6989 In the process of applying your company's MCU MSP430FR6989, there is a crash situation. At present, there is 1 case in production (16 cases in the same batch of production), and 3 cases have been found in field application.…
Part Number: MSP430FR6989 Other Parts Discussed in Thread: MSP-EXP430FR6989 Im using a MSP-EXP430FR6989 launchpad with BMI160 accelerometer(Booster sensor pack) to read accelerometer values from z-axis and also to put microcontroller to sleep whenever…
Part Number: MSP430FR6989 When I was trying to run TI-RTOS MSP430FR6989, I realized CCS Theia and CCS 12.7 was no-go. One of the earlier forum replies just suggested using CCS version mentioned in the TI-RTOS release notes. And it worked. However, the…
Part Number: MSP430FR6989 Team,
The datasheet is only showing the digital input threshold levels for 2.2 V and 3.0 V supply. How are these levels if VCC=2.8 V?
Thanks, Robert
Part Number: MSP430FR6989 Hi team,
What do I need to do with the Pin PJ.5/LFXOUT when using the LFXT bypass mode especially in an battery operated application to avoid leakage current?
Do I need an external pull-up / pull-down or can the pin be left…
Other Parts Discussed in Thread: MSP430FR6989 , MSP-FET Whenever I try to debug the code to the MSP430FR6989, Code Composer Studio throws "Error initializing emulator: One of the connected MSP-FETs/eZ-FETs debuggers needs recovery. Select 'Recover' to start…
Part Number: MSP430FR6989 Hello, I have been attempting to use my MSP430 however whenever I try to debug or flash the program onto the board I consistetly get an error : Error initializing emulator: MSP-FET430UIF is already in use and I'm unable to change…
Part Number: BQ78350-R1A Other Parts Discussed in Thread: BQ76930 , MSP430FR6989 , EV2400 Hi,
I am building a BMS with the BQ76930 and the BQ7835-R1A, communicated between them. But I want to communicate with this module from the main microcontroller (MSP430FR6989…
Part Number: MSP430FR6989 Other Parts Discussed in Thread: MSP-FET Consult, when reading this chip found the following display, generally what causes the debugging interface to be locked