> Do you have anything better with JTAG OCD documentation for AVR8?
I have read some, but I can not open it.
> Yes, but if somebody reworked AVR support in openOCD in a sane way,
it would be a matter of adding another config file, fairly trivial.
In VSprog, avr8.xml is the only thing needed to be
It will be hard if no official spec is available.
But even if implemented, not all dongles supported by OpenOCD can support DW
interface for Mega8.
2010/1/16 Alan Carvalho de Assis
> Hi Paul,
>
> On 1/16/10, Paul Fertser wrote:
> ...
> >
> >> In my programmer VSProg, I use a .xml configuration
Yes, actually I use auto-detect for AVR8 chips both on ISP and JTAG
according to the JTAG ID. So no need to specify the chip module.
2010/1/16 David Brownell
> On Saturday 16 January 2010, Paul Fertser wrote:
> > > If use .cfg for a AVR8 chip, there will be many such configure
> > > files.
> >
>
Hi Paul,
On 1/16/10, Paul Fertser wrote:
...
>
>> In my programmer VSProg, I use a .xml configuration file for all
>> these settings.
>
> Does it work over JTAG? Which JTAG adapters does it support?
>
Do you think it could be possible to implement ICD for AVR8 which
doesn't have a JTAG TAP inter
Hi,
On Sat, Jan 16, 2010 at 12:13:33PM +0300, Paul Fertser wrote:
> On Sat, Jan 16, 2010 at 04:44:37PM +0800, simon qian wrote:
> > For AVR8 support, there are other problems:
> > 1. chips library
> > Different AVR chips have different parameters, including Flash Page Size,
> > EEPROM Page Size, F
On Saturday 16 January 2010, Paul Fertser wrote:
> > If use .cfg for a AVR8 chip, there will be many such configure
> > files.
>
> I do not see a problem. Moreover if openOCD implements proper avr
> support one can automatically convert configs.
Simon, do the AVR8 chips have proper JTAG IDs, from
On Sat, Jan 16, 2010 at 04:44:37PM +0800, simon qian wrote:
> AVR-OCD-Document is verry old, it doesn't support some new
> devices.
Do you have anything better with JTAG OCD documentation for AVR8?
> For AVR8 support, there are other problems:
> 1. chips library
> Different AVR chips have dif
AVR-OCD-Document is verry old, it doesn't support some new devices.
As I know, Atmel will never open the debugging protocol of their JTAG spec.
You can hack current AVRs for the protocol, but if Atmel releases new chips
which is different from the hacked protocol, it will be an endless work to
On Thursday 14 January 2010, Paul Fertser wrote:
> > The On-chip Debug support is considered being private
> > JTAG instructions, and distributed within ATMEL and to
> > selected third party vendors only.
> >
> > Clearly, someone needs to throw a JTAG/SPI sniffer at some of the
>
2010/1/14 David Brownell :
> On Wednesday 13 January 2010, Řyvind Harboe wrote:
>> Perhaps there will be some feedback on minor things to change,
>> perhaps use size_t i for iteration variable instead of uint32_t i...
>
> Use "unsigned" ... :)
In this case it is a bit less obvious because it is an
On Wednesday 13 January 2010, Øyvind Harboe wrote:
> Perhaps there will be some feedback on minor things to change,
> perhaps use size_t i for iteration variable instead of uint32_t i...
Use "unsigned" ... :)
___
Openocd-development mailing list
Openocd
On Thu, Jan 14, 2010 at 12:16:59AM -0800, David Brownell wrote:
> On Wednesday 13 January 2010, ?yvind Harboe wrote:
> > Seing that avr is not at the level of an "official feature" I don't have
> > a problem with merging this work in progress as it does not affect
> > any other code. It can probabl
On Wednesday 13 January 2010, Øyvind Harboe wrote:
> Seing that avr is not at the level of an "official feature" I don't have
> a problem with merging this work in progress as it does not affect
> any other code. It can probably be refactored easily enough.
>
> Meanwhile we can "measure" how much
Seing that avr is not at the level of an "official feature" I don't have
a problem with merging this work in progress as it does not affect
any other code. It can probably be refactored easily enough.
Meanwhile we can "measure" how much interest there is openocd
+ avr w/some crude support...
Perh
Hi,
Attached is the patch that allows me to program both flash and eeprom of
atmega128.
Indeed it's not elegant but so is the whole AVR support :|
The question i still have no idea how to answer is how to properly implement
verification support? The problem is that the memory in question is NOR
15 matches
Mail list logo
