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 handling, I didn't do it for the old mkI code, since I didn't think it's worth the effort. > I called GDB from Eclipse so it is difficult to say, which commands were > already issued. I think Eclipse logs the GDB communication somewhere. However, that's not much relevant here it seems. As you already mentioned, it tries to read two bytes from address 0x140, which is certainly an explicit request. All of the related code lines for jtagRead() (in src/jtagrw.cc) are still from SVN revision 2, almost 10 years old. ;-) > What do I have to do during compilation to switch on the > output from "debugOut"? 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. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) ------------------------------------------------------------------------------ Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS and more. Get SQL Server skills now (including 2012) with LearnDevNow - 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only - learn more at: http://p.sf.net/sfu/learnmore_122512 _______________________________________________ avarice-user mailing list avarice-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/avarice-user
