USBJtag .39 Stuck
-
- Junior Member
- Posts: 33
- Joined: Mon May 10, 2010 7:50 pm
USBJtag .39 Stuck
Hi USBBDM,
Why it get stuck at eraser start. In the past -- I use the old USBJTAG with the old debrick command line -- So simple and so easy -- why not have it in the new usbjtag nt .39 -- Can you make a script to to the debrick instead of tap c | tap a ...
What is a easy and sreaight forward to debrick 5101 please.
Thank you
Why it get stuck at eraser start. In the past -- I use the old USBJTAG with the old debrick command line -- So simple and so easy -- why not have it in the new usbjtag nt .39 -- Can you make a script to to the debrick instead of tap c | tap a ...
What is a easy and sreaight forward to debrick 5101 please.
Thank you
-
- Junior Member
- Posts: 5011
- Joined: Sat Dec 27, 2008 3:25 pm
If you have used the Old USBJTAG Which is OLD Then How is it you don't know How to make your Own Scripts? You can make your own scripts to suite your needs.number1001 wrote:Hi USBBDM,
Why it get stuck at eraser start. In the past -- I use the old USBJTAG with the old debrick command line -- So simple and so easy -- why not have it in the new usbjtag nt .39 -- Can you make a script to to the debrick instead of tap c | tap a ...
What is a easy and sreaight forward to debrick 5101 please.
Thank you
-
- Junior Member
- Posts: 8981
- Joined: Mon Jul 18, 2005 9:33 pm
USB JTAG NT is much powerful in terms of debrick. The "tap" command does not exist in old USB JTAG. It is very useful.
Please tell me what command you use to debrick on old command and there is 100% equivalent command in NT. Beside the NT can adjust the JTAG clock and make the debrick more reliable.
If you use the script to debrick, it was made for 3.3V method. Are you using 3.3V? If not do not use that script.
Which target you are using? I can make more debrick script if that helps.
Please tell me what command you use to debrick on old command and there is 100% equivalent command in NT. Beside the NT can adjust the JTAG clock and make the debrick more reliable.
If you use the script to debrick, it was made for 3.3V method. Are you using 3.3V? If not do not use that script.
Which target you are using? I can make more debrick script if that helps.
-
- Junior Member
- Posts: 161
- Joined: Thu Jun 28, 2007 6:48 pm
-
- Junior Member
- Posts: 33
- Joined: Mon May 10, 2010 7:50 pm
Okay -- Thank you for your advice -- Pls be patient with me because I have this new USBJtag NT and this is my first time to use it.
I used the command line 'debrick' to debrick the 5101 ( on the old usbjtag -- red one -- No problem whatsoever -- Very easy to do).
I did not know exactly what happened but when I tried to load .39 several times -- I guess it get confused or whatever -- The 5101 bricked.
My question is what is in the debrick command (eg ldram | image0 | program image0 | program image1 -- or what?) -- I have tried to use these commands on ver .39 -- it get stuck.
Any idea ?
I used the command line 'debrick' to debrick the 5101 ( on the old usbjtag -- red one -- No problem whatsoever -- Very easy to do).
I did not know exactly what happened but when I tried to load .39 several times -- I guess it get confused or whatever -- The 5101 bricked.
My question is what is in the debrick command (eg ldram | image0 | program image0 | program image1 -- or what?) -- I have tried to use these commands on ver .39 -- it get stuck.
Any idea ?
-
- Junior Member
- Posts: 33
- Joined: Mon May 10, 2010 7:50 pm
Hi USBBDM
If you use the script to debrick, it was made for 3.3V method. Are you using 3.3V? If not do not use that script.
>> I did not use this method 3.3V _ I just simply use 'debrick' command line on the old USBjtag.
Which target you are using? I can make more debrick script if that helps.
>>> SB5101
If you use the script to debrick, it was made for 3.3V method. Are you using 3.3V? If not do not use that script.
>> I did not use this method 3.3V _ I just simply use 'debrick' command line on the old USBjtag.
Which target you are using? I can make more debrick script if that helps.
>>> SB5101
-
- Junior Member
- Posts: 8981
- Joined: Mon Jul 18, 2005 9:33 pm
"debrick" is not the command but a script I believe. Then copy the same "debrick.usp" to new script directory. I will be in chat and help you out(logmein prefered).number1001 wrote:Hi USBBDM
If you use the script to debrick, it was made for 3.3V method. Are you using 3.3V? If not do not use that script.
>> I did not use this method 3.3V _ I just simply use 'debrick' command line on the old USBjtag.
Which target you are using? I can make more debrick script if that helps.
>>> SB5101
[Edit]
Sorry, I found the "debrick" command. It just set a flag. The tap will do the same work. I am in chat and if you need help go to chat. Check your PM.
-
- Junior Member
- Posts: 8981
- Joined: Mon Jul 18, 2005 9:33 pm
If you can detect flash you can usenumber1001 wrote:Hi USBBDM
If you use the script to debrick, it was made for 3.3V method. Are you using 3.3V? If not do not use that script.
>> I did not use this method 3.3V _ I just simply use 'debrick' command line on the old USBjtag.
Which target you are using? I can make more debrick script if that helps.
>>> SB5101
"erase boot"
"sprogram boot"
"cmpram boot"
If all OK. Then power off on the modem and use normal command to program the modem. It will not stuck.
The reason it gets stuck is the boot is not programmed properly. Without boot you need.
1. Program the good boot to use fast programming.
2. Use poke command in http://www.usbjtag.com/jtagdevices/sb5100.php to allow fast programming.
Otherwise it will pause at the "erase".
-
- Junior Member
- Posts: 33
- Joined: Mon May 10, 2010 7:50 pm
-
- Junior Member
- Posts: 33
- Joined: Mon May 10, 2010 7:50 pm
-
- Junior Member
- Posts: 8981
- Joined: Mon Jul 18, 2005 9:33 pm
One debrick sb5101 script.
This script will fix your problem.
You have load the haxomatic to the boot area. You can still detect the flash. So this will help you to slow program the boot with DMA mode.
Some time the debrick needs the non-DMA mode. Try this and see if it works for you.
I encourage everyone try to use script to do the routine work. Any task can be achieved with script.
You have load the haxomatic to the boot area. You can still detect the flash. So this will help you to slow program the boot with DMA mode.
Some time the debrick needs the non-DMA mode. Try this and see if it works for you.
I encourage everyone try to use script to do the routine work. Any task can be achieved with script.
You do not have the required permissions to view the files attached to this post.
-
- Junior Member
- Posts: 161
- Joined: Thu Jun 28, 2007 6:48 pm
Who is online
Users browsing this forum: No registered users and 5 guests