As Frank Storm wrote:
> GDB: Read 2 bytes from 0x82
> jtagRead
> command[R, 1]: 52 A0 00 00 00 41 20 20
> response: CF F7 00 41
> ->GDB: f7cf
> GDB:
> ->GDB:
> GDB:
>
> GDB: Read 2 bytes from 0x8C
> jtagRead
> command[R, 1]: 52 A0 00 00 00 46 20 20
> response: FF FF 00 41
> ->GDB:
> GDB:
> It's not a compile-time option but a run-time option: -d. Yes, please
> add this to the AVaRICE commandline. This will trace the ICE
> communication. From a glance at the code, the only reason for
> jtagRead() returning a NULL pointer could be a non-OK response from
> the ICE.
Ok, here is the
As Frank Storm wrote:
> Hm, the variable jtagBuffer is 0 after jtagRead, which explains the
> crash.
That means jtagRead() returned a NULL pointer, rather than sensible
data. It should probably rather throw an exception ... but while I
converted the JTAGICEmkII code to use exceptions for error h
Hi Jörg,
> Could you also provide the call stack here? Obviously, it must be the
> caller of mem2hex already calling it with a NULL pointer.
#2 0x0040dc65 in main (argc=4, argv=0x7fffd468) at main.cc:735
// Now do the actual processing of GDB messages
// We
As Frank Storm wrote:
> static char *mem2hex(uchar *mem, char *buf, int count)
> {
> for (int i = 0; i < count; i++)
> ->buf = byteToHex(*mem++, buf);
> *buf = 0;
>
> return (buf);
Could you also provide the call stack here? Obviously, it must be the
caller of mem2hex al
Hi,
my first trials with AVaRICE were not that successful :-( AVaRICE
crashes after it is contacted by GDB. So I compiled AVaRICE with debug
information to see whether I could identify the position in the code
where the error occurred. Here is the GDB output of the debug session:
(gdb) run --j
