| Products > Test Equipment |
| Sniffing the Rigol's internal I2C bus |
| << < (842/899) > >> |
| psysc0rpi0n:
Is it need anything special to connect the J-Link device to the PC?? (I'm using Debian Jessie). I can't make J-Link software to connect with the device. After connected the device to the USB port, if I start the software only with "./JLinkEXE" I get this error: --- Code: ---SEGGER J-Link Commander V6.10a (Compiled Sep 19 2016 20:08:32) DLL version V6.10a, compiled Sep 19 2016 20:08:23 Connecting to J-Link via USB...FAILED: Can not connect to J-Link via USB. --- End code --- If I use sudo prior to the launch I get this error: --- Code: ---SEGGER J-Link Commander V6.10a (Compiled Sep 19 2016 20:08:32) DLL version V6.10a, compiled Sep 19 2016 20:08:23 Connecting to J-Link via USB... *** J-Link V6.10a Error *** The connected emulator can not be used with this software. Reason: "Broken. No longer used" *** J-Link V6.10a Error *** FAILED: Can not connect to J-Link via USB. --- End code --- What is wrong??? |
| McBryce:
The first error is due to the user permissions being set wrong for USB. Not sure about the second sudo error. Do you have a Windows PC that you could try? McBryce. |
| psysc0rpi0n:
I'm now checking and redoing the wiring but I have a question about the pin out of the J-Link device. I'm following J-Link site to plug some wires, but I'm used to see around the internet the following: TCK, TMS, TDI, TRST, TDO and SRST The J-Link site has: TDI, TMS, TCK, RTCK, TDO and RESET. I'm wondering which one, RTCK or RESET, matches the SRST... |
| psysc0rpi0n:
Ok, I got it... SRST is RESET I guess... Anyway I issued the following command --- Code: ---sudo openocd -d1 -f interface/jlink.cfg -c "transport select jtag" -c "adapter_khz 6000" -f board/imx28evk.cfg -l ~/openocd_log --- End code --- and the first time I got this: --- Code: ---Open On-Chip Debugger 0.9.0 (2016-09-30-19:43) Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Error: Invalid command argument new_level option value ('l') is not valid jtag adapter speed: 6000 kHz trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst adapter_nsrst_delay: 100 jtag_ntrst_delay: 100 dcc downloads are enabled imx28evk_init Info : J-Link ARM V8 compiled Nov 28 2014 13:44:46 Info : J-Link caps 0xb9ff7bbf Info : J-Link hw version 80000 Info : J-Link hw type J-Link Info : J-Link max mem block 9224 Info : J-Link configuration Info : USB-Address: 0x0 Info : Kickstart power on JTAG-pin 19: 0xffffffff Info : Vref = 3.448 TCK = 1 TDI = 1 TDO = 0 TMS = 1 SRST = 1 TRST = 1 Info : J-Link JTAG Interface ready Info : clock speed 6000 kHz Info : JTAG tap: imx28.cpu tap/device found: 0x079264f3 (mfg: 0x279, part: 0x7926, ver: 0x0) Info : Embedded ICE version 6 Info : imx28.cpu: hardware has 2 breakpoint/watchpoint units Info : accepting 'telnet' connection on tcp/4444 --- End code --- I mistyped -dl instead of -d1... Then I did the telnet connection and it worked! Then I trid again the connection but added a new option, to save the output log of openOCD like this: --- Code: ---sudo openocd -d1 -f interface/jlink.cfg -c "transport select jtag" -c "adapter_khz 6000" -f board/imx28evk.cfg -l ~/openocd_log --- End code --- and I got this: --- Code: ---Open On-Chip Debugger 0.9.0 (2016-09-30-19:43) Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html debug_level: 1 --- End code --- I hope this is OK... Now I'm going foe the telnet connection again... But before I want to ask another question: What I'm doing is just a memory dump, right? Is this anyway dangerous to the scope? Can I brick the scope? |
| psysc0rpi0n:
I tried to halt the scope a few seconds after powering it up while the Rigol logo is still on the screen but I always get "time out"... When I issue the "reset" command i get this: --- Code: ---Error: IR capture error at bit 4, saw 0x21 not 0x...3 Warn : Bypassing JTAG setup events due to errors Warn : ThumbEE -- incomplete support Error: cp15 read operation timed out in procedure 'reset' in procedure 'ocd_bouncer' --- End code --- |
| Navigation |
| Message Index |
| Next page |
| Previous page |