USB SPI Flasher with PIC18F2455 - now with source and binaries

[gepal]

You can try, don't think it will damage PIC or console. The wiring will be different of course.

[kirua]

can i use
PIC18F4455

instead of 18f2455

I have two USB SPI Flasher, one is using 2455, and the other 4455, both are working fine. I have done more than 10 jtags with the 4455, I haven't encountered any problem.

[wes11ph]

can i use
PIC18F4455

instead of 18f2455

I have two USB SPI Flasher, one is using 2455, and the other 4455, both are working fine. I have done more than 10 jtags with the 4455, I haven't encountered any problem.

thanks duh..

[gr3nad3]

just droppin in Doin a jasper and using the mini schematics, this thread ROX

[Xumpy]

Ok, I've managed it this far...

I've programmed the art2003 and was able to flash picxboot v3 to my pic18f2550...

I was able to flash the v3 picflash file with pdfsusb.

I was able to detect my controller and I was able to dump my nand with nandpro2a.

So my next step was first of all update the picxboot driver from v3 to v3plus2. (the new one, thank you cory).

Flashing the v3plus2 picxboot was no problem, but when I wanted to flash my picflash file with pdfsusb I got USB Read Failed. Failed with error 6: The handle is invalid.

The strange thing is when I use the old picflash file it gave the same error. So I suspect it is the new boot-loader?

I tried this many times and check and rechecked all my solder work. Any help would be greatly appreciated.

Thanks

Xump

[Xumpy]

Ok, still in need of help...

The tutorial I was following is found over here : http://dev360.wikia.com/wiki/USB_Nand_SPI_Flasher

Could it be that the cristal is to low. Anyone able to build the nand flasher found on this link and update it with corys latest update???

Also this tutorial was using the 18F2550. I didn't use the 18F2455. Is this a problem for the new drivers???

Thnx & Greetz

Xump

[Xumpy]

So I searched the datasheet of the pic18f2550 and compared it with pic18f2455. The result is that the 2550 is even larger then the 2455.

Why isn't this working then??? Is it possible the new picflash should be rebuild for the pic18f2550.

Am I missing something else, it's very strange but I tried this at 3 different pc's. In the end picflash v3 can be flashed on 2 of the 3 pc's.

The last pc only writes a part and errors out with the same error 6, when I disconnet the device it isn't found anymore...

Writing the bootloaders of both version works fine... So I don't believe it's my art2003 that's not working...

Please anyone

[cory1492]

Xumpy, I used to use the 2455 bootloader build without issue on my 4550's but for some reason I've had to relink against different libs on new flashes to make it work.
PicXBoot_multitarget.zip (link)
Give that link a go, it has a bin built for your specific PIC (has: 2455/2550/4455/4550). Also make sure to set your divider for the oscillator you use with something like winpic800 before flashing and verify the options you need (ie: if you need LVP make sure it's enabled and remember to put the correct pull on the lvp pin, if you don't want to use MCLR for a reset switch disable it or remember to put a pull on that pin.)

[Xumpy]

Hey cory,

thnx for the link. I've tried this bootloader but there was no difference.

The bootloader works, the device is present in picdem but when I click the program button it still crashes with error 6.

My osc values are 'Devided by 3 (12mhz as my cristal is)


By using a pull down switch I've read in your readme you mean put a 10k resistor between pin 26. This is also done as you can see I followed this image exactly

http://images1.wikia.nocookie.net/__cb20100130150835/dev360/images/d/df/Xbox360usbflashermini.png

Could the mclr be the problem. I have no clue what this is or how this could be responsible for this famous handle is invalid error???

[cory1492]

If you did it just as the diagram shows, pin 1 is mclr and has a resistor on it. Are you sure you are loading the proper hex (not the bootloader, should have no fuse info in it) in picdem?

[Xumpy]

Hmm, I'm loading your PicXBoot_2550.hex to it with winpic800 as the bootloader.

For this I tried the latest version and version 3.55. I've read that there was a difference in loading the file.

When I tried 3.55 I needed to pull my vdd to 5v instead of 2.74 else there was a write protect mode active.

When this is done I disconnect it from the pc and put the pic onto the usbflasher.

