WM 6.5 Kitchen QVGA and VGA Developer Edition - Page 361

**starmans** · #**3601** (**permalink**) 05-05-2009, 03:12 PM

Does anyone have a 21222 xip.bin for herman they could upload?

**Da_G** · #**3602** (**permalink**) 05-05-2009, 03:20 PM

Here's a good article on "Slot 1 XIP" vs. "Slot 0"

http://blogs.msdn.com/hegenderfer/ar...r-part-ii.aspx

note that it differs slightly for wm6.5 as theres more than one "Slot 1", which is what allows us to have more xip modules, which is what borks when you are using a non-native kernel, which is why you need to flatten some

XIP was truely intended for devices running NOR flash (older wm5 and pre-wm5 devices)

With NOR flash you can eXecute In Place.. thus not having to create a local copy in your device's memory.. saving (what was at the time) precious little ram..

**joojoobee666** · #**3603** (**permalink**) 05-05-2009, 03:25 PM

Quote:

Originally Posted by starmans

Does anyone have a 21222 xip.bin for herman they could upload?

I posted one a few pages back. But here it is again

Herman_21222_XIP.zip

rawdeadfish · #**3604** (**permalink**) 05-05-2009, 03:31 PM

Quote:

Originally Posted by CRACING

tried everything but still suck on 2nd splash screen.

- Used the WinCENLS_WWE from the source.
- Placed the WinCENLS_WWE in ROM/XIP but kitchen crashes by saying "Doesn't fit
- Used bepe's xip dumper and xipporter.
- Tried working XIP ( 21215 ) and device boots fine, that means the SYS and OEM are ok.

I tried all my ways.

Edit: I got it, Used the MSXIPKernel and MSXIPKernelLTK from XIP of Vogue ported and it worked. But I cannot figureout why does the MSXIPKernel and MSXIPKernelLTK changes in different ported XIPs of same build.

Can you provide more details of how you are doing this. I have an apache for vzw with bootloader 2.02 and i am having the same problem with 21501 build from the PPCK. First splash comes up, then the text in the lower part of the screen, then freeze.

I can build ROMS fine with 21198, but not the 21501. Where are you getting these files, where are you putting them, and when, and do you still build using PPCK? TIA!

**Getitnowmarketing** · #**3605** (**permalink**) 05-05-2009, 04:25 PM

Quote:

Originally Posted by indagroove

Try recmodding the dlls in the browsing folders that are posted here:
http://www.mediafire.com/download.php?zzmmdnm1jnz

That fixed 21222 sip issue for me

**da_reeseboy** · #**3606** (**permalink**) 05-05-2009, 04:29 PM

Quote:

Originally Posted by conflipper

anyone test out the 21221 build yet? I will try and do compare of 21221 vs 21222 today and tomw. i will have to see i guess.

had to format HD and do a fresh install, so still getting everything right.

Did I miss a post? Where is it?

krazy_about_technology · #**3607** (**permalink**) 05-05-2009, 04:34 PM

Quote:

Originally Posted by Da_G

Here's a good article on "Slot 1 XIP" vs. "Slot 0"

http://blogs.msdn.com/hegenderfer/ar...r-part-ii.aspx

note that it differs slightly for wm6.5 as theres more than one "Slot 1", which is what allows us to have more xip modules, which is what borks when you are using a non-native kernel, which is why you need to flatten some

XIP was truely intended for devices running NOR flash (older wm5 and pre-wm5 devices)

With NOR flash you can eXecute In Place.. thus not having to create a local copy in your device's memory.. saving (what was at the time) precious little ram..

Hey thanks for the link buddy, although i am got the bold point of the story, i am re-reading it again and again to grasp as as much as possible as well as searching for other content. This is really cool stuff

Now if that's the thing, i think we wont have these kinda problems on a device which comes preloaded with Wm 6.5 as the nk.exe must be natively built for WM 6.5 slot structure.