I don't have a m328 to test with, but it builds fine:
I created this local.cfg (based on sample cfg):
------
_include: world.cfg
devices:
_default:
_ref: defaults.target.m88
types:
_ref: defaults.types
code: []
m328test:
_ref: mcu.mega328
defs:
f_cpu: 8000000
port:
1: B0~
2: B1~
------
and then built it using:
$ CFG=local.cfg make m328test
Resulting file:
$ avr-size device/m328test/image.elf
text data bss dec hex filename
4054 46 65 4165 1045
device/m328test/image.elf
So at least it builds fine!
Johan
On 10/11/15 21:30, Colin Reese wrote:
> I will look again as I did not see this. I did not have success with the
> attiny moat. Using another owslave (by youen) I needed to run at 16mhz to get
> it working. Rather than rewrite to expose local IO (and other arbitrary
> values like serial), my end goal, I'd much rather get moat working.
>
> C
>
>> On Nov 10, 2015, at 12:16 PM, Johan Ström <jo...@stromnet.se> wrote:
>>
>> While I haven't tested it myself, there are specific code for mega328
>> (and 168, 88 and 8), besides tiny84/85 (which is marked "untested for
>> some time" though).
>> I've only used it on the mega8 and mega88 so far, running at 8Mhz with
>> internal oscillator with great success.
>>
>>> On 10/11/15 20:32, Colin Reese wrote:
>>> Is this still only for attiny? I've been limping along with code for
>>> atmega328 from elsewhere and would love if someone has time to help me port
>>> it. I love the idea.
>>>
>>>> On Nov 10, 2015, at 11:10 AM, Johan Ström <jo...@stromnet.se> wrote:
>>>>
>>>> Hi,
>>>>
>>>> a ticket was opened a few days ago regarding merging the "moat" device
>>>> specific owfs code into master:
>>>>
>>>> http://sourceforge.net/p/owfs/feature-requests/9/
>>>>
>>>> Does anyone object that I merge this? I've run this code myself for
>>>> months without any issues.
>>>> The only reason I can come to think of is that it uses the family code
>>>> 'F0' (re older discussion:
>>>> http://sourceforge.net/p/owfs/mailman/message/33029728/).
>>>> Paul's last comment regarding type/version fields is almost fulfilled;
>>>> there is no version field, but the device advertises which different
>>>> data types (adc, counter etc) it has support for.
>>>>
>>>> I don't know about Matthias Urlichs' ideas regarding any
>>>> commercialization, for me it is for private use. But as he (I assume it
>>>> his him) mentions in the ticket, it apparently has a few users now.
>>>>
>>>> As this is a well-working and pretty easy-to-use open-source variant of
>>>> a custom owslave, I'd love to see "official" support for it!
>>>>
>>>> Regards
>>>> Johan
>>>>
>>>> ------------------------------------------------------------------------------
>>>> _______________________________________________
>>>> 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 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
