I understand, but if not already defined, what is the default value? Or, why is this not defined in the code already?
On Thu, Nov 12, 2015 at 9:13 AM, Johan Ström <jo...@stromnet.se> wrote: > Yes, the f_cpu define only controls timing calculations, which must match > the clock speed. If incorrectly configured, it won't be able to talk on the > 1wire net. > > > On 12/11/15 18:04, Colin Reese wrote: > > I see this in main: > > #elif defined (__AVR_ATmega168__) || defined (__AVR_ATmega88__) || > defined(__AVR_ATmega328__) > // Clock is set via fuse > > is the f_cpu definition necessary here? > > C > > On Thu, Nov 12, 2015 at 8:44 AM, Johan Ström <jo...@stromnet.se> wrote: > >> As long as your built it for 16MHz it should probably be compatible (I'm >> not familiar with any specific fuses the m328 might have). >> >> Thus, f_cpu: 16000000 >> >> On 12/11/15 03:39, Colin Reese wrote: >> > So to avoid trying to get WinAVR to behave, on a windows machine with >> > avrdude I would do something like: >> > >> > avrdude -c usbtiny -p m328p -U flash:w:image.hex -U eeprom:w:eprom.hex >> > >> > That should do the trick? Do I really need to set the fuses? I have it >> > set up as external 16Mhz. I assume this is compatible. >> > >> > C >> > >> > On 11/11/2015 12:34 PM, Matthias Urlichs wrote: >> >> On 11.11.2015 20:45, Colin Reese wrote: >> >>> In the meantime, getting an updated libc from elsewhere than the apt >> repos is an option? >> >> I'd be wary of compiler/libc or libc/header incompatibilities when >> >> upgrading partially. IMHO it'd be safer to examine your existing >> >> pgmspace.h and add a patch to MoaT that works around not having the >> >> current version of pgmspace.h. (I already tried that, but apparently >> not >> >> quite successfully.) >> >> >> >> In fact you might just email your version to me, I can certainly take a >> >> look. >> >> >> >> >> >> -- Matthias Urlichs >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> >> Owfs-developers mailing list >> >> Owfs-developers@lists.sourceforge.net >> >> https://lists.sourceforge.net/lists/listinfo/owfs-developers >> > >> > >> ------------------------------------------------------------------------------ >> > _______________________________________________ >> > Owfs-developers mailing list >> > Owfs-developers@lists.sourceforge.net >> > https://lists.sourceforge.net/lists/listinfo/owfs-developers >> >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Owfs-developers mailing list >> Owfs-developers@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/owfs-developers >> > > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > Owfs-developers mailing > listOwfs-developers@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/owfs-developers > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Owfs-developers mailing list > Owfs-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/owfs-developers > >
------------------------------------------------------------------------------
_______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
