Drd420re
-
- Junior Member
- Posts: 41
- Joined: Mon Apr 20, 2009 8:08 pm
Drd420re
The box is not listed, I did try all STi5500 based devices - no go.
The program doesn't sense the device after it turned on: "USB CONNECTED" and "BOX OFF". Same if I boot it in BFR mode (a jumper to GND).
It should report IDCODE at least, but I'm getting ID=0.
The receiver is good - jKeys (using direct cable to LPT) works fine with all parts: RAM, flash, OTP and NVRAM.
The program doesn't sense the device after it turned on: "USB CONNECTED" and "BOX OFF". Same if I boot it in BFR mode (a jumper to GND).
It should report IDCODE at least, but I'm getting ID=0.
The receiver is good - jKeys (using direct cable to LPT) works fine with all parts: RAM, flash, OTP and NVRAM.
-
- Junior Member
- Posts: 8974
- Joined: Mon Jul 18, 2005 9:33 pm
First you need to see if it is DCU or DCU3. Then make an xml for that target.
Most testers here testing MIPS and if you select MIPS then you are not going anywhere.
However I think in this case it is more likely the connection and JTAG speed. NT has 12MHz JTAG clock and can adjust to 6M and 3M. Some device if it is bricked can only use 3M clock.
Most testers here testing MIPS and if you select MIPS then you are not going anywhere.
However I think in this case it is more likely the connection and JTAG speed. NT has 12MHz JTAG clock and can adjust to 6M and 3M. Some device if it is bricked can only use 3M clock.
-
- Junior Member
- Posts: 41
- Joined: Mon Apr 20, 2009 8:08 pm
It's good to know - I'll check.usbbdm wrote:If reset pin is connected then you can type "reset" to get reset function.
As to connection - custom made cable checked by DMM for continuity and proper pinout.
Could be something in algos ? My beef is in the status"BOX OFF" when it on.
How the indicator creating ?
Code: Select all
Sig DRD420RE <-> USBJTAG
GND 1 - X
TDO 3 - 5
TCK 5 - 9
TMS 7 - 7
TDI 9 - 3
TRST 11 - 1
RST 13 - 11
GND 1,2,6,8,10,12,14 - 2,4,6,8,10
-
- Junior Member
- Posts: 8974
- Joined: Mon Jul 18, 2005 9:33 pm
Your connection does not like ST20 JTAG. Unless JTAG NT is bad, you should always get CPU ID regardless the JTAG clock selection is good or not.JTog wrote:It's good to know - I'll check.
As to connection - custom made cable checked by DMM for continuity and proper pinout.
Could be something in algos ? My beef is in the status"BOX OFF" when it on.
How the indicator creating ?
Code: Select all
Sig DRD420RE <-> USBJTAG GND 1 - X TDO 3 - 5 TCK 5 - 9 TMS 7 - 7 TDI 9 - 3 TRST 11 - 1 RST 13 - 11 GND 1,2,6,8,10,12,14 - 2,4,6,8,10
-
- Junior Member
- Posts: 41
- Joined: Mon Apr 20, 2009 8:08 pm
Some info from STi5500 specs:
- TCK min period is 50 nS, adding propagation 50 nS ...
So for old STM models from ST20 family recommended run JTAG at 5 MHz by STM manuals.
Perhaps if it possible you could add a few more freqs ?
Like 5 MHz, 10 MHz and 20 MHz.
STi5518 support x2.5 JTAG speed.
Perhaps newest models has higher rate.
- TCK min period is 50 nS, adding propagation 50 nS ...
So for old STM models from ST20 family recommended run JTAG at 5 MHz by STM manuals.
Perhaps if it possible you could add a few more freqs ?
Like 5 MHz, 10 MHz and 20 MHz.
STi5518 support x2.5 JTAG speed.
Perhaps newest models has higher rate.
-
- Junior Member
- Posts: 41
- Joined: Mon Apr 20, 2009 8:08 pm
It's not DCU style connector, but by all other means: signals and CPU it's the same.usbbdm wrote:Your connection does not like ST20 JTAG. Unless JTAG NT is bad, you should always get CPU ID regardless the JTAG clock selection is good or not.
Don't judge by different pinout.
The gadget is OK - I told that in other thread last days.
Wanna see scope pictures or Logic Ananlyzer snapshot ?
PS. Debug control unit [DCU] doesn't limited to 20 pin connector and its pinout as used in dish boxes.
-
- Junior Member
- Posts: 8974
- Joined: Mon Jul 18, 2005 9:33 pm
Type "speed 2" will give you 3M JTAG clock.
JTAG is asynchronous protocol, thus the JTAG clock is not required to be precise. As long as you do not use higher clock than it allowed. I have not yet seen any CPU which cannot support 12M JTAG clock when it is not bricked. If it is bricked you might need to use slower clock since the registers are not initialized properly.
JTAG is asynchronous protocol, thus the JTAG clock is not required to be precise. As long as you do not use higher clock than it allowed. I have not yet seen any CPU which cannot support 12M JTAG clock when it is not bricked. If it is bricked you might need to use slower clock since the registers are not initialized properly.
Who is online
Users browsing this forum: No registered users and 8 guests