Part Number: MSP430F5309 Other Parts Discussed in Thread: MSP430F5508 Hello! The following messages appeared on the msp430f5309 and MSP430F5508 product web-pages:"We are currently planning the next generation of this product. The new part will leverage…
Part Number: MSP430F5309 It appears MSP430F5309IZQER is being discontinued. Can you suggest comparable solutions in the portfolio with the following features:
Small package (5x5mm or smaller, ideally)
DVDD/AVDD = 1.8V
System clock 1MHz ( < 180µA…
Part Number: MSP430F5309 Hello,
I am looking for a Free version of IAR Workbench Limited Version 16K that TI used to give away free since you used their MSP430 devices.
It was always limtied to, I think 16K Bytes which is fine for what I am doing…
Other Parts Discussed in Thread: MSP430F5309 , MSP430F5310 , MSP430F5529 Hello,
We want to interface CC3000 with MSP430F5309 micro controller.
Is it possible to do that ?
If yes, Can you give some guidance in porting the code from MSP430F5739…
Okay folks,
I narrow down the problem scope to the exit of low power mode.
If I disable the low power mode, MSP430F5309 works fine.
Is there any problem on MSP430F5309 to exit low power mode(LPM3) through UART interrupt?
Other Parts Discussed in Thread: MSP430F5309 Hi,
I have a question about erasing flash memory of MSP430F5309.
I know that it is possible to erase flash by using the JTAG Interface with Fet-Pro430 tool.
But now I can not use the JTAG Interface…
This code calls the TIMER0_A0_VECTOR ISR after 50000 ACLK ticks. Probably for a timeout detection, or a delay.
Details about the individual meanings are found in the 2x family users guide.
Part Number: MSP430F5310 Other Parts Discussed in Thread: MSP430F5309 , , MSP-GANG Hello
Our production facility has notified me that they are unable to acquire the MSP430F5309 and would like to use the MSP430F5310 for one of our products.
I was wondering…
Okay I understand now, you are trying to program an MSP430 device using a Raspberry Pi. I did a quick search online and found some forums and threads with solutions using the dll's provided in the msp-debug-stack. Please refer to the following resources…
