Part Number: MSP430FG6426 Hi,
I'm trying to bring up the I2C peripheral on an MSP430FG6426 in slave mode (BeagleBoneBlack - BBB is master).
What I know:
1. I can used "i2cdetect -y 1" on BBB to detect MSP and other devices on the bus.
2. I…
Part Number: MSP430FG6426 Hi
If MSP430FG6426 COM0(30 in PZ) pin is unused,
Is there recommanded connection state?
In datasheet 7.6(Connection of Unused Pins), there is not COM0(LCD output only Analog pin).
https://www.ti.com/lit/ds/symlink/msp430fg6426…
Thanks Luke for all your quick help. The temp sensor seems to be working well now! I've also implemented the ADC calibration values, though it seems to have skewed the results a bit more than before. Though I need to do more work on whether it is coming…
Part Number: ENERGYTRACE Hi
Be Energy Trace Support MSP430FG6xx device?
I can not find in "supported products" in Energy Trace page.
But I think MSP430FG6xx series is same userguids to MSP430F6xx.
However I can find MSP430F6xx in "supported products…
Part Number: MSP430FG6426 I'm having trouble with the long CTSD16 conversion time. Please tell me the reason.
The main settings of CTSD are as follows. Sampling rate = 32 clocks PreloadValue=0 clock CTSD16INTDLY=1b (First sample causes interrupt) CTSD16RRI…
Part Number: MSP430FG6426 I'm having trouble with the long CTSD16 conversion time. Please tell me the reason.
The main settings of CTSD are as follows. Sampling rate = 32 clocks PreloadValue=0 clock CTSD16INTDLY=1b (First sample causes interrupt) CTSD16RRI…
Part Number: MSP430FG6426 Hi Team,
Please teach the relationship between the input voltage to the CTSD, the reference voltage (VR) and the result (CTSD_MEM).
Input setting: in+ = AD2+, in- = AD2- Input voltage: AD2+ = 1.0(V) Input voltage: AD2- = 1.2(V…
Part Number: MSP430FG6426 I've tried setting the clock, but I keep getting UCSCTL7.XT2OFFG=1 (Falt error on XT2).
WDTCTL = WDTPW | WDTHOLD; // Disable the Watchdog CTSD16CCTL0 |= CTSD16SC; // Workaround for CTSD16OFFG errata do { …
Part Number: MSP430FG6426 Dear Team,
A strange problem suddenly arised which we have no clue about, could you please help here ?
When we flash our software in debug session the code runs well until the first hit of __delay_cycles and does not proceed further…
