有一定的局限性，请参阅文档资料CDI：#543811

（更多智能系统的技术交流，请关注我们微博weibo.com/onlinesalesgroup、并浏览我们官方社区http://embedded.communities.intel.com/community/zh_cn，或者官方技术交流QQ群120966104）

The biggest Android related event in France, carefully crafted for you by the PAUG & BMA! Awesome speakers and lots of fun!

Come with your content and share directly with the audience.

This is an Intel sponsored event!

Register Here

Intel® Cluster Checker inspects more than 100 characteristics that indicate cluster health. It examines the system at both the node and cluster levels, making sure all components work together and can deliver optimal performance. This webinar will give you tips for using Intel Cluster Checker to verify system functionality. It will include information on how to embed capabilities into software, as well as how to customize and extend capabilities of the tool.

Register Here

Hi,

I am trying to get the i210 to work with the existing driver for the 82574 on VxWorks 5.5.1 which is built on the original 82643 driver.  Everything looks good (to me) but no data is actually transmitted.  The device appears to be able to receive ok as there is evidence in the counters and these match reasonably well with the counters in the Cisco switch for the port it is connected to. We have a link at both ends and auto-negotiation is successful.

The VxWorks driver uses queue 0 only and it creates the context on each send.

Below are the main registers of interest - VxWorks only modifies registers 0, 4 and 9 in the PHY.

10:02:38 gei82543EndStart:Link is up

10:02:38 phy  reg 0: 00001000

10:02:38 phy  reg 1: 0000796d

10:02:38 phy  reg 2: 00000141

10:02:38 phy  reg 3: 00000c00

10:02:38 phy  reg 4: 00000de1

10:02:38 phy  reg 5: 000043e1

10:02:38 phy  reg 6: 00000005

10:02:38 phy  reg 7: 00002001

10:02:38 phy  reg 8: 00000000

10:02:38 phy  reg 9: 00000300

10:02:38 phy  reg 10: 00004000

10:02:38 phy  reg 15: 00003000

10:02:38 phy  reg 17: 00007c08

10:02:38 gei82543EndStart: TCTL is: a40400fa

10:02:38 gei82543EndStart: STATUS is: 00280743

10:02:38 gei82543EndStart: CTRL_EXT is: 101c0000

10:02:38 gei82543EndStart: CTRL is: 00001941

10:02:38 gei82543EndStart: IPCNFG is: 0000000f

10:02:38 gei82543EndStart: PHPM is: 0000019d

10:02:38 gei82543EndStart: TXDCTL is: 02010000

I would appreciate any ideas as to what may cause this behaviour.

Thank you.

Our mission:

Assess the business cases for IoT

Identify added value profitable opportunities across the supply chain

Cover the full scope of IoT systems from the market leaders

Learn about the new disruptive technologies enabling IoT

This IDTechEx event addresses the opportunity for the Internet of Things. It does not cover hype and unrealistic dreams but addresses the business models, case studies, actions, profitability and missing gaps. We delve into specific market verticals and appraise new enabling technologies coming on-stream. The event is designed to help you assess your business strategy and timing, the technical, consumer and governmental challenges, new business models and opportunities. Hosted by IDTechEx, a 15 year old technology scouting and market research firm on the topic, this event offers a platform to gain insight, informed analysis and to meet new partners through the conference, exhibition, masterclasses and networking sessions.
Read more at: http://www.idtechex.com/internet-of-things-usa/conference.asp

Register Here

I'm trying to setup a system with two I210 controllers. The 2nd one operates in Flash-less mode

and I have problems to get it working.

I have successfully programmed the INVM using the eeupdate64e tool with:

eeupdate64e /nic=2 /invmupdate /file=I210_Invm_Copper_NoAPM_v0.6.txt

It now reports:

Using: Intel (R) PRO Network Connections SDK v2.25.20

EEUPDATE v5.25.20.03

Copyright (C) 1995 - 2015 Intel Corporation

Intel (R) Confidential and not for general distribution.

Driverless Mode

Warning: No Adapter Selected

NIC Bus Dev Fun Vendor-Device  Branding string

=== === === === ============= =================================================

  1   1  00  00   8086-1533    Intel(R) I210 Gigabit Network Connection

  2   3  00  00   8086-157B    Intel(R) I210 Gigabit Network Connection

The 2nd NIC is the one without flash.

However, when I try to program the MAC address, it fails:

eeupdate64e /nic=2 /mac=001395160935

