is there a pinout file in xls format available in a row available ? For the CN10 and CN12 Connector?

thanks
alex

I've seen people on the forum connecting a msata ssd to the mpcie/msata port on the UP2. I would like to know weather if it is possible to connect an msata ssd to the high speed carrier board (i am using a Up Core Plus). In case it is not possible, what SSD (M2.0) board do you recommend?. I've seen some people recommend sometheing this https://www.memory4less.com/super-talent-corestore-128gb-pci-express-2-0-x1-ssd-fpn128c2rm but this product seems very specific and its not available in my country. If there is no mpcie m2.0 hard drive available for this board, could we get a reference for a mpcie to msata or NMVE converter board that you think might work?

The UP Core has an excellent design guide with precise measurements of the location and function of the 100 pin header, is there a version that describes the UP Core Plus and the 2nd 100 pin header?

I've been trying to set up UP Core Plus extended with UP Vision Plus X with Ubuntu 18.04 by following the instructions from https://wiki.up-community.org/Ubuntu#Ubuntu_18.04_installation_and_configuration

After completing all the steps from the guide Ethernet adapter from Vision Plus X is not detected, the output from ifconfig gives the following

upcore@upcore-UPC-PLUS:~$ ifconfig
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 597  bytes 61040 (61.0 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 597  bytes 61040 (61.0 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.104  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::579b:3cdc:817a:409e  prefixlen 64  scopeid 0x20<link>
        ether 10:d0:7a:15:3c:68  txqueuelen 1000  (Ethernet)
        RX packets 4281  bytes 2679864 (2.6 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 4391  bytes 775471 (775.4 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lshw:
upcore@upcore-UPC-PLUS:~$ sudo lshw |grep -A 6 network
*-network
description: Wireless interface
physical id: 1
logical name: wlan0
serial: 10:d0:7a:15:3c:68
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=brcmfmac driverversion=7.45.18 firmware=01-6a2c8ad4 ip=192.168.0.104 multicast=yes wireless=IEEE 802.11

lspci:
upcore@upcore-UPC-PLUS:~$ sudo lspci
00:00.0 Host bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Host Bridge (rev 0b)
00:02.0 VGA compatible controller: Intel Corporation Device 5a85 (rev 0b)
00:0e.0 Multimedia audio controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Audio Cluster (rev 0b)
00:0f.0 Communication controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Trusted Execution Engine (rev 0b)
00:11.0 Unclassified device [0050]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Integrated Sensor Hub (rev 0b)
00:12.0 SATA controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SATA AHCI Controller (rev 0b)
00:13.0 PCI bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port A #1 (rev fb)
00:13.1 PCI bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port A #2 (rev fb)
00:13.2 PCI bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port A #3 (rev fb)
00:13.3 PCI bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port A #4 (rev fb)
00:14.0 PCI bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port B #1 (rev fb)
00:14.1 PCI bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port B #2 (rev fb)
00:15.0 USB controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series USB xHCI (rev 0b)
00:15.1 USB controller: Intel Corporation Device 5aaa (rev 0b)
00:16.0 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series I2C Controller #1 (rev 0b)
00:16.1 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series I2C Controller #2 (rev 0b)
00:17.0 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series I2C Controller #5 (rev 0b)
00:17.2 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series I2C Controller #7 (rev 0b)
00:17.3 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series I2C Controller #8 (rev 0b)
00:18.0 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #1 (rev 0b)
00:18.1 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #2 (rev 0b)
00:18.2 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #3 (rev 0b)
00:19.0 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SPI Controller #1 (rev 0b)
00:1a.0 Serial bus controller [0c80]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PWM Pin Controller (rev 0b)
00:1b.0 SD Host controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SDXC/MMC Host Controller (rev 0b)
00:1c.0 SD Host controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series eMMC Controller (rev 0b)
00:1e.0 SD Host controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SDIO Controller (rev 0b)
00:1f.0 ISA bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Low Pin Count Interface (rev 0b)
00:1f.1 SMBus: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SMBus Controller (rev 0b)

However, dmidecode seems to be able to detect ethernet adapter
upcore@upcore-UPC-PLUS:~$ sudo dmidecode -t baseboard
# dmidecode 3.1
Getting SMBIOS data from sysfs.
SMBIOS 3.0.0 present.

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
    Manufacturer: AAEON
    Product Name: UPC-PLUS
    Version: V0.1
    Serial Number: Default string
    Asset Tag: Default string
    Features:
        Board is a hosting board
        Board is replaceable
    Location In Chassis: Default string
    Chassis Handle: 0x0003
    Type: Motherboard
    Contained Object Handles: 0

Handle 0x0025, DMI type 10, 6 bytes
On Board Device Information
    Type: Video
    Status: Enabled
    Description:    To Be Filled By O.E.M.

Handle 0x002D, DMI type 41, 11 bytes
Onboard Device
    Reference Designation:  Onboard IGD
    Type: Video
    Status: Enabled
    Type Instance: 1
    Bus Address: 0000:00:02.0

Handle 0x002E, DMI type 41, 11 bytes
Onboard Device
    Reference Designation:  Onboard LAN
    Type: Ethernet
    Status: Enabled
    Type Instance: 1
    Bus Address: 0000:00:19.0

Handle 0x002F, DMI type 41, 11 bytes
Onboard Device
    Reference Designation:  Onboard 1394
    Type: Other
    Status: Enabled
    Type Instance: 1
    Bus Address: 0000:03:1c.2

I've tried to manually install driver for Realtek 8111G driver (since that is the one it seems to be the right one according to https://up-board.org/ai-edge/vision-plus-x) with:
sudo apt-get install r8168-dkms
...but still nothing

Also, when plugging live LAN cable LED diodes on the ethernet port on the Vision Plus X light up, so it seems that it is alive to some extent, but still I'm not sure if this is hardware issue or not. The USB ports on Vision Plus X are working without any issue, and Myriad chips can be detected and used, although not without issues, but that is the topic for another discussion

Has anybody encountered this issue with the UP Core Plus and Vision Plus X, any idea what can be done to make it work?

Thanks,
Damir

EDIT: Sorry for the formatting, I've put all the console commands/output under code, not sure why it didn't work for all the sections

On the datasheet, it is named "DOCKING III (i2c)".

We would like to connect an i2c IMU on it so I need the pinout and the voltage level please.

Thank you.

Is it typically just visible as another PCIe device? I only see drivers in the software section for Windows 10, I assume Linux systems detect it on PCIe and use the appropriate module from the kernel for it.

For those of you that are using the Net Plus board, which OS are you using and did you have to perform any extra steps to make it accessible from the OS?

I've assembled them together and installed Ubuntu 18.04 and OpenVINO 2019R1.1, which works fine on CPU.
But when I try to run it with -d MYRIAD flag it fails with errors like can not find device, same thing for -d HDDL. I have followed all Linux installation guide steps and tried security_camera_bla_bla demo from OpenVINO demo directory.

Can you please provide proven step by step instruction for preparing and running Intel OpenVINO samples with all three embedded VPUs.

I have already run OpenVINO asynchronous yolo detection on Windows with IEI Acceleration board Mustang and 4 NCUs 2 under Windows 10 on my desktop PC using tiny-yolo model and 4 network instances per VPU.
It seems that my assembly works fine with NCS2, but it still reports some errors even it executed successfully.

Best regards
Aleksandr.

If i'm looking things up correctly EMEA means Europe, Middle East, Asia. But it also seems that it works in America. so i'm confused.

my hope is to use it as a pfsence gateway using multiple internet connections with lte/4g as a "fail safe"

currently use an up^2 at home. want to test this new set up at home before I put it in my business.

are they m.2?

do they happen to be mini-pcu compatable?

means i can use my up squared for something else

I want to know if it's possible to combine these boards together. I know I can combine the Core Plus + Net Plus boards but I don't know If I can put the AI Core in the Net Plus mPCIe slot. The reason for this is that I want to be able to use tensorflow (CNN) and also be able to connect any IP related product.

If that's possible, which enclosures, power adapters, etc..., do I need to buy?

Thanks in advance for the help.