Part Number: MSP430F5509 Other Parts Discussed in Thread: MSP430F5522 , MSP430F5510 , , MSP430F5529 , MSP430F5528 Hi,
due to the shortage of MSP430F5509IRGC, I try to find the alternative.
I found that pins definition and spec of MSP430F5522 and MSP430F5510…
Part Number: MSP430F5522 Other Parts Discussed in Thread: MSP430F6459-HIREL Dear TI Team, First, I am a big fan of your products and solutions. As a design engineer, I am obliged to follow standards, quality protocols and even regulatory regimes and treaties…
Part Number: MSP430F5522 I'm new to this part and my customer is requiring me to wire up a parallel bus (I already suggested SPI and was shot down). He's willing to bit bang this but I'm hoping there's a better option.
Are there any app…
Part Number: MSP430F5522 Tool/software: Code Composer Studio Hi,
We are trying to add debug messages via UART in bootloader of MSP430F5522 but we are unable to succeed. Compilation is done successfully but while flashing,, we didn't get the debug messages…
I recommend the MSP430F5522 .
We unfortunately do not have an exact p2p replacement device but our options are pretty close. This device comes in NFBGA | 80pin and VQFN | 64pin packages.
Yes, there is some difference between PUC and POR. I can't find a total description about what the system will do in PUC. You can only check every you cared registers compared with this chart. I think it is enough to answer your customer's question…
Luis H. S. said: What are they using to read the BQ76952/BQ769142? bqStudio or their own MCU?
They are using MSP430F5522 to read BQ769142, BQ769142's CommType=0x11, and have enabled IIC CRC.
Thanks and regards,
Part Number: MSP430F5522 Other Parts Discussed in Thread: TEST Tool/software: Code Composer Studio I'm not sure if I'm even asking this question correctly so please bear with me.
I'm having an issue with my stored data read from an A/D converter…
Part Number: MSP430F5522
Tool/software: Code Composer Studio
I deleted and a .h file from my project that contained an enum value that is referenced in a different .h file. I readded the file (possibly from a different location, but the same file) back…
Thank you for coming back with that update. Yes there is a known issue with the hex utility where it is not able to handle spaces in the output file name. The workaround for the moment, as you already determined, is to avoid spaces in the file name…