Future WinCE 6 images

Hello,
for updating current NetDCU10 (N10) with new model NetDCU14 (N14) in our developments, we would like to have at least same functionality and compatibility as far as possible betwwen both CPUs.
For it, we have flashed N14 with WinCE 6 image from download area, to compare functionalities.
Until now, we was using N10 with WinCE6 and CF2 inside, perfectly working (even with WZC for wifi recently added to latest N10 image).
After flashing N14 and testing this available image, we see several differences not implemented yet. We know this images are currently under development, but we'd like to list some of the functionalities that could be working because it does not seems a driver problem, but some other problem maybe.
- RAS dial connection seems not be supported properly (i.e: properties of modem connection created are different and not all options appears to change them), but we dont know why.
- CF2 or CF3.5 seems not to be compiled inside any WCE6 image available for N14, will be in the future?
- Some colors of our application seems not to be working properly on N14 and WinCE 6 (N14 have 2 bits more for RGB color resolution, but it must be transparent to us with our older carrier design for N10 (this bits are LSB), so it must show same colors to our understand..., or we are wrong ?

And one more suggestion:
why not implement a general "logo" text saying something like "booting..." or "initializing..." or "please wait..." inmediatly after power of CPU system, in order to know that CPU is booting operative system? this could be applied to any general (not customized) image of your CPUs portfolio.

Thanks for support.

Hello,
we need really CF2.0 as we have in NetDCU10 image, because would like to replace this CPU for the new NetDCU14 and all our project are implemented in CF2.0 under VS2005.

On the other hand, we have tested again RASDIAL and its seems to work OK in current WinCE 6 N14 image. The only issue to be corrected by F&S is that new RAS connection is created on COM1, but this port is busy by debug, so connection created can not open port, we modify register for Hayes to PORT = COM2: as you have in other CPU kernels, and it works.
Can do same in next WinCE 6 N14 image, please?

And last, we does not undertand why we have some different colors showed on screen for same HW and bits used in N10 vs N14, we understand that 2 more RGB bits, "offers more colors", but maintains the existing ones? have we can solve this without modifiying HW ?

Can you explain what it's a PSD file and how it's "installed", it's considered a image kernel customization or it's only a file necessary?

Thanks.

Quote from "fs-support_ZU"

Hello,

Ok, that is no problem we will provide you such an image in KW51/2012..

Perfect, thank you for it.

Quote

Which register path? Is it a problem for you to do these registering by yourself?.I think you have to set a lot of personal settings?

No, what we can not understand is why creating a RASDial connection from control panel WinCE 6 current image, only allows to create it on port COM1, that is used by debug by default, while in other CPUs images is created on COM2 by default, that it's the correct one because its free. We can modify by ourselves

Quote

Can you provide me a connection list "NetDCU-LCD"?

Our current LCD 5.7 TFT is a 18 bits RGB color display (262K). We discard then lines R0-R1, G0-G1, and B0-B1 (pin1 to pin6 of J3) for new NetDCU14 CPU (not connected/routed), because they are LSB bits and to our understand, they are not necessary to have same color range than with NetDCU10...

Quote

Only a file is necessary. You can install PSD file via "NetDCUUSBLoader" or "NDCUCfg". PSD file contails all bootlaoder settings and boot display information. You can show a fix bitmap immediately from power on. For details contact <!-- e --><a href="mailto:sales@fs-net.de">sales@fs-net.de</a><!-- e -->.

OK, we'll contact with sales department.

Quote from "fs-support_ZU"

Hello,
please confirm:
1. RASDAIL, following should work for modifiy the port:

Code

1. reg open \ExtModems\HayesCompat
2. reg set value Port string COM2:
3. reg set value FriedlyName string "Hayes Comp. on COM2:"
4. reg save

Yes, its works, it's exactly what we do manually to have rasdial working in N14 and WinCE6, but we wonder why to do it manually if this configuration could be included by default in the future kernel, because now COM1: can not be used without deactivating debug.

Quote

2.LCD:
What do you mean by "discard the lines". Please connect all lines (NetDCU10/14 ColorX -> LCD ColorX ).
In the very worst case connect NetDCU14 R5 also to LCD R0 and NetDCU14 B5 also to LCD B0 and let NetDCU14 R0, B0 open, this should deliver the same result as NetDCU10. But connction of all lines should give you the best result.

With N10 and our current LCD display, we connect directly lines between N10 and LCD, because both use 6 lines for each color (R0-R5),(G0-G5),(B0-B5). Now N14 add 2 more bits to each color, so for connecting to same LCD, can you specify then where to connect new lines R1-R0, G1-G0 and B1-B0 ?

This is our connection schema:
LCD________ N10 _________ N14
--------------------------------------------------
R5 --------------> R5 --------------> R7
R4 --------------> R4 --------------> R6
R3 --------------> R3 --------------> R5
R2 --------------> R2 --------------> R4
R1 --------------> R1 --------------> R3
R0 --------------> R0 --------------> R2

So we have R1 and R0 of N14 without connecting to LCD (open).These pins are new in J3 of N14. Same situation for other two colors (Green and Blue)
Can you tell us where to connect this pins R1 and R0 for correct result colors?

Thanks.

Quote from "hpb"

Hello again,
RAS: I understand your intension but would like to retain this value as it is for the standard kernel. Some customers may already use this on other FSS5PV210 boards or even on NetDCU14 (with disabled serial debug line). Is it a problem for you to add these few register lines to your "personal registry setup"? I think you use a batch file to do the personal settings?

Sorry, but it's not the COM2 the only that support RTS and CTS lines for modem/Rasdial? That what we use in N10 and in this board is not neccesary to modify anything form standard kernel to create a rasdial connection working from factory configuration. Obviously, we have a batch file and we'll modify it for working rasdial.

Quote

LCD: please refer the latest NetDCU14 HW documentation. On J3 is also a 18bit RGB interface available (J3.7 - J3.40 on NetDCU14 is same as J3 on NetDCU10).

Yes, and this is the problem, connecting same 18 bits lines, extra lines J3.1 - J3.6 of NetDCU14 left open... and some colors of our application are not show correctly on LCD, but most of them are ok, Why?...dont know.

Yes connection is right (verifying datasheets, R7 of NetDCU14 is the same physical pin than R5 of NetDCU10 ...) and using same carrier board for both CPUs, colors only fails with NetDCU14.
The problem could be maybe we does not have latest Nboot/Eboot, I will confirm soon.
Thanks.

Hello,

last kernels launched did not include CF2 from too many time ago, can you include CF2 in the next WinCE6 kernel core release for NetDCU14 ?

On ther other hand, about my first question in this thread for including some default bmp logo while booting kernel, is clear that you need to know which display will be connected previously to show this logo "properly", but in the same manner, after booting winCE6/7 from factory, normally F&S determines a default display parameters and resolution (now in NetDCU14 is 800x480), that could be OK for some customers to start using their HMIs initially, without configuring anything else (maybe is neccesary to adjust some parameter in register for optimizing image for their display, and this is our situation but wince desktop is showed in our current display from the beggining), so my question/proposal is:
why not to use same LCD parameters to try to show a default logo image while booting kernel? ... in the worst case, the customer can not see "anything while boot system (like now), but others customers with compatible displays could see this logo and knows that system is "booting" after power on system.

Sorry, I did not see it, I will verify today.
Thanks.

I just donwloaded it and see the changelog of this new kernel, and one of the new features is:

- 0001535: [USB host] Expand USB driver for second USB Host - closed

How can we do that ? only modifying the register ? Can you then response the necessary changes in the thread
<!-- l --><a class="postlink-local" href="http://www.forum.fs-net.de/viewtopic.php?f=59&t=3355">viewtopic.php?f=59&t=3355</a><!-- l -->?

Thanks.