Thursday, 24 December 2009

Merry Christmas

Hi folks,

I’d like to wish all of you a Merry Christmas and a Happy New Year, also on behalf of our entire team! Hopefully you get to spend some quiet, peaceful time with your loved ones.

Of course we will continue to post interesting and helpful news from the world of Windows Embedded here on our blog in 2010.

Meanwhile, if there are any topics that your would like to discuss further or that you think that are missing on our blog, please let me know so in the comment section!

Again, Happy Holidays to you all!
-Jochen
Read more! Post this to a friend!

Wednesday, 23 December 2009

Season Greetings and a small Quiz

I guess it's time to wish all our readers and followers a very Merry Christmas and a Happy and Prosperous New Year 2010!

As this is the Season of Giving we thought we would give away some Windows CE 6.0 books. For free? Well, we thought we would do a small quiz and then draw 5 Winners from those readers who get all answers right.

So have fun with the quiz, have yourselfs a nice and quiet Christmas and a really loud New Year!

Simply send the answers to our EMail Adress and we will let you know if you are one of the lucky winners! Btw: You can find (nearly) all answers in this Blog.

1) What is the name of the missing symbol by the following error message "Error: Can't find import 2508 in coredll.dll".
2) What is the recommended size for the (MTU = maximum transmission unit) while using PB KITL debugger?
3) What was the codname of Microsoft Auto 4.0 RTM?
4) In which country is the Microsofts Student Technology Competition "Imagine Cup 2010" going to be hosted?
5) With which Version of Windows CE did Microsoft start to use Whiskeys as code names?
6) Which define is required (in the sources file) to get the wMMX2 instruction set for your XScale processor in your assembler code?
7) From which book is "So long and thanks for all the fish!" and who said it?

So long and thanks for all the fish!
Read more! Post this to a friend!

Friday, 18 December 2009

"Snowing" news from Nürnberg ...

to all Windows Embedded developers!!! :)

and I hope that you have also nice weather like us here in Nürnberg. If not I recommend you to visit the "Christkindlesmarkt" at Nürnbergs downtown. Just have fun!
Read more! Post this to a friend!

Wednesday, 16 December 2009

Use previous Windows Embedded CE 6.0 Rx install for your next project

Using your previous Windows Embedded CE 6.0 Rx install for your next project should actually be a valid use case. But as a feedback from yesterdays post in this blog I got a phone call from one of my colleagues asking: "Look: Half of my development team has build problems after installing the new BSP in our new project. Any idea?"

I remembered the Peanuts comics, smiled and said: "The doctor is in! So tell me..."

Doing a blddemo -q build errors occur stating error C2677: Undefined assembler operation. The current build directory is c:\wince600\platform\common\src\soc\....blabla...

So what's happening here?

error C2677 is a MIPS Error Message. The directory above is listing the SOC (System On Chip) designs supported by all installed BSPs. Inside that directory we identified BSP support for various SOCs. These causing the problems and used in previous projects were Freescale's iMX27, iMX31, and iMX35. And these are non MIPS but ARM core SOC designs. And surely the selected MIPS assembler does not know how to handle ARM assembler operations.

So I suggested to deinstall these iMX BSPs which would surely solve the build problem. But that's not a valid solution if you still have to support the old project.

2nd proposal is to introduce some logic checking an environment variable defining the CPU or SOC (TGTCPU) selected for the current build in the C:\WINCE600\PLATFORM\COMMON\SRC\SOC\dirs until now stating to traverse all subdirectories (DIRS=*). But that's most likely causing maintenance issues on this file for upcoming BSP installs or removals that have to be solved manually even if these BSPs do not have the drawbacks from Freescales BSPs mentioned.

So how and where do other BSPs control if they are MIPS or ARM or whatever?

Well, directly in the sources files inside the subdirectories below C:\WINCE600\PLATFORM\COMMON\SRC\SOC\. Inside these sources files you can use NOMIPS16CODE=1 or identify ARM assembler sources by ARM_SOURCES= foobar.s ...

So you can add this type of control where needed in the sources files of the iMX BSPs coming from Freescale. Surprisingly this takes just a few minor changes.

Surely it would be nice if Freescale would solve these build issues directly in their BSPs to improve such compatibility issues in multi platform scenarios with different target CPU cores.

So much for project hopping from Freescale iMX (ARM core) to MIPS II FP. You mean I have not explained how this is solved in x86 or SH? Correct! I haven't... But there always has to be some magic left over. Especially at this time of the year...

-- Oliver Merkel

