Windows Embedded Compact 2013 supports TLS 1.1 as well as TLS 1.2.
For more information please read the following article:
TLS 1.1 and 1.2 support on Windows Embedded Compact 2013 (microsoft.com)
Posts by fs-support_HF
-
-
The cryptography security module of Windows Embedded Compact 2013 is FIPS 140-2 validated.
Cryptographic Module Validation Program CMVP:
https://csrc.nist.gov/projects…-program/certificate/3630
Cryptographic Algorithm Validation Program CAVP:
-
The WLAN module on PicoCore can also be used as access point.
It's important to know, that the interface mlan0 is used for station mode and the interface uap0 is used for softAP mode.
By default, only mlan0 is started during boot.
To start uap0 during boot you have to set the paramter "driver_mode" of module "mwifiex" to th value 3.
Best way to do this, is to set the variable "extra" in u-boot like following:
The result is, that the interface mlan0 and the interface uap0 are started during boot.
-
The WLAN module on PicoCore can also be used as access point.
It's important to know, that the interface mlan0 is used for station mode and the interface uap0 is used for softAP mode.
By default, only mlan0 is started during boot.
To start uap0 during boot you have to set the paramter "driver_mode" of module "mwifiex" to th value 3.
Best way to do this, is to set the variable "extra" in u-boot like following:
The result is, that the interface mlan0 and the interface uap0 are started during boot.
-
The WLAN module on PicoCore can also be used as access point.
It's important to know, that the interface mlan0 is used for station mode and the interface uap0 is used for softAP mode.
By default, only mlan0 is started during boot.
To start uap0 during boot you have to set the paramter "driver_mode" of module "mwifiex" to th value 3.
Best way to do this, is to set the variable "extra" in u-boot like following:
The result is, that the interface mlan0 and the interface uap0 are started during boot.
-
Under the following link, documentation for PicoCoreM6SX is ready for download:
You can find:
- PicoCoreMX7ULP hardware documentation
- PicoCoreMX7ULP base board hardware documentation
- PicoCoreMX6SX base board design files
- PicoCoreMX6SX base board schematic
- Several documents regarding Linux
- Use or FreeRTOS on Cortex-M4
PicoCoreMX6SX is pin compatible to PicoCoreMX6UL and shares the same base board.
Main Advantage of PicoCoreCoreMX6SX over PicCoreMX6UL:
PicoCoreMX6SX PicoCoreMX6UL 2x GBit LAN 2x 100MBit LAN Cortex-A9+Cortex-M4 Cortex-A7 2D/3D GPU --- Please note:
To download our Linux BSP for PicoCoreMX7ULP, you have to create an account under "My F&S" first.
-
Under the following link, documentation for PicoCoreMX7ULP is ready for download:
You can find:
- PicoCoreMX7ULP hardware documentation
- PicoCoreMX7ULP base board hardware documentation
- Several documents regarding Linux
Please note:
To download our Linux BSP for PicoCoreMX7ULP, you have to create an account under "My F&S" first.
-
Hardware documentation for PicoCoreMX6UL is now ready for download.
PicoCoreMX6UL Hardware Documentation
Documentation includes information about routing of connector pins to CPU pins. This makes it easier for customers to adapt their own operating system to the board.
In addition to hardware documentation we provide carrier board schematic and Eagle design files for carrier board.
-
There is a open source webcam driver for Windows Embedded. The driver was originally provided on CodePlex.
The driver supports webcams which use the USB UVC class. SO other not tested webcams with support for UVC should also work.
We have integrated this driver in our binary BSP. You can add the driver to your image by selecting it in the catalog.
We have tested the driver with following webcams:
- Logitech C270
- Logitech C920
To test the camera you can use the tool DShowCamTest.exe.
-
-
Everyone who needs to use OPC-UA can take a look to the following GitHub project:
https://github.com/open62541/open62541/issues/884As you can read, it is working with WEC7 and VS2008 or WEC8 and VS2015.
-
FTDI has now released version 1.0.0 of the driver.
Because our boards are based on ARM CPUs, please use the ARM version (not the X86 version). -
Currently we don't support SATA with our efusA9 board under Windows Embedded Compact.
Beside this, only the i.MX6 Dual and Quad have SATA integrated. -
FTDI has now released a BETA VCP (Virtual COM Port Driver) Driver for Windows Embedded Compact 2013.
That's important, because the old driver for Compact 7 will not run on Compact 2013. -
Following drivers are included by default.
Resistive Touch Controller:
* Semtech SX865x (-> See schematic of efusA9 carrier board)
* Texas Instruments TSC2007Capacitive Touch Controller:
* Focaltech
* Armel MaxTouch MXT224Additional drivers are possible. Please contact support.
-
Some customers asking, for the well known standard shell form Compact 7.
The answer is, that this is also a removed functionality of Compact 2013.
The new MinShell only shows a bitmap and has a "Start" button on the top left of the window.
F&S has ported the old control panel to Compact 2013 and added a menu entry to start this under the "Start" button.
Using this you have access to "F&S Board Config" can change date/time, play some system sounds and much more. -
Hello,
The name of the file is fs_canbusio.h.
This file is included in the SDK. You can find it in
C:\Program Files (x86)\Windows CE Tools\SDKs\FSVYBRID_WEC2013\Sdk\IncRgeards
-
This problem is fixed since image version 0,80.
Please take a look at the changelog for our iMX6 kernel to get more information.
https://www.fs-net.de/projectstate/get/changelog/FSiMX6Information about future version scan be found here:
https://www.fs-net.de/projectstate/get/roadmap/FSiMX6 -
The commands "backlight off" and "backlight on" are not implemented in the current version.
Please take a look at the roadmap for our iMX6 kernel.
We have also checked command "display power on" and "display power off". Both commands are not working correctly.
Please take a look at the roadmap for our iMX6 kernel too.Our apologies about this problems.
-
One or two Ethernet ports is a soldering Option.
Means you have to order with one or two boards.
It's not possible to simply set a regsitry value to switch second port on.
In case of 2nd LAN port you loose the Audio feature.
