Products > Test Equipment
Sniffing the Rigol's internal I2C bus
psysc0rpi0n:
--- Quote from: qwertymodo on September 23, 2016, 08:29:15 pm ---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
--- End quote ---
Yes, I understood that since the other post you said the only thing I could see with the LA was a dump of the JTAG port activity. And it's exactly that I was trying to see but I'm not sure of how the setp should be done in Saleae Logic software to be able to pick up the JTAG port activity...
qwertymodo:
You don't need to connect SRST, that's for resetting the host system. The logic analyzer just needs TRST to reset the internal JTAG state machine.
psysc0rpi0n:
What about TDI and TDO?
Sent from my GT-I9505 using Tapatalk
psysc0rpi0n:
Looks like I managed to use an Arduino to get some info from the JTAG of my scope!
I'm not sure if I can do anything else but I used a library available here I managed to pick up some bits of info, using "minicom" or the serial monitor of Arduino:
At boot time, I try to interrogate the JTAG interface to find all the connected devices (chips). It lists their built-in identification codes which take the form of 32 bits in four groups,and i get this:
03c93279 [0000 0011110010010011 00100111100 1]
--- Quote from: http://www.khjk.org/log/2013/aug.html ---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.
--- End quote ---
After the boot, if I interrogate the JTAG interface again, I get different results:
079264f3 [0000 0111100100100110 01001111001 1]
Does this means that there are at least 2 memories being used by the scope?
Edited;
I need to make a correction...
No matter what, the first time I interrogate the JTAG interface, I get the 03c93279 code, and the second time I interrogate it, I get 079264f3. Then if I try again, I always get the 079264f3 code.
Pinkus:
--- Quote from: rsivan on January 22, 2014, 07:50:36 pm ---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.
--- End quote ---
I know, the above it is quite old, but did rsivan or somebody else tried this?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version