Bowlsnapper

Updated to version 1.2.2. Will save you the headache of going through the whole Visual Studio install just to encounter an error message.

As per Kaos: "Sorry, on an Xbox Softmodding Tool modded console, the Dashloader configuration files are not stored/found in the C drive's Dashloader subfolder. They are in: /E/UDATA/21585554/000000000000/nkpatcher settings/dashloader" I'm not sure if that addresses the dashloader question directly, but you are dealing with shifting partitions and it is hard to keep track of them when doing stuff like this. Do yourself a favor and get rid of your softmod. It's causing you needless headaches. You reinstating that backup basically undid the intended benefits of formatting those partitions once hardmodded. Backup your C and E data manually, only keeping what you know you want. Wipe out the rest. Whichever way you format the drive, make sure that you use the "Setup" files that the installer disc wants to load onto the partitions. THEN start building and setting up your dashboard/launchpoint configuration, as well as replacing the files you wanted to backup (which really should only be homebrew apps or maybe gamesaves. NOTHING from the exploit should be preserved). @NokSueCow Check for latest edits... again @ 3:16.

I suspect your problems stem from the fact that you may be dealing with a shadowC partition, among other things. The "P" and "Q" partitions (which are never present with a hardmod and are present when running a softmod) are evidence of this. I think that even though you deleted the settings folder, nkPatcher is still loading, just with default settings. If you're going from a softmod to a hardmod, I would try backing up what you wanna keep on that drive and formatting and "setting up" C and E (there should be an option to do this on the OGXbox installer and the Cerbios Disc). That should really ALWAYS be done when switching from soft to hard... Giggity.

How did you TSOP flash, from a softmod? Do you have a softmod setup now, by chance? What happens when you load xboxdash.xbe from Unleash's file manager?

What does this mean in practical terms? Was serial debugging possible with the MCPX X2, but not used? I guess it may have just been what came before the X3 and that's all. ---------------------------------------------------------------------------------------------------------------------- The fuzz has since been removed.

@applesauceman You should be able to upload this into Mouser. I don't have time for a true BOM file right now (who knows; maybe this actually IS a BOM and it's simpler than I think it is. lol), but if you go to tools on their website you should be able to easily upload and translate this Excel spreadsheet to a "BOM". I tested it and it loads perfectly, creating a useable cart for checkout. I made sure to include proper quantities and Customer Reference numbers so you can follow the silkscreen part designations. Edit: @applesauceman BTW, I had to substitute the 14.3181MHZ crystal for another one that was still being manufactured. The pinout is the same and it is compatible, according to both the datasheets. The footprint is slightly different, but the contact spacing and placement is more or less the same. If you must have the original crystals, they are available on ebay from China, although, I can see you've built a few recently so I'm sure you've settled on a solution at this point. SuperIO BOM: https://mega.nz/file/JqNHkaKK#tw1_BUJcyYm6pITErpMtecFOayQmK3zlAkBKJWbTRsA

Nah, I don't think you're MM. I'm glad you had an old Aladdin to use. Looks like they had what they needed to make BT and D0 work. "he said he did it because the pin header can corrode." - That is 100 percent BS and makes absolutely no sense whatsoever. Total Gibberish. If that were true then you would be seeing other people doing it. NOBODY does it. A pin header is no more subject to corrosion than soldering the chip directly to the LPC. He did it to make it hard to work on so you would send it back to him and not be able to upgrade anything on your own... He is lying to you, dude.

Nice work. I envy you and want to start doing the same!

Can anybody verify that this Version of the Aladdin has the D0 and BT pads working? I'm not calling you a liar, just not familiar with ANY Aladdins with working D0 and BT. I notice that it is a bit different than my AliExpress PCB, 1MB upgraded version.

https://www.amazon.com/RS232-Converter-interfacing-microcontroller-device/dp/B01M4PZA7R I may choose to install this UART to Serial converter in order to have native serial output on the Devkit. It's just an idea, as the USB-C FTDI serial output should already do what I need, but It would be very DXT-4-ish.

SICK. I was wondering if this existed. Perhaps I should give it a try. Thank you, Saucer! @applesauceman What revision of the Serial Debugger is this? The UART header looks different and there is 5V power on the corner!

But does NOT work on Aladdins CURRENTLY... So what gives here?

