This is an automated email from Gerrit.
Andrey Yurovsky (yurov...@gmail.com) just uploaded a new patch set to Gerrit,
which you can find at http://openocd.zylin.com/1641
-- gerrit
commit 67ded5c64e5f591811804afffdaa9ed0408dc6d1
Author: Andrey Yurovsky
Date: Fri Sep 20 22:21:10 2013 -0700
This is an automated email from Gerrit.
Andreas Fritiofson (andreas.fritiof...@gmail.com) just uploaded a new patch set
to Gerrit, which you can find at http://openocd.zylin.com/1640
-- gerrit
commit 6755b3d7162eb3bddfd92ba39e7dcfd77690547d
Author: Andreas Fritiofson
Date: Fri Sep 20 23:06:2
On 09/20/2013 05:03 PM, Andrey Skvortsov wrote:
> Hello, guys.
>
> When I am connecting to the target for a first time after reset, I see
> error messages:
>
> Error: JTAG-DP STICKY ERROR
> Error: MEM_AP_CSW 0x8042, MEM_AP_TAR 0x54011140
> Error: JTAG-DP STICKY ERROR
> Error: MEM_AP_CSW 0x800
Hello,
I am using board with AM3517. It seems that our AM3517 has a newer
revision. I added new id to the target configuration file and now it
works correctly.
Here is the small patch. I hope you will include it in the next releases.
diff --git a/tcl/target/amdm37x.cfg b/tcl/target/amdm37x.cfg
i
Hello, guys.
When I am connecting to the target for a first time after reset, I see
error messages:
Error: JTAG-DP STICKY ERROR
Error: MEM_AP_CSW 0x8042, MEM_AP_TAR 0x54011140
Error: JTAG-DP STICKY ERROR
Error: MEM_AP_CSW 0x8042, MEM_AP_TAR 0x54011140
Error: JTAG-DP STICKY ERROR
Error: ME
Hi,
I have to backpedal to what I said.
I forgot to do a sudo make install so I was still running code without
this change...
Sorry.
Now with this code I get a mmap error bad argument.
I was able to make code run and get a profile but I had to change the
code in fact exactly in the way of my orig
Spencer,
The binary I sent above still bricks my oocd connections. I am not 100%
sure why, but I believe that it reconfigures the reset GPIO line to be a
regular output pin and pulls it low.
Anyway, if I have a proper C code with good startup scripts, everything
works just fine. The interesting
On 20 September 2013 09:46, Chris Fryer wrote:
> On 20/09/13 08:44, Chris Fryer wrote:
>
> I'll try to find a more controlled way to break my uC to see if I can bring
> it back without manual reset intervention.
>
> I can now send my device to DEEPSLEEP (Kinetis VLLS0) and connect properly
> using
On 20/09/13 08:44, Chris Fryer wrote:
I'll try to find a more controlled way to break my uC to see if I can
bring it back without manual reset intervention.
I can now send my device to DEEPSLEEP (Kinetis VLLS0) and connect
properly using oocd without any manual intervention.
Thanks as ever fo
I can confirm that (using the patch and correct reset_config) I /do/ now
see a pulse on the resetb line (two in fact) during oocd attach (using
the right channel on the scope helps :-[ ).
I'll try to find a more controlled way to break my uC to see if I can
bring it back without manual reset i
10 matches
Mail list logo