latest findings

radu_moisan,
can you tell me What is written on the RAM chip?

Well, at this point I can't tell for sure about what and where. Config.bib file might give you a first look but keep in mind that address space is virtual so as long as we are not sure how PA-VA is mapped we cannot make assumptions about what might be loaded in RAM. The source files have a lot of #ifdef's and is hard to follow in some sections. But I have a good feeling about RAM being at PA 0x30000000 and mapped as VA at 0x80000000. Considering your question is about Win image and not bootloader, I assume RAM will contain some space reserved for Applications (App cotext) and some for kernel library (like Xip/nonXip DLLs) but could be also other components of Win image.

Anyway, I rather not jump into any conclusion yet since I still have a lot to digest concerning this issue.

radu_moisan wrote:Well, at this point I can't tell for sure about what and where. Config.bib file might give you a first look but keep in mind that address space is virtual so as long as we are not sure how PA-VA is mapped we cannot make assumptions about what might be loaded in RAM. The source files have a lot of #ifdef's and is hard to follow in some sections. But I have a good feeling about RAM being at PA 0x30000000 and mapped as VA at 0x80000000. Considering your question is about Win image and not bootloader, I assume RAM will contain some space reserved for Applications (App cotext) and some for kernel library (like Xip/nonXip DLLs) but could be also other components of Win image.

Anyway, I rather not jump into any conclusion yet since I still have a lot to digest concerning this issue.

I do not mean it , I just want to know What is written on your RAM chip On the mainboard,such as "NT5DS32MXXXXX"..

Hi Admin,
I would gladly tell you the chip number of my ram but the thing is, I slightly modified my case to route out the UART connection and is quite difficult for me at this point to open it. If it's of big importance this number let me know and I'll make time for it and open the case.

With concern to my latest findings, I've been trying for the last couple of days to compile a WinCE 6.0 image. The problems I'm facing at this point are with regard to display - it seams to be incomplete. The folder ..\SRC\AK_PRIVATE\DRIVERS\AKDDK contains the following folders:

DDK_2D
DDK_CRITICAL
DDK_ENCODE
ddk_mem
ddk_reg
DLL

whitin which the first three are empty and are included in build path. The error I get is with regard to ANYKA_DDK_2D.lib which seams to be missing. Do you have any knowledge about this library.

PS: the lib directory should be
%_WINCEROOT%\Platform\%_TGTPLAT%\lib\ARMV4I\debug\ or
%_WINCEROOT%\Platform\%_TGTPLAT%\lib\ARMV4I\debug\
in my case is
C:\WINCE600\platform\AK780X\lib\ARMV4I\debug\

This library might not be the only one missing, the build stoped, so I can't tell.

Thanks.

radu_moisan wrote:Hi Admin,
I would gladly tell you the chip number of my ram but the thing is, I slightly modified my case to route out the UART connection and is quite difficult for me at this point to open it. If it's of big importance this number let me know and I'll make time for it and open the case.

NO importance, no importance, I just suspect that there are not a real 128m version machine that its price is less than 100 dollars.

With concern to my latest findings, I've been trying for the last couple of days to compile a WinCE 6.0 image. The problems I'm facing at this point are with regard to display - it seams to be incomplete. The folder ..\SRC\AK_PRIVATE\DRIVERS\AKDDK contains the following folders:

DDK_2D
DDK_CRITICAL
DDK_ENCODE
ddk_mem
ddk_reg
DLL

whitin which the first three are empty and are included in build path. The error I get is with regard to ANYKA_DDK_2D.lib which seams to be missing. Do you have any knowledge about this library.

Thanks.

I will go looking for what is lost.

With regard to your suspicion over RAM size I can tell the looking trough code I noticed that they work with only 64M but I though it might not be of real interest at driver level and maybe Windows will handle the rest by itself. But maybe you are right.

hi，radu_moisan

due to my friend, this may take a few days to get lost files. don't worry,Do something else code first.

hi，radu_moisan

some code don't be open by anyka,but anyka provides some libs as an alternative.lucky,I get them. there are all libs file. just put them in \AK780X\lib\ARMV4I\retail\

get all libs from:

https://mininetbooks.forumotion.com/knights-club-f2/all-libs-of-wince-bsp-t25.htm#141

thanks admin, that's all I need... hopefully

...and finally I managed to build successfully, but without multimedia support. I haven't tested it yet though. Hope I'll do that today and if successful then I'll share this first build with you guys just to have a WinCE 6.0 fill and look on our gadgets

radu_moisan wrote:...and finally I managed to build successfully, but without multimedia support. I haven't tested it yet though. Hope I'll do that today and if successful then I'll share this first build with you guys just to have a WinCE 6.0 fill and look on our gadgets

a big step !!

Is there a good power management system in ce6 allows us to increase battery life?

Hi Admin,
I don't have prior experience with WinCE 5.0 so I can't tell much from my experience, but as I documented on the net, it seams that WinCE 6.0 introduces a lot new features mainly focusing on faster responsiveness from OS and application layer. Another feature implemented is to support user mode drivers which means we can add drivers on the fly. As far as the power management goes I can't tell much, I suppose it should be at least as good as it was in WinCE 5.0

I tried to boot up with my new build image but no luck so far - it hangs in Anyka logo screen at startup. Eboot seems not to work at all, so I tried with the old eboot, producer and nboot, only changed the xip, but still no luck. I wil brainstorm further on this

radu_moisan wrote:I tried to boot up with my new build image but no luck so far - it hangs in Anyka logo screen at startup. Eboot seems not to work at all, so I tried with the old eboot, producer and nboot, only changed the xip, but still no luck. I wil brainstorm further on this

