Skip to contentSkip to conversation

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

DISCUSSION Andy Shevchenko 4 participants 12 messages Jul 9 – Sep 22 1 message not in the archive GPIO

lore
Share & tools
lore
#0 lore raw

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?

Signature · 2 lines
With Best Regards,
Andy Shevchenko
#1 lore raw

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.

Quoted 24 lines · 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

#2 lore raw
Quoted 1 line · GaryWang

Add AAEON software JunYing.

Thanks, waiting for the response!

Quoted 3 lines

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.)

Quoted 18 lines
Quoted 16 lines · Andy Shevchenko

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?

Signature · 2 lines
With Best Regards,
Andy Shevchenko

A message that is not in the archive (sent off-list or not yet received): TY1PPFA4928F5D95D0BFF5F087E44F8B166F0C02@TY1PPFA4928F5D9.apcprd02.prod.outlook.com

#4 lore raw

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 賴俊穎 <[email protected]>
Sent: Thursday, July 23, 2026 2:48 PM
To: BillyChou 周博倫 <[email protected]>
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 <[email protected]>
Sent: Friday, July 10, 2026 5:11 PM
To: GaryWang <[email protected]>
Cc: JunYingLai 賴俊穎 <[email protected]>; Thomas Richard <[email protected]>; [email protected]; JasonHuang 黃仁杰 <[email protected]>
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.

Quoted 1 line · GaryWang

Add AAEON software JunYing.

Thanks, waiting for the response!

Quoted 3 lines

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.)

Quoted 12 lines
Quoted 10 lines · Andy Shevchenko

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?

Quoted 6 lines
Quoted 6 lines

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

#5 lore raw
Quoted 9 lines · 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.

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

Quoted 70 lines

-----Original Message-----
From: JunYingLai 賴俊穎 <[email protected]>
Sent: Thursday, July 23, 2026 2:48 PM
To: BillyChou 周博倫 <[email protected]>
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 <[email protected]>
Sent: Friday, July 10, 2026 5:11 PM
To: GaryWang <[email protected]>
Cc: JunYingLai 賴俊穎 <[email protected]>; Thomas Richard <[email protected]>; [email protected]; JasonHuang 黃仁杰 <[email protected]>
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.

Quoted 1 line · GaryWang

Add AAEON software JunYing.

Thanks, waiting for the response!

Quoted 3 lines

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.)

Quoted 18 lines
Quoted 16 lines · Andy Shevchenko

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?

Signature · 2 lines
With Best Regards,
Andy Shevchenko
#6 lore raw
Quoted 5 lines · BillyChou 周博倫
Quoted 4 lines

Dear Andy,

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

Quoted 8 lines
Quoted 5 lines

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

Quoted 82 lines
Quoted 31 lines

-----Original Message-----
From: JunYingLai 賴俊穎 <[email protected]>
Sent: Thursday, July 23, 2026 2:48 PM
To: BillyChou 周博倫 <[email protected]>
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 <[email protected]>
Sent: Friday, July 10, 2026 5:11 PM
To: GaryWang <[email protected]>
Cc: JunYingLai 賴俊穎 <[email protected]>; Thomas Richard <[email protected]>; [email protected]; JasonHuang 黃仁杰 <[email protected]>
Subject: Re: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?

Quoted 1 line

這是外部郵件:在打開連結和附件之前,請確保電子郵件是安全的。 This

is an external email: please make sure the email is secure before opening links and attachments.

Quoted 9 lines · GaryWang
Quoted 1 line

Add AAEON software JunYing.

Thanks, waiting for the response!

Quoted 3 lines

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.

Quoted 9 lines

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).

Quoted 12 lines

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.)

Quoted 7 lines
Quoted 5 lines · Andy Shevchenko

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.

Quoted 11 lines
Quoted 11 lines
Quoted 11 lines

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

#7 lore raw
Quoted 9 lines · BillyChou 周博倫
Quoted 9 lines · BillyChou 周博倫
Quoted 8 lines

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.

Quoted 6 lines
Quoted 4 lines
Quoted 1 line

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?

