Kees Jongenburger wrote:
> Hi
>
> I am trying the run a drscan 0 32 0xa3002048 and I am getting a
> SIGSEGV. Just posting here so you know :p
>
I don't see anything obvious :-(
FYI -you should be able to specify "drscan TAPNAME 32 0xa3002048"
instead of the hard coded 0 above.
That was the intent of tap names.
=================
Perhaps it would be helpful if there where some jtag shift level debug
messages.
Sadly - there is little there.
And adding them by default would be come be painful (logs would be huge).
I have an idea.... if you want to give it a crack.
I can't look at it much more today - maybe +2 days realistically
================
A command like this would be very helpful:
jtag debugflags NUMBER
The functions you would need to look at are - all there in
"jim_jtag_command()'
The one extra you might need is "Jim_GetOpt_Wide()"
You'd want to add it to "jtag_jim_command()" - like the others.
Where the NUMBER - sets some U32 global in the JTAG file.
Then - each bit in the global would represent - various areas to enable
"LOG_DEBUG()" messages.
=== Then ===
For example: in jtag.[ch]
extern u32 jtag_debug_flags = 0;
In "jtag.c" - jtag jim command
Add support for the new command.
And in "jtag_build_buffer()" do things like:
if( jtag_debug_flags & SOMEBITFLAG ){
LOG_DEBUG("scan-size: %d, bit_count );
LOG_DEBUG("n-fields %d", cmd->num_fields );
}
And other associated messages - one bit per interesting area?
======
*END*
======
-Duane.
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
