UP Core i2c

grize · March 2021

Hi,

I'm trying to get the i2c interface working in Windows 10 64bit (full version, not IOT).

I have an UP Core 4GB/64GB with the Low Speed Carrier board. Latest BIOS is installed (UCR1BM18).

All drivers and the UP SDK have been installed.
One unknown device (Hardware ID *AANT0F02) in device manager since plugging in Low speed carrier board.

Could someone please confirm the pin out of the 30pin connector on the low speed carrier board? The pinout on the wiki page is different to the pinout in the UP carrier design guide pdf.

The bios has the option to select OS IMAGE ID: Windows or Android. It does not have the option to select Windows IOT. I understand it is necessary to select Windows IOT even when installing the full version of Windows if you want to use i2c, SPI etc, as this exposes the "Resource hub proxy device" in device manager. However this is not possible on the UP Core as far as I can see.

I would be grateful if anyone can help me to get the i2c interface enabled on the UP Core.

Thanks

grize · March 2021

Please can someone from the AAEON team respond regarding this?

Thanks

rogertsai(AAEON) · March 2021

@grize
What’s OS & SDK version you use?
You can find Windows 10 build number & version in Winver, and also check the SDK driver info about UpFramework in the Device Manager

grize · March 2021

@rogertsai(AAEON) Thanks for the reply.

Here are the details requested:
Windows 10 Version 20H2 (OS Build 19042.804)
Up Framework Service in device manager reports driver version: 14.39.25.704

I have got the i2c interface working now by using the ACPITABL file that is provided in this post: https://forum.up-community.org/discussion/comment/10778#Comment_10778

Please can you comment whether using this file is the recommended way of enabling i2c on the UP Core? If so can you add the file to the official downloads section for the board along with some documentation relating to the file contents and usage?

Thanks

UP Core i2c

Comments

Categories