|
gupek
|
 |
« Reply #160 on: November 07, 2009, 07:20:31 PM » |
|
yes, multimeter says yes... have no idea where the problem can be 
|
|
|
|
|
Logged
|
|
|
|
|
Grim187
|
 |
« Reply #161 on: November 07, 2009, 08:29:12 PM » |
|
@cory1492 i would code it in if i knew the first thing about coding a pic but i'll look in to it.
|
|
|
|
|
Logged
|
|
|
|
|
gupek
|
 |
« Reply #162 on: November 09, 2009, 04:00:53 PM » |
|
SOLUTION: too long cable, to close to each other... from flasher to mb... thx all 4 help
|
|
|
|
|
Logged
|
|
|
|
|
Grim187
|
 |
« Reply #163 on: November 09, 2009, 09:13:23 PM » |
|
@gupek how long where cables? 3ft?...6ft?...12ft?
|
|
|
|
|
Logged
|
|
|
|
|
dusan75
|
 |
« Reply #164 on: November 09, 2009, 09:21:05 PM » |
|
Thanx for good job guys! This thing is awesome, I build it and working smooth. 
|
|
|
|
|
Logged
|
|
|
|
|
stuntpenguin007
|
 |
« Reply #165 on: November 10, 2009, 08:02:17 PM » |
|
nice work. I'm definately going to try this out. In the parts list under "for programmer" it says an lpt connector is needed, thats not actually something I need is it? Just the stuff under "flasher" right? If I order the pic from mouser, it says shipping is estimated around $6 - $7 for a 1lb package. Will that price be lower if I try order it being that it's less than a pound? --I'll buy it either way, but just looking for the cheapest price first 
|
|
|
|
|
Logged
|
|
|
|
|
gupek
|
 |
« Reply #166 on: November 11, 2009, 11:06:59 AM » |
|
Grim187: 0.75 meters, now 0,35 meters
|
|
|
|
« Last Edit: November 11, 2009, 11:36:50 AM by gupek »
|
Logged
|
|
|
|
|
Grim187
|
 |
« Reply #167 on: November 11, 2009, 11:12:17 AM » |
|
@ gupek ya 2 and a half feet is to long, i would guesstimate the longest the wires from the flasher could be is about a foot (0.3 meters)
@stuntpenguin007 yes you need the lpt and diodes to flash the pic before you build it and use it as a flasher.
|
|
|
|
|
Logged
|
|
|
|
|
stuntpenguin007
|
 |
« Reply #168 on: November 11, 2009, 12:14:52 PM » |
|
I already have a compatible pic programmer, so I guess that won't be a problem for me.
Thanks
|
|
|
|
|
Logged
|
|
|
|
|
mackarry
|
 |
« Reply #169 on: November 11, 2009, 11:46:25 PM » |
|
I have big problems, with nandpro 20b: Looking for usb interface device Incompatible ARM hardware for this version of NandPro! Can not continue and nandpro 20a: Looking for usb interface device Could not detect a flash controller Fatal Error I try with pic 18f2550 and the pc show me MemoryAccess, I install driver that @cory1492 get in this link
|
|
|
|
|
Logged
|
|
|
|
|
cory1492
|
 |
« Reply #170 on: November 12, 2009, 12:39:56 AM » |
|
This hasn't been updated to work with NandPro20b, just NandPro20a which is why you get "incompatible ARM hardware". Make sure your wiring from PIC to xbox is correct and soldered well, and that you are powering the xbox with a power brick (need not be turned on for this; in fact if it is and connections are correct nandpro will turn it off.)
|
|
|
|
|
Logged
|
|
|
|
federicobj
Newbie

Posts: 8
|
 |
« Reply #171 on: November 12, 2009, 03:22:03 PM » |
|
sorry if this is a noob question, but can i just flash the chip with the PICFLASH.hex whit a PIC prgramer without the need of first flashe the bootloader???
PS:sorri for mi english
|
|
|
|
|
Logged
|
|
|
|
|
cory1492
|
 |
« Reply #172 on: November 12, 2009, 03:43:01 PM » |
|
can i just flash the chip with PICFLASH.hex with a PIC programmer without the needing to first flash the bootloader?
With some modifications to the source, yes. As is, I don't think so (only interrupts are remapped, not startup which is needed for stand-alone use without bootloader.)
|
|
|
|
« Last Edit: November 12, 2009, 03:44:38 PM by cory1492 »
|
Logged
|
|
|
|
federicobj
Newbie

Posts: 8
|
 |
« Reply #173 on: November 12, 2009, 09:52:30 PM » |
|
can a use a 18f2550 instead of an 18F2455???, whats the diference???, i cant find an 18F2455 here in argentina, thanks, federico
|
|
|
|
|
Logged
|
|
|
|
|
cory1492
|
 |
« Reply #174 on: November 12, 2009, 11:14:46 PM » |
|
Yeah, 18f2550 should be fine. Far as I can tell the only difference is that 2550 has a bit more program flash memory than 2455. The 18f4455 or 18f4550 will also work.
|
|
|
|
|
Logged
|
|
|
|
|
Grim187
|
 |
« Reply #175 on: November 13, 2009, 06:34:51 PM » |
|
im trying to flash using lvp and im haveing problems with the diodes. 4.40 from the diodes, pin 28 is 0.53.
Now the diodes are giving me 0.3V, from what i can tell the diodes work fine w/o them im only getting 0.1V from each line (db25 pin 2-9), it worked to program the chip to %97 when i first hooked it up then stoped after about 3 mins (w/o me disconnecting it or even touching it) so i think i might have blowen my lpt port (not sure how tho), i tried another pc and it gave me 0.6v from the diodes so i guess i will replace them and see if that works, if you guys have any other ideas of what it could be let me know. the diagram im usingedit: replaced the diodes, no change. edit2: changed the settings in my bios and got it working, programed and verified %100.
|
|
|
|
« Last Edit: November 14, 2009, 06:12:36 PM by Grim187 »
|
Logged
|
|
|
|
|
Straßenkampf
|
 |
« Reply #176 on: November 15, 2009, 04:51:25 PM » |
|
anybody had problems with writing 256mb jasper nand?? Tried and when i read back just FFFFF at the beginning = box not booting. Flashed with LPT =everything fine.
|
|
|
|
|
Logged
|
|
|
|
|
cory1492
|
 |
« Reply #177 on: November 15, 2009, 09:38:52 PM » |
|
I figured as much, the 256/512 NAND is detected and possibly treated differently internally in the LPC's hex and in nandpro, code which isn't replicated in the PIC source. Does it at least give the same config value as others/your LPT?
Hrm, wonder what DarkStarTM's plans are on this. I'm decent with ARM, if I had a jasper I wanted to mod I'd look at updating the PIC source but (thankfully as life is busy) I don't. Getting over the ARM version check was relatively simple, though the SPI protocol in the PIC may also require other changes beyond just the new version command to actually work with the latest nandpro (haven't tested on a 360, nandpro doesn't complain about wrong arm version though - if someone wants to test just lmk as it's going to be a while before I've got the 360 wired up on my bench..er, desk, again - which, now that I've come to terms with readline, is what is holding up that exe I had mentioned to you DarkStarTM.)
|
|
|
|
|
Logged
|
|
|
|
|
vgplayer
|
 |
« Reply #178 on: November 18, 2009, 01:37:06 PM » |
|
I am trying to get this working with my 18F2550 and 20MHz oscillator. I got the source and changed the 18f2455.lib to 18f2550.lib in both projects. In PicXBoot I changed PLLDIV to 5. I set MPLAB to 18f2550 and both compiled. I uploaded PicXBoot with my Pickit2 and it appears to be working as it shows up in PDFSUSB when I put it in bootloader mode. I used PDFSUSB to upload PICFLASH. After reset I ran XFlash.py says "XFlash USB hardware not found" both in Windows and Ubuntu.
I feel like the missing something obvious.
|
|
|
|
|
Logged
|
|
|
|
|
cory1492
|
 |
« Reply #179 on: November 18, 2009, 07:17:18 PM » |
|
Is it detecting as a usb device under windows, at which point you'd install the libusb drivers? Do you have Pin 1 (MCLR) pulled up? Do you have Pin 13 (RC2) connected to USB 5V (it's for usb presence sense - the bootloader doesn't use it, the xflash program does)?
|
|
|
|
|
Logged
|
|
|
|
|