[Openocd-development] Fwd: Re: Still J-Link problems
Hello, in the meantime, I connected broken JLink to the good one to read the firmware. But I could not init the target. I got following: D:\projects\arm-CortexM3openocd -f sam7x256.cfg Open On-Chip Debugger 0.4.0 (2010-02-22-19:05) Licensed under GNU GPL v2 For bug reports, read http://openocd.berlios.de/doc/doxygen/bugs.html 1 kHz jtag_nsrst_assert_width: 10 jtag_nsrst_delay: 100 srst_only separate srst_gates_jtag srst_open_drain Info : J-Link initialization started / target CPU reset initiated Info : J-Link ARM V8 compiled Aug 24 2011 17:23:32 Info : JLink caps 0xb9ff7bbf Info : JLink hw version 8 Info : JLink max mem block 9424 Info : Vref = 3.364 TCK = 1 TDI = 0 TDO = 0 TMS = 0 SRST = 0 TRST = 0 Info : J-Link JTAG Interface ready Info : clock speed 1 kHz Info : JTAG tap: sam7x256.cpu tap/device found: 0x3f0f0f0f (mfg: 0x787, part: 0xf0f0, ver: 0x3) Warn : Unexpected idcode after end of chain: 32 0x Warn : Unexpected idcode after end of chain: 64 0x Warn : Unexpected idcode after end of chain: 96 0x Warn : Unexpected idcode after end of chain: 128 0x Warn : Unexpected idcode after end of chain: 160 0x Warn : Unexpected idcode after end of chain: 192 0x Warn : Unexpected idcode after end of chain: 224 0x Warn : Unexpected idcode after end of chain: 256 0x Warn : Unexpected idcode after end of chain: 288 0x Warn : Unexpected idcode after end of chain: 320 0x Warn : Unexpected idcode after end of chain: 352 0x Warn : Unexpected idcode after end of chain: 384 0x Warn : Unexpected idcode after end of chain: 416 0x Warn : Unexpected idcode after end of chain: 448 0x Warn : Unexpected idcode after end of chain: 480 0x Warn : Unexpected idcode after end of chain: 512 0x Warn : Unexpected idcode after end of chain: 544 0x Warn : Unexpected idcode after end of chain: 576 0x Warn : Unexpected idcode after end of chain: 608 0x Error: double-check your JTAG setup (interface, speed, missing TAPs, ...) Info : JTAG tap: sam7x256.cpu tap/device found: 0x3f0f0f0f (mfg: 0x787, part: 0xf0f0, ver: 0x3) Warn : Unexpected idcode after end of chain: 32 0x Warn : Unexpected idcode after end of chain: 64 0x Warn : Unexpected idcode after end of chain: 96 0x Warn : Unexpected idcode after end of chain: 128 0x Warn : Unexpected idcode after end of chain: 160 0x Warn : Unexpected idcode after end of chain: 192 0x Warn : Unexpected idcode after end of chain: 224 0x Warn : Unexpected idcode after end of chain: 256 0x Warn : Unexpected idcode after end of chain: 288 0x Warn : Unexpected idcode after end of chain: 320 0x Warn : Unexpected idcode after end of chain: 352 0x Warn : Unexpected idcode after end of chain: 384 0x Warn : Unexpected idcode after end of chain: 416 0x Warn : Unexpected idcode after end of chain: 448 0x Warn : Unexpected idcode after end of chain: 480 0x Warn : Unexpected idcode after end of chain: 512 0x Warn : Unexpected idcode after end of chain: 544 0x Warn : Unexpected idcode after end of chain: 576 0x Warn : Unexpected idcode after end of chain: 608 0x Error: double-check your JTAG setup (interface, speed, missing TAPs, ...) Command handler execution failed Warn : jtag initialization failed; try 'jtag init' again. I use original sam7x256.cfg. I just added following lines at the beginning: interface jlink jtag_khz 1 jtag_nsrst_assert_width 10 jtag_nsrst_delay 100 reset_config srst_only I found that more people has problems with ATMEL chips: http://forum.sparkfun.com/viewtopic.php?t=19958 http://www.proxmark.org/forum/viewtopic.php?pid=3348 What is the correct setting then? Should I connect RTCK somewhere ? Any experience with it ? For those interested, I can connect logic analyzer to JTAG and capture some waves... Vaclav ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] openocd patch: 09b1704 dsp5680xx: add missing and broken error propagation
On Tue, Nov 1, 2011 at 3:30 PM, ger...@openocd.zylin.com wrote:
This is an automated email from Gerrit.
?yvind Harboe (oyvindhar...@gmail.com) just uploaded a new patch set to
Gerrit, which you can find at http://openocd.zylin.com/156
-- gerrit
commit 09b17046aaca462496d634508567e3a543719c17
Author: Øyvind Harboe oyvind.har...@zylin.com
Date: Tue Nov 1 23:28:10 2011 +0100
dsp5680xx: add missing and broken error propagation
found by clang.
Change-Id: Ie7e2ecad71bf0838ece93727e4778ad368b890ef
Signed-off-by: Øyvind Harboe oyvind.har...@zylin.com
diff --git a/src/target/dsp5680xx.c b/src/target/dsp5680xx.c
index 116f609..bf406c7 100644
--- a/src/target/dsp5680xx.c
+++ b/src/target/dsp5680xx.c
@@ -538,7 +538,7 @@ static int eonce_enter_debug_mode_without_reset(struct
target * target, uint16_t
}
if(eonce_status!=NULL)
*eonce_status = data_read_from_dr;
- return ERROR_OK;
+ return retval;
}
the code will never reach that point if retval!=ERROR_OK, but i agree
it's good to apply this change, for clarity.
#define TIME_DIV_FREESCALE 0.3
@@ -606,6 +606,7 @@ static int eonce_enter_debug_mode(struct target * target,
uint16_t * eonce_statu
err_check_propagate(retval);
instr_16 = 0x1;
retval = dsp5680xx_drscan(target,(uint8_t *) instr_16,(uint8_t *)
read_16,8);
+ err_check_propagate(retval);
instr_16 = 0x20;
retval = dsp5680xx_drscan(target,(uint8_t *) instr_16,(uint8_t *)
read_16,8);
jtag_add_sleep(TIME_DIV_FREESCALE*100*1000);
@@ -1446,7 +1447,7 @@ int dsp5680xx_f_erase(struct target * target, int
first, int last){
if(do_mass_erase){
//Mass erase
retval = mass_erase(target,hfm_ustat);
- err_check_propagate(retval);
+ err_check_propagate(retval);
is this just a whitespace?
last = HFM_SECTOR_COUNT-1;
}else{
for(int i = first;i=last;i++){
@@ -1704,8 +1705,10 @@ int dsp5680xx_f_unlock(struct target * target){
err_check_propagate(retval);
instr_16 = 0x1;
retval = dsp5680xx_drscan(target,(uint8_t *) instr_16,(uint8_t *)
read_16,8);
+ err_check_propagate(retval);
instr_16 = 0x20;
retval = dsp5680xx_drscan(target,(uint8_t *) instr_16,(uint8_t *)
read_16,8);
+ err_check_propagate(retval);
jtag_add_sleep(TIME_DIV_FREESCALE*100*1000);
jtag_add_reset(0,0);
jtag_add_sleep(TIME_DIV_FREESCALE*300*1000);
--
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
this patch seems fine, doesn't affect normal operation.
--
Rodrigo.
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] openocd patch: 09b1704 dsp5680xx: add missing and broken error propagation
We're switching to checkpatch's coding standard and gerrit will automatically do all the checks now, so a whitespace fix snuck into this patch. We plan to do a wholesale reformatting after next release, meanwhile we require all new patches to be checkpatch clean. The plan is to get the entire OpenOCD to build clean of clang warnings, but it will be some time until we're there. At that point we will probably make 0 clang warnings a requirement for new patches. -- Øyvind Harboe - Can Zylin Consulting help on your project? US toll free 1-866-980-3434 http://www.zylin.com/ ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] mailing lists
Hi, I have been waiting quite a while for sf to move the mailing list archives/users - it is now done :) Everybody that was subscribed to the old lists should be moved over to the ones at sf. This msg has been sent to both lists so that people can check the list settings have moved over correctly. https://lists.sourceforge.net/lists/listinfo/openocd-devel https://lists.sourceforge.net/lists/listinfo/openocd-commit So update your spam filters etc and use new list asap For info all commit/gerrit messages will now use the new list. Cheers Spen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
