ROM Cooking! A Pain In The Ass!! Lets Put Are Heads Together

austinsnyc · 7th October 2007, 05:01 AM

ROM Cooking! A Pain In The Ass!! Lets Put Are Heads Together

well I got BuildOS to work up to the point of building the Defualt.hv and boot.hv and then it crashes. I got the Imgfs tools all the way up to the point of rebuilding the Nb and then I get "MSFLSH50" error so I feel like I'm banging my head back and forth for nothing. I know we dont need to remove bytes like we did with the Hermes but I need some help here!! Pof, Oli, Taz Someone help!!

pof · 7th October 2007, 05:09 AM

Using the ImgFsTools should be exactly the same as Hermes, except that in hermes the NAND block count was 0x200 and in kaiser is 0x800.

austinsnyc · 05:48 AM

OK so after thinking about this for a second we need to change the code to to dump and build at that block count correct? thats something i dont know how to do myself

austinsnyc · 7th October 2007, 07:08 PM

Anyone have any other thoughts on this?

donsaxena · 7th October 2007, 07:59 PM

dude that perceptive pixel thing is amazing. you developed that?

duttythroy · 7th October 2007, 08:25 PM

I'm pulling out my head here as well friend so near but yet to wait

austinsnyc · 7th October 2007, 09:03 PM

Quote:

Originally Posted by donsaxena

dude that perceptive pixel thing is amazing. you developed that?

I build them yes we have a whole team of software and optics eng... people that work with us. I am the one that builds the units, Lead production manager yes thank you it is the only true Multi-touch system on the Market today

tadzio · 8th October 2007, 04:22 AM

Quote:

Originally Posted by pof

Using the ImgFsTools should be exactly the same as Hermes, except that in hermes the NAND block count was 0x200 and in kaiser is 0x800.

There's another difference: the MSFLSH50 header is at position 0x800 rather than 0x200. That's why ImgFsToNb fails currently.

A new, Kaiser-compatible version will be available shortly.

Cheers
tadzio

duttythroy · 8th October 2007, 06:08 AM

Quote:

Originally Posted by tadzio

There's another difference: the MSFLSH50 header is at position 0x800 rather than 0x200. That's why ImgFsToNb fails currently.

A new, Kaiser-compatible version will be available shortly.

Cheers
tadzio

Great job ,thanks again

pof · 8th October 2007, 01:32 PM

Quote:

Originally Posted by tadzio

There's another difference: the MSFLSH50 header is at position 0x800 rather than 0x200. That's why ImgFsToNb fails currently.

A new, Kaiser-compatible version will be available shortly.

Thank you tadzio