Complete software in "C"

[tim10243]

Hi,
I am starting to think about the software now. I´ll find a lot of
parts of the software here:
http://code.google.com/p/strobist-project-opensource-trigger/wiki/SoftwareArchitecture
and here:
http://code.google.com/p/strobist-project-opensource-trigger/source/browse/#svn/trunk/SPOT
But I don´t have an idea what to do with these parts. Do I have to
compile them one by one and put them in hex on the atmega or do i have
to bring them together and then compile them? Would it be possibel to
get one file wich contains all the software which have to be compiled
and to be put on the atmega? That would help me a lot.
thanks
Tim

[Till Seyfarth]

Hi Tim,

 

splitting up functionality in more than one source code file ("modularization") is generally considered to improve understandability, reuseability, testability, changeability and several other software quality characteristics. Putting it all in one big chunk is not an option. 

What you find in the wiki is a description and a few citations from the source. It's documentation. The .c and .h files in the repository form the software source code that needs to be compiled. I think it would be best if you took a day or so to understand the basics of how to import the modules into a project of your development environment of choice (there are several free options), compile them to get the .hex file that is then transferred to the controller. There are plenty of excellent sources on this topic, some of them are pointed out on the wiki: http://code.google.com/p/strobist-project-opensource-trigger/wiki/FindHelp. If you do not intend to change the software you could simply download the compiled SPOT.hex file here: http://groups.google.com/group/spot-development/files.

 

Cheers

Till

[tim10243]

Hi Till,

to spilt up the software in parts to handle them easier makes sense -
no doubt.
But how do I know if I got all parts which are needed and have not
forgotten something?
That may be a foolish question, but ..... as i said, I am a greenhorn
in this.

Tim

On 10 Sep., 13:38, Till Seyfarth <tillseyfa...@gmail.com> wrote:
> Hi Tim,
>
> splitting up functionality in more than one source code
> file ("modularization") is generally considered
> to improve understandability, reuseability, testability, changeability and
> several other software quality characteristics. Putting it all in one big
> chunk is not an option.
>
> What you find in the wiki is a description and a few citations from the
> source. It's documentation. The .c and .h files in the repository form the
> software source code that needs to be compiled. I think it would be best if
> you took a day or so to understand the basics of how to import the modules
> into a project of your development environment of choice (there are several
> free options), compile them to get the .hex file that is then transferred to
> the controller. There are plenty of excellent sources on this topic, some of

> them are pointed out on the wiki:http://code.google.com/p/strobist-project-opensource-trigger/wiki/Fin....

> If you do not intend to change the software you could simply download the
> compiled SPOT.hex file here:http://groups.google.com/group/spot-development/files.
>
> Cheers
> Till
>
> On Thu, Sep 10, 2009 at 12:04 PM, tim10243 <t...@brakemeier.info> wrote:
>
> > Hi,
> > I am starting to think about the software now. I´ll find a lot of
> > parts of the software here:
>

> >http://code.google.com/p/strobist-project-opensource-trigger/wiki/Sof...
> > and here:
>
> >http://code.google.com/p/strobist-project-opensource-trigger/source/b...

[Till Seyfarth]

Hi Tim,

 

you need exactly these: global.h, lcd3110.c, lcd3110.h, rfm12.c, rfm12.h, spot.c, timer.c and timer.h.

I see two options for you:

 

1) Get the hex-file and don't care about the compiler part - just learn how to burn it onto the MC and how to fuse it.

 

2) Learn about compiling source code. My suggestion: Try the free AVR Studio http://www.atmel.com/dyn/Products/tools_card.asp?tool_id=2725. It's probably more beginner-friendly than Ecplise. I started with it and switched to Eclipse later.

 

Would you care to write a little tutorial along the way to help the next guy in your position? That would be very helpful!

 

Cheers

Till

[tim10243]

I am already preparing a little tutorial for the hardwarework - "spot
for dummies" including part list and so on
as soon as i finished the softwarework I´ll prepare a tutorial on this
too.

On 10 Sep., 16:01, Till Seyfarth <tillseyfa...@gmail.com> wrote:
> Hi Tim,
>

> you need exactly these: global.h, lcd3110.c, lcd3110.h, rfm12.c, rfm12.h,
> spot.c, timer.c and timer.h.
> I see two options for you:
>
> 1) Get the hex-file and don't care about the compiler part - just learn how
> to burn it onto the MC and how to fuse it.
>
> 2) Learn about compiling source code. My suggestion: Try the free AVR

> Studiohttp://www.atmel.com/dyn/Products/tools_card.asp?tool_id=2725. It's

[Jake]

Tim and Till,

Thanks for all of these discussions. Others are benefiting as well, I
can assure you. I'd be happy to be that "next guy", working on
getting some hardware now. Although I should say that I am hoping to
build the "simple spot" that has been discussed, without LCD. But
there is a good chance that I will be unable to engineer that and will
end up looking for more of a cookbook solution (with LCD).

- Jake

[tim10243]

hi jake,
i wanted to have the simple spot as well. but because i coulnd´t get a
detailed tutorial i switched to the "original" version made by till. i
hope the hardwarework is done next week - i am just waiting for nokia
5110 display - and than i´ll publish a hardware tutorial.
tim

[tim10243]

till,

I see a third option :-)
I have to find someone who will help me
your "basic" version would be good for me in 99%
all i would need are two little changes
- the power adjustment in half or thrid stop steps
- some more devices to choose from (SB-24, SB-25, SB-28DX, Metz
60CT-1)
so if someone here would liek to help me in this point I´am sure we
find a win win solution ;-)

tim