Quoted 77 lines
Quoted 77 lines
Quoted 31 lines

-----Original Message-----
From: JunYingLai 賴俊穎 <[email protected]>
Sent: Thursday, July 23, 2026 2:48 PM
To: BillyChou 周博倫 <[email protected]>
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 <[email protected]>
Sent: Friday, July 10, 2026 5:11 PM
To: GaryWang <[email protected]>
Cc: JunYingLai 賴俊穎 <[email protected]>; Thomas Richard <[email protected]>; [email protected]; JasonHuang 黃仁杰 <[email protected]>
Subject: Re: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?

Quoted 1 line

這是外部郵件:在打開連結和附件之前,請確保電子郵件是安全的。 This

is an external email: please make sure the email is secure before opening links and attachments.

Quoted 9 lines · GaryWang
Quoted 1 line

Add AAEON software JunYing.

Thanks, waiting for the response!

Quoted 3 lines

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.

Quoted 9 lines

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).

Quoted 12 lines

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.)

Quoted 7 lines
Quoted 5 lines · Andy Shevchenko

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.

Quoted 11 lines
Quoted 11 lines
Quoted 11 lines

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?

Signature · 2 lines
With Best Regards,
Andy Shevchenko
#8 lore raw
Quoted 12 lines · Andy Shevchenko
Quoted 11 lines · BillyChou 周博倫
Quoted 11 lines · BillyChou 周博倫
Quoted 9 lines

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.

Quoted 7 lines
Quoted 4 lines
Quoted 2 lines

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?

Quoted 83 lines
Quoted 77 lines
Quoted 77 lines
Quoted 31 lines

-----Original Message-----
From: JunYingLai 賴俊穎 <[email protected]>
Sent: Thursday, July 23, 2026 2:48 PM
To: BillyChou 周博倫 <[email protected]>
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 <[email protected]>
Sent: Friday, July 10, 2026 5:11 PM
To: GaryWang <[email protected]>
Cc: JunYingLai 賴俊穎 <[email protected]>; Thomas Richard <[email protected]>; [email protected]; JasonHuang 黃仁杰 <[email protected]>
Subject: Re: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?

Quoted 1 line

這是外部郵件:在打開連結和附件之前,請確保電子郵件是安全的。 This

is an external email: please make sure the email is secure before opening links and attachments.

Quoted 9 lines · GaryWang
Quoted 1 line

Add AAEON software JunYing.

Thanks, waiting for the response!

Quoted 3 lines

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.

Quoted 9 lines

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).

Quoted 12 lines

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.)

Quoted 7 lines
Quoted 5 lines · Andy Shevchenko

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.

Quoted 11 lines
Quoted 11 lines
Quoted 11 lines

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?

Signature · 2 lines
With Best Regards,
Andy Shevchenko
Signature · 2 lines
With Best Regards,
Andy Shevchenko
#9 lore raw
Quoted 47 lines · Andy Shevchenko
Quoted 8 lines · BillyChou 周博倫
Quoted 7 lines
Quoted 7 lines · BillyChou 周博倫
Quoted 6 lines

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.

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

We will update the BIOS as soon as possible and share it with you for

testing.

Quoted 6 lines
Quoted 6 lines
Quoted 5 lines
Quoted 2 lines

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:

Quoted 2 lines
Quoted 2 lines

https://aaeon365-my.sharepoint.com/personal/nas_aaeon_com_tw/_layout

s/15/onedrive.aspx?id=%2fpersonal%2fnas_aaeon_com_tw%2fDocuments%2f0

Quoted 1 line
Quoted 1 line

07%E8%BB%9F%E9%AB%94%E9%96%8B%E7%99%BC%E8%99%95%2fBIOS%2f _Released_B

Quoted 1 line
Quoted 1 line

IOS%2fUPN-ADLN01%2fUNASAM36.zip&parent=%2fpersonal%2fnas_aaeon_co m_t

Quoted 1 line
Quoted 1 line

w%2fDocuments%2f007%E8%BB%9F%E9%AB%94%E9%96%8B%E7%99%BC%E8 %99%95%2fB

