USB SPI Flasher with PIC18F2455 - now with source and binaries

[kipper2k]

 One more thing, should i use the Picxboot and picxflash files dated sept 19th or Sept 22nd, or does it matter ?

[cory1492]

Use the newest ones I put up (git sept 22 IIRC), supports bootloader flashing entry via python script (and exit via picdem despite that it gives error) and matches the pinout in the first post. Once you have the bootloader flashed, you can put aside the pic programmer entirely.

ernestino: wire size/AWG and length from 360 to PIC? They aren't all different lengths right? Good and solid connections? The bootloader just jumps directly into the main app if the right pin or POR condition isn't set, not likely the problem if USB is detecting fine.

You can also read flash in chunks and combine the files later... something like

Code:

nandpro.exe usb: -r16 dump1.bin 0 100
nandpro.exe usb: -r16 dump2.bin 100 100
nandpro.exe usb: -r16 dump3.bin 200 100
nandpro.exe usb: -r16 dump4.bin 300 100
copy /b dump1.bin + dump2.bin + dump3.bin + dump4.bin fulldump.bin

Though you'll have to check the syntax, for some reason I never know for sure where I should be subtracting 1 with nandpro.

[ernestino]

It must been something wrong with fuses I used when programming PIC with Kitsrus K149 programmer.

I decide to make ART2003 programmer and programed PIC again, then PICFLASH.hex with PICDEM.
It´s working now .

It looks like:

[iLLNESS]

ok i've been following this post... but i got confused when people were saying they were unable to flash 256/512MB nands... is this true?

if it is, is there ANY solution to flashing them?

[cory1492]

ernestino: nice looking gadget you built there, congrats on fixing up the issue. I'm still working with a breadboard

ok i've been following this post... but i got confused when people were saying they were unable to flash 256/512MB nands... is this true?

if it is, is there ANY solution to flashing them?

Read back a bit, I'm pretty sure I made it quite clear where things stand on this right now:
http://www.xboxhacker.net/index.php?topic=12306.msg87884#msg87884

On that note, if anyone wants to try and guinea pig (aka: test) a 256/512 solution I believe I've found the issue (it's not terribly complicated when you consider large block nands are treated like small block nands by nandpro - but I also spent the time today to verify this is indeed the problem/missing bit by looking through Tiros' hex for the LPC.) I've already left it for one person, but it's a friend of a friend kind of a situation that could prove to have really long lead times to results. Testing would be very basic, on the order of extracting, writing and dumping one or two 128K(+spare) blocks; as well, requires being able to correct a bad block write via lpt or other method if things don't work as expected. PM if able and willing, hopefully there will be a solution for 256/512 sooner rather than later.

[federicobj]

cory:
i have no problem on test your "test program" on mi jasper 512...then i will share mi experience about it...thanks, federico

[kipper2k]

