This is my repository where I am storing all my Proteus v8.9 Project Files and these are project files for simulation of Texas Instrument’s MSP430G2553 microcontroller with various example programs. I am keeping the Proteus design files only and some .HEX, .ELF, and .INO files.
The hardware UART feature does not work at all that is why "Exp01_LunchBox_UART_Template" the hardware version does not work, I have tried with varying sources of ACLK, SMCLK for UART and other options of clock source to generate the baud rate necessary but cannot get it working. So, leaving the hardware UART, I have managed to get software UART, the one with "INO" suffix, but however that does not uses Embedded C, but I did it with the help of .ino style program with Energia IDE.
On simulation, there is no error for hardware UART, but there is no signal from the TXD hardware pin of MSP430G2553, Also I have tested it for MSP430G2x53 and MSP430G2x13 but still there is no signal.
So, I think it must be something else, something I still don't know or it just might be a bug in proteus. As at first I thought it as an issue of clock source, but then I tired many many combinations, probed everywhere but couldn't manage to get it working.
So, this is some unknown fault.
The hardware UART feature does not work at all that is why "Exp01_LunchBox_UART_Template" the hardware version does not work, I have tried with varying sources of ACLK, SMCLK for UART and other options of clock source to generate the baud rate necessary but cannot get it working. So, leaving the hardware UART, I have managed to get software UART, the one with "INO" suffix, but however that does not uses Embedded C, but I did it with the help of .ino style program with Energia IDE.
On simulation, there is no error for hardware UART, but there is no signal from the TXD hardware pin of MSP430G2553, Also I have tested it for MSP430G2x53 and MSP430G2x13 but still there is no signal.
So, I think it must be something else, something I still don't know or it just might be a bug in proteus. As at first I thought it as an issue of clock source, but then I tired many many combinations, probed everywhere but couldn't manage to get it working. So, this is some unknown fault.