# RSB-3720CQ-ACA2E GPIO Pins in Windows on ARM OS

**URL:** <https://forum.aim-linux.advantech.com/t/rsb-3720cq-aca2e-gpio-pins-in-windows-on-arm-os/681>\
**Category:** Technical Supports\
**Tags:** windows-10-iot-arm\
**Created:** [January 15, 2024, 11:39pm UTC](https://forum.aim-linux.advantech.com/t/rsb-3720cq-aca2e-gpio-pins-in-windows-on-arm-os/681 "2024-01-15T23:39:33Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andrew\_Chou](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.aim-linux.advantech.com/andrew_chou/32/89_2.png) [@Andrew\_Chou](https://forum.aim-linux.advantech.com/u/Andrew_Chou)\
**Post date:** [January 15, 2024, 11:39pm UTC](https://forum.aim-linux.advantech.com/t/rsb-3720cq-aca2e-gpio-pins-in-windows-on-arm-os/681/1 "2024-01-15T23:39:33Z")

</div>

According to RSB-3720 User’s Manual, RSB-3720 should have 10 Pins: 501, 503, 504, 505, 506, 507, 508, 509, 139, 138.  
But it shows 16 pins available: 83, 84, 85, 86, 87, 88, 136, 137, 138, 139, 140, 141, 146, 147, 154, 155 when I run “GpioTestTool.exe -list” command in Windows on ARM OS.  
I’m using the firmware and image from EPC3720A1AIM20WIV0007\_20230816 release.

![user_manual](https://us1.discourse-cdn.com/flex016/uploads/aim_linux/original/1X/695157b3b56039420d4874432dfe656d2ef0a035.png)  
 ![GpioTestTool](https://us1.discourse-cdn.com/flex016/uploads/aim_linux/original/1X/f8b5bdd17f053985a776b2d0ef6254fb7de15445.png)

---

<div class="post-metadata">

**Author:** ![charles.huang](https://avatars.discourse-cdn.com/v4/letter/c/76d3ee/32.png) [@charles.huang](https://forum.aim-linux.advantech.com/u/charles.huang)\
**Post date:** [January 16, 2024, 7:07am UTC](https://forum.aim-linux.advantech.com/t/rsb-3720cq-aca2e-gpio-pins-in-windows-on-arm-os/681/2 "2024-01-16T07:07:35Z")

</div>

The gpio interfaces are from i2c to gpio expander.  
We can’t use the standard tool to set/get the value.  
Here’s the limitation from NXP release at this moment

 ![image](https://us1.discourse-cdn.com/flex016/uploads/aim_linux/original/1X/81dd1bdaa4021b134c6125203643a7da75942af4.png)

---

<div class="post-metadata">

**Author:** ![Andrew\_Chou](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.aim-linux.advantech.com/andrew_chou/32/89_2.png) [@Andrew\_Chou](https://forum.aim-linux.advantech.com/u/Andrew_Chou)\
**Post date:** [January 16, 2024, 5:47pm UTC](https://forum.aim-linux.advantech.com/t/rsb-3720cq-aca2e-gpio-pins-in-windows-on-arm-os/681/3 "2024-01-16T17:47:48Z")

</div>

Thanks for replying. I have two additional questions:

1. RSB-3720 schematic shows the IO Expander we use in RSB-3720 is TI\_TCA9538PWR. Is that correct, or is it should be PCA6416?

2. Those 10 GPIO pins: 138, 139, 501, 503, 504, 505, 506, 507, 508, 509 are all controllable in Yocto Linux. Does that mean there is TI\_TCA9538/PCA6416 driver support for Linux, but not for Windows?

---

<div class="post-metadata">

**Author:** ![charles.huang](https://avatars.discourse-cdn.com/v4/letter/c/76d3ee/32.png) [@charles.huang](https://forum.aim-linux.advantech.com/u/charles.huang)\
**Post date:** [January 17, 2024, 5:40am UTC](https://forum.aim-linux.advantech.com/t/rsb-3720cq-aca2e-gpio-pins-in-windows-on-arm-os/681/4 "2024-01-17T05:40:29Z")

</div>

> [@Andrew\_Chou](#):
>
> - RSB-3720 schematic shows the IO Expander we use in RSB-3720 is TI\_TCA9538PWR. Is that correct, or is it should be PCA6416?
> - Those 10 GPIO pins: 138, 139, 501, 503, 504, 505, 506, 507, 508, 509 are all controllable in Yocto Linux. Does that mean there is TI\_TCA9538/PCA6416 driver support for Linux, but not for Windows?

Item 1: It’s TI\_TCA9538PWR. It can’t be supported without the Windows driver the same as PCA6416.  
Item 2: Yes, it’s directly supported by Linux on Arm platform.