NIC Bus Dev Fun Vendor-Device  Branding string

=== === === === ============= =================================================

  1   1  00  00   8086-1533    Intel(R) I210 Gigabit Network Connection

  2   3  00  00   8086-157B    Intel(R) I210 Gigabit Network Connection

2:  Updating Mac Address to 001395160935...Failed!

Further more when I load the driver "igb" in linux, it reports an

invalid checksum on the 2nd NIC:

Intel(R) Gigabit Ethernet Network Driver - version 5.3.2

Copyright (c) 2007-2015 Intel Corporation.

igb 0000:01:00.0: irq 76 for MSI/MSI-X

igb 0000:01:00.0: irq 77 for MSI/MSI-X

igb 0000:01:00.0: added PHC on eth0

igb 0000:01:00.0: Intel(R) Gigabit Ethernet Network Connection

igb 0000:01:00.0: eth0: (PCIe:2.5GT/s:Width x1)

igb 0000:01:00.0 eth0: MAC: 00:13:95:16:09:34

igb 0000:01:00.0: eth0: PBA No: 000300-000

igb 0000:01:00.0: LRO is disabled

igb 0000:01:00.0: Using MSI-X interrupts. 1 rx queue(s), 1 tx queue(s)

igb 0000:03:00.0: irq 78 for MSI/MSI-X

igb 0000:03:00.0: irq 79 for MSI/MSI-X

igb 0000:03:00.0: The NVM Checksum Is Not Valid

igb: probe of 0000:03:00.0 failed with error -5

Basically I have two questions now:

1. Why does the MAC address programming fail?

2. Why does the driver complain about the checksum? As far as I know there isn't

a checksum in the internal memory.

Regards,

Felix

Hello,

I need BSDL files for NHI350AM4 device (PBSA-256-1.0p 17x17). Please can someone tell me where to download the files? Cant find anything in the download center and our Fortune 500 distributor can't find them either.

With best regards from Jena,

Thomas

Hi,

I am using Intel's NUC Baytrail device and have connected a temperature sensor to the I2C interface.

Platform: Intel NUC Baytrail device

Operating System: Windows 7

Testing interface: I2C

Situations handled:

1. Changed BIOS from UEFI to Secured mode

2.  Step 1 helped to show the I2C device in the device manager.

3. Writing a test application program to perform read / write operation

4. Createfile() returns the handle of the temperature sensor device

5. The write / read operation does not succeed.

Below is the code for the same.

// LocalPortTestApp.cpp : Defines the entry point for the console application.

//

//

#include "stdafx.h"

#include <objbase.h>

#include <initguid.h>

#include "I2Cpublic.h"

#include <SetupAPI.h>

#include <iostream>

#include <algorithm>

#include <combaseapi.h>

#include <Windows.h>

#include <RegStr.h>

#include <WinBase.h>

#include <tchar.h>

#include <strsafe.h>

#include <winioctl.h>

using namespace std;

/**

* These are the generic rights used in serial com port open

*/

#define S_GENERIC_READ           (0x80000000UL)       ///<Windows Constant

#define S_GENERIC_WRITE          (0x40000000UL)       ///<Windows Constant

#define S_GENERIC_EXECUTE        (0x20000000UL)       ///<Windows Constant

#define S_GENERIC_ALL            (0x10000000U1L)      ///<Windows Constant

/**

* Constants used in serial com port open

*/

#define S_CREATE_NEW          1UL    ///<Windows Constant

#define S_CREATE_ALWAYS       2UL    ///<Windows Constant

#define S_OPEN_EXISTING       3UL    ///<Windows Constant

#define S_OPEN_ALWAYS         4UL    ///<Windows Constant

#define S_TRUNCATE_EXISTING   5UL    ///<Windows Constant

/*****************************************************************************************************

*                               GENERAL TYPEDEF

****************************************************************************************************/

typedef unsigned char         sUINT8;     ///<8 bit variable

typedef signed char           sINT8;      ///<7 bit variable

typedef unsigned char*        sUINT8P;    ///<8 bit variable pointer

typedef const unsigned char*  sCUINT8P;   ///<8 bit constant variable pointer

typedef short int             sINT16;     ///<15 bit variable

typedef unsigned short        sUINT16;    ///<16 bit variable

typedef unsigned short*       sUINT16P;   ///<16 bit variable pointer

typedef long                  sINT32;     ///<31 bit variable

typedef unsigned long         sUINT32;    ///<32 bit variable

