AVR-Chat

Yes,

I've used a compare utility to compare the entire directory between my new  build and the archived build.

All 4 *.lst files change and of course the *.elf file and *.hex files are different.

Of course, the source files *.C, *.h, makefile remain unchanged.

The *.aps file remains the same as well.


The new build directory is a copy of the archived directory, just rebuilt.







--- In AVR-Chat@yahoogroups.com, Cagri Tanriover <dr_cagri_tanriover@...> wrote:

>
> 
> Have you tried comparing the archived version and the version that does not work using a tool such as Beyond Compare? This will clearly show any differences between the two versions if any exists.
> 
> Since the two hex files are different, there must be a difference somewhere in the two projects. The above tool will help you identify this on a file by file basis.
> 
> Regards...
> 
> [Non-text portions of this message have been removed]
>

Have you tried comparing the archived version and the version that does not work using a tool such as Beyond Compare? This will clearly show any differences between the two versions if any exists.

Since the two hex files are different, there must be a difference somewhere in the two projects. The above tool will help you identify this on a file by file basis.

Regards...

[Non-text portions of this message have been removed]

I figured this out!  If anyone upgrades their machine, be careful to do it correctly.

When I built my Windows 7 machine I installed a new version of WinAVR.  I copied over the original WinAVR (and AVRLib) directory, as well.

All of my projects (the makefile) points to this original directory.

The new install of WinAVR set the path in Environmental Variables to point to the new WinAVR directory.  I changed the path to point to my original WinAVR directory, rebooted, rebuilt, AND perfect!


I should probably figure out how to get my builds to work when pointing to the new WinAVR directory.

Actually, I see that the makefile points to AVR and AVRLIB.

Perhaps I just neeed to update this in all my projects.


AVR = C:\WinAVR-SEP_08_20080610

AVRLIB = C:\WinAVR-SEP_08_20080610\avrlib


Thanks for your help guys!


--- In AVR-Chat@yahoogroups.com, "englsprogeny1" <englsprogeny1@...> wrote:

>
> Yes,
> 
> I've used a compare utility to compare the entire directory between my new  build and the archived build.
> 
> All 4 *.lst files change and of course the *.elf file and *.hex files are different.
> 
> Of course, the source files *.C, *.h, makefile remain unchanged.
> 
> The *.aps file remains the same as well.
> 
> 
> The new build directory is a copy of the archived directory, just rebuilt.
> 
> 
> 
> 
> 
> 
> 
> --- In AVR-Chat@yahoogroups.com, Cagri Tanriover <dr_cagri_tanriover@> wrote:
> >
> > 
> > Have you tried comparing the archived version and the version that does not work using a tool such as Beyond Compare? This will clearly show any differences between the two versions if any exists.
> > 
> > Since the two hex files are different, there must be a difference somewhere in the two projects. The above tool will help you identify this on a file by file basis.
> > 
> > Regards...
> > 
> > [Non-text portions of this message have been removed]
> >
>

John,

You are correct, I am using AS4.18  
I do not have 4.19 installed.

I do however have MS Visual C# 2010 installed on my machine and I heard on here (AVR-Chat) that this could cause issues with my AVR projects.

My TWI issue came with the newer install of WinAVR.

The original WinAVR installation (from 2008) that I have been using all along is called in the user manual (WinAVR-user-manual.html):
20080610

The new WinAVR installation is called:
20100110

When I point to this new directory in my makefile and in the AS4.18 Project I get: the TWI issue

When I point to the original directory, the TWI issues go away.

I should probably update everything I do to work with the newest WinAVR but it's not working.


Just a note:
I also use AVRLib and copied this into the new directory, as well.
 

When I installed AS4.18 I pointed to the new WinAVR directory, So I have to manually update the projects each time:

Project|Configuration Options|Custom Options

External Tools:
To point to my original WinAVR directory:

(I deselect "Use AVR Toolchain" and enter my own paths to the original directory)

So, I update my makefile and project settings to point to the 2008 WinAVR directory and all is good.

Do you think that I should make things work with the Newer WinAVR directory?


Thanks,

David







--- In AVR-Chat@yahoogroups.com, John Samperi <samperi@...> wrote:

>
> At 12:36 PM 28/07/2013, you wrote:
> >I installed a new version of WinAVR.
> 
> Didn't you say that you were using AS4.18? Or did you also
> install AS4.19 with the new Atmel Tool-chain?
> 
> AFAIK there is NO new version of winAvr as it got frozen in
> January 2010, the only new version is the Atmel tool-chain which
> may or may not work with AS4.18.
> 
> 
> 
> Regards
> 
> John Samperi
> 
> ********************************************************
> Ampertronics Pty. Ltd.
> 11 Brokenwood Place Baulkham Hills, NSW 2153 AUSTRALIA
> Tel. (02) 9674-6495
> Website  http://www.ampertronics.com.au
> *Electronic Design * Custom Products * Contract Assembly
> ********************************************************
>

At 12:36 PM 28/07/2013, you wrote:
>I installed a new version of WinAVR.

Didn't you say that you were using AS4.18? Or did you also
install AS4.19 with the new Atmel Tool-chain?

AFAIK there is NO new version of winAvr as it got frozen in
January 2010, the only new version is the Atmel tool-chain which
may or may not work with AS4.18.



Regards

John Samperi

********************************************************
Ampertronics Pty. Ltd.
11 Brokenwood Place Baulkham Hills, NSW 2153 AUSTRALIA
Tel. (02) 9674-6495
Website  http://www.ampertronics.com.au
*Electronic Design * Custom Products * Contract Assembly
********************************************************