Search the Community

Hi all, I'm relatively new to the original Xbox modding scene, and if you read my recent post in the welcome section you will be aware that I'm currently making up a batch of Jafar modchips. I know there are better chips with more features, but I wanted to start with something simple and work my way up to the more complex things if that makes sense. It's been going well and I've learned a lot but I'm curious about a small issue I've come across and wondered if anybody in the community has come across the same thing and created a work-around... I ordered 100 SST49LF080A chips from aliexpress (yes, I know, but I'm not made of money and 50p each vs £3 - £4 each from somewhere like digikey I figured it was worth the risk!). Anyway, out of these 100, 93 of them work absolutely fine. In Xgecu Pro, the device ID is shown to be BF 5B. These all flash perfectly and work perfectly in the Jafar modchips. 6 of the 7 that don't work, show a device ID of BF 5A instead. The 1 remaining chip shows a device ID of 3B 3B. The 6 "BF 5A" ones will flash absolutely fine in Xgecu Pro providing I untick the device id check first, and the contents of the flash chip are read back absolutely fine also (again, with device id check unticked). This leads me to believe that although the device ID is slightly different, the pin outs etc and the way the device operates must be the same, since I can both read and flash using the SST49LF080A@PLCC32 profile in Xgecu Pro. HOWEVER, when I put any of these in a Jafar and install in the Xbox, I get the 3 boot attempts and FRAG. This leads me to think that the Lattice CPLD code has been written to specifically target device IDs BF 5B and wont work with anything else even if the pinouts etc are the same. Am I wrong in making that assumption? So, since the VHDL coding for the Lattice CPLD has been released and is open source, I thought I may be able to inspect it, find the reference to BF 5B and possibly modify it to include BF 5A aswell. I clearly have a lot to learn because I cant find reference to that device ID anywhere. Furthermore, the ispLever classic software required to compile the CPLD code is no longer free, its something ridiculous like $600 per year and I don't have that kind of money. So I was wondering if anybody else who is familiar with building the Jafar modchips, had come across these chips branded as SST49LF080A but with the slightly different device ID's, and had managed to make an updated CPLD code that would allow them to work? For reference, I've been using the 1MB_LPCmod_OSSupport_MosfetD0 from https://github.com/Team-Resurgent/Aladdin-Lattice It's a shame Lattice have made the software so expensive because I would have liked to have learned how to make my own code etc and would love to learn how these modchips work, so that one day I may be able to make meaningful contributions to projects myself. As for the one chip identified as 3B 3B - it doesn't even read, flash or erase in Xgecu Pro using the SST49LF080A profile, so that one must be some completely different chip altogether, unless it's just corrupted somehow and that's causing a false ID to be read?. As I say, I don't really fully understand how these things work yet - but I'd like to learn, just not sure where to start!