Quoted 1 line
Quoted 1 line

IOS%2f_Released_BIOS%2fUPN-ADLN01&ga=1&LOF=1&xsdata=MDV8MDJ8Q mlsbHlD

Quoted 1 line
Quoted 1 line

aG91QGFhZW9uLmNvbS50d3w5MDU1ZThjNmE5NjQ0YjA1ZWQxYjA4ZGVmZTgz YjJiZHw1

Quoted 1 line
Quoted 1 line

NmEyZDRiZTlmZTM0MzBlYjUzOTdlMTNhNDc0NDg1N3wwfDB8NjM5MjI4MDM 4OTk2Njk3

Quoted 1 line
Quoted 1 line

MjY5fFVua25vd258VFdGcGJHWnNiM2Q4ZXlKRmJYQjBlVTFoY0draU9uUnlkV1Vz SWxZ

Quoted 1 line
Quoted 1 line

aU9pSXdMakF1TURBd01DSXNJbEFpT2lKWGFXNHpNaUlzSWtGT0lqb2lUV0ZwYk NJc0ls

Quoted 1 line
Quoted 1 line
Quoted 9 lines

ZFVJam95ZlE9PXwwfHx8&sdata=UldHMlhFNWxXM3htaDFCMGdKV3pZTTZ1Mz ZOMFBzW

Quoted 4 lines
Quoted 1 line

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

Quoted 95 lines
Quoted 21 lines
Quoted 21 lines
Quoted 21 lines
Quoted 21 lines

-----Original Message-----
From: JunYingLai 賴俊穎 <[email protected]>
Sent: Thursday, July 23, 2026 2:48 PM
To: BillyChou 周博倫 <[email protected]>
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

Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

-----Original Message-----
From: Andy Shevchenko <[email protected]>
Sent: Friday, July 10, 2026 5:11 PM
To: GaryWang <[email protected]>
Cc: JunYingLai 賴俊穎 <[email protected]>; Thomas Richard <[email protected]>; [email protected];

JasonHuang

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

黃仁杰 <[email protected]>
Subject: Re: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?

這是外部郵件:在打開連結和附件之前,請確保電子郵件是安全的。

This

Quoted 1 line
Quoted 1 line
Quoted 1 line

is an external email: please make sure the email is secure before

opening links

Quoted 10 lines
Quoted 10 lines
Quoted 10 lines

and attachments.

Quoted 9 lines · GaryWang
Quoted 1 line

Add AAEON software JunYing.

Thanks, waiting for the response!

Quoted 3 lines

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

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

usage.

Quoted 3 lines

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

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

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

Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines

"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.)

Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 5 lines · Andy Shevchenko

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

Quoted 11 lines
Quoted 11 lines
Quoted 11 lines

instance.

Quoted 10 lines
Quoted 10 lines
Quoted 10 lines

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

Quoted 7 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

does these UP boards nowadays?

--
With Best Regards,
Andy Shevchenko

--
With Best Regards,
Andy Shevchenko

#10 lore raw
Quoted 51 lines · BillyChou 周博倫
Quoted 51 lines · Andy Shevchenko
Quoted 8 lines · BillyChou 周博倫
Quoted 7 lines
Quoted 7 lines · BillyChou 周博倫
Quoted 6 lines

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.

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

We will update the BIOS as soon as possible and share it with you for

testing.

Quoted 6 lines
Quoted 6 lines
Quoted 5 lines
Quoted 2 lines

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:

Quoted 2 lines
Quoted 2 lines

https://aaeon365-my.sharepoint.com/personal/nas_aaeon_com_tw/_layout

s/15/onedrive.aspx?id=%2fpersonal%2fnas_aaeon_com_tw%2fDocuments%2f0

Quoted 1 line
Quoted 1 line

07%E8%BB%9F%E9%AB%94%E9%96%8B%E7%99%BC%E8%99%95%2fBIOS%2f _Released_B

Quoted 1 line
Quoted 1 line

IOS%2fUPN-ADLN01%2fUNASAM36.zip&parent=%2fpersonal%2fnas_aaeon_co m_t

Quoted 1 line
Quoted 1 line

w%2fDocuments%2f007%E8%BB%9F%E9%AB%94%E9%96%8B%E7%99%BC%E8 %99%95%2fB

Quoted 1 line
Quoted 1 line

IOS%2f_Released_BIOS%2fUPN-ADLN01&ga=1&LOF=1&xsdata=MDV8MDJ8Q mlsbHlD

Quoted 1 line
Quoted 1 line

aG91QGFhZW9uLmNvbS50d3w5MDU1ZThjNmE5NjQ0YjA1ZWQxYjA4ZGVmZTgz YjJiZHw1

Quoted 1 line
Quoted 1 line

NmEyZDRiZTlmZTM0MzBlYjUzOTdlMTNhNDc0NDg1N3wwfDB8NjM5MjI4MDM 4OTk2Njk3

Quoted 1 line
Quoted 1 line

MjY5fFVua25vd258VFdGcGJHWnNiM2Q4ZXlKRmJYQjBlVTFoY0draU9uUnlkV1Vz SWxZ

Quoted 1 line
Quoted 1 line

aU9pSXdMakF1TURBd01DSXNJbEFpT2lKWGFXNHpNaUlzSWtGT0lqb2lUV0ZwYk NJc0ls

Quoted 1 line
Quoted 1 line

ZFVJam95ZlE9PXwwfHx8&sdata=UldHMlhFNWxXM3htaDFCMGdKV3pZTTZ1Mz ZOMFBzW

Quoted 2 lines
Quoted 1 line

GdSNmthM2RsNnFzST0%3d

Quoted 7 lines
Quoted 5 lines
Quoted 2 lines

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?

Quoted 84 lines
Quoted 84 lines
Quoted 21 lines
Quoted 21 lines
Quoted 21 lines
Quoted 21 lines

-----Original Message-----
From: JunYingLai 賴俊穎 <[email protected]>
Sent: Thursday, July 23, 2026 2:48 PM
To: BillyChou 周博倫 <[email protected]>
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

Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

-----Original Message-----
From: Andy Shevchenko <[email protected]>
Sent: Friday, July 10, 2026 5:11 PM
To: GaryWang <[email protected]>
Cc: JunYingLai 賴俊穎 <[email protected]>; Thomas Richard <[email protected]>; [email protected];

JasonHuang

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

黃仁杰 <[email protected]>
Subject: Re: Up Squared Pro 7000 (UPN-ADLN01) broken BIOS?

這是外部郵件:在打開連結和附件之前,請確保電子郵件是安全的。

This

Quoted 1 line
Quoted 1 line
Quoted 1 line

is an external email: please make sure the email is secure before

opening links

Quoted 10 lines
Quoted 10 lines
Quoted 10 lines

and attachments.

Quoted 9 lines · GaryWang
Quoted 1 line

Add AAEON software JunYing.

Thanks, waiting for the response!

Quoted 3 lines

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

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

usage.

Quoted 3 lines

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

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

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

Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines

"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.)

Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 5 lines · Andy Shevchenko

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

Quoted 11 lines
Quoted 11 lines
Quoted 11 lines

instance.

Quoted 10 lines
Quoted 10 lines
Quoted 10 lines

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

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

does these UP boards nowadays?

Signature · 2 lines
With Best Regards,
Andy Shevchenko
#11 lore raw
Quoted 62 lines · Andy Shevchenko
Quoted 51 lines · BillyChou 周博倫
Quoted 51 lines · Andy Shevchenko
Quoted 8 lines · BillyChou 周博倫
Quoted 7 lines
Quoted 7 lines · BillyChou 周博倫
Quoted 6 lines

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.

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

We will update the BIOS as soon as possible and share it with you for

testing.

Quoted 6 lines
Quoted 6 lines
Quoted 5 lines
Quoted 2 lines

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:

Quoted 2 lines
Quoted 2 lines

https://aaeon365-my.sharepoint.com/personal/nas_aaeon_com_tw/_layout