if 128m version xip load failure, try to build a image of 64m ram version.

Hello guys, I thought to post some comments about my latest work. I haven't reached any important milestone unfortunately but I did progress.

First of all I think Admin's suspicions about having 64M RAM are correct. Phisical RAM is only 64M but can be manipulated in configuration and exposed as 128M (with the rest of 64M residing on FLASH).

I manged to build a variety of OS's ranging from a typical PDA platform to a thin client version (with or without debug enabled or other memory constrains enabled or disabled). The bad news is that all this images won't boot neither on real hardware nor on WinCE Device Emulator. My suspicion is that configuration is not consistent with regard to memory layout. In other words I think startup code is never reached. This happens both for bootloader and OS.

I still have my doubts about what exactly nboot does and what producer does. Producer image is based on the same template as eboot but still is a lot shorter, so a lot of functionality is removed. I can tell for sure that Producer has no partition designed to retain it in nonvolatile memory so it must run in RAM, but then I don't see the point in running it at all, because with BurnTool all necessary images are downloaded. I also noticed that producer and eboot have the same run address in RAM, so again I find no practical use for Producer image. Having all that being said, I must mention that Producer and eboot and not 100% identical (considering the eboot code inherited by producer).

Anyway, I don't anticipate problems with drivers so eventually I think I'll be able to boot something I'll start with fixing the bootloader.

just to put some numbers, maybe someone may come with additions, memory mapping is as follows:

.......(VA)........|.........(PA).........|........Obs.
0x80000000..|..0x30000000..|..(128/64MB)RAM
0x88000000..|..0x20000000..|..1MB on-chip ram or flash
0x88100000..|..0x08000000..|..1MB on-chip ram or flash
0x88200000..|..0x48000000..|..1MB on-chip L2 cache
0x88300000..|..0x70000000..|..1MB USB
........??..........|..0x10000000..|..2GB flash (not 100% sure)

RAM space is further divided in partitions and reserved areas. Coming up soon ...

I think, this is usefull for you!

http://hpcmonex.net/romstuff.htm

The ROM Dump Programs are working well! :-)

Regards
J.

taken into consideration. Thanks juergen.

And finally ... I've just booted WinCE 600 on my Anyka Netbook Unfortunately it's just an empty image and it would make no sense to share it with you guys yet (and so far I can power-up and boot successfully only by plugging in the usb, it also happens with WinCE 500 - pressing the power button it gets me stuck somewhere in the bootloader). Anyway, for me it is a big step, and I thought to share with you. I'll keep doing what I do and keep you posted. If someone is doing the same thing please share your thoughts . Soon as I have a bootable image (from the power button) with some basic applications loaded and working I'll post that xip right away.

Until next time .... take care.

Radu

radu_moisan wrote:And finally ... I've just booted WinCE 600 on my Anyka Netbook Unfortunately it's just an empty image and it would make no sense to share it with you guys yet (and so far I can power-up and boot successfully only by plugging in the usb, it also happens with WinCE 500 - pressing the power button it gets me stuck somewhere in the bootloader). Anyway, for me it is a big step, and I thought to share with you. I'll keep doing what I do and keep you posted. If someone is doing the same thing please share your thoughts . Soon as I have a bootable image (from the power button) with some basic applications loaded and working I'll post that xip right away.

Until next time .... take care.

Radu

!!!!!!!!!!! today is radu_moisan day !!!!!!!!! windows mobile 6 is upon earth.

Thats excellent news. Im still trying to recover mine as it wont boot. All i get is 3green lights flash when i press the on button.

It happens to me to with WinCE 600 when I press power button, and I investigated it in serial output and it seems it does not pass the bootloader stage, and I mean it doesn't reach the point in which it loads the WinCE image. That is because, in my case the power goes down immediately after I release the power button. It works though if I hold the power button pressed or if I plug whatever usb cable(so it can draw power from it). Anyway, in your case I think the nboot.nb0 is not the wright one. Producer.nb0 doesn't make sense to be the problem since it does pretty much nothing at boot time(it handles .nb0 files download and partition manager for flash), but eboot.nb0 on the other hand might be with problems because is the one calling the start-up functions for WinCE. Check if you have the proper board for V1.90 rom files, it should work, in my case worked from the first try. If you have other board try with the other versions available form CMN

radu_moisan wrote:It happens to me to with WinCE 600 when I press power button, and I investigated it in serial output and it seems it does not pass the bootloader stage, and I mean it doesn't reach the point in which it loads the WinCE image. That is because, in my case the power goes down immediately after I release the power button. It works though if I hold the power button pressed or if I plug whatever usb cable(so it can draw power from it). Anyway, in your case I think the nboot.nb0 is not the wright one. Producer.nb0 doesn't make sense to be the problem since it does pretty much nothing at boot time(it handles .nb0 files download and partition manager for flash), but eboot.nb0 on the other hand might be with problems because is the one calling the start-up functions for WinCE. Check if you have the proper board for V1.90 rom files, it should work, in my case worked from the first try. If you have other board try with the other versions available form CMN

Thanks for the info, i really need to start looking into this project

Thanks for your work radu_moisan. Any luck with porting WinCE 6.0 onto the machine? I recently purchased a similar model (rebranded by VisualLand) that's running WinCE 5.0, but I'd like to get WinCE 6.0 running on it. Most of the discussion threads have been dead ends. Hopefully you can provide your latest findings or a link to a solution/discussion. Thanks in advance.