** Official JTAG Tool Thread **

Status
Not open for further replies.
There seems to be a problem with jaspers and 512 MB Nand. Jtag Tool crasches with a .Net error. I copied the whole folder to another drive with the same error. After that the program wont start until I delete the copied big nand file from the jtagtool folder. Is this known?
 
Jun 4, 2010
3,080
0
What size was the original NAND file you tried to use?
 

GlenC

Noob Account
Dec 11, 2002
3
0
uk
There is definately an issue with 16MB Jaspers Alt points SMC, it simply doesn't work.

I ended up creating my own and having to flash the first 50 blocks directly with nandpro.

Cheers

Glen.
 

coolshrimp

1
VIP Member
Nov 25, 2009
596
33
Canada
New Update thanks to the donators
Enjoy

**Like i said on official Tech-Modz Forum
**If No one Donates i will not be updating in the future.
 

freakyfabe

Noob Account
Mar 30, 2011
5
0
Just did my first JTAG!!! Shrimp, you are the MAN!!! I just wanted to thank you and ALL the people who had something to do with the JTAG Tool. Donation is on the way! :D Great thread BTW, it really helped me a lot. My biggest problem was my soldering. (I'm a noob) I'm getting better, but I still need practice. :p
 

mafia 5k

Senior Member
Oct 27, 2010
145
0
Massachusetts,USA
i need some help i am using the new jtag tool i am recieving an error unable to access freeboot.bin when i attempt to write fb.bin ... it allows me to write xell,read nand but it wont write fb.bin????

i tried on 2 computers as admin an 2 nandx flashers with no luck??????
 

stereorage

Junior Member
Jan 31, 2011
11
0
London, UK
Hey y'all, I'd just like to report 2 bugs:

1. as mentioned by some other posters, the jasper xell files do not work. i've had trouble with every jasper board, bigblock and 16mb. tried all the usual stuff, reinstalled, used a different computer etc. i think it's only a problem when using any non-original wiring method.
i was able to get it working by taking the xell file from the folder and using updatemysmc.

2. a smaller bug, but still quite troublesome. when creating freeboot and using the original nand directly from a CD (or any other read-only source), the program will crash and won't let you re-open it.
This is because jtag tool copies the NAND file you browse for into the program files directory in the jtag tool folder. The problem is that it also copies the file attributes (i.e. the read-only attribute). Because of this, jtag tool is unable to access the file and crashes. Easily resolved by changing the attribute of nand.bin in the jtag tool folder by removing read-only.
this is the only solution and reinstalling does not work.

Hope that helps with the next revision (hopefully it will incorporate the glitch hack) :)
 

QcMarque

Senior Member
Jan 20, 2005
104
0
Seattle, WA
www.jboxmods.com
So with this version (as with various other versions) I'm getting an error saying "be sure you've supplied an unencrypted extended.bin" well, I haven't supplied anything, and I've reinstalled a few times, and am using the same pc I always do for jtags. Seems to just be on my BB jasper... the freeboot image works just fine (minus the occasional graphic/audio glitch + freeze at the M$ logo).

Anyone seen this and have a solution? Ideas as to why my jasper is freezing and glitching? I'm using the transistor jtag method w/ aud_clamp (same as I always have since it came out)
 
Last edited:

stereorage

Junior Member
Jan 31, 2011
11
0
London, UK
So with this version (as with various other versions) I'm getting an error saying "be sure you've supplied an unencrypted extended.bin" well, I haven't supplied anything, and I've reinstalled a few times, and am using the same pc I always do for jtags. Seems to just be on my BB jasper... the freeboot image works just fine (minus the occasional graphic/audio glitch + freeze at the M$ logo).

Anyone seen this and have a solution? Ideas as to why my jasper is freezing and glitching? I'm using the transistor jtag method w/ aud_clamp (same as I always have since it came out)
Must be the freeboot image that's causing the glitching. If you were using any other motherboard I would suspect the GPU is faulty, but since it's a Jasper it's highly unlikely.

Did you check for any bad blocks and remap them accordingly? That seems to be the main reason this happens, at least in my experience.
 

QcMarque

Senior Member
Jan 20, 2005
104
0
Seattle, WA
www.jboxmods.com
Must be the freeboot image that's causing the glitching. If you were using any other motherboard I would suspect the GPU is faulty, but since it's a Jasper it's highly unlikely.

Did you check for any bad blocks and remap them accordingly? That seems to be the main reason this happens, at least in my experience.
All of my dumps from my system have no bad blocks and no ecc errors. This just is sooo odd. I've done tons of systems and never had an issue like this (even with other systems where jtag tool said to use an unencrypted extended.bin).

I may rebuild my freeboot image using another tool (or just the command prompt) and see if that clears up the random issues (unless anyone has other thoughts? could it make a difference if I used aud_clamp and open_tray instead of just aud_clamp?)
 

[AD]

Staff member
Troll Eating Dogs
Dec 8, 2002
815
43
Bolton, Lancs. UK
Looks awesome Coolshrimp :)

-=AD=-
 

82ross

Full Member
Dec 7, 2002
46
0
Liverpool
Looks nice coolshrimp. New features are great, refreshed interface is a great bonus.
 

coolshrimp

1
VIP Member
Nov 25, 2009
596
33
Canada
Hey y'all, I'd just like to report 2 bugs:

