Dcu3 jtag

Post by **usbbdm** » Mon Mar 16, 2009 9:41 am

slugworth wrote:The default settings for the st20 burner is a 4k buffer,which was ideal for the sst39vf3201 since it has 4k blocks.It programs at about 1meg per minute,so the 4meg flash takes around 4 minutes.It erases the entire chip at once,so that is fast.

I am thinking of having the programming speed for 150-250KB/s so program the flash will take about half a minute and in case of the FTA it will be much less if we skip the blank sectors.

slugworth · Post by **slugworth** » Mon Mar 16, 2009 11:51 am

Some dcu3 receivers have a 2meg flash,others have 4meg so it would be good to have an option of choosing flash size also,or some kind of autodetect.

Post by **usbbdm** » Mon Mar 16, 2009 1:12 pm

USB JTAG NT is highly configurable and the flash is always detected. For big flashes CFI is required to have more accurate programming.

slugworth · Post by **slugworth** » Tue Mar 17, 2009 2:17 pm

Sti5105 pins to eeprom from a vestel schematic showing the sti5105 pinouts.
On a magnum3300 and skyview1000 the eeprom is a 24lc64
The chip on the right is the sti5105

Post by **usbbdm** » Fri Mar 20, 2009 2:03 pm

I can now set my own trap. There is a little bit inconsistence. Once that is fixed then I can have USB JTAG NT support DCU3 (Sti5105).

Hanukkah · Post by **Hanukkah** » Thu Mar 26, 2009 3:44 pm

Will Sti5107 also be supported soon? I have an box with this cpu and cannot dump flash using Jkeys. Understanding that it is already DCU3 I've changed the start address to 40000000 but still would not dump. I get DCU peek error upon connection.

BTW the flash is a 32Mbit m28w320FS Top boot. I've read the datasheet and it says that is it has "Krypto" technology. I'm not sure if its "read protection" was activated, that is why I am having DCU peek errors.

slugworth · Post by **slugworth** » Thu Mar 26, 2009 4:16 pm

Jkeys dcu peek errors are almost always due to jtag wires too long or a bad ground between receiver and pc.Try adding another ground wire from receiver to pc case.

Post by **usbbdm** » Thu Mar 26, 2009 4:30 pm

The DCU3 has completely different instruction set.
Like We used to use "diff" and this command is not there for ST20 C1 (5105).
Due the the sudden move to N3 I might stop this development for DCU3 for a while.
What I have archieved is I can stop the CPU inject the trap code and detect the flash. The problem is that the trap code is not stable, some flags in the core crashed (or interrupted the trap). If that has passed then it will be quite simple to program the flash (a lot faster than the old USB JTAG that uses sprogram). But for now I might switch the task.

slugworth · Post by **slugworth** » Thu Mar 26, 2009 6:06 pm

I believe a "brain dead" receiver reacts differently.
I assume the receiver you play with is functioning normally.
I was after a dcu3 jtag to repair a dead receiver,which I finally did via the st20 toolset route.Dcu3 jtag once N3 takes over will just appeal to cloners or possible playing with receiver ram "on the fly" like I did with the 301.013 receiver with bev in the N1 days with jtango.I found the channel maps in ram and changed the service byte in ram so I could use dishnet firmware to watch bev which was unheard of at the time.I changed the service byte from 96 to 01 to watch bev channels but you had to refresh ram every 45 minutes to keep the channels from dropping off.Bev caught on and went to multiple channel maps in ram and moved them around,so a simple jtango script wouldn't work anymore to refresh ram.N2 put an end to that fun.

slugworth · Post by **slugworth** » Fri Mar 27, 2009 5:44 pm

Hanukkah wrote:Will Sti5107 also be supported soon? I have an box with this cpu and cannot dump flash using Jkeys. Understanding that it is already DCU3 I've changed the start address to 40000000 but still would not dump. I get DCU peek error upon connection.

For jkeys the uctap wiring seems better than the standard 9-11-13-15-19
You use 9-11-13-15-17 and tie pin19 high.

Post by **usbbdm** » Fri Mar 27, 2009 6:23 pm

pin 17 should be reset and is it needed to have pin 17 connected for JTAGing?

slugworth · Post by **slugworth** » Fri Mar 27, 2009 7:08 pm

For just dumping with jkeys pin17 works better.
For older dcu2 receivers use pin19.
I use the uctap connector wiring with uctap and with jkeys(dumping)

elkora · Post by **elkora** » Fri Mar 27, 2009 7:17 pm

slugworth wrote:For just dumping with jkeys pin17 works better.
For older dcu2 receivers use pin19.
I use the uctap connector wiring with uctap and with jkeys(dumping)

you dump de 311?

slugworth · Post by **slugworth** » Fri Mar 27, 2009 7:48 pm

elkora wrote:you dump de 311?

don't have one.

elkora · Post by **elkora** » Fri Mar 27, 2009 8:12 pm

but you think will work?

USB JTAG

Dcu3 jtag

options

eeprom

Update for DCU3 development.

peeks

response

uctap

dump

sti5517

Who is online