Windows Embedded Compact 2013 – Understanding STARTUPTEXT macro - Part 2

This post is the continuation of the WEC2013 – Understanding STARTUPTEXT macro - Part 1. Finally found a solution on how to fix the entry point at the beginning of the code in the executable. Let’s make the hand dirty.

Please click the below link to know more...

http://www.e-consystems.com/blog/windowsce/?p=1006 

Windows Embedded Compact 2013 – Understanding STARTUPTEXT macro - Part 1

On continuation of WEC2013 porting blog series, I would like to share about the change in STARTUPTEXT macro and its effect on WEC2013. Before that we have to understand the purpose of this macro. Go ahead with the following link..
http://www.e-consystems.com/blog/windowsce/?p=981 

On continuation of WEC2013 porting blog series, I would like to share about the change in STARTUPTEXT macro and its effect on WEC2013. Before that we have to understand the purpose of this macro. - See more at: http://www.e-consystems.com/blog/windowsce/?p=981#sthash.L8Bxc734.dpuf

On continuation of WEC2013 porting blog series, I would like to share about the change in STARTUPTEXT macro and its effect on WEC2013. Before that we have to understand the purpose of this macro. - See more at: http://www.e-consystems.com/blog/windowsce/?p=981#sthash.L8Bxc734.dpuf

Windows Embedded Compact 2013 THUMB2 porting – ARM pre UAL syntax and its equivalent UAL syntax

As a continuation of the WEC 2013 – THUMB2 porting considerations article, I would like to share few more considerations during THUMB2 porting specifically during compilation, assembler will through an error “pre UAL syntax not allowed” frequently in earlier CE version BSPs.
Please click the below link to know more...
http://www.e-consystems.com/blog/windowsce/?p=945

Windows Embedded compact 2013 - Camera solutions

WEC2013 is running on TI DM37x EVM with e-con systems e-CAM52_35x (5MP camera solution for TI DM37x EVM).




 Soon you can expect more camera solutions on WEC2013.

Article: Difference between Windows Embedded Compact 7 and Windows Embedded Compact 2013 (Core Performance)

Windows Embedded Compact 2013 – A next version of Windows Embedded Compact series released by Microsoft with new and improved features to overcome major issues faced in Windows Embedded Compact 7 (earlier version). There are several improvements in Windows Embedded Compact 2013 and this article demonstrates the performance and code size improvement. Please see the below link to know more....
http://www.e-consystems.com/WEC7-vs-WEC2013.asp

Article: Windows Embedded Compact 2013 – THUMB2 Porting Considerations

As you know Windows Embedded Compact 2013 (WEC2013) is supporting only ARMv7 Thumb2 mode and earlier versions of ARM BSPs (ARMv7) are forced to support Thumb2 mode while porting. Although Windows Embedded Compact 2013 team has released an ARM porting guide, this article reveal some implicit information, real world issues and solutions required to make THUMB2 porting success.  Please see the below given link to go ahead.....
http://www.e-consystems.com/windows-embedded-compact-2013-thumb2.asp 

Windows Embedded Compact 2013 Released

Finally the hot cake has come to our basket. Microsoft release WEC2013 the next version of Windows Embedded Compact series. Again the hot cake has come with new flavors let us enjoy. Here is the official announcement link.
Microsoft announces general availability of Windows Embedded Compact 2013
WEC 2013 Download 
MSDN link
Soon you can expect blogs and article regarding Windows Embedded Compact 2013 and enjoy our journey with WEC2013.

Retrieving USB VID/PID in application on Windows CE 6.0/7.0

Since Windows CE is used for customized devices and some requirements demanded from the customers to restrict certain USB devices based on the Vendor ID (VID) or Product ID(PID). Device has to respond only to their USB accessories, for example, Customer has designed their own USB HID device accessories for their devices and expected to respond only for their accessories. Even with their accessories they are introducing special featured accessories and expecting the device (application) to act accordingly for each accessory dynamically. So we need to take some decision on the application which requires some unique ID(VID/PID) to identify the connected accessory. Please see the below link to know more...
http://www.e-consystems.com/blog/windowsce/?p=878