Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?

Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?

[Andy Shevchenko]

Hi!

Since I have been playing with the $Subject board, I wondering if I miss
something or the BIOS configuration is utterly broken. The problem what
I see is that most of the pins on the SoC are marked with [ACPI] if you
look at the debugfs 'pins' file for INTC1057:00 device instance.

This means *none* of them (which are user visible via HAT connector) may
serve as an interrupt resource to the OS. How the OS should request interrupts
on those pins?

As far as I understand that the BIOS does initial settings of CPLD and
basically I can use transparently the pins as per their configuration done
in BIOS. Right?

Btw, do we have any contacts to engineers in AAEON or whoever who does these
UP boards nowadays?

-- 
With Best Regards,
Andy Shevchenko

Re: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?

[GaryWang]

Add AAEON software JunYing.

Hi Andy,
yeah the ACPI flag should not set for HAT pins, JunYin knows it,
They clear the ACPI flag from the driver now, their BIOS uses the default
from CRB, but they should fix it from the BIOS to match the right usage.

BR,
Gary.

On Fri, Jul 10, 2026 at 4:48 AM Andy Shevchenko
<andriy.shevchenko@intel.com> wrote:
>
> Hi!
>
> Since I have been playing with the $Subject board, I wondering if I miss
> something or the BIOS configuration is utterly broken. The problem what
> I see is that most of the pins on the SoC are marked with [ACPI] if you
> look at the debugfs 'pins' file for INTC1057:00 device instance.
>
> This means *none* of them (which are user visible via HAT connector) may
> serve as an interrupt resource to the OS. How the OS should request interrupts
> on those pins?
>
> As far as I understand that the BIOS does initial settings of CPLD and
> basically I can use transparently the pins as per their configuration done
> in BIOS. Right?
>
> Btw, do we have any contacts to engineers in AAEON or whoever who does these
> UP boards nowadays?
>
> --
> With Best Regards,
> Andy Shevchenko
>
>

Re: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?

[Andy Shevchenko]

On Fri, Jul 10, 2026 at 04:37:56PM +0800, GaryWang wrote:
> Add AAEON software JunYing.

Thanks, waiting for the response!

> yeah the ACPI flag should not set for HAT pins, JunYin knows it,
> They clear the ACPI flag from the driver now, their BIOS uses the default
> from CRB, but they should fix it from the BIOS to match the right usage.

How do they clean it from the driver? IIRC the ownership registers are locked
when BIOS hands over to the OS. Technically any pin that marked as GPIO input
must not be owned by ACPI to allow users to connect whatever they want there
and get an interrupts. Many of them also have "Locked full" permissions,
that's also may not be convenient. Another thing is the absence of bi-di GPIO
configuration (or did I miss that?), which people may want to have (my
use case, for instance).

In any case I have latest and greatest BIOS version (r3.5 of this year) and
problem still persists. Can AAEON share a BIOS for testing? (Note, if you
want, it can be done under our Intel-AAEON existing NDA, I believe.)

> On Fri, Jul 10, 2026 at 4:48 AM Andy Shevchenko
> <andriy.shevchenko@intel.com> wrote:
> >
> > Since I have been playing with the $Subject board, I wondering if I miss
> > something or the BIOS configuration is utterly broken. The problem what
> > I see is that most of the pins on the SoC are marked with [ACPI] if you
> > look at the debugfs 'pins' file for INTC1057:00 device instance.
> >
> > This means *none* of them (which are user visible via HAT connector) may
> > serve as an interrupt resource to the OS. How the OS should request interrupts
> > on those pins?
> >
> > As far as I understand that the BIOS does initial settings of CPLD and
> > basically I can use transparently the pins as per their configuration done
> > in BIOS. Right?
> >
> > Btw, do we have any contacts to engineers in AAEON or whoever who does these
> > UP boards nowadays?

-- 
With Best Regards,
Andy Shevchenko

RE: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?

[BillyChou 周博倫]

Dear Andy,

Thank you for your feedback, and we sincerely apologize for the delay.

We are currently updating the BIOS to configure the HAT connector pins to GPIO/GPO mode, which will ensure interrupt support on the OS side. We will update the BIOS as soon as possible and share it with you for testing.

Thanks again for your patience and support.

Best regards,
Billy Chou


-----Original Message-----
From: JunYingLai 賴俊穎 <JunYingLai@aaeon.com.tw> 
Sent: Thursday, July 23, 2026 2:48 PM
To: BillyChou 周博倫 <BillyChou@aaeon.com.tw>
Subject: FW: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?

FYI

Best Regards,
JunYing Lai

JunYing Lai
AAEON Technology Inc.
5F, No. 135, Lane 235, Pao Chiao Rd.
Hsin-Tien Dist, New Taipei City, 231
Taiwan, R.O.C.


TEL: +886-2-8919-1234 Ext.1891



-----Original Message-----
From: Andy Shevchenko <andriy.shevchenko@intel.com>
Sent: Friday, July 10, 2026 5:11 PM
To: GaryWang <is0124@gmail.com>
Cc: JunYingLai 賴俊穎 <JunYingLai@aaeon.com.tw>; Thomas Richard <thomas.richard@bootlin.com>; linux-gpio@vger.kernel.org; JasonHuang 黃仁杰 <JasonHuang@aaeon.com.tw>
Subject: Re: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?

這是外部郵件：在打開連結和附件之前，請確保電子郵件是安全的。 This is an external email: please make sure the email is secure before opening links and attachments.

On Fri, Jul 10, 2026 at 04:37:56PM +0800, GaryWang wrote:
> Add AAEON software JunYing.

Thanks, waiting for the response!

> yeah the ACPI flag should not set for HAT pins, JunYin knows it, They 
> clear the ACPI flag from the driver now, their BIOS uses the default 
> from CRB, but they should fix it from the BIOS to match the right usage.

How do they clean it from the driver? IIRC the ownership registers are locked when BIOS hands over to the OS. Technically any pin that marked as GPIO input must not be owned by ACPI to allow users to connect whatever they want there and get an interrupts. Many of them also have "Locked full" permissions, that's also may not be convenient. Another thing is the absence of bi-di GPIO configuration (or did I miss that?), which people may want to have (my use case, for instance).

In any case I have latest and greatest BIOS version (r3.5 of this year) and problem still persists. Can AAEON share a BIOS for testing? (Note, if you want, it can be done under our Intel-AAEON existing NDA, I believe.)

> On Fri, Jul 10, 2026 at 4:48 AM Andy Shevchenko 
> <andriy.shevchenko@intel.com> wrote:
> >
> > Since I have been playing with the $Subject board, I wondering if I 
> > miss something or the BIOS configuration is utterly broken. The 
> > problem what I see is that most of the pins on the SoC are marked 
> > with [ACPI] if you look at the debugfs 'pins' file for INTC1057:00 device instance.
> >
> > This means *none* of them (which are user visible via HAT connector) 
> > may serve as an interrupt resource to the OS. How the OS should 
> > request interrupts on those pins?
> >
> > As far as I understand that the BIOS does initial settings of CPLD 
> > and basically I can use transparently the pins as per their 
> > configuration done in BIOS. Right?
> >
> > Btw, do we have any contacts to engineers in AAEON or whoever who 
> > does these UP boards nowadays?

