Hey,
I agree that's inconsistent but can we just change it? There might be
out-of-tree scripts that depend on the current behaviour.
Since string concatenation in Tcl is easy, it shouldn't really get too messy
IMHO, here's an example from my manual boundary scan script, see 0x$word there:
global bsrstate
set i 1
foreach word $state {
set bsrstate [lreplace $bsrstate $i $i 0x$word]
incr i 2
}
---
** [tickets:#94] drscan low level JTAG commnand returns hex value without a
prefix**
**Status:** new
**Milestone:** 0.9.0
**Created:** Fri Apr 17, 2015 10:29 PM UTC by Steven
**Last Updated:** Fri Apr 17, 2015 10:29 PM UTC
**Owner:** nobody
The output of the drscan command should have a prefix of "0x" as it's base 16.
Without it, Tcl scripts can get pretty messy to say the least!
Test case:
irscan test.cpu 0x2fff
irscan test.cpu 0x1004
drscan test.cpu 32 0x0
Expected:
0x10007243
Actual:
10007243
---
Sent from sourceforge.net because openocd-devel@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/openocd/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/openocd/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel
