Part Number: MSP430F67691 Other Parts Discussed in Thread: UNIFLASH Dear Team,
I am working with the MSP430F67691 controller in one of our projects. We are facing a critical issue where the device shuts down automatically after approximately one month…
Part Number: MSP430F67691A Other Parts Discussed in Thread: MSP430F67691 Dear Team ,
We are currently working with MSP430F67691/MSP430F67691A microcontrollers across multiple projects and have encountered an issue where, in some cases, one random pin…
Part Number: MSP430F67691 Other Parts Discussed in Thread: , MSP-FET , MSP430F67791A Dear TI Team ,
I am working On MCU MSP430F67691/ MSP430F67691A where I need to update using uart/USB but , I don't know how to write code for bootloader ,how download…
Part Number: MSP430F67691 Other Parts Discussed in Thread: MSP-FET , UNIFLASH Tool/software: I'm currently experiencing problem with flashing the MSP430F67691 controller via the MSP-FET emulation tool in Spy-Bi-Wire mode.
software used: FET-Pro430 …
Part Number: MSP430F67691 Dear Team,
I m having an issue with measuring analog millivolts in the range of 0 mV to 2400mV on SD0P0, SD1P0, SD2P0.
There is a difference of 28-35mV offset between the value measured by Digital Multimeter and ADC count…
Part Number: MSP430F67691 Hi Team,
Our customer would like to know the differences between MSP430F67691AIPZ and MSP430F67691IPZ. There are no differences in the device comparison table below. I have checked the datasheet and forum but can't find the…
Part Number: MSP430F67691 Hi Team,
On the errata, ADC42 says it applies to ADC10_A module, but the registers referenced in the description and workaround seems to be ADC12 registers. Could you help clarify this for our customer?
Thanks for the…
Part Number: MSP430F67691 Tool/software: Code Composer Studio Hi Team,
I have a customer who is using an MSP430F67691 and running into a build problem. They are currently using CCS 7.4.0.00015. Please see the description below and thanks for the help…
I think first step is to figure out what goes wrong. If you have some unused I/O pins, try adding code to set different pins at different stages of the process, i.e. set test point 1 (TP1) when banks 2/3 erase, TP2 when firmware is received, TP3 if CRC…