I saw you in this page here, Kaos... : @KaosEngineer https://assemblergames.org/viewtopic.php?t=59850 - More info about serial/kernel debugging. It seems that the Debug Kit simply had 128MB of RAM and the only debugging came from the dashboard or bios and transferred through LAN. As far as I know nothing else is different from a stock/retail console. However... If you go to 4:00, you will see what the SuperIO I am building and featuring in the build is taking the place of. It was featured in the DXT-3 and 4. This is Kernel level debugging. When using the simple, green Debug Kit, I don't think these consoles had this. They only could debug at a certain level, which was the software being run, but not any lower than that. This is pretty much the ultimate debugger, and you can actually see that it shares the same basic chipset and interfaces through the LPC, albeit with LFrame attached. So what the HELL is LFrame, anyway? What is it's purpose when kicking the MCPX over to the LPC in a 1.6? Why does it enable debugging through the LPC? Why did the Debug Kits (DXT-1 &2) not have Kernel level debugging but the Development Kits (DXT-3&4) did? And what is the UART pin header for on this debugger? I need to be straightened out here!

In order to use the Super IO Kernel debugging unit, I will need to reconnect LFrame to the LPC/MCPX. https://xboxdevwiki.net/LPC_Debug_Port I seem to have pulled it off. I won't know for sure until I get the second resistor array for the debugger. I have so many overly rich, green parts to install and I am jonesing. This debugger needs to get done and these LEDs need to come in already. I am using molex connectors to attach the status LED wires, so that if I ever need to do work on the motherboard, I can just unplug the LED wires going up front and pull out the board. I don't know why there is fuzz on one of the molexes. I will learn to code for the Xbox... Oh yes... I WILL learn to code for the Xbox.

WTF would he SOLDER the chip to the LPC for? That is the dumbest, most pointless thing. The only thing I can think of is that you wouldn't want to even touch it if you wanted to change something with the chip or whatever and he wanted to make it difficult to do so so that you would send it back to them. Literally. That pisses me off. I keep hearing about these modding services and seeing results that are so much fucking worse than the work I would have done. Also... BT and D0 don't work on Aladdins yet, so I dunno what those wires are hooked up to.

https://www.prusa3d.com/en/cart/ - I found this color in PETG I believe and I think it matches the color better than the PETG I have now... That is the 6 LED clip I will be using. The color is WAY off and it WILL bother me. The above link is the only color that I think MIGHT be even close. What do you guys think? @dtomcat Added the comparison pic. It's 50 bucks because of shipping from England...

I laughed as I looked back on this post. I was such a tool even a few MONTHS ago. So I still love "HDD Ready" structure, but I understand the practicality of ISOs in many instances. I do feel comfy though when I'm able to just go into a folder and browse contents, kinda like going into "Program Files" on my PC like I have over all these years. Just makes sense to me. I talked with @lopenator about this a while back and I think he said it equated to some gigs in difference between ISOs and files. Like, 1.4TB to 1.7 maybe? I could be wrong. My question is, what else is really going to take up several gigs of space on a 2TB HDD (the most relevant capacity in this instance)? All the roms and emulators are already there. Maybe DVDs or music? I can't think of anything else...

You were correct. It IS this. Works perfect

Lol, I should have mentioned, @dtomcat Sent me this diagram. If I succeed, this guy gets credit for showing me the pinout.

I'll try to start going through the list this week and I'll start updating the document accordingly.

@arfows Yes, I remember saying that. It is a daunting task which will take time, however, I can load up a certain amount of games every day, really. Is this strictly for the Origins setup? Because I KNOW it doesn't have every game in it... Also, how far into the game are we trying to get? Just loading, or running it? Because beating the game obviously isn't practical. Are the errors just due to things that ACL patching cannot remedy, or other things? Do people know what they are?

I'm gonna try to tap into this on the "yellow cable" port.

Yes, the DVD drive is what I am wondering about. The HDD and LAN are in the Xecuter 3 install guide as well. This seems to be separate, however from the IDE activity signal.

From left to right: DVD Ready, DVD Activity, HDD activity, LAN activity. The DVD activity light is separated from the HDD activity light and DVD Ready light is present. How was this done? I know about the HDD activity signal, but that is handled on the right of this little custom housing. The left two LEDs are the ones I am wondering about. I assume it involves tapping onto the DVD ROM drive PCB. @KaosEngineer

Looks like the LED idea is gonna work fine. Now I just need my transparent, green resin.