1. as mentioned by some other posters, the jasper xell files do not work. i've had trouble with every jasper board, bigblock and 16mb. tried all the usual stuff, reinstalled, used a different computer etc. i think it's only a problem when using any non-original wiring method.
i was able to get it working by taking the xell file from the folder and using updatemysmc.

2. a smaller bug, but still quite troublesome. when creating freeboot and using the original nand directly from a CD (or any other read-only source), the program will crash and won't let you re-open it.
This is because jtag tool copies the NAND file you browse for into the program files directory in the jtag tool folder. The problem is that it also copies the file attributes (i.e. the read-only attribute). Because of this, jtag tool is unable to access the file and crashes. Easily resolved by changing the attribute of nand.bin in the jtag tool folder by removing read-only.
this is the only solution and reinstalling does not work.

Hope that helps with the next revision (hopefully it will incorporate the glitch hack) :)

thanks the jasper issue has been fixed.

as for the read only issue im looking into it.
 
Well I get this .NET error with a bigblock (512MB Jasper box)

Code:
Informationen über das Aufrufen von JIT-Debuggen
anstelle dieses Dialogfelds finden Sie am Ende dieser Meldung.

************** Ausnahmetext **************
System.UnauthorizedAccessException: Der Zugriff auf den Pfad "c:\Program Files (x86)\Jtag Tool\Nand.bin" wurde verweigert.
   bei System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   bei System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
   bei System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
   bei System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
   bei PackageIO.Reader..ctor(String Package, Endian EndianType, Int64 Position)
   bei Jtag_Tool.JtagTool.ConsoleDetect()
   bei Jtag_Tool.JtagTool.FBCreateButton_Click(Object sender, EventArgs e)
   bei System.Windows.Forms.Control.OnClick(EventArgs e)
   bei System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   bei System.Windows.Forms.Control.WndProc(Message& m)
   bei System.Windows.Forms.ButtonBase.WndProc(Message& m)
   bei System.Windows.Forms.Button.WndProc(Message& m)
   bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Geladene Assemblys **************
mscorlib
    Assembly-Version: 2.0.0.0.
    Win32-Version: 2.0.50727.5448 (Win7SP1GDR.050727-5400).
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll.
----------------------------------------
Jtag Tool
    Assembly-Version: 1.0.0.0.
    Win32-Version: 1.0.0.0.
    CodeBase: file:///C:/Program%20Files%20(x86)/Jtag%20Tool/Jtag%20Tool.exe.
----------------------------------------
Microsoft.VisualBasic
    Assembly-Version: 8.0.0.0.
    Win32-Version: 8.0.50727.5420 (Win7SP1.050727-5400).
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll.
----------------------------------------
System
    Assembly-Version: 2.0.0.0.
    Win32-Version: 2.0.50727.5447 (Win7SP1GDR.050727-5400).
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll.
----------------------------------------
System.Windows.Forms
    Assembly-Version: 2.0.0.0.
    Win32-Version: 2.0.50727.5446 (Win7SP1GDR.050727-5400).
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll.
----------------------------------------
System.Drawing
    Assembly-Version: 2.0.0.0.
    Win32-Version: 2.0.50727.5420 (Win7SP1.050727-5400).
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll.
----------------------------------------
System.Runtime.Remoting
    Assembly-Version: 2.0.0.0.
    Win32-Version: 2.0.50727.5420 (Win7SP1.050727-5400).
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll.
----------------------------------------
DevComponents.DotNetBar2
    Assembly-Version: 9.0.0.0.
    Win32-Version: 9.0.0.0.
    CodeBase: file:///C:/Program%20Files%20(x86)/Jtag%20Tool/DevComponents.DotNetBar2.DLL.
----------------------------------------
Accessibility
    Assembly-Version: 2.0.0.0.
    Win32-Version: 2.0.50727.4927 (NetFXspW7.050727-4900).
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll.
----------------------------------------
System.Configuration
    Assembly-Version: 2.0.0.0.
    Win32-Version: 2.0.50727.5420 (Win7SP1.050727-5400).
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll.
----------------------------------------
System.Xml
    Assembly-Version: 2.0.0.0.
    Win32-Version: 2.0.50727.5420 (Win7SP1.050727-5400).
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll.
----------------------------------------
PackageIO
    Assembly-Version: 0.1.7.0.
    Win32-Version: 0.1.7.0.
    CodeBase: file:///C:/Program%20Files%20(x86)/Jtag%20Tool/PackageIO.DLL.
----------------------------------------
mscorlib.resources
    Assembly-Version: 2.0.0.0.
    Win32-Version: 2.0.50727.5448 (Win7SP1GDR.050727-5400).
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll.
----------------------------------------
System.Windows.Forms.resources
    Assembly-Version: 2.0.0.0.
    Win32-Version: 2.0.50727.5420 (Win7SP1.050727-5400).
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms.resources/2.0.0.0_de_b77a5c561934e089/System.Windows.Forms.resources.dll.
----------------------------------------

************** JIT-Debuggen **************
Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der
Konfigurationsdatei der Anwendung oder des Computers
(machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden.
Die Anwendung muss mit aktiviertem Debuggen kompiliert werden.

Zum Beispiel:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten
Ausnahmen an den JIT-Debugger gesendet, der auf dem
Computer registriert ist, und nicht in diesem Dialogfeld behandelt.
The smaller ones (16MB) work OK.
Can anyone help here?
 
Status
Not open for further replies.