Menu
▾
▴
openocd-devel
|
From: axel <axe...@fr...> - 2013-12-21 17:21:52
|
Hi, I tried to use a AT91SAM3N00A on openocd. A scan_chain brought: _________________________ Info : JTAG tap: at91sam3n.cpu tap/device found: 0x05b2e03f (mfg: 0x01f, part: 0x5b2e, ver: 0x0) Warn : JTAG tap: at91sam3n.cpu UNEXPECTED: 0x05b2e03f (mfg: 0x01f, part: 0x5b2e, ver: 0x0) Error: JTAG tap: at91sam3n.cpu expected 1 of 1: 0x4ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x4) ... The datasheet of the SAM3N by Atmel shows as JTAG ID Code 0x05b2e03f, so the scan of the chain seems to be correct. Here's the relevant part of my *.cfg: _________________________ #interface source [find interface/openocd-usb.cfg] #set CPU source [find cpu/arm/cortex_m3.tcl] #set target source [find target/at91sam3nXX.cfg] .... What happens with the scripts for chip identification? Thanks, Hardy-13 |
|
From: Paul F. <fer...@gm...> - 2013-12-22 06:16:03
|
Hi, On Sat, Dec 21, 2013 at 06:19:43PM +0100, axel wrote: > I tried to use a AT91SAM3N00A on openocd. A scan_chain brought: ... > The datasheet of the SAM3N by Atmel shows as JTAG ID Code 0x05b2e03f, so > the scan of the chain seems to be correct. Right. I think earlier SAM3N devices used generic Cortex-M ID code, but this is not the case with SAM3N00A apparently. I suggest you add _CPUTAPID2 the same way it works for the existing tap id and append -expected-id to jtag newtap command. And if that works for you, please send a patch. > #interface > source [find interface/openocd-usb.cfg] Please use configs from interface/ftdi/ instead for all ftdi-based adapters, the ftdi driver is actively supported, much faster and saner. > #set CPU > source [find cpu/arm/cortex_m3.tcl] You shouldn't source CPU-specific files manually, just omit it, the target script will do what's appropriate. > > #set target > source [find target/at91sam3nXX.cfg] -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fer...@gm... |
|
From: axel <axe...@fr...> - 2013-12-22 10:46:48
|
Hi Paul,
I made a new config, named 'at91sam3n00.cfg containing:
---------------------------------------------
#
# Configuration for Atmel's SAM3N series
#
# CPUTAPID changed to 0x05b2e03f for SAM3N00 chips
if { [info exists CHIPNAME] } {
set _CHIPNAME $CHIPNAME
} else {
set _CHIPNAME at91sam3n
}
if { [info exists CPUTAPID] } {
set _CPUTAPID $CPUTAPID
} else {
set _CPUTAPID 0x05b2e03f
}
jtag newtap $_CHIPNAME cpu -irlen 3 -ircapture 0x1 -irmask 0x1
-expected-id $_CPUTAPID
set _TARGETNAME $_CHIPNAME.cpu
target create $_TARGETNAME cortex_m -endian little -chain-position
$_TARGETNAME
set _FLASHNAME $_CHIPNAME.flash
flash bank flash0 at91sam3 0x00400000 0 0 0 $_TARGETNAME
# if srst is not fitted use SYSRESETREQ to
# perform a soft reset
cortex_m reset_config sysresetreq
---------------------------------------------
CPUTAPID is now correct. Furthermore I adjusted the -irlen to 3 and
-ircapture to 0x1 (seen in the appropriate BSDL file).
Not sure about -irmask; 0x9 was to long. I didn't find this keyword and
it's meaning :-(
But now I get another warning 'Invalid ACK 0x6' and polling the device
don't work:
---------------------------------------------
Open On-Chip Debugger 0.7.0 (2013-12-20-15:38)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.sourceforge.net/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
Warn : at91sam3n.cpu: nonstandard IR mask
cortex_m3 reset_config sysresetreq
adapter speed: 20 kHz
TapName Enabled IdCode Expected IrLen IrCap IrMask
-- ------------------- -------- ---------- ---------- ----- ----- ------
0 at91sam3n.cpu Y 0x00000000 0x05b2e03f 3 0x01 0x01
shutdown command invoked
Info : clock speed 20 kHz
Info : JTAG tap: at91sam3n.cpu tap/device found: 0x05b2e03f (mfg: 0x01f,
part: 0x5b2e, ver: 0x0)
Warn : Invalid ACK 0x6 in JTAG-DP transaction
Polling target at91sam3n.cpu failed, GDB will be halted. Polling again
in 100ms
Polling target at91sam3n.cpu failed, GDB will be halted. Polling again
in 300ms
---------------------------------------------
Any hints?
On 22.12.2013 07:15, Paul Fertser wrote:
> I suggest you add
> _CPUTAPID2 the same way it works for the existing tap id and append
> -expected-id to jtag newtap command.
|
|
From: Paul F. <fer...@gm...> - 2013-12-22 12:49:09
|
On Sun, Dec 22, 2013 at 11:43:02AM +0100, axel wrote: > CPUTAPID is now correct. Furthermore I adjusted the -irlen to 3 and > -ircapture to 0x1 (seen in the appropriate BSDL file). Even though the BSDL file says IR length is only three bits, it seems wrong as ADIv5 mandates IR to be of at least 4 bits long as that's necessary for the documented instructions to access debug registers. I can't figure yet what dirty tricks Atmel does here to use a 3-bit IR. Probably when JTAGSEL is high it uses a 3-bit IR and when it's low (or unconnected) it uses the usual 4-bit IR. So please make sure you're not pulling JTAGSEL high and also try with 4-bit IR. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fer...@gm... |
|
From: axel <axe...@fr...> - 2013-12-22 14:39:58
|
My fault: JTAGSEL was high; I thought the JTAG is activated instead of IO operation. Now the original 'at91sam3nXX.cfg' is working. But the error: __ Warn : Invalid ACK 0x6 in JTAG-DP transaction Polling target at91sam3n.cpu failed, GDB will be halted. Polling again in 100ms Polling target at91sam3n.cpu failed, GDB will be halted. Polling again in 300ms __ still happens. Is it because of a virgin chip? On 22.12.2013 13:48, Paul Fertser wrote: > On Sun, Dec 22, 2013 at 11:43:02AM +0100, axel wrote: >> CPUTAPID is now correct. Furthermore I adjusted the -irlen to 3 and >> -ircapture to 0x1 (seen in the appropriate BSDL file). > Even though the BSDL file says IR length is only three bits, it seems > wrong as ADIv5 mandates IR to be of at least 4 bits long as that's > necessary for the documented instructions to access debug registers. > > I can't figure yet what dirty tricks Atmel does here to use a 3-bit > IR. Probably when JTAGSEL is high it uses a 3-bit IR and when it's low > (or unconnected) it uses the usual 4-bit IR. > > So please make sure you're not pulling JTAGSEL high and also try with > 4-bit IR. > |
|
From: Paul F. <fer...@gm...> - 2013-12-22 15:59:17
|
On Sun, Dec 22, 2013 at 03:37:33PM +0100, axel wrote: > My fault: JTAGSEL was high; I thought the JTAG is activated instead of > IO operation. > > Now the original 'at91sam3nXX.cfg' is working. But the error: Ok, nice. So it presents the usual Cortex-M ID when it's not in JTAG Boundary Scan mode. > Warn : Invalid ACK 0x6 in JTAG-DP transaction > Polling target at91sam3n.cpu failed, GDB will be halted. Polling again > in 100ms > Polling target at91sam3n.cpu failed, GDB will be halted. Polling again > in 300ms > __ > > still happens. Is it because of a virgin chip? Might be so. Or probably the wires are too long. Or probably you need to issue "reset halt" or "reset init" and it'll start working. You should also consider physically connecting SRST and using "reset_config srst_only". -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fer...@gm... |
|
From: axel <axe...@fr...> - 2013-12-22 17:16:24
|
So I will check my board against the SAM3N00-EK. And there is a job for my oscilloscope for signal quality. All of these... work for tomorrow. BTW: 'reset init' and 'reset halt' in the *.cfg didn't work, unknown command :-( NRST of my SAM3 is already connected with SRST On 22.12.2013 16:59, Paul Fertser wrote: > On Sun, Dec 22, 2013 at 03:37:33PM +0100, axel wrote: >> My fault: JTAGSEL was high; I thought the JTAG is activated instead of >> IO operation. >> >> Now the original 'at91sam3nXX.cfg' is working. But the error: > Ok, nice. So it presents the usual Cortex-M ID when it's not in JTAG > Boundary Scan mode. > >> Warn : Invalid ACK 0x6 in JTAG-DP transaction >> Polling target at91sam3n.cpu failed, GDB will be halted. Polling again >> in 100ms >> Polling target at91sam3n.cpu failed, GDB will be halted. Polling again >> in 300ms >> __ >> >> still happens. Is it because of a virgin chip? > Might be so. Or probably the wires are too long. Or probably you need > to issue "reset halt" or "reset init" and it'll start working. You > should also consider physically connecting SRST and using > "reset_config srst_only". > |
|
From: Paul F. <fer...@gm...> - 2013-12-22 17:27:41
|
On Sun, Dec 22, 2013 at 06:14:04PM +0100, axel wrote: > BTW: 'reset init' and 'reset halt' in the *.cfg didn't work, unknown > command :-( Wasn't supposed to be used in a config file. Either you perform them manually (via telnet or gdb) or you add them after "init" command. I'd appreciate it if you avoided top-posting, please. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fer...@gm... |
|
From: axel <axe...@fr...> - 2013-12-23 15:20:29
|
Problem was a strong (100 Ohm) pull-up at TDI instaed of 100 kOhm. So the TDI changed only between high- an mid level. Sometime it worked (reading JTAG ID) and sometime not :-( Thank's for your hints!! |
|
From: Paul F. <fer...@gm...> - 2013-12-23 15:44:55
|
Hey :) On Mon, Dec 23, 2013 at 04:17:50PM +0100, axel wrote: > Problem was a strong (100 Ohm) pull-up at TDI instaed of 100 kOhm. So > the TDI changed only between high- an mid level. Hehe, 'scoping does wonders ;) > Thank's for your hints!! Welcome, and best of luck with your projects. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fer...@gm... |
|
From: Chris F. <chr...@gm...> - 2013-12-23 10:07:42
|
I'm having problems getting the latest development version of oocd with cmsis-dap support to find the HIDAPI library files. I've built and installed HIDAPI and can see the following files in /usr/local/lib: libhidapi-hidraw.a libhidapi-libusb.la libhidapi-hidraw.la libhidapi-libusb.so libhidapi-hidraw.so libhidapi-libusb.so.0 libhidapi-hidraw.so.0 libhidapi-libusb.so.0.0.0 libhidapi-hidraw.so.0.0.0 libopenocd.a libhidapi-libusb.a libopenocd.la When I run ./bootstrap && ./configure on commit 8994597a08eb43ae86649d3ef200b47da4d7075e Author: Spencer Oliver <sp...@sp...> Date: Thu Dec 19 21:33:19 2013 +0000 I see: checking for LIBUSB1... yes configure: libusb-1.0 header bug workaround: LIBUSB1_CFLAGS changed to "-isystem /usr/include/libusb-1.0" checking for LIBUSB0... no checking for HIDAPI... no checking for HIDAPI... yes then: OpenOCD configuration summary -------------------------------------------------- MPSSE mode of FTDI based devices yes (auto) ST-Link JTAG Programmer yes (auto) TI ICDI JTAG Programmer yes (auto) Keil ULINK JTAG Programmer yes (auto) Segger J-Link JTAG Programmer yes (auto) OSBDM (JTAG only) Programmer yes (auto) eStick/opendous JTAG Programmer yes (auto) Andes JTAG Programmer yes (auto) Versaloon-Link JTAG Programmer no USBProg JTAG Programmer no Raisonance RLink JTAG Programmer no Olimex ARM-JTAG-EW Programmer no CMSIS-DAP Compliant Debugger yes (auto) but after make && sudo make install, oocd can't see the device: Error: unable to open CMSIS-DAP device Error: unable to init CMSIS-DAP driver What have I done wrong? Regards Chris |
|
From: Spencer O. <sp...@sp...> - 2013-12-23 10:35:56
|
On 23 December 2013 10:07, Chris Fryer <chr...@gm...> wrote: > I'm having problems getting the latest development version of oocd with > cmsis-dap support to find the HIDAPI library files. > > I've built and installed HIDAPI and can see the following files in > /usr/local/lib: > libhidapi-hidraw.a libhidapi-libusb.la > libhidapi-hidraw.la libhidapi-libusb.so > libhidapi-hidraw.so libhidapi-libusb.so.0 > libhidapi-hidraw.so.0 libhidapi-libusb.so.0.0.0 > libhidapi-hidraw.so.0.0.0 libopenocd.a > libhidapi-libusb.a libopenocd.la > > When I run ./bootstrap && ./configure on commit > 8994597a08eb43ae86649d3ef200b47da4d7075e Author: Spencer Oliver > <sp...@sp...> Date: Thu Dec 19 21:33:19 2013 +0000 > I see: > checking for LIBUSB1... yes > configure: libusb-1.0 header bug workaround: LIBUSB1_CFLAGS changed to > "-isystem /usr/include/libusb-1.0" > checking for LIBUSB0... no > checking for HIDAPI... no > checking for HIDAPI... yes > > then: > > OpenOCD configuration summary > -------------------------------------------------- > MPSSE mode of FTDI based devices yes (auto) > ST-Link JTAG Programmer yes (auto) > TI ICDI JTAG Programmer yes (auto) > Keil ULINK JTAG Programmer yes (auto) > Segger J-Link JTAG Programmer yes (auto) > OSBDM (JTAG only) Programmer yes (auto) > eStick/opendous JTAG Programmer yes (auto) > Andes JTAG Programmer yes (auto) > Versaloon-Link JTAG Programmer no > USBProg JTAG Programmer no > Raisonance RLink JTAG Programmer no > Olimex ARM-JTAG-EW Programmer no > CMSIS-DAP Compliant Debugger yes (auto) > > > but after make && sudo make install, oocd can't see the device: > > Error: unable to open CMSIS-DAP device > Error: unable to init CMSIS-DAP driver > > What have I done wrong? > Just a thought did you run ldconfig after installing hidapi ? Cheers Spen |
|
From: Chris F. <chr...@gm...> - 2013-12-23 11:30:15
|
On 23/12/13 10:29, Spencer Oliver wrote: > Just a thought did you run ldconfig after installing hidapi ? Cheers Spen I hadn't done that. I just ran sudo ldconfig (is there more to it than that?). That completed with no reports but it's made no difference. I get the same reports from ./configure and when running oocd. Regards Chris |
|
From: Spencer O. <sp...@sp...> - 2013-12-23 12:39:01
|
On 23 December 2013 11:30, Chris Fryer <chr...@gm...> wrote: > On 23/12/13 10:29, Spencer Oliver wrote: >> >> Just a thought did you run ldconfig after installing hidapi ? Cheers Spen > > I hadn't done that. > > I just ran sudo ldconfig (is there more to it than that?). That completed > with no reports but it's made no difference. I get the same reports from > ./configure and when running oocd. > see if the lib is available with ldconfig -p | grep hid can you provide a full -d3 log ? Spen |
|
From: Chris F. <chr...@gm...> - 2013-12-23 12:57:39
|
On 23/12/13 12:38, Spencer Oliver wrote:
> see if the lib is available with ldconfig -p | grep hid
chris:~$ ldconfig -p | grep hid
libhidapi-libusb.so.0 (libc6,x86-64) =>
/usr/local/lib/libhidapi-libusb.so.0
libhidapi-libusb.so (libc6,x86-64) =>
/usr/local/lib/libhidapi-libusb.so
libhidapi-hidraw.so.0 (libc6,x86-64) =>
/usr/local/lib/libhidapi-hidraw.so.0
libhidapi-hidraw.so (libc6,x86-64) =>
/usr/local/lib/libhidapi-hidraw.so
chris:~$
I'm a little surprised to see x86 in there as I thought everything on my
system was 64-bit.
>
> can you provide a full -d3 log ?
>
>
Err ... what do I pass -d3 to?
|
|
From: Spencer O. <sp...@sp...> - 2013-12-23 13:11:18
|
On 23 December 2013 12:57, Chris Fryer <chr...@gm...> wrote: > On 23/12/13 12:38, Spencer Oliver wrote: >> >> see if the lib is available with ldconfig -p | grep hid > > chris:~$ ldconfig -p | grep hid > libhidapi-libusb.so.0 (libc6,x86-64) => > /usr/local/lib/libhidapi-libusb.so.0 > libhidapi-libusb.so (libc6,x86-64) => /usr/local/lib/libhidapi-libusb.so > libhidapi-hidraw.so.0 (libc6,x86-64) => > /usr/local/lib/libhidapi-hidraw.so.0 > libhidapi-hidraw.so (libc6,x86-64) => /usr/local/lib/libhidapi-hidraw.so > chris:~$ > > I'm a little surprised to see x86 in there as I thought everything on my > system was 64-bit. > x86-64 is 64bit. > >> >> can you provide a full -d3 log ? >> >> openocd -d3 ... Spen |
|
From: Chris F. <chr...@gm...> - 2013-12-23 13:16:50
|
On 23/12/13 13:11, Spencer Oliver wrote:
> x86-64 is 64bit.
... :-[
>
> openocd -d3 ...
>
chris:~$ openocd -d3
Open On-Chip Debugger 0.8.0-dev-00283-g8994597 (2013-12-20-15:28)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.sourceforge.net/doc/doxygen/bugs.html
User : 13 3 command.c:546 command_print(): debug_level: 3
Debug: 14 3 configuration.c:44 add_script_search_dir(): adding
/home/chris/.openocd
Debug: 15 3 configuration.c:44 add_script_search_dir(): adding
/usr/local/share/openocd/site
Debug: 16 3 configuration.c:44 add_script_search_dir(): adding
/usr/local/share/openocd/scripts
Debug: 17 3 configuration.c:84 find_file(): found openocd.cfg
Debug: 18 3 command.c:145 script_debug(): command - ocd_command
ocd_command type ocd_reset_config srst_only srst_nogate connect_assert_srst
Debug: 19 3 command.c:145 script_debug(): command - reset_config
ocd_reset_config srst_only srst_nogate connect_assert_srst
User : 21 3 command.c:546 command_print(): srst_only separate
srst_nogate srst_open_drain connect_assert_srst
Debug: 22 3 command.c:145 script_debug(): command - ocd_command
ocd_command type ocd_adapter_khz 1000
Debug: 23 3 command.c:145 script_debug(): command - adapter_khz
ocd_adapter_khz 1000
Debug: 25 3 core.c:1644 jtag_config_khz(): handle jtag khz
Debug: 26 3 core.c:1611 adapter_khz_to_speed(): convert khz to interface
specific speed value
Debug: 27 3 core.c:1611 adapter_khz_to_speed(): convert khz to interface
specific speed value
User : 28 3 command.c:546 command_print(): adapter speed: 1000 kHz
Debug: 29 4 configuration.c:84 find_file(): found
/usr/local/share/openocd/scripts/board/frdm-kl25z.cfg
Debug: 30 4 configuration.c:84 find_file(): found
/usr/local/share/openocd/scripts/interface/cmsis-dap.cfg
Debug: 31 4 command.c:145 script_debug(): command - ocd_command
ocd_command type ocd_interface cmsis-dap
Debug: 32 4 command.c:145 script_debug(): command - interface
ocd_interface cmsis-dap
Debug: 34 4 command.c:366 register_command_handler(): registering
'ocd_cmsis-dap'...
Debug: 35 4 command.c:366 register_command_handler(): registering
'ocd_cmsis_dap_vid_pid'...
Debug: 36 4 command.c:366 register_command_handler(): registering
'ocd_jtag'...
Debug: 37 4 command.c:366 register_command_handler(): registering
'ocd_jtag'...
Debug: 38 4 command.c:366 register_command_handler(): registering
'ocd_jtag'...
Debug: 39 4 command.c:366 register_command_handler(): registering
'ocd_jtag'...
Debug: 40 4 command.c:366 register_command_handler(): registering
'ocd_jtag'...
Debug: 41 4 command.c:366 register_command_handler(): registering
'ocd_jtag'...
Debug: 42 4 command.c:366 register_command_handler(): registering
'ocd_jtag'...
Debug: 43 4 command.c:366 register_command_handler(): registering
'ocd_jtag'...
Debug: 44 4 command.c:366 register_command_handler(): registering
'ocd_jtag'...
Info : 45 4 transport.c:118 allow_transports(): only one transport
option; autoselect 'cmsis-dap'
Debug: 46 4 adi_v5_cmsis_dap.c:246 cmsis_dap_select(): CMSIS-ADI:
cmsis_dap_select
Debug: 47 4 command.c:401 register_command(): command 'cmsis-dap' is
already registered in '<global>' context
Debug: 48 4 command.c:366 register_command_handler(): registering
'ocd_cmsis-dap'...
Error: 49 7 cmsis_dap_usb.c:175 cmsis_dap_usb_open(): unable to open
CMSIS-DAP device
Error: 50 7 adi_v5_cmsis_dap.c:266 cmsis_dap_select(): unable to init
CMSIS-DAP driver
Error: 51 7 transport.c:83 transport_select(): Error selecting
'cmsis-dap' as transport
Debug: 52 7 command.c:628 run_command(): Command failed with error code -4
User : 53 7 command.c:666 command_run_line(): Runtime Error:
/usr/local/share/openocd/scripts/interface/cmsis-dap.cfg:7:
in procedure 'script'
at file "embedded:startup.tcl", line 58
at file "openocd.cfg", line 4
at file "/usr/local/share/openocd/scripts/board/frdm-kl25z.cfg", line 5
in procedure 'interface' called at file
"/usr/local/share/openocd/scripts/interface/cmsis-dap.cfg", line 7
Debug: 54 7 command.c:145 script_debug(): command - ocd_command
ocd_command type ocd_init
Debug: 55 7 command.c:145 script_debug(): command - init ocd_init
Debug: 57 7 command.c:145 script_debug(): command - ocd_command
ocd_command type ocd_target init
Debug: 58 7 command.c:145 script_debug(): command - ocd_target
ocd_target init
Debug: 60 7 target.c:1279 handle_target_init_command(): Initializing
targets...
Error: 61 10 cmsis_dap_usb.c:175 cmsis_dap_usb_open(): unable to open
CMSIS-DAP device
Debug: 62 10 command.c:628 run_command(): Command failed with error code -4
User : 63 10 command.c:666 command_run_line(): in procedure 'init'
|
|
From: Spencer O. <sp...@sp...> - 2013-12-23 13:19:15
|
On 23 December 2013 13:16, Chris Fryer <chr...@gm...> wrote: > chris:~$ openocd -d3 > Open On-Chip Debugger 0.8.0-dev-00283-g8994597 (2013-12-20-15:28) > Licensed under GNU GPL v2 > For bug reports, read > http://openocd.sourceforge.net/doc/doxygen/bugs.html > User : 13 3 command.c:546 command_print(): debug_level: 3 > Debug: 14 3 configuration.c:44 add_script_search_dir(): adding > /home/chris/.openocd > Debug: 15 3 configuration.c:44 add_script_search_dir(): adding > /usr/local/share/openocd/site > Debug: 16 3 configuration.c:44 add_script_search_dir(): adding > /usr/local/share/openocd/scripts > Debug: 17 3 configuration.c:84 find_file(): found openocd.cfg > Debug: 18 3 command.c:145 script_debug(): command - ocd_command ocd_command > type ocd_reset_config srst_only srst_nogate connect_assert_srst > Debug: 19 3 command.c:145 script_debug(): command - reset_config > ocd_reset_config srst_only srst_nogate connect_assert_srst > User : 21 3 command.c:546 command_print(): srst_only separate srst_nogate > srst_open_drain connect_assert_srst > Debug: 22 3 command.c:145 script_debug(): command - ocd_command ocd_command > type ocd_adapter_khz 1000 > Debug: 23 3 command.c:145 script_debug(): command - adapter_khz > ocd_adapter_khz 1000 > Debug: 25 3 core.c:1644 jtag_config_khz(): handle jtag khz > Debug: 26 3 core.c:1611 adapter_khz_to_speed(): convert khz to interface > specific speed value > Debug: 27 3 core.c:1611 adapter_khz_to_speed(): convert khz to interface > specific speed value > User : 28 3 command.c:546 command_print(): adapter speed: 1000 kHz > Debug: 29 4 configuration.c:84 find_file(): found > /usr/local/share/openocd/scripts/board/frdm-kl25z.cfg > Debug: 30 4 configuration.c:84 find_file(): found > /usr/local/share/openocd/scripts/interface/cmsis-dap.cfg > Debug: 31 4 command.c:145 script_debug(): command - ocd_command ocd_command > type ocd_interface cmsis-dap > Debug: 32 4 command.c:145 script_debug(): command - interface ocd_interface > cmsis-dap > Debug: 34 4 command.c:366 register_command_handler(): registering > 'ocd_cmsis-dap'... > Debug: 35 4 command.c:366 register_command_handler(): registering > 'ocd_cmsis_dap_vid_pid'... > Debug: 36 4 command.c:366 register_command_handler(): registering > 'ocd_jtag'... > Debug: 37 4 command.c:366 register_command_handler(): registering > 'ocd_jtag'... > Debug: 38 4 command.c:366 register_command_handler(): registering > 'ocd_jtag'... > Debug: 39 4 command.c:366 register_command_handler(): registering > 'ocd_jtag'... > Debug: 40 4 command.c:366 register_command_handler(): registering > 'ocd_jtag'... > Debug: 41 4 command.c:366 register_command_handler(): registering > 'ocd_jtag'... > Debug: 42 4 command.c:366 register_command_handler(): registering > 'ocd_jtag'... > Debug: 43 4 command.c:366 register_command_handler(): registering > 'ocd_jtag'... > Debug: 44 4 command.c:366 register_command_handler(): registering > 'ocd_jtag'... > Info : 45 4 transport.c:118 allow_transports(): only one transport option; > autoselect 'cmsis-dap' > Debug: 46 4 adi_v5_cmsis_dap.c:246 cmsis_dap_select(): CMSIS-ADI: > cmsis_dap_select > Debug: 47 4 command.c:401 register_command(): command 'cmsis-dap' is already > registered in '<global>' context > Debug: 48 4 command.c:366 register_command_handler(): registering > 'ocd_cmsis-dap'... > Error: 49 7 cmsis_dap_usb.c:175 cmsis_dap_usb_open(): unable to open > CMSIS-DAP device > Error: 50 7 adi_v5_cmsis_dap.c:266 cmsis_dap_select(): unable to init > CMSIS-DAP driver > Error: 51 7 transport.c:83 transport_select(): Error selecting 'cmsis-dap' > as transport > Debug: 52 7 command.c:628 run_command(): Command failed with error code -4 > User : 53 7 command.c:666 command_run_line(): Runtime Error: > /usr/local/share/openocd/scripts/interface/cmsis-dap.cfg:7: > in procedure 'script' > at file "embedded:startup.tcl", line 58 > at file "openocd.cfg", line 4 > at file "/usr/local/share/openocd/scripts/board/frdm-kl25z.cfg", line 5 > in procedure 'interface' called at file > "/usr/local/share/openocd/scripts/interface/cmsis-dap.cfg", line 7 > Debug: 54 7 command.c:145 script_debug(): command - ocd_command ocd_command > type ocd_init > Debug: 55 7 command.c:145 script_debug(): command - init ocd_init > Debug: 57 7 command.c:145 script_debug(): command - ocd_command ocd_command > type ocd_target init > Debug: 58 7 command.c:145 script_debug(): command - ocd_target ocd_target > init > Debug: 60 7 target.c:1279 handle_target_init_command(): Initializing > targets... > Error: 61 10 cmsis_dap_usb.c:175 cmsis_dap_usb_open(): unable to open > CMSIS-DAP device > Debug: 62 10 command.c:628 run_command(): Command failed with error code -4 > User : 63 10 command.c:666 command_run_line(): in procedure 'init' > I am assuming you have tweaked your udev rules, as a test run as sudo Spen |
|
From: Chris F. <chr...@gm...> - 2013-12-23 13:35:50
|
On 23/12/13 13:19, Spencer Oliver wrote: > I am assuming you have tweaked your udev rules, as a test run as sudo Sir, you assume way too much!!! Running as sudo solves the issue. Pointers as to how to go about tweaking my udev rules would be appreciated. I can't see any hidraw rules ... |
|
From: Spencer O. <sp...@sp...> - 2013-12-23 14:53:23
|
On 23 December 2013 13:35, Chris Fryer <chr...@gm...> wrote: > On 23/12/13 13:19, Spencer Oliver wrote: >> >> I am assuming you have tweaked your udev rules, as a test run as sudo > > Sir, you assume way too much!!! > > Running as sudo solves the issue. > > Pointers as to how to go about tweaking my udev rules would be appreciated. > I can't see any hidraw rules ... you will see updated rules in the patch http://openocd.zylin.com/#/c/1542/17/contrib/openocd.udev Cheers Spen |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X