Studio 4.19 build 730 on Windows 10

Go To Last Post
15 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

I like Studio 4, sorry.  It has support for devices I still have 1000's of, which have disappeared from the devices support of newer versions of studio.  I have a STK500 and I just want to burn AVR 8 bit chips.  Forced to get a new laptop lately and they all come with Windows 10.

 

Found it is possible to get Studio 4.19 build 730 running on Windows 10, but it's a bit tricky to get installed.  I have the studio setupexe stashed away forever on my own backups so I don't even have to waste time going to the internet to find it.  

 

Here's how I did it: 

studio 4 on windows 10 has tricks to install
- turn off UAC
Control Panel\User Accounts\User Accounts
"change user account control settings" to "never" 
- and a reboot to take effect
-turn off wifi/network (no access)
-to run the avrsetup "run as administrator" by right click on it to start

getting the stk500 to work with usb-to-serial adapter (prolific chipset)
- must install the 'downlevel' 3.2.0.0 driver for the adapter
newer drivers will cause a boken yellow ! device on the COM port
there's a web page that walked through it
http://www.miklor.com/COM/UV_Dri...
-downloaded the 3.2 driver from the link provided on that site 

 

 

I still don't know what the requirement of having the avrsetup install a "Junga" usb device driver, but do it anyway as part of the Wizard.

 

Look in your Windows 10 device manager to spot the COM port number assigned when you plug in the usb-to-serial adapter. 

Here's a shortcut to getting to device manager in Win10:  press and hold the Windows control button on the keyboard and press "x" character, brings up a popup menu, pick 'device manager' off it.

 

Launch Studio, Tools ... program connect... pick STK500 and the COM port you observed, or let it autoconnect to find it... not finding it, like mine didn't at first??  Power up the STK500, then try the autoconnect again.. Doh!

 

 

So, here's what I have to say to Atmel:   Studio-4-ever!!! cheeky   Lives on ONE MORE GENERATION of Windows and life is still good, probably 'til I die now I can program what I need to. 

 

Regards,
Scott

Last Edited: Sun. Nov 29, 2015 - 03:20 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I followed your instructions to install AVR Studio 4.19 Build 730 but when I try recompiling a project that I used in my class, I get

 

"rm.exe - Application Error

X The application was unable to start correctly (0xc0000142). Click OK to close the application"

 

I did click OK and what happens is that the .hex file is NOT generated.

 

I also tried an assembler project and it "Build" correctly.

 

I have an older ATMega128 board on some robots and MUST use AVR Studio 4 because of the JTAG interface. These projects are classroom related projects so I can demo the robot in class. They have been around for 6-8 years and I use them unchanged every semester. Everything works correctly in Windows 7 (x32) but I wanted to try out Windows 10 (x32). The world does not end if I can't use Windows 10 but it would be nice. Any ideas?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I only do assembler, tried a build and it worked fine. 

 

And I just burned three dozen chips, using STK500 on a usb-to-serial adapter, and it worked. 

 

Sorry, that's all I use Studio 4 for. 

 

 

Regards,
Scott

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

"rm.exe - Application Error

X The application was unable to start correctly (0xc0000142). Click OK to close the application"

"rm" is the Linux equivalent of "DEL" in MS-DOS. When make runs to execute a Makefile it can invoke one of two "shells". One might be a Linux "bash-like" shell and it will understand commands like "rm", "cat" and the other Linux shell commands. One would be the Windows CMD.EXE and it just understands the MS-DOS commands like "del", "type" and so on. If make runs with CMD.EXE as the sell but is then asked to invoke a Linux command like "rm" it will simply say "I don't know any command called 'rm' he must mean he wants me to run RM.EXE".

 

The error you are getting suggests this is exactly what is happening here. it could be that the wrong make.exe is found first in the PATH on your machine.

 

While it's not a great solution (in my opinion) if you install Cygwin on your machine and let it add to your PATH it will add commands such as "rm.exe" so the invocation would work.

 

The reason assembler projects work is that is all "Atmel only". All they do is invoke avrasm2.exe directly. They aren't trying to build and execute a Makefile using make.exe in that case.

 

BTW "rm" is only invoked for a "clean" not a "build". However if you are attempting to use "build all" then this is a "clean" and then a "build". Try using just "build" and do any "cleaning" manually. But this just prevents it trying to invoke rm.exe - there may be other rules in the AS4 generated Makefile that try to use other Linux commands and they'll hit the same problem.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

 

Hi: Thank you for your response above. 

 

"it could be that the wrong make.exe is found first in the PATH on your machine."

I looked at the path on the Windows 7 and Windows 10 machine and they look reasonable.

 

Windows 7: C:\Users\Amauri>path
PATH=C:\Program Files\Parallels\Parallels Tools\Applications;C:\ProgramData\Orac
le\Java\javapath;C:\WinAVR-20100110\bin;C:\WinAVR-20100110\utils\bin;C:\Windows\
system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShe
ll\v1.0\;C:\Program Files\TortoiseSVN\bin

 

Windows 10

C:\Users\Arroyo>path
PATH=C:\WinAVR-20100110\bin;C:\WinAVR-20100110\utils\bin;C:\ProgramData\Oracle\Java\javapath;C:\Program Files\Parallels\Parallels Tools\Applications;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\

 

They both point to WinAVR to do the compelling & Make

 

I also uninstalled Atmel Studio 7 from Windows 10 just in case there was a conflict (but I have Studio 4.19 and 7 in Windows 7 and they both work), but that did not solve the problem. I also uninstalled them both and reinstalled Studio 4.19 but no go.

 

BTW, rm works on both Windows 7 and Windows 10. Try "rm --help" and they respond correctly...

 

I tried your suggestion in using BUILD and not BUILD ALL but it also fails but with a different message, and this may truly be the culprit. Here is the error window I got in using Compile (to see if the compiler was being called correctly):

 

 

I get the same error when using Build: "sync_with_child" died...

 

 

The command "sh --help" produce the same identical output on both machines. Could WinAVR be the culprit since the Assembler part works suggesting that the problem is in the C invocation?

 

Thank you again! As a professor I like to figure out what is wrong and how to fix it...

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

The windows content did not render in my previous post, so here is a text version:

 

for compile:

0 [main] sh 9592 sync_with_child: child 1456 (0x144) died before initialization with status code 0xc0000142

75171 [main] sh 9592 sync_with child: *** child state waiting for longjmp

/usr/bin/sh: fork: Resource temporarily unavailable

 

for build:

same error but the 9592 became 3532  (all else the same)

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Oh that's just the old 4.19 problem. See my Sticky about that at the top of the Studio forum. Atmel deliberately knobbled 4.19 so (unlike 4.18 SP3) it would not "see" WinAVR any more.

 

To be honest, in this day and age you don't actually want to be using WinAVR (4.3.3) anyway when you can get an avr-gcc 4.9.2 "Atml Toolchain" from Atmel that is 6 years more advanced.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thank you Mr Clawson. I am not sure I found your sticky note. I am OK using the AVR Toolchain but am not familiar with installing it or letting AVR Studio know that it is installed. The documentation has not helped. I did find your instructions on making WinAVR work but you convinced me to use the AVR Toolchain. How do I do it?

 

I reinstalled Studio 4.19 and just need to know how to get AVR Toolchain installed correctly (the install file is a zip file, but where does it go?) and how do I let AVR Studio know where it is ...  Sorry for the lack of knowledge here...

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi:

 

I installed WinAVR and AVR Studio 4.19 (Build 730) on Windows 10 (x32) and added the information from your sticky note:

 

In the External Tools box untick (if ticked) the "Use AVr Toolchain" box.

In the avr-gcc: box below set the path to be C:\WinAVR20100110\bin\avr-gcc.exe (adjusting drive and pathname if you installed in a different location - use the file browser button there if you are not sure of the location).

In the make: box set it to be C:\WinAVR20100110\utils\bin\make.exe

Click the [OK] button.

 

I'm sad to say that nothing changed. The BUILD error message is the same I have been getting, mainly:

 

0 [main] sh 9592 sync_with_child: child 1456 (0x144) died before initialization with status code 0xc0000142

75171 [main] sh 9592 sync_with child: *** child state waiting for longjmp

/usr/bin/sh: fork: Resource temporarily unavailable

 

I think I can get an AVR Dragon to replace the JTAGICE and use Atmel Studio 7 and forget about trying to use AVR Studio 4.19 in Windows 10 (x32). Too bad because I have several robots with JTAGICE programmers and we will have to stay with Windows 7 (x32) to run them or buy several AVR Dragons.  :-(   Our lab computers are old and slow and running a small program like AVR Studio 4.19 is fast compared to Atmel Studio 7.

 

I will continue to monitor the forum for any other suggestions. Thank you to all who have responded...

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

OK so forget Studio for the time being. Just go to the directory where the source and Makefile are located and try to "make" the code. Does that work? (the Makefile may be in a subdirectory in fact).

just need to know how to get AVR Toolchain installed correctly (the install file is a zip file, but where does it go?) and how do I let AVR Studio know where it is ...  Sorry for the lack of knowledge here...

Toolchain puts a location into the Windows registry so Studio 4 should just "see" it when it is installed. There's no action required on your part. As I say Studio 4 used to do this for WinAVR too but in the step from 4.18 to 4.19 Atmel changed it so it would no longer "see" WinAVR but only their own Toolchain.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Clawson:

 

On the Windows 10 (x32) Machine:

 

I installed avr8-gnu-toolchain-installer-3.5.0.85-win32.any.x86.exe

It unzips a directory called avr8-gnu-toolchain and it asks for a location. I gave it "C:\Program Files\Atmel\AVR Tools" The directory has subdirectories: avr bin doc i686-w64-mingw32 include info lib lib exec man share avr8-gnu-toolchain-3.5.0.1662-readme.pdf and license-3.5.0.1662.txt

 

Now I installed AvrStudio4Setup.exe (AVR Studio 4.19 Build 730). It also installs the Jungo USB Driver

 

I opened AVR Studio 4.19 and open an existing project done with AVR Studio 4.19 on the Windows 7 (x32) machine. The Use AVR Toolchain is checked. I get the message:

 

Loaded plugin STK500
gcc plug-in: No AVR Toolchain installation found. The AVR GCC plug-in can still be used if you set up your own build tools.
Loaded plugin AVR GCC
Loaded partfile: C:\Program Files\Atmel\AVR Tools\PartDescriptionFiles\ATmega128.xml

 

 

I tried BUILD and get:

      0 [main] sh 10112 sync_with_child: child 3348(0x144) died before initialization with status code 0xC0000142
  67729 [main] sh 10112 sync_with_child: *** child state waiting for longjmp
/usr/bin/sh: fork: Resource temporarily unavailable
rm -rf irtst.o AAA.o  IR_CDS_Test.elf dep/* IR_CDS_Test.hex IR_CDS_Test.eep IR_CDS_Test.lss IR_CDS_Test.map
make: [clean] Error -1073741502 (ignored)
Build succeeded with 0 Warnings...
      0 [main] sh 5920 sync_with_child: child 6800(0x144) died before initialization with status code 0xC0000142
  65074 [main] sh 5920 sync_with_child: *** child state waiting for longjmp
/usr/bin/sh: fork: Resource temporarily unavailable
I"C:\Arroyo\EEL-5666\Fall 2015\EGN Robot\IR_CDS_Test\.."  -mmcu=atmega128 -Wall -gdwarf-2 -std=gnu99 -O0 -funsigned-char -funsigned-bitfields -fpack-struct -fshort-enums -MD -MP -MT AAA.o -MF dep/AAA.o.d  -c  ../../AAA.c
/usr/bin/sh: IC:\Arroyo\EEL-5666\Fall 2015\EGN Robot\IR_CDS_Test\..: command not found
make: [AAA.o] Error 127 (ignored)
mmcu=atmega128 -Wl,-Map=IR_CDS_Test.map irtst.o AAA.o     -o IR_CDS_Test.elf
/usr/bin/sh: -Wl,-Map=IR_CDS_Test.map: command not found
make: [IR_CDS_Test.elf] Error 127 (ignored)
avr-objcopy -O ihex -R .eeprom -R .fuse -R .lock -R .signature  IR_CDS_Test.elf IR_CDS_Test.hex
avr-objcopy: 'IR_CDS_Test.elf': No such file
make: *** [IR_CDS_Test.hex] Error 1
Build failed with 1 errors and 0 warnings...

 

 

---Same Errors as before---

 

Now I opened the Command Prompt and went to the project directory. Copied the "rm" command from above and it works

c:\Arroyo\EEL-5666\Fall 2015\EGN Robot>dir
 Volume in drive C has no label.
 Volume Serial Number is 5093-6E04

 Directory of c:\Arroyo\EEL-5666\Fall 2015\EGN Robot

11/30/15  12:16 PM    <DIR>          .
11/30/15  12:16 PM    <DIR>          ..
10/13/15  11:46 AM             9,865 AAA.c
10/01/15  02:59 PM             1,277 AAA.h
11/27/15  03:18 PM    <DIR>          Hacked_Servo_Test
11/27/15  03:18 PM    <DIR>          IR_CDS_Test
11/27/15  03:18 PM    <DIR>          Motor_Test_1
11/27/15  03:18 PM    <DIR>          Motor_Test_2
11/27/15  03:18 PM    <DIR>          Obstacle_Avoid
11/27/15  03:18 PM    <DIR>          Obstacle_Avoidance_CDS
11/29/15  02:12 PM    <DIR>          test_EGN_1935_robot
               2 File(s)         11,142 bytes
               9 Dir(s)  44,712,476,672 bytes free

 

c:\Arroyo\EEL-5666\Fall 2015\EGN Robot\IR_CDS_Test\default>rm -rf irtst.o AAA.o  IR_CDS_Test.elf dep/* IR_CDS_Test.hex IR_CDS_Test.eep IR_CDS_Test.lss IR_CDS_Test.map

c:\Arroyo\EEL-5666\Fall 2015\EGN Robot\IR_CDS_Test\default>
c:\Arroyo\EEL-5666\Fall 2015\EGN Robot\IR_CDS_Test\default>dir
 Volume in drive C has no label.
 Volume Serial Number is 5093-6E04

 Directory of c:\Arroyo\EEL-5666\Fall 2015\EGN Robot\IR_CDS_Test\default

12/01/15  01:26 PM    <DIR>          .
12/01/15  01:26 PM    <DIR>          ..
12/01/15  01:26 PM    <DIR>          dep
12/01/15  01:23 PM             2,087 Makefile
               1 File(s)          2,087 bytes
               3 Dir(s)  44,712,456,192 bytes free

 

So the "rm" works by hand. Then I tried the make:

 

c:\Arroyo\EEL-5666\Fall 2015\EGN Robot\IR_CDS_Test\default>make
      0 [main] sh 6660 sync_with_child: child 1888(0x158) died before initialization with status code 0xC0000142
    842 [main] sh 6660 sync_with_child: *** child state waiting for longjmp
/usr/bin/sh: fork: Resource temporarily unavailable
avr-gcc -I"C:\Arroyo\EEL-5666\Fall 2015\EGN Robot\IR_CDS_Test\.."  -mmcu=atmega128 -Wall -gdwarf-2 -std=gnu99 -O0 -funsigned-char -funsigned-bitfields -fpack-struct -fshort-enums -MD -MP -MT AAA.o -MF dep/AAA.o.d  -c  ../../AAA.c
make: *** [AAA.o] Error -1073741502

 

---Now I tried the compile call directly--- Seems to work because it generated artst.o

c:\Arroyo\EEL-5666\Fall 2015\EGN Robot\IR_CDS_Test\default>avr-gcc -I"C:\Arroyo\EEL-5666\Fall 2015\EGN Robot\IR_CDS_Test\.."  -mmcu=atmega128 -Wall -gdwarf-2 -std=gnu99 -O0 -funsigned-char -funsigned-bitfields -fpack-struct -fshort-enums -MD -MP -MT irtst.o -MF dep/irtst.o.d  -c  ../irtst.c

 

I tried BUILD ALL and got:

Build started 1.12.2015 at 14:24:13
      0 [main] sh 8816 sync_with_child: child 4468(0x144) died before initialization with status code 0xC0000142
  68926 [main] sh 8816 sync_with_child: *** child state waiting for longjmp
/usr/bin/sh: fork: Resource temporarily unavailable
I"C:\Arroyo\EEL-5666\Fall 2015\EGN Robot\IR_CDS_Test\.."  -mmcu=atmega128 -Wall -gdwarf-2 -std=gnu99 -O0 -funsigned-char -funsigned-bitfields -fpack-struct -fshort-enums -MD -MP -MT AAA.o -MF dep/AAA.o.d  -c  ../../AAA.c
/usr/bin/sh: IC:\Arroyo\EEL-5666\Fall 2015\EGN Robot\IR_CDS_Test\..: command not found
make: [AAA.o] Error 127 (ignored)
mmcu=atmega128 -Wl,-Map=IR_CDS_Test.map irtst.o AAA.o     -o IR_CDS_Test.elf
/usr/bin/sh: -Wl,-Map=IR_CDS_Test.map: command not found
make: [IR_CDS_Test.elf] Error 127 (ignored)
avr-objcopy -O ihex -R .eeprom -R .fuse -R .lock -R .signature  IR_CDS_Test.elf IR_CDS_Test.hex
avr-objcopy: 'IR_CDS_Test.elf': No such file
make: *** [IR_CDS_Test.hex] Error 1
Build failed with 1 errors and 0 warnings...

 

 

Does not appear to me that AVR Studio 4.19 recognized the toolchain. BTW, the reason "rm" and "make" work at all is because the PATH contains C:\WinAVR

 

Is there anything you would like for me to try?

 

I also tried: 

In the External Tools box untick (if ticked) the "Use AVr Toolchain" box.

In the avr-gcc: box below set the path to be C:\WinAVR20100110\bin\avr-gcc.exe (adjusting drive and pathname if you installed in a different location - use the file browser button there if you are not sure of the location).

In the make: box set it to be C:\WinAVR20100110\utils\bin\make.exe

Click the [OK] button.

 

Now after BUILD I get:

      0 [main] sh 7256 sync_with_child: child 8880(0x144) died before initialization with status code 0xC0000142
  59049 [main] sh 7256 sync_with_child: *** child state waiting for longjmp
/usr/bin/sh: fork: Resource temporarily unavailable
rm -rf irtst.o AAA.o  IR_CDS_Test.elf dep/* IR_CDS_Test.hex IR_CDS_Test.eep IR_CDS_Test.lss IR_CDS_Test.map
make: [clean] Error -1073741502 (ignored)
Build succeeded with 0 Warnings...
      0 [main] sh 1596 sync_with_child: child 10040(0x144) died before initialization with status code 0xC0000142
  74764 [main] sh 1596 sync_with_child: *** child state waiting for longjmp
/usr/bin/sh: fork: Resource temporarily unavailable
avr-gcc -I"C:\Arroyo\EEL-5666\Fall 2015\EGN Robot\IR_CDS_Test\.."  -mmcu=atmega128 -Wall -gdwarf-2 -std=gnu99 -O0 -funsigned-char -funsigned-bitfields -fpack-struct -fshort-enums -MD -MP -MT AAA.o -MF dep/AAA.o.d  -c  ../../AAA.c
make: *** [AAA.o] Error -1073741502
Build failed with 1 errors and 0 warnings...

 

 

Same type of errors...

 

(1) It does not appear to me that AVR Studio 4.19 found the installed toolchain.

(2) Even pointing to WINAVR it does not work either

 

Again, any ideas?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

Scottm,

 

You're the best.   Similar to you, just got my first W10 laptop and have tried for about 5hrs to get 4.19 installed..... your tips saved my arse.    Very appreciated that you shared.   

 

-mark

Mark
Elgin, IL (near Chicago)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi ScottM,

 

Today I tried both of my Win10 laptops, and while 4.19 still runs fine for editing/assembly, neither will connect to my AVRISP MKII or my Dragon.   Tested both cards on a crappy old machine running XP and they are fine.

 

I suspect that a Win10 update broke the USB drivers.    I reinstalled 4.19 on both machines and no better.

 

Have you run into this?

 

tnx,

 

-mark

Mark
Elgin, IL (near Chicago)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

fmr300 wrote:
I suspect that a Win10 update broke the USB drivers.
One has 10 days after an update of Windows 10 version 1607 to roll-back an update of it.

If CBB is not stable wrt Atmel USB drivers then that would be at least data, maybe information, to some here.


https://www.askwoody.com/win10-tips/

https://www.askwoody.com/2016/new-windows-10-version-1607-build-14393-479-kb-3201845-rolling-out/ (December 9th, 2016)

Microsoft

Manage updates using Windows Update for Business (Windows 10)

by jdeckerMS

Last Updated: 12/1/2016

https://technet.microsoft.com/en-us/itpro/windows/manage/waas-manage-updates-wufb

...

Specifically, Windows Update for Business allows for:

...

  • Selectively including or excluding drivers as part of Microsoft-provided updates

...

Comparing Windows Update for Business in Windows 10, version 1511 and version 1607

...

(Windows 10, version 1607)

Drivers can be selectively excluded from Windows Update for Business.

...

Edit : WUB

 

"Dare to be naïve." - Buckminster Fuller

Last Edited: Fri. Dec 9, 2016 - 03:25 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

If you have installed AS7 on your win10 machines at anytime it is likely that you have installed a newer USB driver which will break AS4.x

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly