USB SPI Flasher with PIC18F2455 - now with source and binaries

[jhonnyp0lak]

Sweet, sweet, well ill be testing it out on my xenon maybe tonight, so ...... we'll see how that goes When i ran it in nandpro last night it said it detected the USb device but couldnt find the flash controller (because i didnt hook up the console), so hopefully this means she's hunky dory

Anyways, now all we do is play the waiting game for the XBRebooter to come out with 256 and 512mb compatible nands

[iLLNESS]

also,

i just figured id throw this out there for anyone who can't figure it out..

i threw together a quick batch file to read your nand a bunch of times with a slight delay between reads. the delay is necessary as it seems after a successful read/write either the 360 spi controller restarts, or the usb flasher i have reboots and i get incompatible arm controller when the second read starts.

Code:

nandpro usb: -r512 jasper1.bin
ping 1.1.1.1 -n 3 -w 1000 > NUL
nandpro usb: -r512 jasper2.bin
ping 1.1.1.1 -n 3 -w 1000 > NUL
nandpro usb: -r512 jasper3.bin

obviously you can change this to do anything (like i am doing this for a jasper, so i have -r512, if you have 16mb change that and filenames if you'd like), but i'd figure i'd throw it out there for anyone who wants to read the 360 nand overnight while they sleep

copy and paste that into notepad, and save it as a .bat file
make sure the files dont exist already.

[jhonnyp0lak]

nice script dude very handy and i like the use of the ping command to delay the reads smart cookie u r:)

[joeyddr]

If you have a very old version of the bootloader it could be a problem if i remember correctly....again is mentioned in this thread.

Mhh, then i belive this is my problem, as it doesn't get recognized... So i have to burn the whole PIC again?

The version v3 of the bootloader (the one that is posted in the first message) is reported as buggy
There is a conflict with the bootloader mode function (and another function that i dont remember)... this blocks the "bootloader mode" and the use of the jumper

The only solution seems to be to write a new bootloader with the PIC programmer and the PIC programmer soft (not the usb circuit and PDFSUSB.exe)

If the bootloader is buggy which one do we use?

[ss3goku]

if i want to buy something similar what i have to search for?

[cory1492]

If the bootloader is buggy which one do we use?

See here:
http://www.xboxhacker.net/index.php?topic=12306.msg89624#msg89624

[joeyddr]

If the bootloader is buggy which one do we use?

See here:
http://www.xboxhacker.net/index.php?topic=12306.msg89624#msg89624

Thank you.

[ColtB45]

if i want to buy something similar what i have to search for?

If you are looking to purchase, this is the Olimex LPC-H2148, the original nandpro USB-SPI interface.

Look here for more info.

[nicomic]

hello everybody
sorry for my english but i'm french
i've made the flasher to flash the pic 18f2550 but when i open winpic and i test the hardware i have a hardware error : not responding
can someone help me i don't know what to do
thank you

[cory1492]

Have you given the PIC power and ground to it's power and ground pins?

You aren't giving much to go on, no idea of your programmer type, whether you have set it correctly in winpic etc.

[dak]

For the programmer i tried this:
http://www.finitesite.com/d3jsys/

and changed to the art2003 now

At both i cant seem to write to the pic 18F2550

My wires are 100% correct.
Art2003:
I messure a little under 4V after the diodes, 4.5V at pin 28.
Winpic800 recognizes my PIC as 12F683 and trying to write gives back: written / read differs

Im using pretty long cables for the whole thing, about 6cm before the db25, could this be it ?

Edit: all set like in the pdf on page 4(?) i think
Both vss to ground and so on, wires are correct...cap 224 and 16V,47uF
Reading gives me only 8484 8484 ...

[nicomic]

thanks for the answer,
i use art2003 programmer like in the first topic
i used this configuration : http://products.foxdelta.com/programmer/art2003/ART2003-LVP.pdf
but it doesn't work i don't know if it's my computer or my flasher that is wrong.
how can i test my flasher?
i see that there must be 4V after the diodes but is it when it's connected to the computer?
can you show me where to test the flasher (which value to which pin)
thank you very much!::!

[sandungas]

Nicomic, the problem is in your PC LPT bios settings
Reboot the PC and try with different LPT modes
If this dont work... try in another different PC with all possibles LPT bios settings

------------------------------------------

There are 2 options in winpic to check if the PIC has been correctly detected:
-Device/test hardware
-Device/detect device

Both options must show you correct info... dont try to read/write the PIC till this 2 options shows you that all is ok


Edit:
Dont forget to configure winpic like is explained in the ART2003 programmer .pdf (there is a screen capture of the settings in this .pdf)
The "config settings screen" (where you must change your oscilator frequency) must be configured AFTER uploading the .hex file in winpic

[nicomic]

thanks for yout answer i've tried the differents settings in bios for lpt : Normal, bi direction, ECC, ECC+EPP.... nothing works,
but i have already read and dump nand with nandpro and my port lpt, so i think it works, don't you think?
thanks

[sandungas]

thanks for yout answer i've tried the differents settings in bios for lpt : Normal, bi direction, ECC, ECC+EPP.... nothing works,
but i have already read and dump nand with nandpro and my port lpt, so i think it works, don't you think?
thanks

In the PC i use normally (the one im writing now) it did not work in none of the possible LPT modes
This gave me lot of headaches...

[nicomic]

it's the same for me now :-)
how can i test my flasher to be sure that the problem doesn't come from here?
thanks

[sandungas]

it's the same for me now :-)
how can i test my flasher to be sure that the problem doesn't come from here?
thanks

The only way i can imagine is what i said

There are 2 options in winpic to check if the PIC has been correctly detected:
-Device/test hardware
-Device/detect device

Without the PIC... the ART2003 programmer has nothing to detect (some diodes, 1  capacitor, 1 resistor) this is not a device
Maybe the voltages can be measured, but i have no idea about it


Btw...
I just remember that somebody comment in the nandpro thread that:
In a overclocked PC... the LPT port is overclocked too
This can mess all comunications with the PIC

I just realized that this PC is overclocked... maybe this is the reason why it did not work here

[vintage_guitar]

My PC read the NAND perfectly from LPT overclocked over 50%.

[cory1492]

Set the PIC model manually instead of relying on detect. When it's blank it doesn't seem to always detect right.

For art2003 issues, be sure to note this post:
http://www.xboxhacker.net/index.php?topic=12306.msg89029#msg89029
ernestino gives some good tips that aren't in that pdf.

[Arakon]

hrm.. I just built the USB flasher, but once I start the dump, I get 1, 2, maybe 3 blocks with errors, afterwards the entire device disconnects and is dead for a while. There's no shorts, I checked several times.
It's flashed with the latest binaries, and does detect normally and all.

edit: wtf.. I found that pin 13 had a bad connection.. fixed it, started dumping, after 40 or so correctly dumped blocks it disconnects again and then only errors again too.