As Andreas Løhre wrote:
> I have attached an strace for 4.6.3 (same behaviour as 4.7.2), but I won't
> be able to do the one for 4.7/4.4/4.5 before tomorrow.
Thanks to all who helped narrowing this down.
I could eventually reproduce it myself with a GCC 4.7, and then find
and fix it.
It's been
I have attached an strace for 4.6.3 (same behaviour as 4.7.2), but I won't
be able to do the one for 4.7/4.4/4.5 before tomorrow.
I did a quick test with gcc 4.5 yesterday, and it did behave slightly
different, but was still not very stable for the 1284P: It got to the point
where it started the G
As Andreas Løhre wrote:
> The full output is:
An interesting list, thanks!
> [jtag2rw.cc:180]: (error) Memory leak: response
> [jtag3rw.cc:182]: (error) Memory leak: response
Both these are actually the same (with the jtag3 code being cloned
from the jtag2 implementation). All this looks confu
I did a check with cppcheck and found one out of bounds array access in the
jtag3 code:
jtag3io.cc:495
The full output is:
[jtag2rw.cc:180]: (error) Memory leak: response
[jtag2usb.cc:422]: (error) Mismatching allocation and deallocation:
devnamecopy
[jtag2usb.cc:302]: (error) Memory leak: devnam
On Thu, Jan 10, 2013 at 8:50 PM, Joerg Wunsch wrote:
> As Andreas Løhre wrote:
>
> > I was still not able to start a session
> > on the 1284P. I will try some more on the different computers I have and
> > send the logs tonight.
>
> Someone reported on avrfreaks.net that he had similar problems o
As Andreas Løhre wrote:
> I was still not able to start a session
> on the 1284P. I will try some more on the different computers I have and
> send the logs tonight.
Someone reported on avrfreaks.net that he had similar problems on
Ubuntu 12.x, but the problems disappeared when he used an older
c
As Andreas Løhre wrote:
> I was still not able to start a session
> on the 1284P.
OK, I'm interested in seeing the debug traces for that.
--
cheers, J"org .-.-. --... ...-- -.. . DL8DTL
http://www.sax.de/~joerg/NIC: JW11-RIPE
Never trust an operating s
I tried it briefly yesterday, and by using the latest SVN I was able to do
a debug session on the ATmega2560. I was still not able to start a session
on the 1284P. I will try some more on the different computers I have and
send the logs tonight.
On Wed, Jan 9, 2013 at 8:24 AM, Andreas Løhre wrot
On Tue, Jan 8, 2013 at 9:31 PM, Joerg Wunsch wrote:
> As Andreas Løhre wrote:
>
> > I have attached a couple of the failing runs on my Atmega2560. The device
> > is running at 8MHz and no clkdiv8.
>
> Please try the current SVN again. I've committed a number of small
> changes. Among them is th
As Andreas Løhre wrote:
> I have attached a couple of the failing runs on my Atmega2560. The device
> is running at 8MHz and no clkdiv8.
Please try the current SVN again. I've committed a number of small
changes. Among them is that the CMD3_START_DEBUG command (which was
failing on you) is no l
As Andreas Løhre wrote:
> It was using JTAG. I haven't tried PDI yet as I don't have the
> connector available.
Both ought to work though, it's just you have to use -X rather than -x
to indicate the target Xmega device uses PDI. There are a number of
Xmega device which don't have any JTAG, but t
As Andreas Løhre wrote:
> I have attached a couple of the failing runs on my Atmega2560. The device
> is running at 8MHz and no clkdiv8.
Kinda strange, it's always the "start debugging" command that fails,
i.e. the target doesn't answer the JTAG initialization.
Curious, is the board's JTAG known
It was using JTAG. I haven't tried PDI yet as I don't have the connector
available.
Andreas
On Mon, Jan 7, 2013 at 8:28 PM, Knut Schwichtenberg wrote:
> Hi Andreas,
>
> which debug IF did you use: PDI or JTAG for the XMega?
>
> Cheers,
> Knut
>
> At 07.01.2013 20:24, wrote Andreas Løhre:
>
>
Hi Andreas,
which debug IF did you use: PDI or JTAG for the XMega?
Cheers,
Knut
At 07.01.2013 20:24, wrote Andreas Løhre:
Same errors as the m2560 with the 1284P - no luck.
XMEGA128A1 works perfectly, as far as I have tested, with some
stepping and a breakpoint inserted.
On Mon, Jan 7, 20
Same errors as the m2560 with the 1284P - no luck.
XMEGA128A1 works perfectly, as far as I have tested, with some stepping and
a breakpoint inserted.
On Mon, Jan 7, 2013 at 7:44 PM, Andreas Løhre wrote:
> I have attached a couple of the failing runs on my Atmega2560. The device
> is running at
I have attached a couple of the failing runs on my Atmega2560. The device
is running at 8MHz and no clkdiv8.
I'll try with the 1284P next.
Andreas
On Mon, Jan 7, 2013 at 11:56 AM, Andreas Løhre wrote:
>
>
>
> On Mon, Jan 7, 2013 at 10:19 AM, Joerg Wunsch wrote:
>
>> As Andreas Løhre wrote
On Mon, Jan 7, 2013 at 10:19 AM, Joerg Wunsch wrote:
> As Andreas Løhre wrote:
>
> > I tried the latest trunk with an ATmega2560 this weekend without success,
> > using the latest firmware from S6 patch 2.
>
> First, thanks for testing!
>
> > What devices and jtag firmware version are you doing y
As Andreas Løhre wrote:
> I tried the latest trunk with an ATmega2560 this weekend without success,
> using the latest firmware from S6 patch 2.
First, thanks for testing!
> What devices and jtag firmware version are you doing your development on ?
The JTAGICE3 firmware is 2.12 (decimal; Atmel
Hi,
I tried the latest trunk with an ATmega2560 this weekend without success,
using the latest firmware from S6 patch 2.
What devices and jtag firmware version are you doing your development on ?
It would be nice to setup matching hardware just to rule out
software/library trouble on my end.
I w
As Knut Schwichtenberg wrote:
> > Record TimeAction
> > 153xx 352.9xx Change EEProm adr: 0x180 from 0xff to 0x55
Thanks, for some reason, I've got an offset of about 3 s, but I can match
your numbers now.
I just committed what I've got so far to SVN. It's
Hi Jörg,
I did not check the record numbers in the reduced file, sorry. I have
the full file and so I can assign the record numbers to timestamps.
> RecordTimeAction
> 153xx 352.9xx Change EEProm adr: 0x180 from 0xff to 0x55
> 178xx 379.
Hi Knut,
> as promised here is my next trace.
Thank you very much! As you might have noticed, I already uploaded
your trace data to your feature request, so all of them can be
accessed from there.
> Sorry for the long delay - but a lot
> of work, > 2 weeks ill and Christmas limits the free amo
22 matches
Mail list logo
