svn head (currently r1943) fails when connecting using a v6/v5.3 jlink and
stm32 target.
Connecting using r1192 is ok, just a little slow.
The strange thing is if i then connect using r1943 it will work !!
Replug the jlink and it will fail with r1943, run r1192 then all is ok
again.
I
I updated to 1933 today and gave my j-links another try loading code
to a STM32. I tried a v3 v4 and v6 jlink. The v4 jlink worked
reliably, v3 worked after trying a few times and power cycling
everything. v6 won't work at all. I attached the console output of
all three jlink sessions.
On
I´ll try out the trunk when I get back into the office. Here is the
patch that I forgot to attach. I think regardless of whether the
trunk works this patch is a good idea just to be safe.
On Sun, May 24, 2009 at 12:29 AM, Zach Welch z...@superlucidity.net wrote:
On Sat, 2009-05-23 at 21:06
I am just updated to svn 1881 to use with my STM32 and jlink(yellow
v6.0). I had been using 1183, which worked every time, but was
unbearably slow. Revision 1881 is lightning fast compared with the
old revision. I am however seeing a few issues.
It takes 5 or six tries to get my program to
Try this again to the whole list.
Here is the trace. I'm taking a quick look at it right now. I am
guessing that having jlink_jtag_handle = 0 is the problem, just trying
to figure out how that happened.
Dylan
(gdb) run -f ../GNUTools/openOCD/newLPM.cfg -c init -c sleep 200 -f
flashAll.script
Something strikes me as pretty broken here. Maybe I am seeing ghosts.
I put in a few prints to see what was going on, then got confused and
ran from the debugger. This is what I found:
static int jlink_get_version_info(void)
{
int result;
int len;
u32 jlink_caps,
I use a JLink to flash my STM32 and I would love to be able to program
at the speeds you are seeing! I have been meaning to look at why this
is so slow for a while but haven't been able to find any time. I hope
to be able to get some of the new instrumentation changes in a give it
a try this
I am pretty sure that there is a problem with the Jlink driver here as
well. This is my config:
# script for stm32
# use jlink
interface jlink
# jtag speed
jtag_khz 500
jtag_nsrst_delay 100
jtag_ntrst_delay 100
#use combined on interfaces or targets that can't set TRST/SRST separately
are you running from RAM or FLASH?
On Mon, Dec 29, 2008 at 3:05 PM, Michel Catudal michelcatu...@gmail.com wrote:
I have a few issues with debugging a STM32-SK board (using eclipse with
the latest Zylin plugin)
I have modified the IAR application so it would work with my arm-elf-gcc
