The logic analyser won't control anything, it's just a passive listener, you need a jtag dongle compatible with openocd, which will control the actual jtag communication.
Sent from my m8wl using Tapatalk
The groups are, from most to least significant bit: 4-bit product version (0), 16-bit product code (3c93), 11-bit manufacturer code (279), and one bit that is always 1 for thaumaturgic reasons.
Hello
If someone can read the spi flash 25x40 of dp832a; I can try to turn my 832 into 832a, because fw is same.
Also other option is a full cloning spi flash + nand flash from 832a to manually program in a 832.
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.
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.
sudo openocd -d1 -f interface/jlink.cfg -c "transport select jtag" -c "adapter_khz 6000" -f board/imx28evk.cfg -l ~/openocd_log
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
sudo openocd -d1 -f interface/jlink.cfg -c "transport select jtag" -c "adapter_khz 6000" -f board/imx28evk.cfg -l ~/openocd_log
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
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'
And you're definitely using the MSO version of riglol not the standard version?
McBryce.
Gesendet von meinem Motorola DynaTEC 8000X mit Tapatalk.
I was successful using rigup-0.4.1-mso1000z exactly as it was provided in that package (no patches), using a memory dump taken immediately after the Rigol logo disappeared and the options dialog appeared on screen, using option code 0x1C0DF for a single license to unlock everything except the non-functional 5uV option (so you only have to type in one code). Give that a try.
Sent from my m8wl using Tapatalk
Just do it right after the Rigol logo disappears.
Sent from my m8wl using Tapatalk
The memory dump is successful but the keys are invalid! I think my hope has now ended!
The memory dump is successful but the keys are invalid! I think my hope has now ended!
You doublechecked the other side? Is your compiled binary from "[urlĀ“=http://gotroot.ca/rigol/rigup-0.4.1-mso1000z.zip]rigup-0.4.1-mso1000z[/url]" ok?
You tried also the provided binary?
I created my keys in December 2014 and I compiled the binary on my RasPi running raspian. My firmware version was 00.04.01.SP2.
What I read here ist querymodo was able to create the keys. Maybe something in your procedure is not working the right way. If you are sure about the dump, please check the other end of your workchain, aka the binary you compiled.
Good luck!
I think I didn't need to compile anything. The binary was ready-to-use, I guess!
I think I didn't need to compile anything. The binary was ready-to-use, I guess!
Ok, I see. This means you had used the provided binary for the key generation, right?
Do you asked someone, maybe querymondo, to generate you keys? Obviously he was able to gernerate the license-keys.
If you transfer your dump to another person who already generated working license-keys, maybe this person could generate your license keys as well.
Can you provide your dump via a download link?
I haven't asked anyone to generate license keys. If anyone is kind enough to do that, I can provide a link to my memory dump!