Search the Community
Showing results for tags 'windows 10'.
Found 3 results
jfd5041 posted a topic in Energia - MSPHas anyone else experienced something like this? I have been using Energia on Windows for years on various LaunchPads, including 430, 432, and Stellaris (now Tiva). The Windows 10 PCs are a Surface Pro 3, a Toshiba Satellite, and an HP Pavilion. Over the last few months, builds and uploads fail in multiple ways unpredictably. The Serial Monitor often doesn't work, even when the TX pin has the correct signal (verified with an oscilloscope decoder). Often the fix is simply to click the Upload button over and over until it works. I've changed to shorter USB cables and switched from USB 3 to USB 2. Sometimes the problem is fixed by restarting Energia or rebooting the PC. It never stays fixed. I've had the same kinds of issues on older versions of Energia, but the code I'm currently developing won't compile if I go back too far. So I'm sticking with the latest version, 1.8.7E21. I've searched the forum for this, but haven't found anything like it. It is possible I just don't know what to search for, so I would be grateful for pointers. I don't want to go down the rabbit hole chasing one of these specific error messages just yet. I suspect the problem is caused by Windows and Java updates, but I have had no problems with Arduinos (UNO, Mega2600). BTW, I have no problems with Energia 1.8.7E21 on an older desktop running Windows 7.
[MSP432][Windows10][Energia 21][Board file 5.23.1] Recently I've been struggling with a run-time error in a very simple program (converting time=0 to 1/1/1970 fails using ctime...granted it's not really an Energia thing, but it's available for use in my CCS builds of energia projects) using the latest code composer, energia and board file (BTW, I don't have this problem with the previous board file) for my msp432. I've figured out a way to "fix' my problem, but it's unclear to me what the implications of this change might be. By default, when I create a new project in CCS, the project is setup to use the GNU v6.3.1 compiler by default. If I use this compiler, my program compiles, but it's operation fails. In looking into the properties of the project, I notice that I have 5 (2 TI and 3 GNU - 1 GNU older than the default and 1 GNU newer) compiler choices in the tool chain. As such, I started changing the compiler to see what would happen with my non-functioning code. First, I started with the TI compilers. If I select either of them, I get a notice about the need for "manual" intervention in the compiler config. As such, I gave up on those. I then selected the oldest version of the GNU compiler (4.8.4). Switching to this version and my compilation fails. Once again, I have up on that one. As a last attempt, I changed to the newer version of the GNU compiler (7.2.1) and lo-and-behold, not only does my problem compile, but ctime now works correctly. Newer things are always better, right? The default (non-working one) and older (non-compiling) versions of the GNU compiler appear to be shipped with Energia while the newer (working) one appears to be shipped with CCSv8. As such, although I've fixed my problem, I'm wondering if switching is just going to lead to other problems as I'm assuming energia was vetted with the default 6.3.1 compiler. Anyone have positive/negative experiences with changing the compiler tool chain? As my program runs with the previous board file (but using the latest Energia 21 otherwise), might I just be better to switch to the older board file (and wait for a board file/compiler update with energia) but leave the compiler as the default 6.3.1 version? jrd
Hi all, I am currently using a MSP430G2 on a Windows 10 64-bit system. My problem is that whenever I try to start up Energia V17, the Energia splash-screen pops up, but the program fails to load. I've tried launching Arduino 1.6.9. on this system and it launches and works perfectly. I've loaded Energia V17 on Windows 7 systems and it worked however it doesn't load on Windows 10. I've tried all Java versions, both 32-bit and 64-bit from version 6 to 8, along with the JDK's, I've tried moving Energia to the root C:\\ drive folders, and I've tried setting full permissions to Energia, all with no avail of it starting up. I have also tried Energia versions 13 to 17. Any ideas as to what I can do to make Energia start up? Thanks