[Request] XDK Documentation and some info on my debug kit

So this is my Xbox debug kit i got of ebay im unsure of the DV number but i do know its a demonstration or showcase xbox something you would take to E3 and say "hay look at my new xbox game, yes its running on real hardware see there is the xbox right there" no development was ever really on these, they where just used for running unsigned debug code but as they are identical for the most part to the green debug kits with devs did dev on
"AV1" is my sticker the rest where on there when I got this xbox
https://i.imgur.com/esyNUfE.jpg
https://i.imgur.com/X83eMGy.jpg
I am unsure about the rules and best practices for posting serial number and other identifying information for XDKs so I blocked it out just to be safe.
https://i.imgur.com/WG13zZ8.jpg
As the xbox had already been opened befoul I got it, i had no qualms showing of the inside, even know theirs not much to show off. The hdd is slightly raised up because I replaced the hdd as the one it came with was slightly corrupted and dying so i just placed the old hdd on top for this pic (its meant to be upside down as well). Sadly it had been wiped befoul I got it so no cool dev games where hiding on the hdd
https://i.imgur.com/DiBDS9C.jpg
https://i.imgur.com/Td9kz89.jpg

OK so my story with this xbox is I bort it of ebay abort 5 years ago for cheap(like $80 I think) and at that point I was just curious if it was even real or a retail to XDK job. The seller did post pics of it working but I don't remember much more then that so at the very least I'd have a XDK of some kind real or fake. So it showed up and I when to plug it in but relied it was a NTSC-US debug kit, cool it was real, not cool that I live in a PAL region. The PAL or NTSC thing is not a issue as i have a chines tv that dose both the issue was the power supply. The us xbox needs110V 60Hz and what comes out of the wall at my house is 240V 50Hz so plugging it in without a inverter would set fire to it and I didn't want to buy a expensive inverter just for one thing so it got wrapped in plastic and stored until abort a week ago. I had another xbox of mine that started to have power issues that turned into a mother board issue so long story short I now had a spear xbox 1.1 version delta branded power supply and lucky for my the debug kit also has the same branded power supply. Now this psu is awesome because from the factory input voltage could be either 110 or 240 depending on a few components in the psu but the wiring was the same to the xbox so it was as easy as dropping this spear psu into my debug kit and bam no fire and I have a working debug kit... well almost I now find that it did not boot properly and the stock content on the HDD wouldn't run and anything I coped to it over the xbox neighborhood would not run either and it took ages to copy anything to the xbox so I stupidly ran the 1.0.5933.0 network recovery and that fixed the samples not working but it was still really slow and the hdd didn't sound that grate so i put a "new" 20GB HDD but then i relied that 1.0.5933.0 wasn't official released to 3ed part devs and that was outside the scope of what I have planed for this xbox so i downgraded to 1.0.5843.1 and i have that working fine even the debugging code from VS 2003 strate to the xbox even works now
So a few things I have learnt from this then ill get on to the project and my request.
Not powering on a xbox for more then 5 years is always not a bad idea and the XDK is no exception.
Changing the HDD is a stupid simple job just put in any IDE HDD 10GB or bigger make sure its set to cable select put a XDK recovery disk of your choice, even burnt non legit ones worked and reboot the xbox so it boots of the disk and the xbox will run the recovery and your right to go.
You can upgrade and downgrade the XDK version as you please, from a dev point of view this is a grate idea but i didn't expect it to work.
You can fix the later model XDKs with retail parts as that are more or less the same thing. Just double and triple check your pin outs and voltages.
I think this xbox as always murdered HDDs as if the sticker on the top is anything to go by the HDD labeled XDK was it's 3ed and my hdd replacement is its 4th so i will need to keep a eye on this
(Original from factory eather a Segate or WD then it had a WD HDD replacement and a upgrade to 1.0.3944.? and the hdd that it came with marked XDK is a Seagate so that's either it's 1st or 3ed HDD)

Ok so what am i going to do with this XDK, i'm going to make a game of course >__<
The idea is to make a xbox game with the same tools and software that a dev back in 2003 would have used. the reason for 2003 is so I can use VS 2003 and windows xp instead of VS 6 and windows 2000.
And this brings me to my request, i have no idea how to program for Direct3D or the xbox in genial I do have some C and C++ experience but not enough to just start coding everything from scratch.
I have some of this game planed out and i have made games befoul but this post is already to long to go into detail abort it.

So yes to the hole point of post out side of showing of my native PAL XDK is I need the documentation that comes with the xbox dev kit and anything else like software disks that would of came with a dev kit xbox and or this xbox. As im trying to make a game with the same tools from back in the day so i documentation from back in the day. I couldn't find any from my googleing I only found openXDK stuff with is not what a legit dev from then would of used and xbox one xdk stuff with doesn't help either. The only tutorial I could find for the official xdk was from here http://www.xbdev.net/tuts/tuts.php and that doesn't seam to be 100% compatible with the 1.0.5843.1 XDK (the tutorial calls a bunch of header and cpp files I don't have)
so yeah documentation for the dev and debug kits and how to program for them and a 1.0.3944 xdk setup and recovery to mach the sticker on top of the xbox would be awesome.
Thanks heaps for reading this long ass post I hope you learned a little and I hope that someone helps me out and i can learn how to program for this thing ^__^

 

@XboxSurgeon looks like your live debug console.

 

Yeah really close. Mine sais debug on the bottom instead of prototype and hes has a better name >__< mine is just called X16 and by the dates on mine are a lot early like weardley enough before the date codes of some the green debug kits I found online ? but by the X16 on the front I have a feeling that my is part of a set for testing a network multiplayer game like halo but not halo as it dose not have a blue and wight MS barcode sticker thing.
This date thing has got me intrigued. So doing a little math my dev xbox pre dates the launch of the xbox by a month and 9 days so it could of also been used as a demonstration unit at the launch event of the xbox but I can't quickly find any info the the launch even for the og xbox as google things I mean xbox one -__-' but yeah if anyone know if theirs a list of useful build dates of xboxs that be awesome soI can get a better idea on where my xbox sits in the timeline / history of xbox or some pictures of videos of the xbox launch event. thanks guys

EDIT: Yes I know xbox live came out a full year after the xbox had launch heance the late date on XboxSurgeon's prototype

 

Its likely just a black debug kit. Many pre-date launch, which is why they say prototype (they werent approved by the FCC and co). They are uncommon, but not all the desirable (one was just on Ebay).

If there was anything special, it would have been in the software, which is now lost so. 3944 isnt an internal dashboard though, so I doubt it.

 

Hmm, granted it isnt as flash as a green debug or a crystal dev kit but you would hold value as a pre release console perhaps? Personally i find these pieces (prototypes) really interesting.

 

No, because there are plenty of debug and dev units out there that also say prototype. The hardware inside is final, so it's just a sticker difference, and with the issues you've had with it that doesn't help. If it was a Dvt3, it would be actual prerelease hardware, but they weren't made in black (or green)

 

Yeah mine said prototype. No debug decals on mine sadly.

 

Thanks guys for the info ^__^ So yeah i'm going to keep using it as a dev kit to make games now as it nothing special but still cool to have.
I will be keeping the og HDD as maybe one day i can work out how to do a remnant data scan on it but i don't have height hopes for that.
I have manage to turn up 4361, 4627, 5558, 5659, 5788, 5849, 5933 version of the XDK and i have tested the last 2 but still waiting on the rest of the XDKs to download to test them out just for lulz.
I still need documentation or at the very lease some more tutorials that ant OpenXDK, I found 3 docs on hear (sorry i cant remember from ectaley who) but yeah its now where near enough docs so yeah still need to find thous

 

I think it's cool because it's a black debug kit, and the sticker on the bottom has JK for some reason. Also the XDK-2K on the motherboard, I wonder what the 2K stands for.

 

Yeah I think JK is cut of by the "Do Not Remove" sticker... I'M not going to remove the sticker though. The 00008 of the the left is interesting as well.
And yeah I know the sticker on the motherboard has something to do with what version of bios and some other config info that it left the factory with or what the last service employee did to it but yeah I would like to know more abort it too hence posting it

 

Fun side note: I'm currently doing some research into how to TSOP flash xboxs as I have always just made my own mod chips in the past but it cost money in parts and TSOP flash is essentially free. And I would expect this for dev kit consoles as the XDK recovery flashes the bios but the R7D3 point seams to have a 0Ω resistor from my picture with means the bios flasher in heXEn might work but i'm not going to do that, i was just surprised the soler point was in the same spot, when I get home ill check the other solder points and see if I can get BIOS checker to run on it for lulz

 

