It should be same for UC3C series, because the port is 5V tolarent.
I'm using KiCAD, eagle has a limitation on the size of the PCB.
I have released the AVR32 code, but it will be tested later this week.
http://code.google.com/p/vsprog/source/browse/trunk/dongle/firmware/STK500v2
http://code.google
On 31/08/2010 11:18, simon qian wrote:
My AVR32 debugger/programmer will be released next week.
I'll get some sample(UC3B0256) from Atmel this week.
I think I can do the test after next week.
Are you planning to support the UC3C series as well?
They are +5V devices and not +3.3V devices a
My AVR32 debugger/programmer will be released next week.
I'll get some sample(UC3B0256) from Atmel this week.
I think I can do the test after next week.
2010/8/17 Michel Catudal
> On 16/08/2010 21:54, David Brownell wrote:
>
>>
>> --- On Mon, 8/16/10, Michel Catudal wrote:
>>
>>
>>
>>> Irreleva
On 16/08/2010 21:54, David Brownell wrote:
--- On Mon, 8/16/10, Michel Catudal wrote:
Irrelevant. AVR32 uses the Nexus protocols,
layered on top of JTAG. Those are public and
need no licensing.
For devices where you need most of the pins Nexus can't be
used.
Not wholly
--- On Mon, 8/16/10, Michel Catudal wrote:
> > Irrelevant. AVR32 uses the Nexus protocols,
> > layered on top of JTAG. Those are public and
> > need no licensing.
> >
> >
>
> For devices where you need most of the pins Nexus can't be
> used.
Not wholly true. Trace needs lots of pins,
On 16/08/2010 12:44, David Brownell wrote:
I have no license to use JTAGICE mkII protocol.
Irrelevant. AVR32 uses the Nexus protocols,
layered on top of JTAG. Those are public and
need no licensing.
For devices where you need most of the pins Nexus can't be used. Nexus
has
It will only matter if you use the registered mark of Atmel.
It should be OK to use protocol of JTAGICE mkII.
But I can't find any license for this protocol opened by Atmel.
What I say is JTAGICE mkII protocol, not Nexus protocol.
Of course, it's no problem to support AVR32 through
nexus protocol
David Brownell wrote:
> > > I have no license to use JTAGICE mkII protocol.
>
> Irrelevant. AVR32 uses the Nexus protocols,
> layered on top of JTAG. Those are public and
> need no licensing.
Might matter if making something that also looks identical to the
original Atmel product from the PC's
> > I have no license to use JTAGICE mkII protocol.
Irrelevant. AVR32 uses the Nexus protocols,
layered on top of JTAG. Those are public and
need no licensing.
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.b
simon qian wrote:
> I have no license to use JTAGICE mkII protocol.
That's a safe option, but on the other hand I don't think anyone can
claim that a communications protocol must be licensed. Clean-room
reverse engineering might be another safe option.
//Peter
___
Great!!
I have tried to add AVR32 support.
Versaloon once can emulate JTAGICE mkII from Atmel, and
can support AVR32 both under IAR EWAVR32 and AVR32 Studio.
But I have removed these supports due to potential license
problem -- I have no license to use JTAGICE mkII protocol.
I'll buy a AVR32 demo
On Sun, Aug 15, 2010 at 9:53 PM, Oleksandr Tymoshenko
wrote:
>
> On 2010-08-15, at 10:49 AM, Øyvind Harboe wrote:
>
>> Looks like a good start to me.
>>
>> Any objections to committing at this point so it can serve
>> as a starting point for collaboration?
> No objections, quite contrary :)
>>
On 2010-08-15, at 10:49 AM, Øyvind Harboe wrote:
> Looks like a good start to me.
>
> Any objections to committing at this point so it can serve
> as a starting point for collaboration?
No objections, quite contrary :)
>
> Some comments:
>
> - I believe error propagation is missing in some
Looks like a good start to me.
Any objections to committing at this point so it can serve
as a starting point for collaboration?
Some comments:
- I believe error propagation is missing in some places
- should there not be a timeout for some of the operations?
--
Øyvind Harboe
US toll free
--- On Sat, 8/14/10, Oleksandr Tymoshenko wrote:
> Here is initial version of AVR32
> support for openocd:
Cool! would you happen to know the latest
story on mainlining binutils, GCC, and GDB support
for that arch? Last I heard, Atmel's code was
public but not (for some silly-ass reasons tha
Here is initial version of AVR32 support for openocd:
http://people.freebsd.org/~gonzo/openocd/avr32.diff
So far it supports:
- halt/resume
- registers inspection
- memory inspection/modification
I'm still getting up to speed with OpenOCD internals and AVR32 so code is a
little
bit messy and I'd
16 matches
Mail list logo
