Custom roms *no kitchen or anything like that* - Page 3

pdub310 · #1 (**permalink**) 10-26-2007, 02:35 PM

When I use BuildOS, I get the error: The system cannot find the file specified. On the program window at the bottom in the status bar it shows: Error, last status "Creating registry". Does anyone know how to get around this? Im lost for the moment.

gzub · #2 (**permalink**) 10-26-2007, 02:43 PM

It took me a while to hunt that one down... I recommend using sysinternals filemon.exe when you get an error in BuildOS, it gives you great clues as to what might be missing or causing issues...

You either need a directory called tools where buildos is running (or the various tools in the path - rgucomp probably in this case) and you need a directory called ROM/XIP with the boot.rgu in it.

Hope that helps,

Geoff

**no2chem** · #3 (**permalink**) 10-26-2007, 04:35 PM

To anyone thinking about porting XIP from other devices - this isn't exactly a matter of copy and pasting nk.exe and dlls, or even taking the xip.bin from other devices - its a lot of work, as you need to change memory spaces around. I would recommend importing the XIP section from the kaiser, as the device is similar enough to ours - to start you would need IDA - which isn't free might I add - the demo should suffice though.

**dcd** · #4 (**permalink**) 10-26-2007, 10:41 PM

Quote:

Originally Posted by no2chem

To anyone thinking about porting XIP from other devices - this isn't exactly a matter of copy and pasting nk.exe and dlls, or even taking the xip.bin from other devices - its a lot of work, as you need to change memory spaces around. I would recommend importing the XIP section from the kaiser, as the device is similar enough to ours - to start you would need IDA - which isn't free might I add - the demo should suffice though.

ive attempted to boot my titan using the kaiser's and the hermes' xip with no success. My understanding was that we cannot modify the xip or its contents without manual table editing. what is IDA, and if the xip from the kaiser would suffice, why would any modification of it be necessary?

if you can point me in the direction of where to get started with 'moving memory spaces around' i am willing to put the time in to do the editing by hand. glad to see someone respond with more knowledge than myself about porting from another device.

**no2chem** · #5 (**permalink**) 10-27-2007, 12:04 AM

Quote:

Originally Posted by dcd

ive attempted to boot my titan using the kaiser's and the hermes' xip with no success. My understanding was that we cannot modify the xip or its contents without manual table editing. what is IDA, and if the xip from the kaiser would suffice, why would any modification of it be necessary?

if you can point me in the direction of where to get started with 'moving memory spaces around' i am willing to put the time in to do the editing by hand. glad to see someone respond with more knowledge than myself about porting from another device.

If you're interested in messing with the XIP section, check in and around XDA-Developers - if you're cooking your own roms, you've probably done this much already. You should know how to hexedit - and probably know some assembly. x86/CISC type assembly should be enough to get you by, but arm assembler knoweldge would be helpful. (note: ARM is 4-byte word aligned, 32 bit! - LITTLE ENDIAN!)

some background - if the DLL is XIP, CE guarantees it will run at a certain load address, so theres no point in putting the base relocation table in the dll when the image is built. When you extract the XIP sections, the files just contain the actual code - the DLL expects to be run from a certain location. You need to recreate this table and such so the DLL gets loaded at the right addresses (or loads stuff from the right addresses!)

Theres a document that describes this somewhere - i think i can find it for you if you're still interested. Oh yeah, IDA pro is a disassembler.

**dcd** · #6 (**permalink**) 10-27-2007, 01:40 AM

Quote:

Originally Posted by no2chem

If you're interested in messing with the XIP section, check in and around XDA-Developers - if you're cooking your own roms, you've probably done this much already. You should know how to hexedit - and probably know some assembly. x86/CISC type assembly should be enough to get you by, but arm assembler knoweldge would be helpful. (note: ARM is 4-byte word aligned, 32 bit! - LITTLE ENDIAN!)

some background - if the DLL is XIP, CE guarantees it will run at a certain load address, so theres no point in putting the base relocation table in the dll when the image is built. When you extract the XIP sections, the files just contain the actual code - the DLL expects to be run from a certain location. You need to recreate this table and such so the DLL gets loaded at the right addresses (or loads stuff from the right addresses!)

Theres a document that describes this somewhere - i think i can find it for you if you're still interested. Oh yeah, IDA pro is a disassembler.

ive gathered most of this on my own but its nice to have someone confirm. i pretty much meet all the requirements except assembler knowledge. i noticed in an older thread where verizonguy mentioned he had taught himself to update the module locations via hex, and it appears he has successfully ported aku 0.7 to the apache - which its my understanding is not as close a match to the kaiser as our titans.

im still interested and im looking for ida pro. if anyone else is working on this, it would be nice to have a few people together on this project. i've seen others "run aku 0.7" on the titan, but it was in 0.2.3 xip, which really doesnt interest me. im far more interested in core os modification than in throwing OEMs at a rom. im pretty well done with my clean rom, and im focusing all my time on the xip now. any reading material you can link me would be helpful, but ive been scouring xda til my eyes hurt lately.

thanks again for the insight

**no2chem** · #7 (**permalink**) 10-27-2007, 01:46 AM

Quote:

Originally Posted by dcd

ive gathered most of this on my own but its nice to have someone confirm. i pretty much meet all the requirements except assembler knowledge. i noticed in an older thread where verizonguy mentioned he had taught himself to update the module locations via hex, and it appears he has successfully ported aku 0.7 to the apache - which its my understanding is not as close a match to the kaiser as our titans.

im still interested and im looking for ida pro. if anyone else is working on this, it would be nice to have a few people together on this project. i've seen others "run aku 0.7" on the titan, but it was in 0.2.3 xip, which really doesnt interest me. im far more interested in core os modification than in throwing OEMs at a rom. im pretty well done with my clean rom, and im focusing all my time on the xip now. any reading material you can link me would be helpful, but ive been scouring xda til my eyes hurt lately.

thanks again for the insight

Yes, updating the module locations is pretty much.. almost all you'll need to do.

http://www.hpcmonex.net/izemize/docs/reloctutpack.zip

is the link. good luck?...

pdub310 · #8 (**permalink**) 10-26-2007, 07:36 PM

thanx gzub.. worked like a charm..

**ImCoKeMaN** · #9 (**permalink**) 10-27-2007, 01:48 AM

Verizonguy didn't port aku 0.7 to the apache he is doing more the "run aku 0.7" thing. The new kitchen from helmi for the apache will have aku 0.7 and proper xip for it. We may see something similar for titan.

**dcd** · #10 (**permalink**) 10-27-2007, 11:28 AM

Quote:

Originally Posted by ImCoKeMaN

Verizonguy didn't port aku 0.7 to the apache he is doing more the "run aku 0.7" thing. The new kitchen from helmi for the apache will have aku 0.7 and proper xip for it. We may see something similar for titan.

thanks eric.

and whats 1.40-olimax?