Re: [Owfs-developers] Merging "moat" device specific code

You'd have to step through the "_ref" in your def, and the "default" section in world.cfg to found out any defaults. In my example, I only have specifically 'ref: mcu.mega328'. Checking the mcu.mega328 section in world.cfg (included) we do not have a f_cpu def. So continue to global

Re: [Owfs-developers] Merging "moat" device specific code

Finally got it. Built it on a machine without the updated code. Thanks. C On 11/12/2015 9:06 PM, Colin Reese wrote: Understood. From what I can see, 1Wire should be on INT0 (D2) per 152 in world.cfg. With the world.cfg below, everything compiles fine and loads from my USBTiny. I verified my

Re: [Owfs-developers] Merging "moat" device specific code

First, I just noticed the HOWTO is much improved and has some details about using the uart. Thanks Matthias. I assume all of the data appears somewhat transparently via owfs as indicated in the HOWTO, which is how I plan to use it typically. Using other code, e.g. through LabVIEW or

Re: [Owfs-developers] Merging "moat" device specific code

Understood. From what I can see, 1Wire should be on INT0 (D2) per 152 in world.cfg. With the world.cfg below, everything compiles fine and loads from my USBTiny. I verified my fuses are xFF, xDE, x05, which looks good. I still don't see anything on my DS9490R. One more thing -- anybody know

Re: [Owfs-developers] Merging "moat" device specific code

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__) ||

Re: [Owfs-developers] Merging "moat" device specific code

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 wrote: > Yes, the f_cpu define only controls timing calculations, which must match > the clock speed. If

Re: [Owfs-developers] Merging "moat" device specific code

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 wrote: > As long as your built it for 16MHz it

Re: [Owfs-developers] Merging "moat" device specific code

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: 1600 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