Re: [Openocd-development] Error in test for current thread?
current_threadid is neither 0 or 1. I think that the 0 is the case where the current thread has not been updated, but I'm not sure why the test for 1. Should it instead be a test for -1 (the initialisation value for the global variable) to check whether it has been updated at all? If so, the attached patch corrects the test. I've had a closer look at how GDB references threads, and I see that it uses -1 for all threads and 0 for any thread. This makes me more confident that the patch attached to the previous email is correct - the function checks for thread IDs that refer to specific threads. Alan ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] Unusual ARM chip
I am attempting to use OpenOCD with a cellular chipset with an ARM11 and an ARM7+DSP core. I can access it with the Lauterbach debugger, but I find the interface very difficult to use and would prefer OpenOCD. It looks like some sort of TAP controller, perhaps like an OMAP3. Has anyone seen anything like this? Any idea how to get past it? Upon a scan, OpenOCD shows me: alex@msp-clx-aaustin:~$ openocd -f interface/jtagkey2.cfg -c jtag_khz\ 1 Open On-Chip Debugger 0.5.0-dev-00219-g737c9b6-dirty (2010-05-06-14:21) Licensed under GNU GPL v2 For bug reports, read http://openocd.berlios.de/doc/doxygen/bugs.html 1 kHz Info : max TCK change to: 3 kHz Info : clock speed 1 kHz Warn : There are no enabled taps. AUTO PROBING MIGHT NOT WORK!! Warn : AUTO auto0.tap - use jtag newtap auto0 tap -expected-id 0x30180083 ... Warn : AUTO auto0.tap - use ... -irlen 8 Warn : gdb services need one or more targets defined -- Alex Austin Associate Software Engineer Spectrum Design Solutions 110 North 5th Street, Floor 3 Minneapolis, MN 55403 Direct: +1.612.435.5537 Main: +1.612.435.0789 Mobile: +1.651.238.9273 Email: alex.aus...@spectrumdsi.com www.spectrumdsi.com ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] [patch] partial support for dsp568013/568037
Good work!
I think your chances of getting help on this one would
improve if we get this into the official repository first.
If your code is well tested, I'm inclined to commit it as-is as
a starting point to make improvements and get testing going.
A general comment about error messages. The error
should be reported where it occurred and not after
the fact(modeled on exceptions) and then the error
message should be propagated.
I.e. a number of the err_check() should only propagate the
error and not add an error message as the error has already
been reported.
You'd have to search through your code, but below I would
consider using a macro to only propagate and not to
amend any information.
+ retval = dsp5680xx_jtag_status(target,jtag_status);
+ err_check(retval,Failed to get JTAG status.);
Something like this?
#define err_check_propagate(retval,err_msg) if(retval !=
ERROR_OK){return retval;}
--
Øyvind Harboe
Can Zylin Consulting help on your project?
US toll free 1-866-980-3434 / International +47 51 87 40 27
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Error in test for current thread?
Any objections? -- Øyvind Harboe Can Zylin Consulting help on your project? US toll free 1-866-980-3434 / International +47 51 87 40 27 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] [PATCH] Get register value if it's invalid in cache
Are you still comfortable with this patch? Any objections? Anyone did any testing on other targets? -- Øyvind Harboe Can Zylin Consulting help on your project? US toll free 1-866-980-3434 / International +47 51 87 40 27 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Unusual ARM chip
Which chip? -- Øyvind Harboe Can Zylin Consulting help on your project? US toll free 1-866-980-3434 / International +47 51 87 40 27 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
