Topics

Problems with vuart on the UP2 board


Geoffroy Van Cutsem
 

Hi folks,

 

I have been setting up ACRN on my UP2 board, specifically:

- ACRN: HV version 0.7-unstable-2019-03-01 (from Clear Linux 28100)

- UP2 bios is the latest: https://downloads.up-community.org/download/up-squared-uefi-bios-v4-0/

- Using the UART from the  40-pin HAT connector (same as in https://projectacrn.github.io/latest/getting-started/up2.html)

 

*But* as soon as I use any of the following values for vuart, the system does not boot correctly (it goes past the bootloader but all I get is a black screen and the system eventually reboots):

- vuart=ttyS1@irq5 (that’s what is in the documentation)

- vuart=ttyS1@irq4 (I wanted to try because that’s what matches the output when running the SOS, see below)

You will find below the ‘dmesg’ and ‘lspci’ outputs in various configurations (that do boot).

 

I’m kind of confused as to what that vuart setting does and how one can know what to set it to. Can you help shed some light on this?

 

Thanks,

Geoffroy

 

== Service OS: no uart, no vuart setting ==

$ dmesg | grep -i uart

[    0.085940] ACPI: SPCR: console: uart,mmio,0x91526000,115200

[    1.363519] dw-apb-uart.8: ttyS1 at MMIO 0x91526000 (irq = 4, base_baud = 115200) is a 16550A

[    1.367025] dw-apb-uart.9: ttyS2 at MMIO 0x91524000 (irq = 5, base_baud = 115200) is a 16550A

 

$ lspci | grep -i uart

00:18.0 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #1 (rev 0b)

00:18.1 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #2 (rev 0b)

 

Note: no serial console connection to ACRN

 

== Service OS: no vuart setting, uart=bdf@0:18.1 ==

$ dmesg | grep -i uart

[ 0.084564] ACPI: SPCR: console: uart,mmio,0x91526000,115200

[ 1.361599] dw-apb-uart.8: ttyS1 at MMIO 0x91526000 (irq = 4, base_baud = 115200) is a 16550A

 

$ lspci | grep -i uart

00:18.0 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #1 (rev 0b)a

 

Note: serial console connection to ACRN working correctly

 

== Service OS: uart=bdf@0:18.1 vuart=ttyS0@irq4 ==

$ dmesg | grep -i uart

[    0.086506] ACPI: SPCR: console: uart,mmio,0x91526000,115200

[    1.365917] dw-apb-uart.8: ttyS1 at MMIO 0x91526000 (irq = 4, base_baud = 115200) is a 16550A

 

$ lspci | grep -i uart

00:18.0 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #1 (rev 0b)

 

Note: serial console connection to ACRN working correctly

 

== Native kernel (no ACRN) ==

$ dmesg | grep -i  uart

[    3.865831] dw-apb-uart.8: ttyS0 at MMIO 0x91526000 (irq = 4, base_baud = 115200) is a 16550A

[    3.877532] probe of dw-apb-uart.8 returned 1 after 13337 usecs

[    3.889789] dw-apb-uart.9: ttyS1 at MMIO 0x91524000 (irq = 5, base_baud = 115200) is a 16550A

[    3.889947] probe of dw-apb-uart.9 returned 1 after 506 usecs

 

$ lspci | grep -i uart

00:18.0 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #1 (rev 0b)

00:18.1 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #2 (rev 0b)

 

Technical Marketing Engineer Manager

Open-Source Technology Centre

Tel: +32 (0)3 450 0851

 

-----------------------------------------------

Intel Corporation NV/SA

Kings Square, Veldkant 31

2550 Kontich

RPM (Bruxelles) 0415.497.718.

Citibank, Brussels, account 570/1031255/09

 


Geoffroy Van Cutsem
 

Update since my initial mail. I have changed the SOS kernel command-line (in acrn.conf) to use ttyS1 (instead of ttyS0) and that allowed me to boot the system with uart=bdf@0:18.1 vuart=ttyS1@irq5.

 

But, that was when starting acrn.efi from the EFI shell (“acrn.efi uart=bdf@0:18.1 vuart=ttyS1@irq5”). If I create an entry using efibootmgr with the same settings [1], that does not boot correctly.

 

Could there be an issue in how these parameters are transferred when using efibootmgr?

 

[1] sudo efibootmgr –c –l “\EFI\acrn\acrn.efi” –d /dev/mmcblk0 –p 1 –L “ACRN” –u “uart=bdf@0:18.1 vuart=ttyS1@irq5”

 

Thanks,

Geoffroy

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Geoffroy Van Cutsem
Sent: Monday, March 4, 2019 3:51 PM
To: acrn-users@...
Subject: [acrn-users] Problems with vuart on the UP2 board

 

Hi folks,

 

I have been setting up ACRN on my UP2 board, specifically:

- ACRN: HV version 0.7-unstable-2019-03-01 (from Clear Linux 28100)

- UP2 bios is the latest: https://downloads.up-community.org/download/up-squared-uefi-bios-v4-0/

- Using the UART from the  40-pin HAT connector (same as in https://projectacrn.github.io/latest/getting-started/up2.html)

 

*But* as soon as I use any of the following values for vuart, the system does not boot correctly (it goes past the bootloader but all I get is a black screen and the system eventually reboots):

- vuart=ttyS1@irq5 (that’s what is in the documentation)

- vuart=ttyS1@irq4 (I wanted to try because that’s what matches the output when running the SOS, see below)

You will find below the ‘dmesg’ and ‘lspci’ outputs in various configurations (that do boot).

 

I’m kind of confused as to what that vuart setting does and how one can know what to set it to. Can you help shed some light on this?

 

Thanks,

Geoffroy

 

== Service OS: no uart, no vuart setting ==

$ dmesg | grep -i uart

[    0.085940] ACPI: SPCR: console: uart,mmio,0x91526000,115200

[    1.363519] dw-apb-uart.8: ttyS1 at MMIO 0x91526000 (irq = 4, base_baud = 115200) is a 16550A

[    1.367025] dw-apb-uart.9: ttyS2 at MMIO 0x91524000 (irq = 5, base_baud = 115200) is a 16550A

 

$ lspci | grep -i uart

00:18.0 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #1 (rev 0b)

00:18.1 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #2 (rev 0b)

 

Note: no serial console connection to ACRN

 

== Service OS: no vuart setting, uart=bdf@0:18.1 ==

$ dmesg | grep -i uart

[ 0.084564] ACPI: SPCR: console: uart,mmio,0x91526000,115200

[ 1.361599] dw-apb-uart.8: ttyS1 at MMIO 0x91526000 (irq = 4, base_baud = 115200) is a 16550A

 

$ lspci | grep -i uart

00:18.0 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #1 (rev 0b)a

 

Note: serial console connection to ACRN working correctly

 

== Service OS: uart=bdf@0:18.1 vuart=ttyS0@irq4 ==

$ dmesg | grep -i uart

[    0.086506] ACPI: SPCR: console: uart,mmio,0x91526000,115200

[    1.365917] dw-apb-uart.8: ttyS1 at MMIO 0x91526000 (irq = 4, base_baud = 115200) is a 16550A

 

$ lspci | grep -i uart

00:18.0 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #1 (rev 0b)

 

Note: serial console connection to ACRN working correctly

 

== Native kernel (no ACRN) ==

$ dmesg | grep -i  uart

[    3.865831] dw-apb-uart.8: ttyS0 at MMIO 0x91526000 (irq = 4, base_baud = 115200) is a 16550A

[    3.877532] probe of dw-apb-uart.8 returned 1 after 13337 usecs

[    3.889789] dw-apb-uart.9: ttyS1 at MMIO 0x91524000 (irq = 5, base_baud = 115200) is a 16550A

[    3.889947] probe of dw-apb-uart.9 returned 1 after 506 usecs

 

$ lspci | grep -i uart

00:18.0 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #1 (rev 0b)

00:18.1 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #2 (rev 0b)

 

Technical Marketing Engineer Manager

Open-Source Technology Centre

Tel: +32 (0)3 450 0851

 

-----------------------------------------------

Intel Corporation NV/SA

Kings Square, Veldkant 31

2550 Kontich

RPM (Bruxelles) 0415.497.718.

Citibank, Brussels, account 570/1031255/09

 


Wang, Minxia
 

@Geoffroy,

We can boot the  system with uart=bdf@0:18.1 vuart=ttyS1@irq5” parameters using efibootmgr, and that serial console connection to ACRN working correctly.

Can you check your efiboot entry by “efibootmgr –v” to confirm if it has been added successfully? As we failed to add the entry by copying the line you attached below but succeed after typing directly. Your line below seems exist auto format dash or letter.

 

Best & Regards,

Wang Minxia(Vanda)

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Geoffroy Van Cutsem
Sent: Monday, March 4, 2019 11:44 PM
To: acrn-users@...
Subject: Re: [acrn-users] Problems with vuart on the UP2 board

 

Update since my initial mail. I have changed the SOS kernel command-line (in acrn.conf) to use ttyS1 (instead of ttyS0) and that allowed me to boot the system with uart=bdf@0:18.1 vuart=ttyS1@irq5.

 

But, that was when starting acrn.efi from the EFI shell (“acrn.efi uart=bdf@0:18.1 vuart=ttyS1@irq5”). If I create an entry using efibootmgr with the same settings [1], that does not boot correctly.

 

Could there be an issue in how these parameters are transferred when using efibootmgr?

 

[1] sudo efibootmgr –c –l “\EFI\acrn\acrn.efi” –d /dev/mmcblk0 –p 1 –L “ACRN” –u “uart=bdf@0:18.1 vuart=ttyS1@irq5

 

Thanks,

Geoffroy

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Geoffroy Van Cutsem
Sent: Monday, March 4, 2019 3:51 PM
To: acrn-users@...
Subject: [acrn-users] Problems with vuart on the UP2 board

 

Hi folks,

 

I have been setting up ACRN on my UP2 board, specifically:

- ACRN: HV version 0.7-unstable-2019-03-01 (from Clear Linux 28100)

- UP2 bios is the latest: https://downloads.up-community.org/download/up-squared-uefi-bios-v4-0/

- Using the UART from the  40-pin HAT connector (same as in https://projectacrn.github.io/latest/getting-started/up2.html)

 

*But* as soon as I use any of the following values for vuart, the system does not boot correctly (it goes past the bootloader but all I get is a black screen and the system eventually reboots):

- vuart=ttyS1@irq5 (that’s what is in the documentation)

- vuart=ttyS1@irq4 (I wanted to try because that’s what matches the output when running the SOS, see below)

You will find below the ‘dmesg’ and ‘lspci’ outputs in various configurations (that do boot).

 

I’m kind of confused as to what that vuart setting does and how one can know what to set it to. Can you help shed some light on this?

 

Thanks,

Geoffroy

 

== Service OS: no uart, no vuart setting ==

$ dmesg | grep -i uart

[    0.085940] ACPI: SPCR: console: uart,mmio,0x91526000,115200

[    1.363519] dw-apb-uart.8: ttyS1 at MMIO 0x91526000 (irq = 4, base_baud = 115200) is a 16550A

[    1.367025] dw-apb-uart.9: ttyS2 at MMIO 0x91524000 (irq = 5, base_baud = 115200) is a 16550A

 

$ lspci | grep -i uart

00:18.0 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #1 (rev 0b)

00:18.1 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #2 (rev 0b)

 

Note: no serial console connection to ACRN

 

== Service OS: no vuart setting, uart=bdf@0:18.1 ==

$ dmesg | grep -i uart

[ 0.084564] ACPI: SPCR: console: uart,mmio,0x91526000,115200

[ 1.361599] dw-apb-uart.8: ttyS1 at MMIO 0x91526000 (irq = 4, base_baud = 115200) is a 16550A

 

$ lspci | grep -i uart

00:18.0 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #1 (rev 0b)a

 

Note: serial console connection to ACRN working correctly

 

== Service OS: uart=bdf@0:18.1 vuart=ttyS0@irq4 ==

$ dmesg | grep -i uart

[    0.086506] ACPI: SPCR: console: uart,mmio,0x91526000,115200

[    1.365917] dw-apb-uart.8: ttyS1 at MMIO 0x91526000 (irq = 4, base_baud = 115200) is a 16550A

 

$ lspci | grep -i uart

00:18.0 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #1 (rev 0b)

 

Note: serial console connection to ACRN working correctly

 

== Native kernel (no ACRN) ==

$ dmesg | grep -i  uart

[    3.865831] dw-apb-uart.8: ttyS0 at MMIO 0x91526000 (irq = 4, base_baud = 115200) is a 16550A

[    3.877532] probe of dw-apb-uart.8 returned 1 after 13337 usecs

[    3.889789] dw-apb-uart.9: ttyS1 at MMIO 0x91524000 (irq = 5, base_baud = 115200) is a 16550A

[    3.889947] probe of dw-apb-uart.9 returned 1 after 506 usecs

 

$ lspci | grep -i uart

00:18.0 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #1 (rev 0b)

00:18.1 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #2 (rev 0b)

 

Technical Marketing Engineer Manager

Open-Source Technology Centre

Tel: +32 (0)3 450 0851

 

-----------------------------------------------

Intel Corporation NV/SA

Kings Square, Veldkant 31

2550 Kontich

RPM (Bruxelles) 0415.497.718.

Citibank, Brussels, account 570/1031255/09

 


Geoffroy Van Cutsem
 

Hi Vanda,

 

Thanks for your confirmation! I think Outlook has been messing with that line below, it’s not something I had copy-pasted from my dev machine but something I typed directly in the email body.

 

I cleaned up the list of entries this morning to give you a clean log… and now it works!! The only difference I can think of from what I did yesterday is to do a “poweroff” after creating the new entry as opposed of a “reboot”. I don’t know whether this could have made a difference. I cannot, of course, rule out that I had a typo in my entry yesterday although I feel this is a bit unlikely given how many times I tried it yesterday, one would think (hope!) that I would have had it right at least once!

 

Anyway, it’s all good now. I’ll make sure to capture more info if it happens again in the future.

 

Thanks!
Geoffroy

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Wang, Minxia
Sent: Tuesday, March 5, 2019 8:10 AM
To: acrn-users@...
Subject: Re: [acrn-users] Problems with vuart on the UP2 board

 

@Geoffroy,

We can boot the  system with uart=bdf@0:18.1 vuart=ttyS1@irq5” parameters using efibootmgr, and that serial console connection to ACRN working correctly.

Can you check your efiboot entry by “efibootmgr –v” to confirm if it has been added successfully? As we failed to add the entry by copying the line you attached below but succeed after typing directly. Your line below seems exist auto format dash or letter.

 

Best & Regards,

Wang Minxia(Vanda)

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Geoffroy Van Cutsem
Sent: Monday, March 4, 2019 11:44 PM
To: acrn-users@...
Subject: Re: [acrn-users] Problems with vuart on the UP2 board

 

Update since my initial mail. I have changed the SOS kernel command-line (in acrn.conf) to use ttyS1 (instead of ttyS0) and that allowed me to boot the system with uart=bdf@0:18.1 vuart=ttyS1@irq5.

 

But, that was when starting acrn.efi from the EFI shell (“acrn.efi uart=bdf@0:18.1 vuart=ttyS1@irq5”). If I create an entry using efibootmgr with the same settings [1], that does not boot correctly.

 

Could there be an issue in how these parameters are transferred when using efibootmgr?

 

[1] sudo efibootmgr –c –l “\EFI\acrn\acrn.efi” –d /dev/mmcblk0 –p 1 –L “ACRN” –u “uart=bdf@0:18.1 vuart=ttyS1@irq5

 

Thanks,

Geoffroy

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Geoffroy Van Cutsem
Sent: Monday, March 4, 2019 3:51 PM
To: acrn-users@...
Subject: [acrn-users] Problems with vuart on the UP2 board

 

Hi folks,

 

I have been setting up ACRN on my UP2 board, specifically:

- ACRN: HV version 0.7-unstable-2019-03-01 (from Clear Linux 28100)

- UP2 bios is the latest: https://downloads.up-community.org/download/up-squared-uefi-bios-v4-0/

- Using the UART from the  40-pin HAT connector (same as in https://projectacrn.github.io/latest/getting-started/up2.html)

 

*But* as soon as I use any of the following values for vuart, the system does not boot correctly (it goes past the bootloader but all I get is a black screen and the system eventually reboots):

- vuart=ttyS1@irq5 (that’s what is in the documentation)

- vuart=ttyS1@irq4 (I wanted to try because that’s what matches the output when running the SOS, see below)

You will find below the ‘dmesg’ and ‘lspci’ outputs in various configurations (that do boot).

 

I’m kind of confused as to what that vuart setting does and how one can know what to set it to. Can you help shed some light on this?

 

Thanks,

Geoffroy

 

== Service OS: no uart, no vuart setting ==

$ dmesg | grep -i uart

[    0.085940] ACPI: SPCR: console: uart,mmio,0x91526000,115200

[    1.363519] dw-apb-uart.8: ttyS1 at MMIO 0x91526000 (irq = 4, base_baud = 115200) is a 16550A

[    1.367025] dw-apb-uart.9: ttyS2 at MMIO 0x91524000 (irq = 5, base_baud = 115200) is a 16550A

 

$ lspci | grep -i uart

00:18.0 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #1 (rev 0b)

00:18.1 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #2 (rev 0b)

 

Note: no serial console connection to ACRN

 

== Service OS: no vuart setting, uart=bdf@0:18.1 ==

$ dmesg | grep -i uart

[ 0.084564] ACPI: SPCR: console: uart,mmio,0x91526000,115200

[ 1.361599] dw-apb-uart.8: ttyS1 at MMIO 0x91526000 (irq = 4, base_baud = 115200) is a 16550A

 

$ lspci | grep -i uart

00:18.0 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #1 (rev 0b)a

 

Note: serial console connection to ACRN working correctly

 

== Service OS: uart=bdf@0:18.1 vuart=ttyS0@irq4 ==

$ dmesg | grep -i uart

[    0.086506] ACPI: SPCR: console: uart,mmio,0x91526000,115200

[    1.365917] dw-apb-uart.8: ttyS1 at MMIO 0x91526000 (irq = 4, base_baud = 115200) is a 16550A

 

$ lspci | grep -i uart

00:18.0 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #1 (rev 0b)

 

Note: serial console connection to ACRN working correctly

 

== Native kernel (no ACRN) ==

$ dmesg | grep -i  uart

[    3.865831] dw-apb-uart.8: ttyS0 at MMIO 0x91526000 (irq = 4, base_baud = 115200) is a 16550A

[    3.877532] probe of dw-apb-uart.8 returned 1 after 13337 usecs

[    3.889789] dw-apb-uart.9: ttyS1 at MMIO 0x91524000 (irq = 5, base_baud = 115200) is a 16550A

[    3.889947] probe of dw-apb-uart.9 returned 1 after 506 usecs

 

$ lspci | grep -i uart

00:18.0 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #1 (rev 0b)

00:18.1 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #2 (rev 0b)

 

Technical Marketing Engineer Manager

Open-Source Technology Centre

Tel: +32 (0)3 450 0851

 

-----------------------------------------------

Intel Corporation NV/SA

Kings Square, Veldkant 31

2550 Kontich

RPM (Bruxelles) 0415.497.718.

Citibank, Brussels, account 570/1031255/09