"Christmas waves a magic wand over this world, and behold, everything is softer and more beautiful." --N. V. Peale


Read more! Post this to a friend!

Windows Embedded CE: touch considerations part II

Hi Folks,

in my last post I talked about improving the touch driver by replacing the timer (SYSINTR_TOUCH_CHANGED) with a Sleep(). Today I want to point out another touch driver improvement.

When using the touch screen the CPU utilization increases dramatically, this of course results in a much worse system performance. After some research and some measurements you will find, that the increase in CPU utilization is mainly caused by busy waits which are used frequently throughout the touch driver (e.g. XllpOstDelayMicroSeconds() in Mainstone BSPs).

Replacing the busy waits with Sleep() will solve this problem while still keeping your touch driver responsive enough.

Have fun!
Read more! Post this to a friend!

Tuesday, 15 December 2009

Windows CE Chat Transcript

If you were hoping to find the chat transcript from the December Windows CE Chat, I'm afraid I have to tell you that it did not take place - I wonder if the CE Team will be there next week :-)

So long and thanks for all the fish!

Read more! Post this to a friend!

CommCtrl with R3 Touch broken after QFE update (Fatal error U1077)

A while ago Jochen already posted some info on Touch Gestures feature introduced in R3. So if this is coming along with Windows CE 6.0 R3 then there must be a situation to mess up things from R2 and R3.

And here it is:

Get the R3 iso image from Microsoft download center. Nearly 1.2 GB of data. But at least if that stuff in your installation gets broken you get all data to do a repair then.

Run R3 update being an incremental install to an existing Windows CE 6.0 R2 and voilá: It's working.

Now we learned one thing: Update everything to have the latest changes available! So get the QFEs!

But be aware: This might break your R3 install. If you have already done so then each blddemo will run into the following situation. Your build.log will show a fatal error:

commctrl.lib(aygutils.obj) : warning LNK4217: locally defined symbol SHCreateDefaultGradient imported in function "public: static int __cdecl AygUtils_t::SHGradientInit(struct tagSHGRADIENT *,int,unsigned short const *)" (?SHGradientInit@AygUtils_t@@SAHPAUtagSHGRADIENT@@HPBG@Z)
commctrl.lib(aygutils.obj) : warning LNK4217: locally defined symbol SHGetSystemMetrics imported in function "public: static int __cdecl AygUtils_t::SHGradientInit(struct tagSHGRADIENT *,int,unsigned short const *)" (?SHGradientInit@AygUtils_t@@SAHPAUtagSHGRADIENT@@HPBG@Z)
commctrl.lib(lvgesture.obj) : error LNK2019: unresolved external symbol "public: static void __cdecl TouchPerf::ReleaseSession(void)" (?ReleaseSession@TouchPerf@@SAXXZ) referenced in function "public: __cdecl GestureTriggeredScrollCtrl::~GestureTriggeredScrollCtrl(void)" (??1GestureTriggeredScrollCtrl@@QAA@XZ)
commctrl.lib(lvgesture.obj) : error LNK2019: unresolved external symbol "public: static void __cdecl TouchPerf::AcquireSession(void)" (?AcquireSession@TouchPerf@@SAXXZ) referenced in function "public: __cdecl GestureTriggeredScrollCtrl::GestureTriggeredScrollCtrl(void)" (??0GestureTriggeredScrollCtrl@@QAA@XZ)
C:\WinCE600\OSDesigns\???_MIPSII_FP\cesysgen\oak\target\MIPSII_FP\debug\commctrl.dll : fatal error LNK1120: 2 unresolved externals
NMAKE : fatal error U1077: 'link' : return code '0x460'
Stop.
NMAKE : fatal error U1077: 'C:\WINCE600\sdk\bin\i386\nmake.exe' : return code '0x2'
Stop.

This one can not be resolved with turning on/off catalog item selections or something like that. The current QFEs simply break your R3 install and overwrite some files but not all being related to Touch Gesture or other R3 features.

This will most likely be fixed in the upcoming QFEs again but meanwhile just re-run the R3 rollout msi (Microsoft Installer) included in the ISO image and select repair from the corresponding menu.

Until now I did not encounter any side effects after using this R3 repair.

Unfortunately it's hard to say if the R2 tree is completely merged in R3 or if some side effect might occur. If I find some time I will check that. But most likely best way is to wait for the next QFEs to get that properly fixed.

At least the repair will allow you to continue work on R3 development that way.

Merry Christmas and Best Wishes for a happy new year, and all your R2 and R3 projects...

--- Oliver
Read more! Post this to a friend!