Print

[Mhawk134]

No problem man.  

Quick note for everyone out there if it doesn't work the first time and you have checked your wires, try a different pc because not all of them are the same and some are stubborn, also change different modes, like AT, EPP AND EPC in your bios settings.

Hawk

[majinsoftware]

Also check on the port its self for the numbering, some can have the numbers backwards. And if your parallel port is 3.3V then you just get errors with the 100ohm resistors.

And finally the older the computer is the more likely the parallel port will work.
Iv got a parallel port to usb adapter ordered so I try that out when it arrives on tuesday, Only cost me $3 so no loss if it doesn't.

The easyest wire iv found to use is solid core network cable.
Just get your soldering iron heat up the back of the board where your putting the wire and you can push it through the hole, Then trim it and add some more solder.

[M37]

I've made a few backups but so far none are 100% the same

when reading I get
Error: 258 reading block 16F

when compared in winhex this is very few differences that all look something like

 5EB712:   C0   E0
 5EB722:   E0   C0
 5EB901:   C0   E0
 5EB908:   C0   E0
 5EB918:   C0   E0

Does this even matter? all the backups open in 360FlashTool so they are somewhat valid.

[Hellzone]

So what about PCI cards that have parallel ports ? I feel like picking one up tomorrow

[cory1492]

QUOTE(M37 @ Aug 22 2009, 09:24 PM)

I've made a few backups but so far none are 100% the same

when reading I get
Error: 258 reading block 16F

when compared in winhex this is very few differences that all look something like

 5EB712:   C0   E0
 5EB722:   E0   C0
 5EB901:   C0   E0
 5EB908:   C0   E0
 5EB918:   C0   E0

Does this even matter? all the backups open in 360FlashTool so they are somewhat valid.

Block 0x16F goes from 0x5E9E00 to 0x5EE000, as far as I can tell from tmbinc's comments error 258 is due to a 'bad block' (normal for NAND, though dumping software usually interprets such an error internally and dumps the equivalent of an erased block instead) - so long as your diffs all fall in the range it reports such a  bad block error in then you should be fine.

Keep in mind, using a pre-built image from someone else with bad blocks in it could affect your ability to restore to original later or may even have issues because of an unreliable block where payload data is. At the same time, having bad blocks and flashing a pre-built image that has none could equally cause issues if the bad block is 'reset' (the spare area contains a bit that the software uses to tell a bad block - if it really is bad it may become impossible to set that bit again.) All in all bad blocks are a good thing (they stop NAND from being fully faulty when just a page is unreliable) but I'm not sure how well they are handled by this software considering no one seems to know exactly what errors mean what.

BTW, for 16M to 64M NAND each block has 32 pages, and each page has 528bytes of data to it (made of 512 data + 16 spare), in case you or anyone else wants to calculate it (0x16F*0d528*0d32).

[majinsoftware]

QUOTE(Hellzone @ Aug 23 2009, 05:42 AM)

So what about PCI cards that have parallel ports ? I feel like picking one up tomorrow

When you get one post back your resaults.
Should work if its in the address range nandpro checks.

[Hellzone]

Correct me if im wrong but once im done reading it, cant i flash xell ?

Im referring to this btw http://www.logic-sunrise.com/forums/topic/...e-without-chip/

[Hellzone]

Sorry for the DP

Forgot to show you my wireing.... i cant get close ups sadly because my 7.1mp cam wont focus like it should ..


"Note the FirstGen heat sink is getting abused" I bought falcon heatsinks for this box   , no need on making in mine and then having it break  




I think ill cut a hole in the back of the metal and mount it.

[majinsoftware]

Personally id move the wires for the jtag hack to the go up by the hdd plug.
You dont want the heat of the gpu heatsink to melt the plastic casing and short out.

[Hellzone]

QUOTE(majinsoftware @ Aug 23 2009, 10:13 AM)

Personally id move the wires for the jtag hack to the go up by the hdd plug.
You dont want the heat of the gpu heatsink to melt the plastic casing and short out.

Thats the way they are now.
Btw this is the card that im getting tomorrow.
Made by Inland

http://www.frys.com/product/5850773?site=s...CH:MAIN_RSLT_PG
Cheep but hopefully it will work, ill let you know.

[utar]

QUOTE(M37 @ Aug 23 2009, 04:24 AM)

I've made a few backups but so far none are 100% the same

when reading I get
Error: 258 reading block 16F

when compared in winhex this is very few differences that all look something like

 5EB712:   C0   E0
 5EB722:   E0   C0
 5EB901:   C0   E0
 5EB908:   C0   E0
 5EB918:   C0   E0

Does this even matter? all the backups open in 360FlashTool so they are somewhat valid.

I had two 250 errors during my reading and there was a one byte difference between the two dumps I made.  I decided to risk it and the reflash worked fine.  



Utar

[utar]

One other thing - I see there is data in the hacked firmware in those locations.  My errors weren't at the start so it may well be risky you attempting a reflash.


Utar

[Kieranl]

can somebody either post here or pm me a link to a successfull nand dump log? i just want to see exactly what it should look like as im somewhat concerned mine isnt working properly thanks

[ToBbErT]

I will be very gratefull if someone posted a simple tutorial on how to connect the LPC2148 Olimex USB header board. Tia!

[Martinchris23]

QUOTE(ToBbErT @ Aug 23 2009, 05:24 PM)

I will be very gratefull if someone posted a simple tutorial on how to connect the LPC2148 Olimex USB header board. Tia!

Hi- from the original post:

QUOTE

USB:
LPC2148 Olimex USB header board
High performance 16MB/2Mins
LibUsb driver

Straightforward enough - here's a link to the product / pinout:

http://www.olimex.co.../lpc-h2148.html

QUOTE

Seven connections must be made from MAINBRD to the HW device interface.
MAINBRD connects as specified to either Olimex board, or a PC printer port.

ArmLpc Olimex LPT MAINBRD

SS EXT1-3 DB25.1 J1D2.2
MISO EXT1-6 DB25.11 J1D2.4
P0.28 EXT2-1 DB25.16 J2B1.6
GND EXT1-26 DB25.18 J1D2.6 or J2B1.12
MOSI EXT1-7 DB25.14 J1D2.1
SCK EXT1-5 DB25.2 J1D2.3
P0.29 EXT2-2 DB25.17 J2B1.5

Ok, this is a table but looks confusing due to forum text layout - strip out the stuff we don't need and use the LPT pinout as a reference as well as the LPT mainboard pinout (http://www.olimex.com/dev/pdf/lpc-h2148-pins.pdf). Instead of wiring from the 360 board to the LPT plug, you're going from the 360 board to the USB device.

So replace :

Pin 1 on LPT plug with EXT1-3 on USB Device
Pin 11 on LPT plug with EXT1-6 on USB Device
Pin 16 on LPT plug with EXT2-1 on USB Device
Pin 18 on LPT plug with EXT1-26 on USB Device
Pin 14 on LPT plug with EXT1-7 on USB Device
Pin 2 on LPT plug with EXT1-5 on USB Device
Pin 17 on LPT plug with EXT2-2 on USB Device

So the wiring to the 360 mainboard is exactly the same. The 3x330ohm bridges won't change either since they're needed to fire up the Xell (short them out or remove them and you'll get error 79).

QUOTE

USB Install:
Flash the .hex file to the LPC2148.
Connect LPC2148 to computer USB.
Point "found new hardware" to the "custom.inf"
Windows reports: "Your new hardware is ready to use"

As above - your new device should be accessible via nandpro as an lpt device.