| Products > Test Equipment |
| Sniffing the Rigol's internal I2C bus |
| << < (427/899) > >> |
| Pehtoori:
--- Quote from: marmad on December 23, 2013, 09:20:57 pm --- --- Quote from: Pehtoori on December 23, 2013, 09:05:39 pm ---Or "they" don't have skill to do it, don't have it yet or don't have job so can't lose warranty from 850€ equipment. I tick at least last 2 of them atm :-\ --- End quote --- Have you just tried downgrading to FW v.01.01.00.02 then using Riglol keygen (for all Trigger, Decode, and Memory options)? --- End quote --- "I tick at least last 2", one of them was "don't have it (the scope) yet" :-DD (ok bit tired) But when I get one hopefully in month or two, thats what I'm going to do for it. |
| cybernet:
--- Quote from: Carrington on December 23, 2013, 06:58:20 pm ---Mode 0 and Mode 1? --- End quote --- likely the BMODE pins of the BFIN - toggle between flash/spi boot - where spi is what they use to flash the bootldr - one of my first posts in that thread was regarding bmode pins. if somebody wants to mess with them with boundary scan u can check the bfin pins logic levels nicely. |
| neamyalo:
I'm getting an error each time I try and dump the memory contents.. --- Code: ---GNU gdb 6.6 Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "--host=i586-mingw32msvc --target=bfin-elf". (gdb) target remote :2000 Remote debugging using :2000 0x0011debc in ?? () (gdb) info mem Using memory regions provided by the target. Num Enb Low Addr High Addr Attrs 0 y 0x20000000 0x20400000 rw nocache 1 y 0xef000000 0xef008000 ro nocache 2 y 0xff800000 0xff804000 rw nocache 3 y 0xff804000 0xff808000 rw nocache 4 y 0xff900000 0xff904000 rw nocache 5 y 0xff904000 0xff908000 rw nocache 6 y 0xffa00000 0xffa0c000 rw nocache 7 y 0xffa10000 0xffa14000 rw nocache 8 y 0xffb00000 0xffb01000 rw nocache 9 y 0xffc00000 0xffe00000 rw nocache 10 y 0xffe00000 0x100000000 rw nocache (gdb) dump binary memory dump.bin 0x20000000 0x20400000 Ignoring packet error, continuing... Reply contains invalid hex digit 116 (gdb) --- End code --- I've tried reducing the JTAG freq from 6MHz down to 60kHz, but there's no difference.. I'm running 2013R1 release on Windows and I can successfully dump 1K, but >= 2K and I get the error and no dump file. >:( |
| m-joy:
Huhu, maybe the cable lengh too large which might cause data loss? Thats what cybernet state on post 2082 |
| neamyalo:
It looks like setting the remotetimeout to 10 has solved it. |
| Navigation |
| Message Index |
| Next page |
| Previous page |