Yes, the recovery disk reflashes the bios and the flash points are enabled.
Be aware that this mobo can't use a retail bios as it's MCPX chip is an MCPX II
Retail xboxes had an MCPX III chip with a 512 byte rom that replaces the top 512 bytes of the Tsop.
Further, your unit should have 128MB of ram instead of the usual 64MB. All ram chip locations should have a chip.
The xdk install on pc have some tutorial program's and a help that describes all possible functions.
Programming the direct3d should be pretty equal to the direct3d for pc from that area.
Further, there is source code available for some existing xbox games. They could be a guidance as well.
You don't need a devkit for an xbox game. A program called phoenix bios loader can load any bios from the harddrive, including debug biosses. It can turn a retail unit into a devkit. The only difference is the amount of memory. Obviously, you also need the debug dashboard files on your E drive.

 

Yeah I figured that all of the solder points for a retail TSOP flash do have 0Ω resistors on this dev kit and any of the retail flashing and dumping tools would work but i'm not going to do it.
And yeah mine has the full 128MB of ram with is rear for rare for a black demo kit .
I have built a retail to dev kit xbox in the past but with the 64MB of ram all the debugging tools don't work that well.
Yeah I found a boat load of of sample code in the SDK but no real tutorials.

 

A tutorial from "Hello World" to a full functional game isn't there. There do exist a port of sdl 1.1.
Depending upon what you intend to create, it can be a good start.
I used it to port cannonball to the xbox 1 and it worked out pretty well.
I had some issues with the boost c++ library as the default 64KB stack space wasn't enough for it.
I remember seeing a website once with a pretty good tutorial, but I can't find it's link anymore.
If you intend to create something 3d, sdl is not what you are looking 4.

 

I haven't even found a traditional "Hello World" tutorial (eg text rendering) just the hears how to set up Driect3D and draw one polygon
But there is enough sample code for most of the features of the xbox even a fulley "functional" game to work it out its just a pain.
SDL sounds interesting but depends on when it was ported my restriction for this project is to make a game for the xbox with only the tools a dev would of had in late 2003 (mainly that date so I can use xp instead of win 2k).
Yeah most of the original xbox links all got crushed by google when the xbox one came out -__-' so trying to find anything is a real pain, wayback machine is your friend but you have to find the url first and that's half the problem .
Your port sounds interesting but aging, can't find it on google -__-.
Yeah I have plans to make a platformer as I can port that to a bunch of consoles with I want to have a go at developing for this year, there arnt many platformers I know for for the original xbox and I thing a 2.5D one would be kinda cool. And a 2D one would a under utilizing the xbox .
but I should start at SDL as I know that runs on a bunch of stuff but yeah I only have a little experience with that as well but at lest I can still find info abort how to program for SDL.
Thanks for your help man ^__^

 

add "-360 -one" to your google search terms, e.g., "xbox -360 -one xdk programming tutorials". It helps to filter out some of the riffraff.

 

Hard drive is from July 2001 and memory chips from week 30 of 2001 which would put it at the last week of July 2001. So this was built late July or early August 2001, I have one from April. I'd just keep it to the side and tinker with another debug / development kit.

 

Earliest software for them is August 2001. Prior to that is beta hardware.

 

Did you take out the clock capacitor yet?

 

Thanks for the info Syclopse I'll have to save it and keep it with the xbox... It's interesting that the HDD with the XDK sticker on it dates the same time as when the xbox was made. so as that XDK HDD is kinda fucked, i'm guessing that the HDD was formatted and replaced with the western digital HDD from the sticker on the top of the xbox at around may 2003 going by the XDK launcher that it came with (5514) then when it was sold or liquidated or whatever that took the replacement HDD out and put the old broken HDD back in.
Whats you though on keeping it to one side and tinker with another debug / development kit. I don't have another debug kit to mess with right now and from my reading into this debug kit is rare but least rare out of all the debug / development kit and not particuley sort after or worth much and i'm not using the original HDD did keep the old PSU so i think its safe to use just for software development and debugging.
And no Forlorn I have not, it's tested and working fine right now and apart from the HDD and PSU everything is in really good shape / original so I don't really want to start tearing things of the motherboard if I don't have too.