(WIP) New modchip coming in

[psyko_chewbacca]

would there be a market for this modchip?

Well it's a niche market. People that just want their Xbox to run homebrew will basically softmod it and be done with it. This modchip is for people who like having more customization options.

[psyko_chewbacca]

I just released XBlast OS v0.50. You can have a look at the release thread over AssemblerGames' forums

[xboxmod]

Some of you will be really happy.

http://www.assemblergames.com/forums/sh ... -coming-in[/quote]

certified_genius_award.gif (8.2 KiB) Viewed 25001 times

thanks for all psyko_chewbacca , you are the man

[Tom M.]

Well, I have DuoX2 in my Xboxes and this new chip PCB looks so huge... or is it just confusion?

[psyko_chewbacca]

Some of you will be really happy.

http://www.assemblergames.com/forums/sh ... -coming-in

certified_genius_award.gif

thanks for all psyko_chewbacca , you are the man[/quote]
Thanks!

Well, I have DuoX2 in my Xboxes and this new chip PCB looks so huge... or is it just confusion?

It's a bit bigger. Duox2 is 43mmx26mm while XBlast Lite is 50mmx31mm excluding soldered on LCD headers.

[Dragoncracker]

Where and when can i buy one... or 10?

[professor_jonny]

You can PM psyko_chewbacca aka ben he will happily sell you some

[mmz16x]

i to want to buy one where and how much are they as assemblergames is down

[professor_jonny]

i to want to buy one where and how much are they as assemblergames is down

Just pm him

memberlist.php?mode=viewprofile&u=529

[cbuchris]

Interested in chip want to buy one

[Taylor]

I wanna buy one too.

[professor_jonny]

I wanna buy one too.

Just pm Ben and have your bitcoins ready
memberlist.php?mode=viewprofile&u=529

[mmz16x]

is the XBlast Lite still available?

[psyko_chewbacca]

I'm all out.

[obitus1990]

Hi! Sorry to post this in the Xblast Lite thread, but, I can't post at all on assemblergames, since it seems near impossible to have an account activated there.

Regarding the Aladdin XT 2+ version of this BIOS/OS, is the file linked in the thread on assembler about the aladdin the very latest version of the software? FOr some reason, I cannot get the svf to flash the Lattice chip on one of my Aladdins, using a FlashCatUSB programmer in JTAG mode. It fails at about halfway. The console output is as follows:

FlashcatUSB Script
> Engine build: 300 Welcome to the FlashcatUSB interfacing software,
> build: 560 LibUsbDotNet version: 2.2.8.104 Running on: Microsoft
> Windows 10 Home (64 bit) Serial NOR memory database loaded: 342
> devices supported Serial NAND database loaded: 28 devices supported
> Parallel NOR memory (x8/x16) database loaded: 269 devices supported
> SLC NAND memory (x8) database loaded: 118 devices supported Connected
> to FlashcatUSB Classic, firmware version: 7.13 Firmware features
> supported: JTAG BSDL definition not found for JEDEC ID: 0x01805043
> JTAG chain detected: 1 devices JTAG TDI size: 8 bits JEDEC ID:
> 0x01805043 (21 0x1805) JTAG engine setup successfully Checking for a
> device specific script to automatically load Loading device specific
> script: SVF_Player.fcs Loading FlashcatUSB script: SVF_Player.fcs
> Script successfully loaded Button Hander::Calling Event: RunSVF
> Running SVF file in internal JTAG SVF player SVF Player: Failed
> sending SDR command (command number: 226) SVF Player: TDO:
> 0x00119CEF7BDFFFFCE7F9FED00610961088CEF7BCBF7B SVF Player: Expected:
> 0x0C119CEF7BDFFFFCE7F9FED00610961088CEF7BCBF7B Error playing the SVF
> file Button Hander::Calling Event: Done

Any ideas as to what might be causing the error?

[psyko_chewbacca]

Hi! Sorry to post this in the Xblast Lite thread, but, I can't post at all on assemblergames, since it seems near impossible to have an account activated there.

Regarding the Aladdin XT 2+ version of this BIOS/OS, is the file linked in the thread on assembler about the aladdin the very latest version of the software? FOr some reason, I cannot get the svf to flash the Lattice chip on one of my Aladdins, using a FlashCatUSB programmer in JTAG mode. It fails at about halfway. The console output is as follows:

FlashcatUSB Script
> Engine build: 300 Welcome to the FlashcatUSB interfacing software,
> build: 560 LibUsbDotNet version: 2.2.8.104 Running on: Microsoft
> Windows 10 Home (64 bit) Serial NOR memory database loaded: 342
> devices supported Serial NAND database loaded: 28 devices supported
> Parallel NOR memory (x8/x16) database loaded: 269 devices supported
> SLC NAND memory (x8) database loaded: 118 devices supported Connected
> to FlashcatUSB Classic, firmware version: 7.13 Firmware features
> supported: JTAG BSDL definition not found for JEDEC ID: 0x01805043
> JTAG chain detected: 1 devices JTAG TDI size: 8 bits JEDEC ID:
> 0x01805043 (21 0x1805) JTAG engine setup successfully Checking for a
> device specific script to automatically load Loading device specific
> script: SVF_Player.fcs Loading FlashcatUSB script: SVF_Player.fcs
> Script successfully loaded Button Hander::Calling Event: RunSVF
> Running SVF file in internal JTAG SVF player SVF Player: Failed
> sending SDR command (command number: 226) SVF Player: TDO:
> 0x00119CEF7BDFFFFCE7F9FED00610961088CEF7BCBF7B SVF Player: Expected:
> 0x0C119CEF7BDFFFFCE7F9FED00610961088CEF7BCBF7B Error playing the SVF
> file Button Hander::Calling Event: Done

Any ideas as to what might be causing the error?

First impression is that FlashCatUSB doesn't support SVF generated by Lattice's ISPLever Classic software suite. It's not unheard of, I know some SVF players have a hard time with SVF generated for XC95** targets for example. SVF is basically a script file that indicates the software running it what operation it must do. Sometimes, chip makers deviate slightly from the standard to include a few customized commands for their product line.

I would try an alternative software solution if possible like Lattice Diamond programmer, Lattive ISPvm, urJTAG or any other solution that can normally handle SVF files.

If it's only a single device that isn't working and you made it work on other Aladdins before, I would not rule out the possibility of that chip having a faulty CPLD. I wouldn't be surprised if they were populated with fake or out of spec ICs to cut costs! If that's so, then getting a unit that behaves all weird is to be expected!

[obitus1990]

Thanks for the reply. I sent the SVF to the maker of the FlashcatUsb, and, he released an updated version of the firmware for the programmer, as well as the programmer software, and it now works with the Xblast's SVF.

[obitus1990]

One more question for you, psyko_chewbacca. In a comparison table of the different BIOS options for the OGXbox that I have read on a reddit group, the XBlastOS has, in its feature list, the option to reflash a corrupted TSOP. Is this correct? I haven't seen that function listed in the XBlastOS options menu, which is on my Aladdin XT Plus2. Is this correct? If so, how do I do it, as I have a 1.4 xbox that I bought that will only boot via the Aladdin modchip (it works every single time). It will only boot from the TSOP one in maybe 30 boot attempts, so, I suspect the winbond TSOP might be bad.

[psyko_chewbacca]

One more question for you, psyko_chewbacca. In a comparison table of the different BIOS options for the OGXbox that I have read on a reddit group, the XBlastOS has, in its feature list, the option to reflash a corrupted TSOP. Is this correct? I haven't seen that function listed in the XBlastOS options menu, which is on my Aladdin XT Plus2. Is this correct? If so, how do I do it, as I have a 1.4 xbox that I bought that will only boot via the Aladdin modchip (it works every single time). It will only boot from the TSOP one in maybe 30 boot attempts, so, I suspect the winbond TSOP might be bad.

TSOP recovery feature is tied to XBlast Lite hardware rather than XBlast OS software.
You need a XBlast Lite modchip (or Chameleon modchip) to pull a TSOP recovery.

In any case, XBlast OS can surely flash a TSOP in most situation but the recovery process of a TSOP starts with a modchip that supports this feature.

In your case if you're getting inconsistent boots from TSOP, I would try to reflash your TSOP the one time on 30 that it successfully boot and move on from there.
If it solves your problem then perfect, if not I would suspect the TSOP chip is acutally physically faulty or not properly soldered in.

[obitus1990]

Thanks again! Will you be selling another run of the XBlast Lite chips soon, by any chance?