empyreal96

(Forgot to add in last post and can't edit) I did decomp into IDA psudocode most functions in the 5933 Kernel, but I do need to go over it and learn how to improve ida's output.. This one is for AvpInitCurrentTvEncoder https://www.github.com/Empyreal96/xboxkrnl-IDA-decomp-test/tree/main/Functions%2FAvpInitCurrentTVEncoder.c Every other function is in the repo's tree

So I have been trawling old x-s forum mirrors, found the original 1.6 thread and there are a few bits of interesting info: https://xbox-scene.xbins.org/forums/index.php/topic,1215.0.html These symbols were extracted from the "latest" 1.6 kernel at the time of the thread, may be handy to look at: AV: Conexant TV encoder _Conexant_CCRegisters Conexant_CCRegisters AV: Focus TV encoder _Focus_MacrovisionHamp Focus_MacrovisionHamp AV: XCalibur TV encoder _XCalibur_RSM53Regs _XCalibur_RSMRegs _XCalibur_RSMRegAddr XCalibur_RSMRegAddr XCalibur_RSMRegs XCalibur_RSM53Regs And some I have stumbled across when looking at the 5933 Kernel: AvpInitCurrentTvEncoder //Not present in available sources AvSendTVEncoderOption I also found Yoshi's asm code for one of his first patches for the xcalibur TV encoder.. // Notes from his post in the x-s link // // "Info Encoder ID : 8A=Conexant , 0D4=Focus & 0E0=Xcalibur " // // "..you need to make a new init table to be able to launch this bios" // // "Support Xcalibur in kernal 5530 extract by Yoshihiro" // .text:80014899 ; --------------------------------------------------------------------------- .text:80014899 .text:80014899 loc_80014899: ; DATA XREF: sub_800148F0+8o .text:80014899 mov eax, ds:xboxkrnl_322 .text:8001489E test ah, 4 .text:800148A1 mov dword_800377F0, offset loc_8001487F .text:800148AB jz short loc_800148BA .text:800148AD push 0Fh .text:800148AF push 4 .text:800148B1 push 4 .text:800148B3 push 0E0h ;ID ENCODER XCALIBUR IN 5530 .text:800148B8 jmp short loc_800148E6 .text:800148BA ; --------------------------------------------------------------------------- .text:800148BA .text:800148BA loc_800148BA: ; CODE XREF: .text:800148ABj .text:800148BA test al, 20h .text:800148BC jz short loc_800148D1 .text:800148BE push 20Fh .text:800148C3 push 2 .text:800148C5 push 0A0h .text:800148CA push 0D4h ;ID ENCODER FOCUS IN 5530 .text:800148CF jmp short loc_800148E6 .text:800148D1 ; --------------------------------------------------------------------------- .text:800148D1 .text:800148D1 loc_800148D1: ; CODE XREF: .text:800148BCj .text:800148D1 push 3Fh .text:800148D3 push 1 .text:800148D5 mov dx, 80D3h .text:800148D9 mov al, 5 .text:800148DB push 0BAh .text:800148E0 out dx, al .text:800148E1 push 8Ah ;ID ENCODER CONEXANT IN 5530 .text:800148E6 .text:800148E6 loc_800148E6: ; CODE XREF: .text:800148B8j .text:800148E6 ; .text:800148CFj .text:800148E6 call sub_800146D1 .text:800148EB mov al, 1 .text:800148ED retn 4 .text:800148F0 For now I am not going to try make sense of this, still learning the basics of this, and just trying to info gather

That's interesting, especially as another thought on the rumour mill was M$ used old/binned chips, and iirc around the time of the 1.6 being spotted SiS chipsets weren't as popular Nice for linking that link, I'll give it a proper tickle later, I guess any registers in the link would be in the `xcalibur-regs.h` file in xbox-linux.. I think I'll try compare that with any that's in the code I have and see if I can make sense of it, I do know that the Xcalibur chip is present at 0xE0 (focus = 0xD4, Conn = 0x8A) but that is all I properly know yet

I'll keep that in mind thanks! Currently still on the digging theough many forums phase trying to compare any info with what I have code wise.. Recently saw someone theorizing that the Xcalibur was a rebranded Connexant chip as some av registers matched, but that could be coincidence/compatibility

Oh you diamond thank you! That's one of the files I was curious in finding

So I haven't been able to dig up much, a couple of files that could be helpful seem to be dead links (mainly .txt files saying certain things like the Xcalibur/1.6 I2C stuff) One thing I am slowly looking into is seeing if I can figure out differences in a 1.6 capable Kernel and the source tree as I have an idea on the functions needed, hopefully any av registers can be extracted, and maybe xbox linux could help? But with no real coding experience it will take some time to piece it together

I was likely gunna take a crack at it myself soon as finally got almost all the bits I need, I'm sure it'll be fine as I had to make a botch up AV cable/extender for another xbox

It's weird I stumbled across the same issue as the OP where upgraded HDD wouldn't boot any disks, not even cold booting an installer disk.. it was an old xbox softmod that I reformatted and setup in my 1.6 chipped, and I did use xbpartitioner with just the F drive.. Symptoms were it booted to the MS dash (so access to C was able) but whenever it tried to load any disk it would halt and start clicking, prior to this, in the old xbox it worked fine loading any disk.. so I think I can vouch with your xbpartitioner theory!

Ahh that's good to know!

I think shall look into the controller cable and the dvd cable to extend, I have several left over.. could be handy to have standard USB ports in ports 3 and 4 bit that can come later I need to avoid a no dvd bios ideally, the rig I'm setting up needs use of the drive when I swap it in I will have to have a ponder on the power supply scenario I think

Yeah I saw some power extenders on ebay, I thought making them would be the case, ideally 3x the size of the default cable.. it's for the inside of a rather large PC case I think I will fetch a few cables and join them up for the dvd power.. I couldn't find any internal controller extended cables, but I was thinking sourcing the cables from another broken console would do the trick for now One other thing, are there any known power supply units that are known to work with the xbox 1.6? I haven't got the tools to make an enclosure

Hopefully this will be an easy solution.. I'm trying to find extended cables for the insides of a 1.6: - DVD Drive Power cables - Gameport cable extention - PSU power into the mobo Ideally I wanna try find some premade cables/adapters.. but If it has to be a DIY jobby then tips would be much appreciated!

As we all know the Xcalibur encoder in the 1.6 Xbox, was Microshafts in-house built chip.. No public documentation or anything. I'm wanting to find bits and pieces of info that may be round from old dead forum threads, randome files etc.. Sadly I have no Reverse Engineering and little coding know how to be able to pick a newer Kernel apart, but I am thinking I may be able to dump some info from my 1.6 itself while it's running. So if anyone has any ideas please post here!!

Sorry to bump an old thread, but I just found this xbdm.rar file and then in turn found this thread It does seem to have some FTP code yeah, and some comments that state about its configured to connect to crusaders ftp when it's done.. so deffo a development stage of their tests.. Its buildable with no errors in the complex/4400 tree but I'm gunna have a better poke at it this week

For any Debug Kit users who may be interested, the initial update adding the Developer Kit Menu to Easy-Build is now up! Currently it supports the following: • Transfer files to and from the console • Update the console with the 4400 XDK Launcher (Requires XDK Launcher of any kind already set up with xbdm.dll) • Shortcut to install the 4400 XDK • Pop-out console to run Xbox CLI tools (e.g xbmemdump.exe) • Reboot the console from Easy-Build • Launch a debug logging session • Launch Yelo Neigborhood for Functions that provides I will slowly add features and incorporate more tools from the XDK to the DevKit Menu, for now its basic as it's in testing. Some info on the DevKit menu can be found on the repo's wiki. Repo for those who don't know https://github.com/Empyreal96/easy-build-xbox *I have only been able to test this on a 1.6b Retail Converted DevKit (So no 4400 Kernel support for me) but when I recieve the parts I will be able to test on a 1.2 xbox.. This *should* work with actual Debug Kits, but christ take caution as I have no idea on compatibility* Images are the DevKit menu and the 4400 XDK Launcher booted on my box