I open picdem fs usb tool (tried version 1.2) and use the file PICFLASH.hex And he give me the error.

I do not exactly understand where I could find these fuses (or what they are). If it is anything like the ID in settings of winpic than it is set to FFFF FFFF FFFF FFFF. Which I believe is correct???

[cory1492]

Version 1.2? Even in current microchip app libraries it is version 1.0... here is the program and drivers that work with darkstar's project for flashing from bootloader.

[Xumpy]

Yes you are correct... It also says 1.0 I was asuming it cause of a reply I found on other forums. (which was incorrect)

So I used these drivers and still I got this USB write error. Is it possible that writing is dissabled cause of some USB settings. I've measerd all voltages, I find it strange but even with the 10k resistor my voltage is still 5V on pin 1??? When I measure the resistor it's 10k so I want to assume all here is right...

Do I have other options, like flashing the whole thing with winpic800? I've tried this but it's giving a write error at 98%

[Xumpy]

Ok some new developments...

When I write the PICFLASH.hex file I see that untill address 002500 all is fine.

So I supose my error happens directly after this address. Is this some kind of upper memory.

I do not seem to be able to write to anything higher???

edit: even more strange is that when I open the picflash.hex file in winpic800 it's only filled until address 0x1288. When I reread my pic in winpic I get the same result as opening my picxboot.hex + picflash.hex file. Yet I can't seem to start the hardware... When I remove the boot jumper and connect my hardware nothing happens. No new hardware is detected :s... Believe it all comes down fixing why picdem won't write any further then address 002500 or why it just won't finilize the job???

Additional info after reading my failed pic:

EEPROM MEMORY:

000000 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
000010 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
000020 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
000030 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
000040 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
000050 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
000060 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
000070 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
000080 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
000090 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0000A0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0000B0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0000C0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0000D0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0000E0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0000F0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

USER ID MEMORY:

200000 FF FF FF FF FF FF FF FF

CONFIGURATION MEMORY:

300000 22 0E 3F 1E 00 81 85 00 0F C0 0F A0 0F 40
3FFFFE 47
3FFFFF 12

[Xumpy]

If you want my whole read I can sent it to you cory???

btw: If I flash the old picxboot_12 and the picflash that belongs to it everything works fine... I just want the latest version cause of the updates of nandpro3b and jasper support

[cory1492]

Here is a full dump off my PIC of bootloader+picxflash_3b_plus2 working, I have 40MHz osc on this board and have set LVP bit - if yours is a different setup change this in the config tab of winpic before flashing.

[Xumpy]

Yess, Cory this did it. Your dump worked perfectly. (It already was at 12mhz which is my cristal)

Though it is strange that the normal way was unsuccessful. I'm going to experiment more with this but at least I have a way now.

Thnx mate

Greetz

Xump

Edit: And of course if you find 1 than 2 is not far away... My problem was my PICFLASH.hex file. Apparently it was outdated though it was the file I found with the picxflash.hex bootloader. No matters. For others who have this problem, just flash this : http://www.360usbspi.com/pub/360usbspi_800_v1.hex Afterwards all will be fine 

[Xumpy]

Pff, getting crazy over this... I'm able to read my entire nand but when I start writing to it, nandpro seems fine (though writing is very slow compared to reading), only the first 512 bytes seems to be written.

When I reread the device and open my read in HxD, only untill ofset 200 contains valid data. The data is ok but after this only FF are written.

I'm starting to get desperate with this damn controller. Does anyone have any experience with this kind of trouble? I already shortened the wire but it has no effect... It's now like 30cm from my controller till the nand spi.

Any help is greatly appreciated

Thnx

Xump

[gepal]

Maybe source of your problem is too long wires. I also had problems until I shortened wires to 10cm. So try shorting wires as much as possible

[Xumpy]

Neh, it's defiantly my pic. I already shortened the wires...

I discovered something interesting.

So when I write with my controller, the first 512bytes are written perfectly. But if I rewrite it without disconnecting the controller these bytes are also filled up with FF. When I disconnect and reconnect the controller, again the first 512bytes will be written perfectly.

It's more likely that there is a problem with my pic. It's like the controller is not able to reset it's memory pointer or something like that...