s/15/onedrive.aspx?id=%2fpersonal%2fnas_aaeon_com_tw%2fDocuments%2f0

Quoted 1 line
Quoted 1 line

07%E8%BB%9F%E9%AB%94%E9%96%8B%E7%99%BC%E8%99%95%2fBIOS%2f _Released_B

Quoted 1 line
Quoted 1 line

IOS%2fUPN-ADLN01%2fUNASAM36.zip&parent=%2fpersonal%2fnas_aaeon_co m_t

Quoted 1 line
Quoted 1 line

w%2fDocuments%2f007%E8%BB%9F%E9%AB%94%E9%96%8B%E7%99%BC%E8 %99%95%2fB

Quoted 1 line
Quoted 1 line

IOS%2f_Released_BIOS%2fUPN-ADLN01&ga=1&LOF=1&xsdata=MDV8MDJ8Q mlsbHlD

Quoted 1 line
Quoted 1 line

aG91QGFhZW9uLmNvbS50d3w5MDU1ZThjNmE5NjQ0YjA1ZWQxYjA4ZGVmZTgz YjJiZHw1

Quoted 1 line
Quoted 1 line

NmEyZDRiZTlmZTM0MzBlYjUzOTdlMTNhNDc0NDg1N3wwfDB8NjM5MjI4MDM 4OTk2Njk3

Quoted 1 line
Quoted 1 line

MjY5fFVua25vd258VFdGcGJHWnNiM2Q4ZXlKRmJYQjBlVTFoY0draU9uUnlkV1Vz SWxZ

Quoted 1 line
Quoted 1 line

aU9pSXdMakF1TURBd01DSXNJbEFpT2lKWGFXNHpNaUlzSWtGT0lqb2lUV0ZwYk NJc0ls

Quoted 1 line
Quoted 1 line

ZFVJam95ZlE9PXwwfHx8&sdata=UldHMlhFNWxXM3htaDFCMGdKV3pZTTZ1Mz ZOMFBzW

Quoted 2 lines
Quoted 1 line

GdSNmthM2RsNnFzST0%3d

Quoted 7 lines
Quoted 5 lines
Quoted 2 lines

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!

Quoted 10 lines

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

#12 lore raw
Quoted 145 lines

-----Original Message-----
From: Thomas Richard <[email protected]>
Sent: Monday, September 14, 2026 4:01 PM
To: Andy Shevchenko <[email protected]>; BillyChou 周博倫 <[email protected]>
Cc: GaryWang <[email protected]>; JunYingLai 賴俊穎 <[email protected]>; [email protected]; JasonHuang 黃仁 杰 <[email protected]>
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.

Quoted 4 lines · Andy Shevchenko
Quoted 3 lines · BillyChou 周博倫
Quoted 3 lines · Andy Shevchenko
Quoted 2 lines · BillyChou 周博倫
Quoted 1 line
Quoted 1 line

On Mon, Aug 10, 2026 at 04:17:43AM +0000, BillyChou 周博倫

Quoted 3 lines · wrote:
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

Dear Andy,

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

delay.

Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

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.

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

We will update the BIOS as soon as possible and share it with you for

testing.

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 6 lines
Quoted 6 lines
Quoted 4 lines
Quoted 1 line

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:

Quoted 1 line
Quoted 1 line

https://aaeon365-my.sharepoint.com/personal/nas_aaeon_com_tw/_layo

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

ut?xsdata=MDV8MDJ8QmlsbHlDaG91QGFhZW9uLmNvbS50d3xhNDMyNDVkN 2M2ZDU0

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

Y2U1YmYwZjA4ZGYxMjM2NjIyYnw1NmEyZDRiZTlmZTM0MzBlYjUzOTdlMTNhN Dc0ND

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

g1N3wwfDB8NjM5MjQ5Njk2OTY3MDU1NTg4fFVua25vd258VFdGcGJHWnNiM 2Q4ZXlK

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

RmJYQjBlVTFoY0draU9uUnlkV1VzSWxZaU9pSXdMakF1TURBd01DSXNJbEFpT2l KWG

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

FXNHpNaUlzSWtGT0lqb2lUV0ZwYkNJc0lsZFVJam95ZlE9PXwwfHx8&sdata=ekZz a

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 2 lines
Quoted 2 lines

kl6S3lpdER5Q0hIRHV6TEFZNmhseXU0c09hUUNHczM1b1pESkFxTT0%3d

s/15/onedrive.aspx?id=%2fpersonal%2fnas_aaeon_com_tw%2fDocuments%2f 0

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 1 line
Quoted 1 line

07%E8%BB%9F%E9%AB%94%E9%96%8B%E7%99%BC%E8%99%95%2fBIOS%2f

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

_Released_B

Quoted 1 line
Quoted 1 line

IOS%2fUPN-ADLN01%2fUNASAM36.zip&parent=%2fpersonal%2fnas_aaeon_co

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

m_t

Quoted 1 line
Quoted 1 line

w%2fDocuments%2f007%E8%BB%9F%E9%AB%94%E9%96%8B%E7%99%BC%E 8

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

%99%95%2fB

Quoted 1 line
Quoted 1 line

IOS%2f_Released_BIOS%2fUPN-ADLN01&ga=1&LOF=1&xsdata=MDV8MDJ8Q

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

mlsbHlD

Quoted 1 line
Quoted 1 line

aG91QGFhZW9uLmNvbS50d3w5MDU1ZThjNmE5NjQ0YjA1ZWQxYjA4ZGVmZTg z

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

YjJiZHw1

Quoted 1 line
Quoted 1 line

NmEyZDRiZTlmZTM0MzBlYjUzOTdlMTNhNDc0NDg1N3wwfDB8NjM5MjI4MDM

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

4OTk2Njk3

Quoted 1 line
Quoted 1 line

MjY5fFVua25vd258VFdGcGJHWnNiM2Q4ZXlKRmJYQjBlVTFoY0draU9uUnlkV1 Vz

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

SWxZ

Quoted 1 line
Quoted 1 line

aU9pSXdMakF1TURBd01DSXNJbEFpT2lKWGFXNHpNaUlzSWtGT0lqb2lUV0ZwY k

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

NJc0ls

Quoted 1 line
Quoted 1 line

ZFVJam95ZlE9PXwwfHx8&sdata=UldHMlhFNWxXM3htaDFCMGdKV3pZTTZ1Mz

Quoted 9 lines
Quoted 9 lines
Quoted 8 lines

ZOMFBzW

Quoted 4 lines
Quoted 1 line

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!

Quoted 2 lines
Quoted 2 lines

https://aaeon365-my.sharepoint.com/:u:/g/personal/billychou_aaeon_com

_tw/IQAdsTdWUQhvQpAoS8lELTe8AZK70ORl6FB-Ndcf0lXUwus?e=ZV0MvS&xs data=M

Quoted 1 line
Quoted 1 line

DV8MDJ8QmlsbHlDaG91QGFhZW9uLmNvbS50d3xhNDMyNDVkN2M2ZDU0Y2 U1YmYwZjA4ZG

Quoted 1 line
Quoted 1 line

YxMjM2NjIyYnw1NmEyZDRiZTlmZTM0MzBlYjUzOTdlMTNhNDc0NDg1N3wwfD B8NjM5MjQ

Quoted 1 line
Quoted 1 line

5Njk2OTY3MDcyMjg1fFVua25vd258VFdGcGJHWnNiM2Q4ZXlKRmJYQjBlVTFoY 0draU9u

Quoted 1 line
Quoted 1 line

UnlkV1VzSWxZaU9pSXdMakF1TURBd01DSXNJbEFpT2lKWGFXNHpNaUlzSWtGT 0lqb2lUV

Quoted 1 line
Quoted 1 line

0ZwYkNJc0lsZFVJam95ZlE9PXwwfHx8&sdata=Sk5oRTUrNEIyakpLbjZwTE1lbEdr bWp

Quoted 10 lines
Quoted 1 line

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.

Quoted 4 lines

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?

Quoted 5 lines

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.