typedef unsigned long*        sUINT32P;   ///<32 bit variable pointer

typedef const unsigned long*  sCUINT32P;  ///<32 bit variable pointer

typedef float                 sFLOAT;     ///<float variable

typedef double                sDOUBLE;    ///<double variable

typedef unsigned char         sBOOL;      ///<8 bit variable

typedef void*                 sVOIDP;     ///<memory pointer

typedef const void*           sCVOIDP;    ///<memory pointer

/**

* ENUM for ERROR CODE which will be return value

*/

enum returnStatus

{

    S_SUCCESS = 0,                   ///<Task completed successfully

    S_ERROR_FAILURE = 1,             ///<Task is not completed, due to some reason

    S_ERROR_PORT_OPEN = 2,           ///<Error occurred while opening PC channel driver port

    S_ERROR_PORT_CLOSE = 3,          ///<Error occurred while closing PC channel driver port

    S_ERROR_CONFIG_PORT = 4,         ///<Error occurred while configuring PC channel driver port

    S_ERROR_READ_BUFFER = 5,         ///<Error occurred while reading data from internal port buffer

    S_ERROR_WRITE_BUFFER = 6,        ///<Error occurred while writing data to internal port buffer

    S_ERROR_ARGUMENT = 7,            ///<API argument is not valid

    S_ERROR_CHANNEL_INVALID = 8,     ///<Proper channel is not selected

    S_ERROR_TIME_OUT = 9,            ///<Waiting Time is over

    S_ERROR_SEND = 10,               ///<Error occurred while sending command to Sunset Pass Module, due to lack of acknowledgment from Sunset Pass Module or timeout.

    S_ERROR_SEQUENCE = 11,           ///<Violating task sequence I.e. configure then open etc.

    S_ERROR_PORT_ACQUIRED = 14,      ///<Error occurred while trying to acquire handle, acquired by else before and not released yet

    S_ERROR_HANDLE_MISMATCH = 15,    ///<Error occurred while port handle supplied as argument is not matching with handle acquired

    S_BOOT_MODE = 16                 ///<Microcontroller is in Boot Mode

};

#define BUF_SIZE  50

int main(int argc, char* argv[])

