jtag strong 6410 ?

JTAG on Dish Receivers.
postit
Junior Member
Posts: 28
Joined: Mon Feb 20, 2012 11:17 am

Post by postit »

yes I find the PDF, but I understand how much has not corespond lines in the flash file of usbjtag, eg can you explain each line of this one:
<id1> 0x1 </ id1>
<id2> 0x227E </ id2>
<name> S29GL320 </ name>
<size> 0x400000 </ size>
<protocol> 0 </ protocol>
<block>
<secnum> 8 </ secnum>
<secsize> 0x2000 </ secsize>
<secnum> 63 </ secnum>
<secsize> 0x10000 </ secsize>
usbbdm
Junior Member
Posts: 8962
Joined: Mon Jul 18, 2005 9:33 pm

Post by usbbdm »

postit wrote:yes I find the PDF, but I understand how much has not corespond lines in the flash file of usbjtag, eg can you explain each line of this one:
<id1> 0x1 </ id1>
<id2> 0x227E </ id2>
<name> S29GL320 </ name>
<size> 0x400000 </ size>
<protocol> 0 </ protocol>
<block>
<secnum> 8 </ secnum>
<secsize> 0x2000 </ secsize>
<secnum> 63 </ secnum>
<secsize> 0x10000 </ secsize>
There is no need to add to flash. This flash support CFI and without any XML file it will still work. The problem for you is the TRAP ON for ST40. Have you tried to remove the reset pin and test again?
CAPONE
Junior Member
Posts: 5011
Joined: Sat Dec 27, 2008 3:25 pm

Post by CAPONE »

postit wrote:yes I find the PDF, but I understand how much has not corespond lines in the flash file of usbjtag, eg can you explain each line of this one:<id1> 0x1 </ id1>
<id2> 0x227E </ id2>
<name> S29GL320 </ name>
<size> 0x400000 </ size>
<protocol> 0 </ protocol>
<block>
<secnum> 8 </ secnum>
<secsize> 0x2000 </ secsize>
<secnum> 63 </ secnum>
<secsize> 0x10000 </ secsize>
There is a Small Tutorial by USBBDM That teaches you About that.
usbbdm
Junior Member
Posts: 8962
Joined: Mon Jul 18, 2005 9:33 pm

Post by usbbdm »

For all new flash chip and chips larger than 2MB, they all support CFI and there is no need to manually enter the flash.xml. Unless CFI gives the wrong data then we might need to hack in the flash.xml.
Edit flash.xml is only useful for smaller chip like 512KB flash on some models of DCT2224.
postit
Junior Member
Posts: 28
Joined: Mon Feb 20, 2012 11:17 am

Post by postit »

Ok thank you for your answer, to answer a yes Usbbdm I try and reset by removing the negative no result
usbbdm
Junior Member
Posts: 8962
Joined: Mon Jul 18, 2005 9:33 pm

Post by usbbdm »

postit wrote:Ok thank you for your answer, to answer a yes Usbbdm I try and reset by removing the negative no result
Maybe I have to have a box in hand to add support to it.
postit
Junior Member
Posts: 28
Joined: Mon Feb 20, 2012 11:17 am

Post by postit »

Bonjour, pouvez vous quand meme m'expliquer en detaille chaque ligne de parametre en prenant pour exemple cet config
Merci

<id1> 0x1 </ id1>
<id2> 0x227E </ id2>
<name> S29GL320 </ name>
<size> 0x400000 </ size>
<protocol> 0 </ protocol>
<block>
<secnum> 8 </ secnum>
<secsize> 0x2000 </ secsize>
<secnum> 63 </ secnum>
<secsize> 0x10000 </ secsize>
CAPONE
Junior Member
Posts: 5011
Joined: Sat Dec 27, 2008 3:25 pm

Post by CAPONE »

postit wrote:Bonjour, pouvez vous quand meme m'expliquer en detaille chaque ligne de parametre en prenant pour exemple cet config
Merci

<id1> 0x1 </ id1>
<id2> 0x227E </ id2>
<name> S29GL320 </ name>
<size> 0x400000 </ size>
<protocol> 0 </ protocol>
<block>
<secnum> 8 </ secnum>
<secsize> 0x2000 </ secsize>
<secnum> 63 </ secnum>
<secsize> 0x10000 </ secsize>
READ HERE

viewtopic.php?t=643&highlight=flash+flash.def
postit
Junior Member
Posts: 28
Joined: Mon Feb 20, 2012 11:17 am

Post by postit »

Nothing to do no result, usbjtag not yet ready for the st40, especially the type of memory in the receiver is protect by a password
usbbdm
Junior Member
Posts: 8962
Joined: Mon Jul 18, 2005 9:33 pm

Post by usbbdm »

postit wrote:Nothing to do no result, usbjtag not yet ready for the st40, especially the type of memory in the receiver is protect by a password
I have only two targets. One is Sonicview (Sti7100) and the other is Sti5202 target.
On Sonicview the detect is reliable and works fine.
On Sti5202 the reset pin is not working at all. However, if the target has the good boot, the detect is reliable with a few clicks.
If the boot is erased it is very difficult to get TRAP ON. I think this is related the timing of reset. I can still get TRAP ON and fix it with a lot of tries(Sometime hit detect and power on at the SAME time!!). I will see if I can add a circuit to force the reset to work and then adjust timing. I might need to add a timing parameter in the xml to make it working reliable.

I have an independent person from other site and he made the NT work on his ST40 target (http://www.avi-plus.com/). Other targets are not tested. Especially your target which is reported as STi5202 but it is not.

Sonicview was donated to me for development ( I will return to him in a few weeks). If you need your target to be supported consider donate the device and I can add this support.

ST40 is very different than the rest of the target and I have only get started. Flash is not a problem at all. So do not focus on which flash it is. CFI will fix all the large flash issue.
usbbdm
Junior Member
Posts: 8962
Joined: Mon Jul 18, 2005 9:33 pm

Post by usbbdm »

postit wrote:Nothing to do no result, usbjtag not yet ready for the st40, especially the type of memory in the receiver is protect by a password
One way to test if reset pin is working for you is this.
1. Power on the box normally. (With JTAG connected and software running).
2. Check to see if the box is booting up normally.
3. If yes type command "reset 10" (or reset 20,30 in case reset does not trigger).

If you see the box resets, then the reset pin works for you, adjust the timing of software should work in the future for your target.
If you do not see the box reset then it is similar to the case I have now for STi5202. I am looking to add a small driver to it and then brick the box to make the detect easier.
Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests