dtomcat
-
Posts
821 -
Joined
-
Last visited
-
Days Won
23
Content Type
Profiles
Forums
Calendar
Store
Posts posted by dtomcat
-
-
Essentially your flash is a bit slower than pi wants. This line tells it to wait until flash is ready for next write command.
-
1
-
-
Xenium-flash.cpp
around line 174
//write byte to flash
flash.Write(i, flash_buffer[i]);
while(flash.Read(0) != flash.Read(0));
float current_progress = (float) i / flash_size * 100.0f;
need to add bold line
-
1
-
-
You need to add a line of code to the source code and recompile. I’ll have to find it later. It’ll be a few hours before I can get to it .
-
1
-
-
Not sure. Possible for issues with eeprom? I actually test on a 1.0 before sending out. (A 1.6 via pin header and 1.0 via pogo).
-
No problem
-
Just now, gehx said:
SD; microsd card.
Ok. So SD is working
-
Since you are having issues booting with HDD… maybe there is an issue with eeprom. Only thing I can suggest is install a pin header so you get a better connection
-
1
-
-
Is that from SD or terminal?
-
That is weird. The board is working. Not sure why nothing is being written to SD card though. It’s passing that check.
Try this:
turn Xbox leave it sit for 30 secs to min. Put power switch on picoPromSD (PPSD) to USB (no usb attached). Put good pressure on PPSD on LPC. Once you have a good connection, slide power switch in PPSD to LPC and try not to move it
-
Uses these pins
9 minutes ago, gehx said:I'm having a really hard time dumping the EEPROM info on a 1.0 box. I have no idea why it won't dump the data? It's not writing any info to the microsd card...and the red led is the last to light up and stays lit. The console boots but there's an issue w/ the HDD so it won't boot w/ the original HDD attached. Might I not be aligning the pins on the pogo adapter up correctly? I'm making sure the pins are aligned from the front to the back (the way you did it in the youtube vid).
-
New Firmware is almost ready
Preview:
-
1
-
-
no info to SD card.... sounds like an SD card problem. Is it Fat32 formatted?
If so... try another card (different manufacturer)... I've had a report of one card type not working... don't remember which brand
2 minutes ago, gehx said:I'm having a really hard time dumping the EEPROM info on a 1.0 box. I have no idea why it won't dump the data? It's not writing any info to the microsd card...and the red led is the last to light up and stays lit. The console boots but there's an issue w/ the HDD so it won't boot w/ the original HDD attached. Might I not be aligning the pins on the pogo adapter up correctly? I'm making sure the pins are aligned from the front to the back (the way you did it in the youtube vid).
-
Send me a message on here. I'll message you back when I have more made (soon) they are 50% completed... but I stopped building them as I'm making really nice changes to the firmware
-
1
-
-
now working on all Seagates (slim and rubber)
now to clean up the code
-
1
-
1
-
-
Sneak peek at firmware 2.0.
@Bowlsnapper will be helpful to you if you get those HDDs
-
1
-
-
Sooooo... working on a thing for fun
no Xbox or EEPROM needed
-
1
-
2
-
-
2 hours ago, Bowlsnapper said:
But I wanna see what's up with that 256. There is no explanation for how that would be accomplished in the first place and it perplexes me.
He has hinted to the fact they are custom ram chips that will replace the factory ram
-
1
-
-
-
Awesome!!! Seagates only require serial and terminal to get password (if they’re locked). WDs require a PC with IDE
-
1
-
-
Final was 13/63 seagate drives with content…6/20 WDs… and 10.3GB of data to look at further
-
2
-
-
Had 19 WD drives sent to me… so purchased an old computer (Seagate trick doesn’t work on WD drives). I was able to get all the passwords
next step… grab all the data
-
2
-
-
Ahhh.
was just joking around
-
1
-
-
1 hour ago, Bowlsnapper said:
LEDs?
In your lamp. Looks like CFL bulbs
-
Oh… and upgrade to LED bulbs
Board Life Status
Board startup date: April 23, 2017 12:45:48
Problems with the Xenium programmer
in Modchips
Posted
Hmmm I would’ve thought that was it. I had same problem