{

    returnStatus eResult = S_ERROR_PORT_OPEN;

    GUID *i2cGuid = const_cast<GUID *>(&I2C_LPSS_INTERFACE_GUID);

    HDEVINFO hDevInfo;

    SP_DEVINFO_DATA devInfoData;

    HANDLE i2c_Handle = HANDLE(NULL); ///<handle of i2c port to access it

    hDevInfo = SetupDiGetClassDevs(i2cGuid, NULL, NULL, DIGCF_DEVICEINTERFACE | DIGCF_ALLCLASSES);

    if(hDevInfo == INVALID_HANDLE_VALUE)

    {

        return S_ERROR_FAILURE;

    }

    else

    {

        std::cout << "SetupDiGetClassDevs is Successfull.\n";

    }

    devInfoData.cbSize = sizeof(SP_DEVINFO_DATA);

    SP_DEVICE_INTERFACE_DATA devInterfData = { 0 };

    devInterfData.cbSize = sizeof(SP_DEVICE_INTERFACE_DATA);

    devInfoData.cbSize = sizeof(SP_DEVINFO_DATA);

    DWORD i = 0;

    if(SetupDiEnumDeviceInterfaces(hDevInfo, NULL, i2cGuid, i, &devInterfData))

    {

        DWORD size = 0;

        if (!SetupDiGetDeviceInterfaceDetail(hDevInfo, &devInterfData, NULL, 0, &size, 0))

        {          

            if (GetLastError() == ERROR_NO_MORE_ITEMS)

            {

                eResult = S_SUCCESS;

                while(1);

                return 0;

            }

            PSP_DEVICE_INTERFACE_DETAIL_DATA pInterfaceDetailData = (PSP_DEVICE_INTERFACE_DETAIL_DATA)LocalAlloc(LPTR, size);

            pInterfaceDetailData->cbSize = sizeof(SP_DEVICE_INTERFACE_DETAIL_DATA);

            if (!SetupDiGetDeviceInterfaceDetail(hDevInfo, &devInterfData, pInterfaceDetailData, size, &size, &devInfoData))

            {

                std :: cout << "SetupDiGetDeviceInterfaceDetail is Failed.\n";

                eResult = S_ERROR_FAILURE;

                while(1);

                return 0;

            }

            std :: cout << "CreatFile Calling.\n";

            std :: cout << "PATH of I2C interface in REGEDIT : "<< pInterfaceDetailData->DevicePath<<endl;

            std :: cout <<endl;

            i2c_Handle = CreateFile(LPCWSTR(pInterfaceDetailData->DevicePath),

                                    DWORD(GENERIC_READ | GENERIC_WRITE),

                                    DWORD(FILE_SHARE_READ | FILE_SHARE_WRITE),

                                    LPSECURITY_ATTRIBUTES(NULL),

                                    DWORD(OPEN_EXISTING),

                                    DWORD(FILE_FLAG_OVERLAPPED),

                                    (HANDLE)NULL);

            //Validation for correct open port

            if(i2c_Handle == INVALID_HANDLE_VALUE)

            {

                std::cout << " Port Open Error : " << GetLastError() <<endl;

            }

            else

            {

                std :: cout << "Creatfile is successfull..... = "<< i2c_Handle << endl;

                std::cout << endl;

            }

        }

    }

    else

    {

        char ch;

        std::cout << "1... Press any key and then ENTER to exit\n";

        std::cin >> ch;

        return 0;

    }

    //HANDLE hEvent;

    DWORD varEventResult;

    //HANDLE varEventObjectHandle = 0;

    /*Overlapped1.hEvent = CreateEvent(NULL, TRUE, FALSE, NULL);

    if(Overlapped1.hEvent)

    {

        std::cout <<"Create Event Successfull - 1." <<endl;

    }

    else

    {

        std::cout <<"Create event failed with error : "<< GetLastError() <<endl;

    }*/

    OVERLAPPED Overlapped1;

    /*Overlapped1.OffsetHigh = 0;

    Overlapped1.Offset = 0;*/

    memset(&Overlapped1, 0, sizeof(Overlapped1));

    BOOL status;

    I2C_SINGLE_TRANSMISSION writeTransmission;

    UCHAR writeBuf[2] = {0x90,0x00};

    UCHAR readBuf[BUF_SIZE] = {};

    UINT16 slaveAdr = 0x90;

    DWORD bytesReturned = 0;

    writeTransmission.Address = slaveAdr;

    writeTransmission.AddressMode = AddressMode7Bit;

    writeTransmission.BusSpeed = I2C_BUS_SPEED_400KHZ;

    writeTransmission.DataLength = sizeof(writeBuf);

    writeTransmission.pBuffer = writeBuf;

    status = DeviceIoControl(i2c_Handle,

                             (DWORD)IOCTL_I2C_EXECUTE_WRITE,

                             &writeTransmission,

                             (DWORD)sizeof(writeTransmission),

                             NULL,

                             0,

                             NULL,

                             (LPOVERLAPPED)&Overlapped1);

    std::cout << "Write Transmission....."<<endl;

    std::cout << "Slave Address : "<<slaveAdr<<endl;

    std::cout << "Status : "<< status << endl << "Get-Last-Error-Code : "<< GetLastError() << endl;

    std::cout << endl;

    Sleep(10);

    //varEventResult = WaitForSingleObject(Overlapped1.hEvent, 10000);

    if(status || (GetLastError() == ERROR_IO_PENDING))

    {      

        status = GetOverlappedResult(i2c_Handle,

                                     (LPOVERLAPPED)&Overlapped1,

                                     &bytesReturned,

                                     TRUE);      

        if(status)

        {

            std::cout << "Write Data : "<< writeBuf[0] << endl;

            std::cout << endl;

        }

        else

        {

            std::cout << "GetOverlappedResult....1 Failed - Write. "<< GetLastError() << endl;

            std::cout << endl;

        }

        //ResetEvent(Overlapped1.hEvent);

        //CloseHandle(Overlapped1.hEvent);

    }

    else

    {

        std::cout << "Write Data Failed. "<< endl;

        std::cout << endl;

    }

    std::cout << "--------------------------------------------------------\n\n";

    OVERLAPPED Overlapped2;

    Overlapped2.hEvent = CreateEvent(NULL, TRUE, FALSE, NULL);

    if(Overlapped2.hEvent)

    {

        std::cout <<"Create Event Successfull - 2." <<endl;

    }

    else

    {

        std::cout <<"Create event failed with error : "<< GetLastError() <<endl;

    }

    Overlapped2.OffsetHigh = 0;

    Overlapped2.Offset = 0;

    I2C_SINGLE_TRANSMISSION readTransmission;

    UINT16 slaveAdr1 = 0x91;

    readTransmission.Address = slaveAdr1;

    readTransmission.AddressMode = AddressMode7Bit;

    readTransmission.BusSpeed = I2C_BUS_SPEED_400KHZ;

    readTransmission.DataLength = sizeof(readBuf);

    readTransmission.pBuffer = readBuf;

    //memset(&Overlapped1, 0, sizeof(Overlapped1));

    ResetEvent(Overlapped1.hEvent);

    status = DeviceIoControl(i2c_Handle,

                             (DWORD)IOCTL_I2C_EXECUTE_READ,

                             NULL,

                             0,

                             &readTransmission,

                             sizeof(readTransmission),

                             NULL,

                             (LPOVERLAPPED)&Overlapped2);

    Sleep(10);

    std::cout << "Read Transmission....."<<endl;

    std::cout << "Status : "<< status << endl << "Get-Last-Error-Code : "<< GetLastError() << endl;

    std::cout << endl;

    varEventResult = WaitForSingleObject(Overlapped2.hEvent, 10000);

    if(status || (GetLastError() == ERROR_IO_PENDING))

    {

        status = GetOverlappedResult(i2c_Handle,

                                     (LPOVERLAPPED)&Overlapped2,

                                     &bytesReturned,

                                     TRUE);

        if(status)

        {

            std::cout << " data is : " << readBuf[0] << endl;

            std::cout << endl;

        }

        else

        {

            std::cout << "GetOverlappedResult....2 Failed - Read. "<< GetLastError() << endl;

            std::cout << endl;

        }

        //ResetEvent(Overlapped2.hEvent);

        CloseHandle(Overlapped2.hEvent);

    }

    else

    {

        std::cout << "Read Data Failed. "<< endl;

    }

     CloseHandle(i2c_Handle);

     char ch;

     std::cout << "2... Press any key and then ENTER to exit.....\n";

     std::cin >> ch;

     return 0;

}

