[McHUG] Success!!!

[n3sb at qis.net]

Hi Rich;

> 1) make clean
> 2) make all
> 3) make program (using the 4 step approach above)

You can also skip steps 1 and 2. Make is smart enough to know which source files
you've touched since your last compile. It looks at the file dates to determine
if any source files are more current than their corresponding object files, and
causes re-builds of the ones that need to be.

This process is dependent on the makefile. You edit the makefile to define the
dependencies, and make takes care of the rest. You can even add the header
files, and the makefile itself, as items required for the object code. Make is
not a tool specific to C programming - you can use it for Fortran, Pascal, or
any other language. You can also use it to process text files, or do anything
else similar, just by defining the dependencies and the steps to be performed
to resolve those dependencies. In the case of the Atmel Butterfly, those steps
involve the avr-gcc compiler and related tools.

So - if you edit any source files, or delete any object files, make will
re-construct the object files. The "program" target also has a definition in
the makefile indicating that it depends on the .hex file, which depends on the
.elf file, which depends on a set of .o files, which depend on .c and .h files.
"make program" will cause a build of everything required, as necessary, to
insure that the programmed image is completely up to date, then cause the chip
to be programmed.

This make tool is really powerful if you're working on a huge program that
contains many source files. If you edit just one source file, make is smart
enough to cause a re-compile of just that one file, and re-link all the objects
to create the end application. This is a good thing because it saves you all the
time in re-compiling all the source files again. 

73; Steve, N3SB

Quoting Rich Mitchell <geobra at att.net>:

> Wow! a night of successes - although it appears that Pete's note was posted
> from oh-dark-thirty this morning.  If we get pictures I can post them on my
> old web site - But we do have mchug.org - maybe I should take steps to get
> that hosted.  
> 
> Steve, after your explanation of how the AVRDUDE tool should work, I tried it
> with my old code.  The steps being:
> 1) turn the Butterfly off
> 2) enter "make project" and wait for it to get to the period.
> 3) turn the Butterfly on
> 4) push and hold the joystick until AVRDUDE completes.
> 
> With no modification to code or makefile the Butterfly programmed.  Worked
> like a charm.  My success rate with this approach and AVRDUDE is 100%.  When
> I was using the load tool in AVR Studio it was 50%.  The first try rarely
> found the chip, but second almost always did.  This has great simplified and
> shortened the process of making a change to the code, compiling it and
> programming it into the Butterfly chip.  Now once I make a code change it's 3
> simple commands:
> 1) make clean
> 2) make all
> 3) make program (using the 4 step approach above)
> 
> Your success with the Arduino chip is now making this simple process standard
> over our Atmel AVR programming.  GREAT STEP FORWARD!!
> 
> So far we have 3 of us signed up for Friday night - Steve, Pete and me (Cindy
> will be there too).
> 
> 73
> Rich, N3III
> --
> McHUG - Physical Computing ;) 
> MicroController Ham User Group
> 
> -------------- Original message from n3sb at qis.net: -------------- 
> 
> 
> > Excellent Pete! 
> > 
> > I hope you are able to post some photos - maybe Rich can put them on his 
> > website. I'd love to see what this looks like! 
> > 
> > 73; Steve, N3SB 
> > 
> > Quoting Peter Morton : 
> > 
> > > Finished building the interface cables for the SI570 and fired 'er up. It
> 
> > > works!! And, the frequency can be set using WinRad. Simply right or left
> 
> > > click on the LO frequency digits in the upper right corner of the WinRad
> 
> > > display and the SI570 changes frequency accordingly (at 4x the LO
> displayed 
> > > frequency). 
> > > 
> > > Next step is to connect the SI570 to the SoftRock Lite. I'll take a look
> at 
> > > that later. I need to decide what tests need to be run to characterize 
> > > performance before and after. I had trouble previously measuring
> sensitivity 
> > > of the SoftRock Lite in an open environment. 
> > > 
> > > I want to eventually package the two boards in a shielded box with
> antenna, 
> > > DC power, I/Q audio, and control connectors. Also, need to implement 
> > > preselectors for desired bands and implement a means to switch them
> easily. 
> > > All the connectors and interfacing tend to dwarf the two little boards
> that 
> > > are the heart of the system. 
> > > 
> > > I noticed that Tony Parks uses the same PIC that is used for the PICAXE
> 08 to 
> > > control the SI570 on his LITE-XTAL board. 
> > > 
> > > -Pete 
> > > ______________________________________________________________ 
> > > McHUG mailing list 
> > > Home: http://mailman.qth.net/mailman/listinfo/mchug 
> > > Help: http://mailman.qth.net/mmmain.htm 
> > > Post: mailto:McHUG at mailman.qth.net 
> > > 
> > 
> > 
> > 
> > ______________________________________________________________ 
> > McHUG mailing list 
> > Home: http://mailman.qth.net/mailman/listinfo/mchug 
> > Help: http://mailman.qth.net/mmmain.htm 
> > Post: mailto:McHUG at mailman.qth.net 
> ______________________________________________________________
> McHUG mailing list
> Home: http://mailman.qth.net/mailman/listinfo/mchug
> Help: http://mailman.qth.net/mmmain.htm
> Post: mailto:McHUG at mailman.qth.net
>