Jump to content
OGXbox.com

Scorpius

Members
  • Posts

    3
  • Joined

  • Last visited

Posts posted by Scorpius

  1. 12 hours ago, KaosEngineer said:

    Ignore XBlastOS's warning.  It gives that for all non-XBlast modchips.  Flashing still works just not all of the enhanced features available when using an XBlast modchip.  The Aladdin only has one 256KB BIOS bank so can only hold 1 BIOS at a time.  When you flash a different BIOS to the modchip, XBlastOS will be replaced by the BIOS you flash.  An XBlast modchip has a 1MB flash that allows it to hold 3 BIOSes - XBlastOS (256KBs), 1 user programmable 256KB BIOS and another user programmable 512KB BIOS.

     

    Edit: Most modified Xbox BIOSes are 256KBs in size; thus, to fill the 512KB Bank a 256KB BIOS is written 2 times one after the other to fill all 512KBs.  X2 5035 is, I believe, one of the only modified Xbox BIOSes that is 512KBs in size.  There was an older proof-of-concept X2 BIOS release with a built-in FTP server that was also 512KBs; however, it should not be used.

    That worked i was able to get evox back up and running without an external progammer.

    Trying to flash a known good 49LF080A with this new variant does not work with or without the jumper changed. I guess the CPLD code will need an update to support it and to use the full xblast os features?

  2. 11 hours ago, KaosEngineer said:

    Did you change the jumper location from R3 to Center then Center to R4 with this new revision to try to flash a BIOS with Evoxdash or XBlastOS to the modchip before trying to reprogram the LC4032V CPLD on it?

    I just got around to this now. I was able to flash a 256kb xblast file to it via evox dash without changing the resistor jumper. However, xblast does not support the chip, so no further flashing is possible without an update to xblast and ofc in this situation a hardware flasher, but that's easy.

Board Life Status


Board startup date: April 23, 2017 12:45:48
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.