--
With Best Regards,
Andy Shevchenko

Re: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?

[Andy Shevchenko]

On Mon, Aug 10, 2026 at 04:17:43AM +0000, BillyChou 周博倫 wrote:
> Dear Andy,
> 
> Thank you for your feedback, and we sincerely apologize for the delay.
> 
> We are currently updating the BIOS to configure the HAT connector pins to
> GPIO/GPO mode, which will ensure interrupt support on the OS side. We will
> update the BIOS as soon as possible and share it with you for testing.
> 
> Thanks again for your patience and support.

Thanks for the good news, I'm looking forward to test it!

> -----Original Message-----
> From: JunYingLai 賴俊穎 <JunYingLai@aaeon.com.tw> 
> Sent: Thursday, July 23, 2026 2:48 PM
> To: BillyChou 周博倫 <BillyChou@aaeon.com.tw>
> Subject: FW: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?
> 
> FYI
> 
> Best Regards,
> JunYing Lai
> 
> JunYing Lai
> AAEON Technology Inc.
> 5F, No. 135, Lane 235, Pao Chiao Rd.
> Hsin-Tien Dist, New Taipei City, 231
> Taiwan, R.O.C.
> 
> 
> TEL: +886-2-8919-1234 Ext.1891
> 
> 
> 
> -----Original Message-----
> From: Andy Shevchenko <andriy.shevchenko@intel.com>
> Sent: Friday, July 10, 2026 5:11 PM
> To: GaryWang <is0124@gmail.com>
> Cc: JunYingLai 賴俊穎 <JunYingLai@aaeon.com.tw>; Thomas Richard <thomas.richard@bootlin.com>; linux-gpio@vger.kernel.org; JasonHuang 黃仁杰 <JasonHuang@aaeon.com.tw>
> Subject: Re: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?
> 
> 這是外部郵件：在打開連結和附件之前，請確保電子郵件是安全的。 This is an external email: please make sure the email is secure before opening links and attachments.
> 
> On Fri, Jul 10, 2026 at 04:37:56PM +0800, GaryWang wrote:
> > Add AAEON software JunYing.
> 
> Thanks, waiting for the response!
> 
> > yeah the ACPI flag should not set for HAT pins, JunYin knows it, They 
> > clear the ACPI flag from the driver now, their BIOS uses the default 
> > from CRB, but they should fix it from the BIOS to match the right usage.
> 
> How do they clean it from the driver? IIRC the ownership registers are locked
> when BIOS hands over to the OS. Technically any pin that marked as GPIO input
> must not be owned by ACPI to allow users to connect whatever they want there
> and get an interrupts. Many of them also have "Locked full" permissions,
> that's also may not be convenient. Another thing is the absence of bi-di GPIO
> configuration (or did I miss that?), which people may want to have (my use
> case, for instance).
> 
> In any case I have latest and greatest BIOS version (r3.5 of this year) and
> problem still persists. Can AAEON share a BIOS for testing? (Note, if you
> want, it can be done under our Intel-AAEON existing NDA, I believe.)
> 
> > On Fri, Jul 10, 2026 at 4:48 AM Andy Shevchenko 
> > <andriy.shevchenko@intel.com> wrote:
> > >
> > > Since I have been playing with the $Subject board, I wondering if I 
> > > miss something or the BIOS configuration is utterly broken. The 
> > > problem what I see is that most of the pins on the SoC are marked 
> > > with [ACPI] if you look at the debugfs 'pins' file for INTC1057:00 device instance.
> > >
> > > This means *none* of them (which are user visible via HAT connector) 
> > > may serve as an interrupt resource to the OS. How the OS should 
> > > request interrupts on those pins?
> > >
> > > As far as I understand that the BIOS does initial settings of CPLD 
> > > and basically I can use transparently the pins as per their 
> > > configuration done in BIOS. Right?
> > >
> > > Btw, do we have any contacts to engineers in AAEON or whoever who 
> > > does these UP boards nowadays?

-- 
With Best Regards,
Andy Shevchenko

RE: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?

[BillyChou 周博倫]

> On Mon, Aug 10, 2026 at 04:17:43AM +0000, BillyChou 周博倫 wrote:
> > Dear Andy,
> >
> > Thank you for your feedback, and we sincerely apologize for the delay.
> >
> > We are currently updating the BIOS to configure the HAT connector pins
> > to GPIO/GPO mode, which will ensure interrupt support on the OS side.
> > We will update the BIOS as soon as possible and share it with you for testing.
> >
> > Thanks again for your patience and support.
> 
> Thanks for the good news, I'm looking forward to test it!
> 
The updated BIOS for the UPN-ADLN01 project with the HAT connector pin configurations is ready. Kindly download it here for testing:
https://aaeon365-my.sharepoint.com/personal/nas_aaeon_com_tw/_layouts/15/onedrive.aspx?id=%2Fpersonal%2Fnas%5Faaeon%5Fcom%5Ftw%2FDocuments%2F007%E8%BB%9F%E9%AB%94%E9%96%8B%E7%99%BC%E8%99%95%2FBIOS%2F%5FReleased%5FBIOS%2FUPN%2DADLN01%2FUNASAM36%2Ezip&parent=%2Fpersonal%2Fnas%5Faaeon%5Fcom%5Ftw%2FDocuments%2F007%E8%BB%9F%E9%AB%94%E9%96%8B%E7%99%BC%E8%99%95%2FBIOS%2F%5FReleased%5FBIOS%2FUPN%2DADLN01&ga=1&LOF=1