Below is the output of the above code:

I would be grateful, If you can help me identify this issue and help resolve.

Thanks in advance of your support.

reg.

-prajose john

Hi,

I have a new PUC DE3815TYBE board.

I installed Windows-10 on it (I am planning on using embedded/real-time Windows or Linux in the future).

I installed the PROC_IO_Win8.1_32 device drivers for the chipset: I2C, GPIO, USART, ...

The Microsoft I2C HID Miniport Driver hidi2c is Stopped.

The I2C Controller Service iaioi2c is Running OK.

The Intel(R) Serial IO I2C Controller Driver iaLPSSi_I2C is Stopped.

Under Device Manager, I have two instances of I2C Controller devices under System Devices:

Manufacturer: Intel Corp.

Location: on Microsoft ACPI-Compliant System

Status: These devices work properly.

Device Instance Paths:  ACPI\80860F41\1 and \2

Events:

Devices installed: iaioi2ce.inf

Devices configured: oem6.inf

Devices started: iaioc2c

Devices configured: oem12.inf

Devices installed: iaioi2ce.inf

Status: 0x0.

I downloaded the Intel(R) Platform Controller Hub EG20T Intel Integrated Circuit (I2C) Driver for Windows Programmer's Guide which is not quite for my platform, but I hope it to be close enough.

QUESTIONS:

==========

1)  I do NOT have the files referred to by this document on page 8:

ioh_I2C_ioctls.h, and

ioh_I2C_common.h.

I NEED these files in order to write my application program!

2)  I tried to call the win32 function CreateFile(), but I do not know the name of the I2C device!

Can someone please help?

Thank you,

Pavel

Our company currently builds IoT products like datacenter power switches and IP controlled power relays. Many of our customers are requesting WiFi  connectivity. We use about 6k/month of Atheros AR9331 modules costing between $8-$13.  Does Intel build anything competitive near this price range?  We're after a microcontroller and radio running Linux.  We have tried the ESP8266, but it's a bit underpowered. Anyone with experience have a suggestion?

Hi,

We have designed a QSeven module carrier board that has an unprogrammed/blank Intel I211AT on PCIe Lane 0.  The I211 is not being detected.

Any ideas why?

The QSeven module uses an Intel Atom Bay Trail E3825 and provides:

- 1 Gigabit Ethernet interface (uses Intel I210)

- 4 PCIe interfaces

- 6 USB 2.0 interfaces

- An LPC Interface

- DisplayPort interface

Our carrier board implements the following high speed interface devices, all appear to work:

- Gigiabit Ethernet port which is directly driven by the QSeven module

- 2 Mini PCIe slots - using PCIe Lanes 1 & 2 and a USB interface each

- A Super I/O chip (Nuvoton W83627DHG-PT) - uses the LPC interface from the QSeven module

- A 2 lane DisplayPort interface

As far as we can tell . . .

- the I211 is connected correctly

- all pull-ups/pull-downs appear correct

- all voltages appear correct (3.3V, 1.5V, 0.9V)

- PCIe clock is present (cannot measure accurately as do not have a high bandwidth scope and high impedance probes, clock freg. is 100MHz though)

- An adapter card with another I211 on it works in the Mini PCIe slots

One other puzzling issue - the crystal connected to the I211 is not oscillating.

Is this normal or should the crystal operate even if the I211 is not detected?

The I211 is also not programmed (as can't communicate with it).

QSeven module is running Ubuntu but have also run in DOS and used Intel DOS tools to check for PCI devices.

I210 on QSeven module is detected in both Ubuntu and DOS.

Any ideas or suggestions appreciated?

Can Intel do a design review?

Board was designed in Altium.

Thanks.

不一定要使用，只需选择符合VR SPEC PMIC即可，CRB只是参考设计板，供验证参考。IoTG建议选择: IDT RoHM

（更多智能系统的技术交流，请关注我们微博weibo.com/onlinesalesgroup、并浏览我们官方社区http://embedded.communities.intel.com/community/zh_cn，或者官方技术交流QQ群120966104）

可以搭配，请根据具体设计需求来决定是否开槽

（更多智能系统的技术交流，请关注我们微博weibo.com/onlinesalesgroup、并浏览我们官方社区http://embedded.communities.intel.com/community/zh_cn，或者官方技术交流QQ群120966104）

Intel Atom Z3735F处理器，2GB内存1.35V DDR3L-L-RS，32GB EMMC，带wireless/Bluetooth,有一个micro SD card slot用来增加容量，预装操作系统是Windows 8.1 32bit

（更多智能系统的技术交流，请关注我们微博weibo.com/onlinesalesgroup、并浏览我们官方社区http://embedded.communities.intel.com/community/zh_cn，或者官方技术交流QQ群120966104）

I want to develop a product using Intel RCM. Is there a trial or demo release of this software. On positive case, what are the steps needed to get it?

The retail industry knows that technology can increase sales and operational efficiency, but many retailers have limited budgets to invest in intelligent retail systems. The challenge for OEMs is finding ways to deliver point-of-sale (POS) systems, kiosks, and digital signage that deliver advanced features while keeping costs down. Below, I am providing links to some community posts on this topic that I think are particularly useful.  Digital Signage Top Picks have moved to a dedicated page.

Blog: Next-Level Retail with 5th Generation Intel® Core™ Processors

5th generation Intel® Core™ processors improve security, manageability, and performance. Learn how they take retail computing to the next level.

Blog: Mobile Point-of-Sale Transforms the Store

Mobile point-of-sale (MPOS) completely changes the retail experience with on-the-spot transactions, easy upselling, and a personal touch. Explore the ways you can transform your store.

Article:  Personalize Retail with Secure Interactivity

Technology can power personalized shopping experiences throughout the store – whether a customer is viewing digital signage or interacting with sales staff. See how you can bring this tech to market with minimal cost and effort.

White paper:  Internet of Things Solution Improves Vending Machine Profitability

Check out a vending machine management and data analytics solutions that connects a fleet of machines to the cloud-based tools that can help generate more revenue and reduce maintenance effort..

Article:  Real-Time Content Management for Retail Displays

Retailers want to coordinate marketing campaigns across signage, kiosks, vending machines, and point-of-sale (POS) devices. Find out how the new Intel® Retail Client Manager (Intel® RCM) helps meet this goal.

Article:  Smart Vending Machines Deliver the Goods

The IoT is revolutionizing vending machines, improving the customer experience and helping vendors optimize their offerings and operations. Learn how you can put the IoT to work in your designs.

Article:  New Intelligence for Entry-Level Retail

Find out how the new Silvermont microarchitecture helps developers deliver the benefits of the Internet of Things (IoT) in low-cost POS terminals, kiosks, ATMs, vending machines, and signage.

Blog:  Protecting Perishables with IoT Sensors

Check out an IoT-enabled temperature management proof-of-concept that uses a wireless gateway based on the Intel® Quark™ SoC X1000 series to automate control, data collection, and notification when temperatures in a retail refrigerated display fall outside thresholds.

Article:  Upgrade Point-of-Sale for the Online Age

Modern POS systems can use Internet of Things technology to enhance customer relationships, improve sales, and inform business decisions. Learn how the 4th generation Intel® Core™ processor family delivers the performance, security, and manageability these systems need.

Click here to browse retail computing solutions (including hardware and software elements of a retail system) based on Intel® architecture from Intel’s trusted embedded ecosystem, the Intel® Internet of Things Solutions Alliance.

Felix

J. Felix McNulty

Community Moderator

Intel® Embedded Community

(Intel contractor)

Industries such as retail, infotainment, and transportation have begun to make smart and connected digital signage a competitive advantage in effectively interacting with customers.  That is why the global market for digital signage is expected to reach $4.5 billion by 2016.  Availability of standards-based, interoperable components are helping OEMs bring large-scale signage solutions to market faster and more cost-effectively.  Below, I am providing links to some community posts on this topic that I think are particularly useful:

Article: Upgrade Entry-Level Signage with Ease

A new turnkey design brings together high-definition video, an intuitive content management system (CMS), and support for vending machine functions. Learn how it can help you create affordable, performance-oriented signage.

White paper: Building Engaging Cloud Classrooms with Digital Media Players

Check out how the computing and graphics capabilities of an Intel-based digital signage solution enable more modern teaching methods, enrich teaching materials, and encourage participation in the classroom and beyond.

White paper: Next generation retail and digital signage solutions

Read about powerful digital signage and vending system solutions including innovative displays and powerful computer-on-modules for the challenging retail sector and contributing to the development of smart selling and connected stores.

Blog: Making Interactive Signage More Effective

You can get the most value from signage when you start with the right platform and content management system (CMS). Find out how the 21.5” Advantech Retail Touch Computer UTC-620E delivers.

Blog: Interactive Whiteboards That Save Schools Money

Julong Educational Technology discovered that standards helped its whiteboards make the grade. Learn how they achieved greater convenience, easier installation, and lower maintenance costs.

Blog:  Service Provider Finds Perfect Signage Recipe

PilotTV saved over 30% on installation and 70% on maintenance with the Intelligent Pluggable System Specification (IPSS). Find out how they did it, and how you can achieve these savings yourself.

Blog:  Tablets Are Now the Sign of the Times

Tablet computers are a great option for small digital signage. Everything you need is built in – media player, display, and wireless capabilities. See how you can use these machines to engage customers with interactive experiences.

Blog:  Powerful, Compact Signage with Intel® NUC

If you want powerful signage in a small package, the Intel® Next Unit of Computing (Intel® NUC) is a good place to start. Discover how these energy-efficient PCs deliver big graphics and sophisticated content management in a footprint as small as 4 x 4 x 2 inches.

Article:  A Turnkey Solution for Smart Signage

The Intelligent Pluggable System Specification (IPSS) combines 4K graphics, interactivity, content management, analytics, and device management in a turnkey package. Learn how it simplifies digital signage design.

Article:  Real-Time Content Management for Retail Displays

Retailers want to coordinate marketing campaigns across signage, kiosks, vending machines, and point-of-sale (POS) devices. Find out how the new Intel® Retail Client Manager (Intel® RCM) helps meet this goal.

Blog:  Improving Advertising Results with Intel® Audience Impression Metrics Suite

Learn how the Intel® Audience Impression Metrics Suite (Intel® AIM Suite) combined with data mining techniques to collect, analyze, and put viewer data to work can improve advertising effectiveness.

Click here to browse digital signage solutions (including hardware and software elements of a retail system) based on Intel® architecture from Intel’s trusted embedded ecosystem, the Intel® Internet of Things Solutions Alliance.

Felix

J. Felix McNulty

Community Moderator

Intel® Embedded Community

  (Intel contractor

Everybody is talking about the Internet of Things (IoT).However,the IoT paradigm comprises of a diverse array of vertical markets and is not a homogenous entity. Take the Industrial Internet of Things (IIoT) for instance.Known to some people, particularly in Europe, as Industry 4.0,such technology often finds a home in the Smart Building or Smart Factory.

The drive behind IIoTcomes from the notion of connecting machines to the cloud and adding intelligence to them, a concept that is easier said than done. Machinesdon't necessarily talk in the language of networks and the cloud.Moreover, the number of network types and protocols operating in an industrial automation environment is steadily rising,so there is a growing need to bridge the gap between the industrial and IT networking domains. That bridge is typically handled with an IoT gateway.

A developer needs to look no further than theIntel® Internet of Things Solutions Alliance for help. One Associate member of the Alliance aiming to bring industrial automation into the IoT arena is AAEON, the industrial and embedded computing subsidiary of ASUS, a large-scalemanufacturer of PCs, tablets, and mobile phones based in Taipei, Taiwan. AAEONspecializes in the design and manufacture of industrial PC (IPC) products, such as industrial motherboards, embedded CPU boards, panel computers, and industrial box computers. Such products are quite suited to Smart Building/Factory applications.

AAEON is leveraging the Intel^®IoT Gateway reference designwhich includes technology from McAfee and Alliance membersWind River. This design is helping AAEON expand connectivity, improve interoperability, and shorten time to market for developers looking to transform business and operations.

AAEON, which recently joined hands with HMS Networks AB, a supplier of communications solutions for industrial automation, is now offering end-to-end IoT solutions that exchange data between "things" and the cloud—hence the need for a gateway as the IIoT bridge. AAEON’s gateway solutions offerIntel® Quark™ SoCs and Intel® Atom™ processors, Wind River Intelligent Device Platform XT* 3,Linux*,and McAfee*Embedded Control security technologies.

The solution targets the Smart Building/Factory,whichwould require a programmable logic controller (PLC) for industrial electromechanical processes, in addition to the industrial I/O modules for multiple arrangements of digital and analog inputs and outputs, and a gateway to pass the information back and forth between the server and end-devices (Figure 1).AAEON's AIOT-DRM isan Intel Quark SoC-based IoT gateway that can function as an industrial I/Omodule. When paired with a PLC, it reduces the overall solution's cost, size and weight, while enabling cloud connectivity and greater flexibility.

Figure 1. The AAEON gatewayforms the bridge required in an Industrial IoT platform.

The steppyramid-shapedgateway is comprised of abase PC board, CPU board, and industrial I/O board, each stacked atop one another from the top to bottom, respectively.The top level of the AIOT-DRM system provides Internet access and expansion capabilities; computation in the middle; and analog-to-digital conversion at the bottom.

This IoT gateway takes data from sensors, video cameras and RFID tags via multiple sources like Wi-Fi and ZigBee and dispatches the data to a server. In the Smart Building/Factory example, it allows those responsible for building management to monitor the data with a tablet or a mobile phone via a gateway link to the cloud.

Embedded computing solution providers like AAEON focuses more on the x86 ecosystem compared to ARM as it is less fragmented and offers greater space for differentiation. Basing the solution on the Intel IoT Gateway design, whichincludes an embedded OS and security software stacks, allows firms like AAEON to offer application-ready embedded platforms. An SDK supplied by AAEON simplifies the access capability needed by third-party software to control or access the IoT gateway and sensors.

Gateway solutions for other IoT applications are also available from AAEON. For example, the AIOT-X1000 subcompact board—powered by theIntel® Quark™SoC X1000 series—integrates rich communication interfaces such as RS-485 and analog and digital I/Os. The motherboard provides the basic building blocks for IoT gateways like AIOT-QA for retail and banking applications, and additional customization and support for industrial communication protocols like EtherCAT, ProfiNET, ModBus, and more (Figure 2).

Figure 2. AAEON offers one-stop shopping for IoT gateway solutions.

AAEON providesIoT solutions combining hardware and software for the specific vertical markets it serves. The Intel IoT Gateway designthat AAEON has adopted provides an integrated software platform and OS board support package (BSP) to support the operation of the gateway. Moreover, the company works closely with system integrators and installer to ensure that it provides validated IoT solutions with actual IoT system integration track records.

See our Solutions Directory for more products from AAEON.

AAEON is an Associate member of the Intel® Internet of Things Solutions Alliance.

Richard Nass

OpenSystems Media by special arrangement with the Intel® Internet of Things Solutions Alliance.

Broadwell-U的USB2.0接口有8组。

（更多智能系统的技术交流，请关注我们微博weibo.com/onlinesalesgroup、并浏览我们官方社区http://embedded.communities.intel.com/community/zh_cn，或者官方技术交流QQ群120966104）

有兼容设计可以参考,PDG#514849 2 Haswell - Broadwell U Platform Compatibility。

（更多智能系统的技术交流，请关注我们微博weibo.com/onlinesalesgroup、并浏览我们官方社区http://embedded.communities.intel.com/community/zh_cn，或者官方技术交流QQ群120966104）