Like this ?

 I built my flashing circuit and it would not recognise it in windows.  I built it again (using fresh components) and i am still having problems (Win XP).  Device manager shows Custom USB Devices "Microchip Custom USB Device" but the device will not start (Code 10). I have tried auto and manual installation of the drivers to no avail.

 To reduce the possibility of wiring errors i used the above schematic to just get the USB device recognised but still no go.

 I am using a default 12Mhz resonator (2 pin resonator with a 22uf cap from each leg going to ground) I used the picxboot.hex boot file programmed onto the pic 18f2455using winpic800 (art2003, osc divided by 3 (12mhz input) and lvp checked. other settings checked are CCP2MX, LVP, MCRLE, STVREN. i did do a verify after i programmed the pic so i am not sure what is going on.  Is there any supporting software supposed to be installed, ie dotnet etc.

any help  appreciated

thanks

[iNsAiNoNe]

kipper2k...after you get it to recognize it as the Microchip Custom USB Device...did you try to open PDFSUSB.exe and flash the pic with picflash.hex?   after it programs it should show differently in device manager...or are you saying you can't get the microchip custom usb device to start at all? (!) <--showing a ! in device manager?

[kipper2k]

kipper2k...after you get it to recognize it as the Microchip Custom USB Device...did you try to open PDFSUSB.exe and flash the pic with picflash.hex?   after it programs it should show differently in device manager...or are you saying you can't get the microchip custom usb device to start at all? (!) <--showing a ! in device manager?

 thanks for the reply, i tried to open pdfsusb.exe and no device shows in the drop down window. 
- yah, the device has an exclamation mark on the device showing device error. I'll try in a different computer to see if it gets recognised there, other than that i dont know.  I built the circuit on a breadboard so its not too bad to play with. The usb cable is about 6" (15cm) long so i dont think thats an issue.  One thing i notice it takes a while for the "USB device not recognised" message to popup and there is no usb connect/disconnect sound

[entropy1911]

Hi. 

I've been reading through this and a couple of other similar topics.  I am just wondering why are the J2B pins necessary.  They are outside of the normal spi spec.  From what I have gathered these have something to do with the remote power on and ejecting the disk. although the pin labeled xx, I still have no idea.  So my question I guess is, what does xx do, and why is it necessary to have remote power on and eject.

Thanks

[cory1492]

ej when held shortly ejects drive, but long forces power off. Between ej and xx a state is created which I presume allows master of the SPI bus externally. The KIOSK pin is used for remote power on. Sorry I have nothing more technical about this, perhaps one of those who discovered the full purpose of these pins can enlighten us both further.

[dpacro]

I just want to thank you guy for this fast method of dumping the xbox 360 nand.

I have used it and it is working pretty well with 24mhz clock and the device takes less then 5 mins to dump the nand.

Perfect device ! it helps me a lot .

Keep the good work going !

Peace.

[droe]

  i cantn get this working,i build a breadboard ,pic18f2455 i/sp,using 3 leg 4mhz res.,using cory's files from git.,,picboot flashed with my willem pro 2 ,with lvp,gets regonized by windows ,custom usb devices(microchip custom usb device),start picdem,picdem fs usb boot,i can choose my device load picflash hex ,program flash ,but fails to reset,if i put jumper on and pull out usb from pc and then reconnect usb ,pc crashes and restarts.
other pcs say unknown devices
why cant i flash the picflash hex ,should i try with the 12v on mlcr or something or is it not needed with lvp setting,or no lvp ,been thru this many times but cant figure out what i am doing wrong , i want to use it to extract a cpukey and dvdkey from an xenen mobo and flash xell to it but it wont work ,cant i flash something on the pic without bootloader so i can read my nand.
the lpt cable wasnt working in first place for me so i thought try this out but i am out of luck
can anyone point me in right direction cos it driving me bonkers is the 4mhz the problem i edited hex with winpic

[cory1492]

You're using the latest ones from the 22nd right? With picdem and this project it always says "failed to reset" even when reset works, you can tell it works because the microchip device disconnects and the nand access will connect shortly after (or at least it should.)

You should be fine with 4MHz, and the fact picdem recognizes and flashes the chip means you set the osc. correctly initially. Make sure you have all the connections done right, especially the pull up resistor on mclr (this one got me for a while with random weirdness), the pull down on RB5 if using LVP, and the cap on VUSB.

[droe]

thanks for the reply cory
i using the latest i am sure,i hear  the windows sound every i connect dissconnect the usb,
i am pretty sure i have every thing wired up correctly,to flash picflash.hex the breadboard doesnt need to
be connected to the  xbox right,it should work without right? and afterwards i connect usb board and  i can read nand with nandpro20a,bootloader should launch automatically?or do i have to launch it with a python script .breadboard is now using mchpusb drivers in order to flash the picflash.hex
i will triple check everything tomorrow

[adcurtin]

This is a little off topic, but not really.

Would it be possible to do the same thing, but using an arduino instead of a pic? I know the code would have to be rewritten for it.
I have a couple arduinos and it would be much more convenient to be able to use that.

Thanks.

[cory1492]

droe: after you have picflash.hex flashed, the only way you'll land in the bootloader again is if you use the pin for bootloader before power or the python script option that causes it to reset to bootloader. As I've said before, without that pin put to a certain state ALL the bootloader does is jump directly to the program/user code (in this case picflash.hex entry/_start function.)

adcurtin: that's the great thing about these microcontroller projects, if you can code it - it will work. There is no reason why it couldn't work on an arduino.

edit:/ with many thanks to federicobj for testing on a jasper 512M, I believe the jasper big block issue and nandpro2b ARM detect issues (but not the underlying reason for 2b having an ARM check?) are now both solved. I could still use a second test though, as federicobj is not able to get their original dump to function on the console through lpt or usb.

[fatjoe]

I have been trying to build art2003 programmer with no luck.. I have tried to rebuild it couple of times but it still doesnt work.. Could it be that my laptop LPT port doesnt support pic programming? It couldnt handle nand dumping throught LPT.. I'll try with different PC at next weekend but it would be nice to hear some thoughts..

[maximilian0017]

Could it be that my laptop LPT port doesnt support pic programming? It couldnt handle nand dumping throught LPT.. I'll try with different PC at next weekend but it would be nice to hear some thoughts..

Probably the same problem for both LPT and PIC programming, pc will 90% work if you built the programmer correctly.

[fatjoe]

Thanks for quick answer.. Im quite sure that i built it correctly.. Ill test programmer on another pc later and then we will see