On 11/05/11 06:53, Rogan Dawes wrote:
Hi,
Yes, I tried downgrading the firmware (installed older versions of the
JLink software until I found the version it came with). No change in
behaviour, unfortunately.
Regards,
Rogan
___
Openocd-development
On 2011/05/11 10:53 AM, Sébastien Baillou wrote:
Hello Rogan,
Did you correctly downgrade the firmware of the JLink ? I asked because
I faced the exact same issue a couple of weeks ago. I don't remember the
exact steps, but here's what I did :
1- Download version 4.10i of the firmware (
On 10/05/11 18:57, Michel JAOUEN wrote:
Hello,
For supporting optimized jtag chain length, you should look at CJTAG
specification, with star topology support.
CJTAG is not yet supported by openocd.
Best regards
Hello Michel,
I had a look at the 1149.7 standard which seemed very promising at
On 10/05/11 20:03, Øyvind Harboe wrote:
There is already some smp support in there, you may want to have a look
at that. Using threads has been discussed, but I think the model would
break down with MMUs. That said for DSP's it could be a good model
if they don't have MMUs.
The OpenOCD
They indeed do not feature any MMUs, so threading seems like the logical
choice from a user's point of view.
OpenOCD now has RTOS threads support. That should offer a lot
of help and examples.
Perhaps you can even come up with some code-reuse or make
your multi-core MMU less DSP's behave like
On 11/05/11 13:54, Laurent Gauch wrote:
Hi Sébastien,
Amontec is working on the SWD CTJTAG support on JTAGkey-3 generation.
Could you please let me know where did you get the info :
TMS is used as a clock while holding TCK at '1' really needs to be
added.
Best regards,
Laurent Gauch
On 11/05/11 13:54, Laurent Gauch wrote:
/ Hi Sébastien,
//
// Amontec is working on the SWD CTJTAG support on JTAGkey-3 generation.
//
// Could you please let me know where did you get the info :
//
// TMS is used as a clock while holding TCK at '1' really needs to be
// added.
//
//
// Best
Hello,
-A-
With 1149.1, hardware is available on table for testing.
Openocd requires the introduction of a mode
tap enable on fly
For doing that, at every device change :
- reset JTAG = jtag chain length is jrc tap length
- reprogram icepick (jrc) in order to include the required tap.
then the
On 11/05/11 15:14, Michel JAOUEN wrote:
Hello,
-A-
With 1149.1, hardware is available on table for testing.
Openocd requires the introduction of a mode
tap enable on fly
For doing that, at every device change :
- reset JTAG = jtag chain length is jrc tap length
- reprogram icepick (jrc) in
In startup.tcl, ocd_process_reset_inner calls init_reset with the
following comment:
# Use TRST or TMS/TCK operations to reset all the tap controllers.
# TAP reset events get reported; they might enable some taps.
So it seems init_reset should only reset TAP controllers.
After that,
I believe the attached patch fixes that, although I don't have
anything using the relevant two RTOSs to test against.
Having changed the direction of stack growth, I failed to correct
another instance of that variable's use. I have made the change to my
local copy and committed it (using the
How about adding a dummy RTOS thread type for testing purposes?
This dummy thread type should be usable with a bare metal
target and exercise as much of the RTOS code paths as
possible.
Even the ability to a basic smoketest would be *great*.
We have done the same with great success for
12 matches
Mail list logo