> > -----Original Message-----
> > From: JunYingLai 賴俊穎 <JunYingLai@aaeon.com.tw>
> > Sent: Thursday, July 23, 2026 2:48 PM
> > To: BillyChou 周博倫 <BillyChou@aaeon.com.tw>
> > Subject: FW: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?
> >
> > FYI
> >
> > Best Regards,
> > JunYing Lai
> >
> > JunYing Lai
> > AAEON Technology Inc.
> > 5F, No. 135, Lane 235, Pao Chiao Rd.
> > Hsin-Tien Dist, New Taipei City, 231
> > Taiwan, R.O.C.
> >
> >
> > TEL: +886-2-8919-1234 Ext.1891
> >
> >
> >
> > -----Original Message-----
> > From: Andy Shevchenko <andriy.shevchenko@intel.com>
> > Sent: Friday, July 10, 2026 5:11 PM
> > To: GaryWang <is0124@gmail.com>
> > Cc: JunYingLai 賴俊穎 <JunYingLai@aaeon.com.tw>; Thomas Richard
> > <thomas.richard@bootlin.com>; linux-gpio@vger.kernel.org; JasonHuang
> > 黃仁杰 <JasonHuang@aaeon.com.tw>
> > Subject: Re: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?
> >
> > 這是外部郵件：在打開連結和附件之前，請確保電子郵件是安全的。 This
> is an external email: please make sure the email is secure before opening links
> and attachments.
> >
> > On Fri, Jul 10, 2026 at 04:37:56PM +0800, GaryWang wrote:
> > > Add AAEON software JunYing.
> >
> > Thanks, waiting for the response!
> >
> > > yeah the ACPI flag should not set for HAT pins, JunYin knows it,
> > > They clear the ACPI flag from the driver now, their BIOS uses the
> > > default from CRB, but they should fix it from the BIOS to match the right
> usage.
> >
> > How do they clean it from the driver? IIRC the ownership registers are
> > locked when BIOS hands over to the OS. Technically any pin that marked
> > as GPIO input must not be owned by ACPI to allow users to connect
> > whatever they want there and get an interrupts. Many of them also have
> > "Locked full" permissions, that's also may not be convenient. Another
> > thing is the absence of bi-di GPIO configuration (or did I miss
> > that?), which people may want to have (my use case, for instance).
> >
> > In any case I have latest and greatest BIOS version (r3.5 of this
> > year) and problem still persists. Can AAEON share a BIOS for testing?
> > (Note, if you want, it can be done under our Intel-AAEON existing NDA,
> > I believe.)
> >
> > > On Fri, Jul 10, 2026 at 4:48 AM Andy Shevchenko
> > > <andriy.shevchenko@intel.com> wrote:
> > > >
> > > > Since I have been playing with the $Subject board, I wondering if
> > > > I miss something or the BIOS configuration is utterly broken. The
> > > > problem what I see is that most of the pins on the SoC are marked
> > > > with [ACPI] if you look at the debugfs 'pins' file for INTC1057:00 device
> instance.
> > > >
> > > > This means *none* of them (which are user visible via HAT
> > > > connector) may serve as an interrupt resource to the OS. How the
> > > > OS should request interrupts on those pins?
> > > >
> > > > As far as I understand that the BIOS does initial settings of CPLD
> > > > and basically I can use transparently the pins as per their
> > > > configuration done in BIOS. Right?
> > > >
> > > > Btw, do we have any contacts to engineers in AAEON or whoever who
> > > > does these UP boards nowadays?
> 
> --
> With Best Regards,
> Andy Shevchenko
> 

Re: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?

[Andy Shevchenko]

On Thu, Aug 20, 2026 at 05:19:06AM +0000, BillyChou 周博倫 wrote:
> > On Mon, Aug 10, 2026 at 04:17:43AM +0000, BillyChou 周博倫 wrote:
> > > Dear Andy,
> > >
> > > Thank you for your feedback, and we sincerely apologize for the delay.
> > >
> > > We are currently updating the BIOS to configure the HAT connector pins
> > > to GPIO/GPO mode, which will ensure interrupt support on the OS side.
> > > We will update the BIOS as soon as possible and share it with you for testing.
> > >
> > > Thanks again for your patience and support.
> > 
> > Thanks for the good news, I'm looking forward to test it!
> > 
> The updated BIOS for the UPN-ADLN01 project with the HAT connector pin configurations is ready. Kindly download it here for testing:
> https://aaeon365-my.sharepoint.com/personal/nas_aaeon_com_tw/_layouts/15/onedrive.aspx?id=%2Fpersonal%2Fnas%5Faaeon%5Fcom%5Ftw%2FDocuments%2F007%E8%BB%9F%E9%AB%94%E9%96%8B%E7%99%BC%E8%99%95%2FBIOS%2F%5FReleased%5FBIOS%2FUPN%2DADLN01%2FUNASAM36%2Ezip&parent=%2Fpersonal%2Fnas%5Faaeon%5Fcom%5Ftw%2FDocuments%2F007%E8%BB%9F%E9%AB%94%E9%96%8B%E7%99%BC%E8%99%95%2FBIOS%2F%5FReleased%5FBIOS%2FUPN%2DADLN01&ga=1&LOF=1

Hmm... I can't login there with my @intel.com account. I suppose that share is
only for your company. Maybe MS Teams will work better?

> > > -----Original Message-----
> > > From: JunYingLai 賴俊穎 <JunYingLai@aaeon.com.tw>
> > > Sent: Thursday, July 23, 2026 2:48 PM
> > > To: BillyChou 周博倫 <BillyChou@aaeon.com.tw>
> > > Subject: FW: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?
> > >
> > > FYI
> > >
> > > Best Regards,
> > > JunYing Lai
> > >
> > > JunYing Lai
> > > AAEON Technology Inc.
> > > 5F, No. 135, Lane 235, Pao Chiao Rd.
> > > Hsin-Tien Dist, New Taipei City, 231
> > > Taiwan, R.O.C.
> > >
> > >
> > > TEL: +886-2-8919-1234 Ext.1891
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: Andy Shevchenko <andriy.shevchenko@intel.com>
> > > Sent: Friday, July 10, 2026 5:11 PM
> > > To: GaryWang <is0124@gmail.com>
> > > Cc: JunYingLai 賴俊穎 <JunYingLai@aaeon.com.tw>; Thomas Richard
> > > <thomas.richard@bootlin.com>; linux-gpio@vger.kernel.org; JasonHuang
> > > 黃仁杰 <JasonHuang@aaeon.com.tw>
> > > Subject: Re: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?
> > >
> > > 這是外部郵件：在打開連結和附件之前，請確保電子郵件是安全的。 This
> > is an external email: please make sure the email is secure before opening links
> > and attachments.
> > >
> > > On Fri, Jul 10, 2026 at 04:37:56PM +0800, GaryWang wrote:
> > > > Add AAEON software JunYing.
> > >
> > > Thanks, waiting for the response!
> > >
> > > > yeah the ACPI flag should not set for HAT pins, JunYin knows it,
> > > > They clear the ACPI flag from the driver now, their BIOS uses the
> > > > default from CRB, but they should fix it from the BIOS to match the right
> > usage.
> > >
> > > How do they clean it from the driver? IIRC the ownership registers are
> > > locked when BIOS hands over to the OS. Technically any pin that marked
> > > as GPIO input must not be owned by ACPI to allow users to connect
> > > whatever they want there and get an interrupts. Many of them also have
> > > "Locked full" permissions, that's also may not be convenient. Another
> > > thing is the absence of bi-di GPIO configuration (or did I miss
> > > that?), which people may want to have (my use case, for instance).
> > >
> > > In any case I have latest and greatest BIOS version (r3.5 of this
> > > year) and problem still persists. Can AAEON share a BIOS for testing?
> > > (Note, if you want, it can be done under our Intel-AAEON existing NDA,
> > > I believe.)
> > >
> > > > On Fri, Jul 10, 2026 at 4:48 AM Andy Shevchenko
> > > > <andriy.shevchenko@intel.com> wrote:
> > > > >
> > > > > Since I have been playing with the $Subject board, I wondering if
> > > > > I miss something or the BIOS configuration is utterly broken. The
> > > > > problem what I see is that most of the pins on the SoC are marked
> > > > > with [ACPI] if you look at the debugfs 'pins' file for INTC1057:00 device
> > instance.
> > > > >
> > > > > This means *none* of them (which are user visible via HAT
> > > > > connector) may serve as an interrupt resource to the OS. How the
> > > > > OS should request interrupts on those pins?
> > > > >
> > > > > As far as I understand that the BIOS does initial settings of CPLD
> > > > > and basically I can use transparently the pins as per their
> > > > > configuration done in BIOS. Right?
> > > > >
> > > > > Btw, do we have any contacts to engineers in AAEON or whoever who
> > > > > does these UP boards nowadays?

-- 
With Best Regards,
Andy Shevchenko

Re: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?

[Andy Shevchenko]

On Thu, Aug 20, 2026 at 09:23:43AM +0300, Andy Shevchenko wrote:
> On Thu, Aug 20, 2026 at 05:19:06AM +0000, BillyChou 周博倫 wrote:
> > > On Mon, Aug 10, 2026 at 04:17:43AM +0000, BillyChou 周博倫 wrote:
> > > > Dear Andy,
> > > >
> > > > Thank you for your feedback, and we sincerely apologize for the delay.
> > > >
> > > > We are currently updating the BIOS to configure the HAT connector pins
> > > > to GPIO/GPO mode, which will ensure interrupt support on the OS side.
> > > > We will update the BIOS as soon as possible and share it with you for testing.
> > > >
> > > > Thanks again for your patience and support.
> > > 
> > > Thanks for the good news, I'm looking forward to test it!
> > > 
> > The updated BIOS for the UPN-ADLN01 project with the HAT connector pin configurations is ready. Kindly download it here for testing:
> > https://aaeon365-my.sharepoint.com/personal/nas_aaeon_com_tw/_layouts/15/onedrive.aspx?id=%2Fpersonal%2Fnas%5Faaeon%5Fcom%5Ftw%2FDocuments%2F007%E8%BB%9F%E9%AB%94%E9%96%8B%E7%99%BC%E8%99%95%2FBIOS%2F%5FReleased%5FBIOS%2FUPN%2DADLN01%2FUNASAM36%2Ezip&parent=%2Fpersonal%2Fnas%5Faaeon%5Fcom%5Ftw%2FDocuments%2F007%E8%BB%9F%E9%AB%94%E9%96%8B%E7%99%BC%E8%99%95%2FBIOS%2F%5FReleased%5FBIOS%2FUPN%2DADLN01&ga=1&LOF=1
> 
> Hmm... I can't login there with my @intel.com account. I suppose that share is
> only for your company. Maybe MS Teams will work better?

Or just sent an archive privately to my @intel.com address?

> > > > -----Original Message-----
> > > > From: JunYingLai 賴俊穎 <JunYingLai@aaeon.com.tw>
> > > > Sent: Thursday, July 23, 2026 2:48 PM
> > > > To: BillyChou 周博倫 <BillyChou@aaeon.com.tw>
> > > > Subject: FW: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?
> > > >
> > > > FYI
> > > >
> > > > Best Regards,
> > > > JunYing Lai
> > > >
> > > > JunYing Lai
> > > > AAEON Technology Inc.
> > > > 5F, No. 135, Lane 235, Pao Chiao Rd.
> > > > Hsin-Tien Dist, New Taipei City, 231
> > > > Taiwan, R.O.C.
> > > >
> > > >
> > > > TEL: +886-2-8919-1234 Ext.1891
> > > >
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: Andy Shevchenko <andriy.shevchenko@intel.com>
> > > > Sent: Friday, July 10, 2026 5:11 PM
> > > > To: GaryWang <is0124@gmail.com>
> > > > Cc: JunYingLai 賴俊穎 <JunYingLai@aaeon.com.tw>; Thomas Richard
> > > > <thomas.richard@bootlin.com>; linux-gpio@vger.kernel.org; JasonHuang
> > > > 黃仁杰 <JasonHuang@aaeon.com.tw>
> > > > Subject: Re: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?
> > > >
> > > > 這是外部郵件：在打開連結和附件之前，請確保電子郵件是安全的。 This
> > > is an external email: please make sure the email is secure before opening links
> > > and attachments.
> > > >
> > > > On Fri, Jul 10, 2026 at 04:37:56PM +0800, GaryWang wrote:
> > > > > Add AAEON software JunYing.
> > > >
> > > > Thanks, waiting for the response!
> > > >
> > > > > yeah the ACPI flag should not set for HAT pins, JunYin knows it,
> > > > > They clear the ACPI flag from the driver now, their BIOS uses the
> > > > > default from CRB, but they should fix it from the BIOS to match the right
> > > usage.
> > > >
> > > > How do they clean it from the driver? IIRC the ownership registers are
> > > > locked when BIOS hands over to the OS. Technically any pin that marked
> > > > as GPIO input must not be owned by ACPI to allow users to connect
> > > > whatever they want there and get an interrupts. Many of them also have
> > > > "Locked full" permissions, that's also may not be convenient. Another
> > > > thing is the absence of bi-di GPIO configuration (or did I miss
> > > > that?), which people may want to have (my use case, for instance).
> > > >
> > > > In any case I have latest and greatest BIOS version (r3.5 of this
> > > > year) and problem still persists. Can AAEON share a BIOS for testing?
> > > > (Note, if you want, it can be done under our Intel-AAEON existing NDA,
> > > > I believe.)
> > > >
> > > > > On Fri, Jul 10, 2026 at 4:48 AM Andy Shevchenko
> > > > > <andriy.shevchenko@intel.com> wrote:
> > > > > >
> > > > > > Since I have been playing with the $Subject board, I wondering if
> > > > > > I miss something or the BIOS configuration is utterly broken. The
> > > > > > problem what I see is that most of the pins on the SoC are marked
> > > > > > with [ACPI] if you look at the debugfs 'pins' file for INTC1057:00 device
> > > instance.
> > > > > >
> > > > > > This means *none* of them (which are user visible via HAT
> > > > > > connector) may serve as an interrupt resource to the OS. How the
> > > > > > OS should request interrupts on those pins?
> > > > > >
> > > > > > As far as I understand that the BIOS does initial settings of CPLD
> > > > > > and basically I can use transparently the pins as per their
> > > > > > configuration done in BIOS. Right?
> > > > > >
> > > > > > Btw, do we have any contacts to engineers in AAEON or whoever who
> > > > > > does these UP boards nowadays?
> 
> -- 
> With Best Regards,
> Andy Shevchenko
> 
> 

-- 
With Best Regards,
Andy Shevchenko

RE: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?

[BillyChou 周博倫]

> On Thu, Aug 20, 2026 at 09:23:43AM +0300, Andy Shevchenko wrote:
> > On Thu, Aug 20, 2026 at 05:19:06AM +0000, BillyChou 周博倫 wrote:
> > > > On Mon, Aug 10, 2026 at 04:17:43AM +0000, BillyChou 周博倫 wrote:
> > > > > Dear Andy,
> > > > >
> > > > > Thank you for your feedback, and we sincerely apologize for the delay.
> > > > >
> > > > > We are currently updating the BIOS to configure the HAT
> > > > > connector pins to GPIO/GPO mode, which will ensure interrupt support
> on the OS side.
> > > > > We will update the BIOS as soon as possible and share it with you for
> testing.
> > > > >
> > > > > Thanks again for your patience and support.
> > > >
> > > > Thanks for the good news, I'm looking forward to test it!
> > > >
> > > The updated BIOS for the UPN-ADLN01 project with the HAT connector pin
> configurations is ready. Kindly download it here for testing:
> > > https://aaeon365-my.sharepoint.com/personal/nas_aaeon_com_tw/_layout
> > >
> s/15/onedrive.aspx?id=%2fpersonal%2fnas_aaeon_com_tw%2fDocuments%2f0
> > >
> 07%E8%BB%9F%E9%AB%94%E9%96%8B%E7%99%BC%E8%99%95%2fBIOS%2f
> _Released_B
> > >
> IOS%2fUPN-ADLN01%2fUNASAM36.zip&parent=%2fpersonal%2fnas_aaeon_co
> m_t
> > >
> w%2fDocuments%2f007%E8%BB%9F%E9%AB%94%E9%96%8B%E7%99%BC%E8
> %99%95%2fB
> > >
> IOS%2f_Released_BIOS%2fUPN-ADLN01&ga=1&LOF=1&xsdata=MDV8MDJ8Q
> mlsbHlD
> > >
> aG91QGFhZW9uLmNvbS50d3w5MDU1ZThjNmE5NjQ0YjA1ZWQxYjA4ZGVmZTgz
> YjJiZHw1
> > >
> NmEyZDRiZTlmZTM0MzBlYjUzOTdlMTNhNDc0NDg1N3wwfDB8NjM5MjI4MDM
> 4OTk2Njk3
> > >
> MjY5fFVua25vd258VFdGcGJHWnNiM2Q4ZXlKRmJYQjBlVTFoY0draU9uUnlkV1Vz
> SWxZ
> > >
> aU9pSXdMakF1TURBd01DSXNJbEFpT2lKWGFXNHpNaUlzSWtGT0lqb2lUV0ZwYk
> NJc0ls
> > >
> ZFVJam95ZlE9PXwwfHx8&sdata=UldHMlhFNWxXM3htaDFCMGdKV3pZTTZ1Mz
> ZOMFBzW
> > > GdSNmthM2RsNnFzST0%3d
> >
> > Hmm... I can't login there with my @intel.com account. I suppose that
> > share is only for your company. Maybe MS Teams will work better?
> 
> Or just sent an archive privately to my @intel.com address?
> 
Sorry about that! I’ve updated the download link and fixed the permissions. Could you please give it another try? Thanks!
https://aaeon365-my.sharepoint.com/:u:/g/personal/billychou_aaeon_com_tw/IQAdsTdWUQhvQpAoS8lELTe8AZK70ORl6FB-Ndcf0lXUwus?e=ZV0MvS

> > > > > -----Original Message-----
> > > > > From: JunYingLai 賴俊穎 <JunYingLai@aaeon.com.tw>
> > > > > Sent: Thursday, July 23, 2026 2:48 PM
> > > > > To: BillyChou 周博倫 <BillyChou@aaeon.com.tw>
> > > > > Subject: FW: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?
> > > > >
> > > > > FYI
> > > > >
> > > > > Best Regards,
> > > > > JunYing Lai
> > > > >
> > > > > JunYing Lai
> > > > > AAEON Technology Inc.
> > > > > 5F, No. 135, Lane 235, Pao Chiao Rd.
> > > > > Hsin-Tien Dist, New Taipei City, 231 Taiwan, R.O.C.
> > > > >
> > > > >
> > > > > TEL: +886-2-8919-1234 Ext.1891
> > > > >
> > > > >
> > > > >
> > > > > -----Original Message-----
> > > > > From: Andy Shevchenko <andriy.shevchenko@intel.com>
> > > > > Sent: Friday, July 10, 2026 5:11 PM
> > > > > To: GaryWang <is0124@gmail.com>
> > > > > Cc: JunYingLai 賴俊穎 <JunYingLai@aaeon.com.tw>; Thomas Richard
> > > > > <thomas.richard@bootlin.com>; linux-gpio@vger.kernel.org;
> JasonHuang
> > > > > 黃仁杰 <JasonHuang@aaeon.com.tw>
> > > > > Subject: Re: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?
> > > > >
> > > > > 這是外部郵件：在打開連結和附件之前，請確保電子郵件是安全的。
> This
> > > > is an external email: please make sure the email is secure before
> opening links
> > > > and attachments.
> > > > >
> > > > > On Fri, Jul 10, 2026 at 04:37:56PM +0800, GaryWang wrote:
> > > > > > Add AAEON software JunYing.
> > > > >
> > > > > Thanks, waiting for the response!
> > > > >
> > > > > > yeah the ACPI flag should not set for HAT pins, JunYin knows it,
> > > > > > They clear the ACPI flag from the driver now, their BIOS uses the
> > > > > > default from CRB, but they should fix it from the BIOS to match the
> right
> > > > usage.
> > > > >
> > > > > How do they clean it from the driver? IIRC the ownership registers are
> > > > > locked when BIOS hands over to the OS. Technically any pin that
> marked
> > > > > as GPIO input must not be owned by ACPI to allow users to connect
> > > > > whatever they want there and get an interrupts. Many of them also
> have
> > > > > "Locked full" permissions, that's also may not be convenient. Another
> > > > > thing is the absence of bi-di GPIO configuration (or did I miss
> > > > > that?), which people may want to have (my use case, for instance).
> > > > >
> > > > > In any case I have latest and greatest BIOS version (r3.5 of this
> > > > > year) and problem still persists. Can AAEON share a BIOS for testing?
> > > > > (Note, if you want, it can be done under our Intel-AAEON existing NDA,
> > > > > I believe.)
> > > > >
> > > > > > On Fri, Jul 10, 2026 at 4:48 AM Andy Shevchenko
> > > > > > <andriy.shevchenko@intel.com> wrote:
> > > > > > >
> > > > > > > Since I have been playing with the $Subject board, I wondering if
> > > > > > > I miss something or the BIOS configuration is utterly broken. The
> > > > > > > problem what I see is that most of the pins on the SoC are marked
> > > > > > > with [ACPI] if you look at the debugfs 'pins' file for INTC1057:00
> device
> > > > instance.
> > > > > > >
> > > > > > > This means *none* of them (which are user visible via HAT
> > > > > > > connector) may serve as an interrupt resource to the OS. How the
> > > > > > > OS should request interrupts on those pins?
> > > > > > >
> > > > > > > As far as I understand that the BIOS does initial settings of CPLD
> > > > > > > and basically I can use transparently the pins as per their
> > > > > > > configuration done in BIOS. Right?
> > > > > > >
> > > > > > > Btw, do we have any contacts to engineers in AAEON or whoever
> who
> > > > > > > does these UP boards nowadays?
> >
> > --
> > With Best Regards,
> > Andy Shevchenko
> >
> >
> 
> --
> With Best Regards,
> Andy Shevchenko
> 

Re: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?

[Andy Shevchenko]

On Thu, Aug 20, 2026 at 10:04:13AM +0000, BillyChou 周博倫 wrote:
> > On Thu, Aug 20, 2026 at 09:23:43AM +0300, Andy Shevchenko wrote:
> > > On Thu, Aug 20, 2026 at 05:19:06AM +0000, BillyChou 周博倫 wrote:
> > > > > On Mon, Aug 10, 2026 at 04:17:43AM +0000, BillyChou 周博倫 wrote:
> > > > > > Dear Andy,
> > > > > >
> > > > > > Thank you for your feedback, and we sincerely apologize for the delay.
> > > > > >
> > > > > > We are currently updating the BIOS to configure the HAT
> > > > > > connector pins to GPIO/GPO mode, which will ensure interrupt support
> > on the OS side.
> > > > > > We will update the BIOS as soon as possible and share it with you for
> > testing.
> > > > > >
> > > > > > Thanks again for your patience and support.
> > > > >
> > > > > Thanks for the good news, I'm looking forward to test it!
> > > > >
> > > > The updated BIOS for the UPN-ADLN01 project with the HAT connector pin
> > configurations is ready. Kindly download it here for testing:
> > > > https://aaeon365-my.sharepoint.com/personal/nas_aaeon_com_tw/_layout
> > > >
> > s/15/onedrive.aspx?id=%2fpersonal%2fnas_aaeon_com_tw%2fDocuments%2f0
> > > >
> > 07%E8%BB%9F%E9%AB%94%E9%96%8B%E7%99%BC%E8%99%95%2fBIOS%2f
> > _Released_B
> > > >
> > IOS%2fUPN-ADLN01%2fUNASAM36.zip&parent=%2fpersonal%2fnas_aaeon_co
> > m_t
> > > >
> > w%2fDocuments%2f007%E8%BB%9F%E9%AB%94%E9%96%8B%E7%99%BC%E8
> > %99%95%2fB
> > > >
> > IOS%2f_Released_BIOS%2fUPN-ADLN01&ga=1&LOF=1&xsdata=MDV8MDJ8Q
> > mlsbHlD
> > > >
> > aG91QGFhZW9uLmNvbS50d3w5MDU1ZThjNmE5NjQ0YjA1ZWQxYjA4ZGVmZTgz
> > YjJiZHw1
> > > >
> > NmEyZDRiZTlmZTM0MzBlYjUzOTdlMTNhNDc0NDg1N3wwfDB8NjM5MjI4MDM
> > 4OTk2Njk3
> > > >
> > MjY5fFVua25vd258VFdGcGJHWnNiM2Q4ZXlKRmJYQjBlVTFoY0draU9uUnlkV1Vz
> > SWxZ
> > > >
> > aU9pSXdMakF1TURBd01DSXNJbEFpT2lKWGFXNHpNaUlzSWtGT0lqb2lUV0ZwYk
> > NJc0ls
> > > >
> > ZFVJam95ZlE9PXwwfHx8&sdata=UldHMlhFNWxXM3htaDFCMGdKV3pZTTZ1Mz
> > ZOMFBzW
> > > > GdSNmthM2RsNnFzST0%3d
> > >
> > > Hmm... I can't login there with my @intel.com account. I suppose that
> > > share is only for your company. Maybe MS Teams will work better?
> > 
> > Or just sent an archive privately to my @intel.com address?
> > 
> Sorry about that! I’ve updated the download link and fixed the permissions. Could you please give it another try? Thanks!
> https://aaeon365-my.sharepoint.com/:u:/g/personal/billychou_aaeon_com_tw/IQAdsTdWUQhvQpAoS8lELTe8AZK70ORl6FB-Ndcf0lXUwus?e=ZV0MvS

Thank you!

Sorry for the delayed reply (for the record I have updated BIOS more than two
weeks ago, but haven't had time actually perform any tests). Today I tried to
use so called GPIO 11 and GPIO 12 (on 40-pin HAT connector) as input for the
event generation. It works nicely. Also I have briefly looked at the 'pins' file
for the pins 205 and 208 (Is that correct mapping? I took it from the _CRS of
the respective Device object in DSDT), and also checked the whole list at a glance.
All seems much better now — no [ACPI], no [LOCKED *] flags were set, which is the
goal. TL;DR: I can confirm it works for me! Would this be an official one or should
I wait for the official release and re-test?

> > > > > > -----Original Message-----
> > > > > > From: JunYingLai 賴俊穎 <JunYingLai@aaeon.com.tw>
> > > > > > Sent: Thursday, July 23, 2026 2:48 PM
> > > > > > To: BillyChou 周博倫 <BillyChou@aaeon.com.tw>
> > > > > > Subject: FW: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?
> > > > > >
> > > > > > FYI
> > > > > >
> > > > > > Best Regards,
> > > > > > JunYing Lai
> > > > > >
> > > > > > JunYing Lai
> > > > > > AAEON Technology Inc.
> > > > > > 5F, No. 135, Lane 235, Pao Chiao Rd.
> > > > > > Hsin-Tien Dist, New Taipei City, 231 Taiwan, R.O.C.
> > > > > >
> > > > > >
> > > > > > TEL: +886-2-8919-1234 Ext.1891
> > > > > >
> > > > > >
> > > > > >
> > > > > > -----Original Message-----
> > > > > > From: Andy Shevchenko <andriy.shevchenko@intel.com>
> > > > > > Sent: Friday, July 10, 2026 5:11 PM
> > > > > > To: GaryWang <is0124@gmail.com>
> > > > > > Cc: JunYingLai 賴俊穎 <JunYingLai@aaeon.com.tw>; Thomas Richard
> > > > > > <thomas.richard@bootlin.com>; linux-gpio@vger.kernel.org;
> > JasonHuang
> > > > > > 黃仁杰 <JasonHuang@aaeon.com.tw>
> > > > > > Subject: Re: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?
> > > > > >
> > > > > > 這是外部郵件：在打開連結和附件之前，請確保電子郵件是安全的。
> > This
> > > > > is an external email: please make sure the email is secure before
> > opening links
> > > > > and attachments.
> > > > > >
> > > > > > On Fri, Jul 10, 2026 at 04:37:56PM +0800, GaryWang wrote:
> > > > > > > Add AAEON software JunYing.
> > > > > >
> > > > > > Thanks, waiting for the response!
> > > > > >
> > > > > > > yeah the ACPI flag should not set for HAT pins, JunYin knows it,
> > > > > > > They clear the ACPI flag from the driver now, their BIOS uses the
> > > > > > > default from CRB, but they should fix it from the BIOS to match the
> > right
> > > > > usage.
> > > > > >
> > > > > > How do they clean it from the driver? IIRC the ownership registers are
> > > > > > locked when BIOS hands over to the OS. Technically any pin that
> > marked
> > > > > > as GPIO input must not be owned by ACPI to allow users to connect
> > > > > > whatever they want there and get an interrupts. Many of them also
> > have
> > > > > > "Locked full" permissions, that's also may not be convenient. Another
> > > > > > thing is the absence of bi-di GPIO configuration (or did I miss
> > > > > > that?), which people may want to have (my use case, for instance).
> > > > > >
> > > > > > In any case I have latest and greatest BIOS version (r3.5 of this
> > > > > > year) and problem still persists. Can AAEON share a BIOS for testing?
> > > > > > (Note, if you want, it can be done under our Intel-AAEON existing NDA,
> > > > > > I believe.)
> > > > > >
> > > > > > > On Fri, Jul 10, 2026 at 4:48 AM Andy Shevchenko
> > > > > > > <andriy.shevchenko@intel.com> wrote:
> > > > > > > >
> > > > > > > > Since I have been playing with the $Subject board, I wondering if
> > > > > > > > I miss something or the BIOS configuration is utterly broken. The
> > > > > > > > problem what I see is that most of the pins on the SoC are marked
> > > > > > > > with [ACPI] if you look at the debugfs 'pins' file for INTC1057:00
> > device
> > > > > instance.
> > > > > > > >
> > > > > > > > This means *none* of them (which are user visible via HAT
> > > > > > > > connector) may serve as an interrupt resource to the OS. How the
> > > > > > > > OS should request interrupts on those pins?
> > > > > > > >
> > > > > > > > As far as I understand that the BIOS does initial settings of CPLD
> > > > > > > > and basically I can use transparently the pins as per their
> > > > > > > > configuration done in BIOS. Right?
> > > > > > > >
> > > > > > > > Btw, do we have any contacts to engineers in AAEON or whoever
> > who
> > > > > > > > does these UP boards nowadays?

-- 
With Best Regards,
Andy Shevchenko

Re: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?

[Thomas Richard]

On 9/11/26 8:18 PM, Andy Shevchenko wrote:
> On Thu, Aug 20, 2026 at 10:04:13AM +0000, BillyChou 周博倫 wrote:
>>> On Thu, Aug 20, 2026 at 09:23:43AM +0300, Andy Shevchenko wrote:
>>>> On Thu, Aug 20, 2026 at 05:19:06AM +0000, BillyChou 周博倫 wrote:
>>>>>> On Mon, Aug 10, 2026 at 04:17:43AM +0000, BillyChou 周博倫 wrote:
>>>>>>> Dear Andy,
>>>>>>>
>>>>>>> Thank you for your feedback, and we sincerely apologize for the delay.
>>>>>>>
>>>>>>> We are currently updating the BIOS to configure the HAT
>>>>>>> connector pins to GPIO/GPO mode, which will ensure interrupt support
>>> on the OS side.
>>>>>>> We will update the BIOS as soon as possible and share it with you for
>>> testing.
>>>>>>>
>>>>>>> Thanks again for your patience and support.
>>>>>>
>>>>>> Thanks for the good news, I'm looking forward to test it!
>>>>>>
>>>>> The updated BIOS for the UPN-ADLN01 project with the HAT connector pin
>>> configurations is ready. Kindly download it here for testing:
>>>>> https://aaeon365-my.sharepoint.com/personal/nas_aaeon_com_tw/_layout
>>>>>
>>> s/15/onedrive.aspx?id=%2fpersonal%2fnas_aaeon_com_tw%2fDocuments%2f0
>>>>>
>>> 07%E8%BB%9F%E9%AB%94%E9%96%8B%E7%99%BC%E8%99%95%2fBIOS%2f
>>> _Released_B
>>>>>
>>> IOS%2fUPN-ADLN01%2fUNASAM36.zip&parent=%2fpersonal%2fnas_aaeon_co
>>> m_t
>>>>>
>>> w%2fDocuments%2f007%E8%BB%9F%E9%AB%94%E9%96%8B%E7%99%BC%E8
>>> %99%95%2fB
>>>>>
>>> IOS%2f_Released_BIOS%2fUPN-ADLN01&ga=1&LOF=1&xsdata=MDV8MDJ8Q
>>> mlsbHlD
>>>>>
>>> aG91QGFhZW9uLmNvbS50d3w5MDU1ZThjNmE5NjQ0YjA1ZWQxYjA4ZGVmZTgz
>>> YjJiZHw1
>>>>>
>>> NmEyZDRiZTlmZTM0MzBlYjUzOTdlMTNhNDc0NDg1N3wwfDB8NjM5MjI4MDM
>>> 4OTk2Njk3
>>>>>
>>> MjY5fFVua25vd258VFdGcGJHWnNiM2Q4ZXlKRmJYQjBlVTFoY0draU9uUnlkV1Vz
>>> SWxZ
>>>>>
>>> aU9pSXdMakF1TURBd01DSXNJbEFpT2lKWGFXNHpNaUlzSWtGT0lqb2lUV0ZwYk
>>> NJc0ls
>>>>>
>>> ZFVJam95ZlE9PXwwfHx8&sdata=UldHMlhFNWxXM3htaDFCMGdKV3pZTTZ1Mz
>>> ZOMFBzW
>>>>> GdSNmthM2RsNnFzST0%3d
>>>>
>>>> Hmm... I can't login there with my @intel.com account. I suppose that
>>>> share is only for your company. Maybe MS Teams will work better?
>>>
>>> Or just sent an archive privately to my @intel.com address?
>>>
>> Sorry about that! I’ve updated the download link and fixed the permissions. Could you please give it another try? Thanks!
>> https://aaeon365-my.sharepoint.com/:u:/g/personal/billychou_aaeon_com_tw/IQAdsTdWUQhvQpAoS8lELTe8AZK70ORl6FB-Ndcf0lXUwus?e=ZV0MvS
> 
> Thank you!
> 
> Sorry for the delayed reply (for the record I have updated BIOS more than two
> weeks ago, but haven't had time actually perform any tests). Today I tried to
> use so called GPIO 11 and GPIO 12 (on 40-pin HAT connector) as input for the
> event generation. It works nicely. Also I have briefly looked at the 'pins' file
> for the pins 205 and 208 (Is that correct mapping? I took it from the _CRS of
> the respective Device object in DSDT), and also checked the whole list at a glance.
> All seems much better now — no [ACPI], no [LOCKED *] flags were set, which is the
> goal. TL;DR: I can confirm it works for me! Would this be an official one or should
> I wait for the official release and re-test?
> 
I have a Up Squared Pro 7000, so I'm also interested by this fix. Please
let me know once the official release is available.

Best Regards,
Thomas

RE: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?

[BillyChou 周博倫]

> -----Original Message-----
> From: Thomas Richard <thomas.richard@bootlin.com>
> Sent: Monday, September 14, 2026 4:01 PM
> To: Andy Shevchenko <andriy.shevchenko@intel.com>; BillyChou 周博倫
> <BillyChou@aaeon.com.tw>
> Cc: GaryWang <is0124@gmail.com>; JunYingLai 賴俊穎
> <JunYingLai@aaeon.com.tw>; linux-gpio@vger.kernel.org; JasonHuang 黃仁
> 杰 <JasonHuang@aaeon.com.tw>
> Subject: Re: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?
> 
> 這是外部郵件：在打開連結和附件之前，請確保電子郵件是安全的。 This
> is an external email: please make sure the email is secure before opening links
> and attachments.
> 
> On 9/11/26 8:18 PM, Andy Shevchenko wrote:
> > On Thu, Aug 20, 2026 at 10:04:13AM +0000, BillyChou 周博倫 wrote:
> >>> On Thu, Aug 20, 2026 at 09:23:43AM +0300, Andy Shevchenko wrote:
> >>>> On Thu, Aug 20, 2026 at 05:19:06AM +0000, BillyChou 周博倫 wrote:
> >>>>>> On Mon, Aug 10, 2026 at 04:17:43AM +0000, BillyChou 周博倫
> wrote:
> >>>>>>> Dear Andy,
> >>>>>>>
> >>>>>>> Thank you for your feedback, and we sincerely apologize for the
> delay.
> >>>>>>>
> >>>>>>> We are currently updating the BIOS to configure the HAT
> >>>>>>> connector pins to GPIO/GPO mode, which will ensure interrupt
> >>>>>>> support
> >>> on the OS side.
> >>>>>>> We will update the BIOS as soon as possible and share it with
> >>>>>>> you for
> >>> testing.
> >>>>>>>
> >>>>>>> Thanks again for your patience and support.
> >>>>>>
> >>>>>> Thanks for the good news, I'm looking forward to test it!
> >>>>>>
> >>>>> The updated BIOS for the UPN-ADLN01 project with the HAT connector
> >>>>> pin
> >>> configurations is ready. Kindly download it here for testing:
> >>>>>
> https://aaeon365-my.sharepoint.com/personal/nas_aaeon_com_tw/_layo
> >>>>>
> ut?xsdata=MDV8MDJ8QmlsbHlDaG91QGFhZW9uLmNvbS50d3xhNDMyNDVkN
> 2M2ZDU0
> >>>>>
> Y2U1YmYwZjA4ZGYxMjM2NjIyYnw1NmEyZDRiZTlmZTM0MzBlYjUzOTdlMTNhN
> Dc0ND
> >>>>>
> g1N3wwfDB8NjM5MjQ5Njk2OTY3MDU1NTg4fFVua25vd258VFdGcGJHWnNiM
> 2Q4ZXlK
> >>>>>
> RmJYQjBlVTFoY0draU9uUnlkV1VzSWxZaU9pSXdMakF1TURBd01DSXNJbEFpT2l
> KWG
> >>>>>
> FXNHpNaUlzSWtGT0lqb2lUV0ZwYkNJc0lsZFVJam95ZlE9PXwwfHx8&sdata=ekZz
> a
> >>>>> kl6S3lpdER5Q0hIRHV6TEFZNmhseXU0c09hUUNHczM1b1pESkFxTT0%3d
> >>>>>
> >>>
> s/15/onedrive.aspx?id=%2fpersonal%2fnas_aaeon_com_tw%2fDocuments%2f
> 0
> >>>>>
> >>>
> 07%E8%BB%9F%E9%AB%94%E9%96%8B%E7%99%BC%E8%99%95%2fBIOS%2f
> >>> _Released_B
> >>>>>
> >>>
> IOS%2fUPN-ADLN01%2fUNASAM36.zip&parent=%2fpersonal%2fnas_aaeon_co
> >>> m_t
> >>>>>
> >>>
> w%2fDocuments%2f007%E8%BB%9F%E9%AB%94%E9%96%8B%E7%99%BC%E
> 8
> >>> %99%95%2fB
> >>>>>
> >>>
> IOS%2f_Released_BIOS%2fUPN-ADLN01&ga=1&LOF=1&xsdata=MDV8MDJ8Q
> >>> mlsbHlD
> >>>>>
> >>>
> aG91QGFhZW9uLmNvbS50d3w5MDU1ZThjNmE5NjQ0YjA1ZWQxYjA4ZGVmZTg
> z
> >>> YjJiZHw1
> >>>>>
> >>>
> NmEyZDRiZTlmZTM0MzBlYjUzOTdlMTNhNDc0NDg1N3wwfDB8NjM5MjI4MDM
> >>> 4OTk2Njk3
> >>>>>
> >>>
> MjY5fFVua25vd258VFdGcGJHWnNiM2Q4ZXlKRmJYQjBlVTFoY0draU9uUnlkV1
> Vz
> >>> SWxZ
> >>>>>
> >>>
> aU9pSXdMakF1TURBd01DSXNJbEFpT2lKWGFXNHpNaUlzSWtGT0lqb2lUV0ZwY
> k
> >>> NJc0ls
> >>>>>
> >>>
> ZFVJam95ZlE9PXwwfHx8&sdata=UldHMlhFNWxXM3htaDFCMGdKV3pZTTZ1Mz
> >>> ZOMFBzW
> >>>>> GdSNmthM2RsNnFzST0%3d
> >>>>
> >>>> Hmm... I can't login there with my @intel.com account. I suppose
> >>>> that share is only for your company. Maybe MS Teams will work better?
> >>>
> >>> Or just sent an archive privately to my @intel.com address?
> >>>
> >> Sorry about that! I’ve updated the download link and fixed the
> permissions. Could you please give it another try? Thanks!
> >> https://aaeon365-my.sharepoint.com/:u:/g/personal/billychou_aaeon_com
> >>
> _tw/IQAdsTdWUQhvQpAoS8lELTe8AZK70ORl6FB-Ndcf0lXUwus?e=ZV0MvS&xs
> data=M
> >>
> DV8MDJ8QmlsbHlDaG91QGFhZW9uLmNvbS50d3xhNDMyNDVkN2M2ZDU0Y2
> U1YmYwZjA4ZG
> >>
> YxMjM2NjIyYnw1NmEyZDRiZTlmZTM0MzBlYjUzOTdlMTNhNDc0NDg1N3wwfD
> B8NjM5MjQ
> >>
> 5Njk2OTY3MDcyMjg1fFVua25vd258VFdGcGJHWnNiM2Q4ZXlKRmJYQjBlVTFoY
> 0draU9u
> >>
> UnlkV1VzSWxZaU9pSXdMakF1TURBd01DSXNJbEFpT2lKWGFXNHpNaUlzSWtGT
> 0lqb2lUV
> >>
> 0ZwYkNJc0lsZFVJam95ZlE9PXwwfHx8&sdata=Sk5oRTUrNEIyakpLbjZwTE1lbEdr
> bWp
> >> wRXRXbGlqbTE4ejdQdExOakFNQT0%3d
> >
> > Thank you!
> >
> > Sorry for the delayed reply (for the record I have updated BIOS more
> > than two weeks ago, but haven't had time actually perform any tests).
> > Today I tried to use so called GPIO 11 and GPIO 12 (on 40-pin HAT
> > connector) as input for the event generation. It works nicely. Also I
> > have briefly looked at the 'pins' file for the pins 205 and 208 (Is
> > that correct mapping? I took it from the _CRS of the respective Device object
> in DSDT), and also checked the whole list at a glance.
> > All seems much better now — no [ACPI], no [LOCKED *] flags were set,
> > which is the goal. TL;DR: I can confirm it works for me! Would this be
> > an official one or should I wait for the official release and re-test?
> >
> I have a Up Squared Pro 7000, so I'm also interested by this fix. Please let me
> know once the official release is available.
> 
> Best Regards,
> Thomas
Hi Andy, Thomas,
Andy,
Thanks for the update and for re-testing.
The BIOS you tested is a pre-release/engineering version. 
We will provide the official BIOS release as soon as possible.
Thomas,
Thanks for your interest. The same BIOS fix will also be applied to the UP Squared Pro 7000.
We will provide the official BIOS release as soon as possible.
Thanks again for the testing and confirmation.