You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I designed a custom board using CP2102N 28Pin device and MSP430G2553. But I cannot program it. Here is the command line output:
C:\ti\msp430-gcc\examples\msp430g2553>python msptool.py -p COM20 -f msp430g2xx3_1_rd.txt
msptool v0.3
Executing: .\mspdebug\mspdebug.exe rom-bsl -d COM20 "prog msp430g2xx3_1_rd.txt"
expand_tilde: getenv: Completed successfully.
MSPDebug version 0.25 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2017 Daniel Beer dlbeer@gmail.com
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Chip info database from MSP430.dll v3.15.0.1 Copyright (C) 2013 TI, Inc.
sport_open: System cannot find the file specified.
expand_tilde: getenv: Completed successfully.
Resetting...
What steps should I follow to program my MSP430?
Best regards,
Onur
The text was updated successfully, but these errors were encountered:
Hello,
I designed a custom board using CP2102N 28Pin device and MSP430G2553. But I cannot program it. Here is the command line output:
C:\ti\msp430-gcc\examples\msp430g2553>python msptool.py -p COM20 -f msp430g2xx3_1_rd.txt
msptool v0.3
Executing: .\mspdebug\mspdebug.exe rom-bsl -d COM20 "prog msp430g2xx3_1_rd.txt"
expand_tilde: getenv: Completed successfully.
MSPDebug version 0.25 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2017 Daniel Beer dlbeer@gmail.com
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Chip info database from MSP430.dll v3.15.0.1 Copyright (C) 2013 TI, Inc.
sport_open: System cannot find the file specified.
expand_tilde: getenv: Completed successfully.
Resetting...
What steps should I follow to program my MSP430?
Best regards,
Onur
The text was updated successfully, but these errors were encountered: