The dll works for me too ... I'm using Windows 10 and after migrating from Win 7-64 bit had the problem that was described here ... after ferreting around for a bit I gave it a whirl and it seems to restore the project build sequences to their correct functioning.
The way this works is that the first time you build the compiler generates a map of all the .h files involved and creates .d (dependency) lists. On subsequent "make" it checks the times on all the .h so that if any have changed it triggers the .c to rebuild even if it hadn't changed itself. But if there's some problem in this process you see the kind of error you are getting above. Usually a "clean" which wipes everything so it all starts from scratch is enough to rectify things.
thank you clawson, I done with clean up, but then also error remain as it is. after cleaning it gives me following msg. Attachement contains error msg and a screen shots. please down load the attachment n help me.
This installer creates registry entries that allow AVRStudio4 to find the toolchain. For a "New Project" it should work straight away, but I don't know whether an existing WinAVR project will. (Probably not actually - Make a new project just in case)
If you have a qualified firmware which was build with a specific compiler version and you want to achieve comparable binary file, it does make sense to use a specific compiler/toolchain.
In the beginning was the Word, and the Word was with God, and the Word was God.
But why in 2016 is anyone using WinAVr (last release January 2010). The avr-gcc compiler has moved on since then. The latest release built by Atmel is 4.9.2 and the really adventurous can even pull the source for 5.0+ and build that.
I just had this issue and the fix solved it, running on 64 bit windows 10. I installed Atmel Studio earlier this year from microchips site. Did it not come up to date?
Not sure I follow what you are asking here. The currect issue of Atmel Studio 7 comes with a copy of avr-gcc 5.4.0 from about 2 years ago so in that sense it is almost "up to date".
(actually avr-gcc is now up to about 9.x but there have been few (though the odd significant) developments for AVR in GCC since the pretty stable 5.4)
thanks a lot. the problem solved as stated.
- Log in or register to post comments
TopThe dll works for me too ... I'm using Windows 10 and after migrating from Win 7-64 bit had the problem that was described here ... after ferreting around for a bit I gave it a whirl and it seems to restore the project build sequences to their correct functioning.
Thanks for getting me out of the hole!
Mike
- Log in or register to post comments
Tophello,
../ledblink.c:14: fatal error: opening dependency file dep/ledblink.o.d: No such file or directory
i am getting this error for windows 10. I am new to the programming. Please help me out.
shree
- Log in or register to post comments
TopTry a "clean" first.
The way this works is that the first time you build the compiler generates a map of all the .h files involved and creates .d (dependency) lists. On subsequent "make" it checks the times on all the .h so that if any have changed it triggers the .c to rebuild even if it hadn't changed itself. But if there's some problem in this process you see the kind of error you are getting above. Usually a "clean" which wipes everything so it all starts from scratch is enough to rectify things.
- Log in or register to post comments
Tophello clawson,
thanks for your advice. You told me to clean it. how can i do that cleaning work, please guide me.
shree
- Log in or register to post comments
TopIf using Studio on the build menu - should be a "clean" entry. If building at a command line "make clean"
- Log in or register to post comments
Topthank you clawson, I done with clean up, but then also error remain as it is. after cleaning it gives me following msg. Attachement contains error msg and a screen shots. please down load the attachment n help me.
Attachment(s):
shree
- Log in or register to post comments
TopOMG WinAVR-20080610. Unless you REALLY need to use this positively geriatric version you should upgrade.
In this post:
https://www.avrfreaks.net/comment/2004601#comment-2004601
I recommended the easiest route for AVRStudio4 users was to install the final version of Atmel Toolchain that was intended to work with AVRStudio4
Atmel AVR 8-bit and 32-bit Toolchain 3.3.1 - Windows
(4921000, updated April 2012)
Windows installer for AVR 8-bit and 32-bit Toolchain version 3.3.2
http://www.atmel.com/System/BaseForm.aspx?target=tcm:26-40855
This installer creates registry entries that allow AVRStudio4 to find the toolchain. For a "New Project" it should work straight away, but I don't know whether an existing WinAVR project will. (Probably not actually - Make a new project just in case)
-- Nigel
- Log in or register to post comments
TopThis worked for me too under Windows 10 x64.
- Log in or register to post comments
TopThis ALMOST worked for me. It solved the issue that was claimed it would! Now I'm on to a new error to work on. At least its progress.
Windows 10 x64, WinAVR 20040404, AVR Studio 4.09.
Thanks
- Log in or register to post comments
TopTry the LATEST 1.0.18 DLL, it works on Win10 fine, old ones (including the one in this topic) do not work.
Attachment(s):
- Log in or register to post comments
TopAnd now we're well into 2017 !!
Top Tips:
- Log in or register to post comments
TopThank you. It worked for me on Windows 10.
If you have a qualified firmware which was build with a specific compiler version and you want to achieve comparable binary file, it does make sense to use a specific compiler/toolchain.
In the beginning was the Word, and the Word was with God, and the Word was God.
- Log in or register to post comments
TopSolved my compilation issue on Windows 10 pro.
was using AVRGCC with programmers notepad.
The issue was :
"main.c:13: fatal error: opening dependency file .dep/main.o.d: No such file or directory"
Thanks!
- Log in or register to post comments
TopSuper agradecido
- Log in or register to post comments
TopThank you a lot! It works for Windows 8.1. I have the AVR 4.18 version.
- Log in or register to post comments
TopThanks so much , i sol my problem
- Log in or register to post comments
Top- Log in or register to post comments
TopYou are a live saver even in 2017.
A Big Thank You.
Variety is the spice of live.
- Log in or register to post comments
TopWorks for me, using Windows 10 :)
- Log in or register to post comments
TopThanks a lot
Worked with windows 10 and WinAvr Studio 4
- Log in or register to post comments
TopSOLVED for me!
I don't believe it! Having this Problem
"the application was unable to start correctly (0xc0000142)"
Searching all through google and found your more then 5 years old answer and it solved it!!
- Log in or register to post comments
TopWell this SOLVED it for me!
I don't believe it! Having this Problem
"the application was unable to start correctly (0xc0000142)"
Searching all through google and found your more then 5 years old answer and it solved it!!
- Log in or register to post comments
TopJust Remove these two lines from "Makefile" of WinAVR:
# Compiler flags to generate dependency files.
GENDEPFLAGS = -MMD -MP -MF .dep/$(@F).d
There's neither any effect nor any need of it, if your particular version of WinAVR isn't able to compile with it.
After Removing, compile again by running "Make all" and find .hex file in respective folder of your project directory.
SARM
- Log in or register to post comments
TopI just had this issue and the fix solved it, running on 64 bit windows 10. I installed Atmel Studio earlier this year from microchips site. Did it not come up to date?
- Log in or register to post comments
Top(actually avr-gcc is now up to about 9.x but there have been few (though the odd significant) developments for AVR in GCC since the pretty stable 5.4)
- Log in or register to post comments
TopThanks for this! Works on Win10-x64
- Log in or register to post comments
TopPages