I am using an AAEON UP4000 board with the default AMI UEFI BIOS.

Currently I configured both passwords:

    Supervisor / Administrator password

    User password

The problem is that when the system boots it asks for the User password before booting the OS.

What I would like instead is this behavior:

          The system should boot automatically without asking for a password

          The password should be required only when entering the BIOS setup

Basically I want the BIOS to behave like this:

           OS boot → no password

           Enter BIOS setup → password required

I tried setting only the Supervisor password, but then the normal user can still modify many BIOS settings.

So my questions are:

Is there a BIOS setting like "Password Check = Setup" or "Security Option = Setup" on the UP4000?

          Is there any hidden BIOS menu where this option exists?

Is there a way to limit the capabilities of the User account in BIOS without requiring a password at boot?

Any advice from people using the UP4000 or AMI BIOS on embedded boards would be very helpful.

Thank you!

is there a way to push an UEFI bios update from linux (i.e. ubuntu 22.04 LTS) instead of EFI shell?

We tested the BIOS update process with the EFI Shell and an startup.nsh to automatically update the bios from an USB stick. This requires physical access and manual inputs to the board.

We do not have physical access to the boards and can not plug in an USB memory stick and go through the bios boot selection menu at the customers place and need to update the bios on those systems.

Thanks in advance,
Farril

I'm trying to figure out how to enable control of the additional LEDs next to the ethernet port on the UP4000.

I'm trying to not install any specific UP board kernel to make this happen - as these will likely be deployed and required to be supported by us for 5-8 years - likely beyond the timeframe of supported software released by UP....

Is there a way to enable certain GPIOs directly to allow this to work?

I notice at the moment, I can see:

# ls -l /sys/class/leds
total 0
lrwxrwxrwx 1 root root 0 May  8 06:20 enp2s0-0::lan -> ../../devices/pci0000:00/0000:00:13.1/0000:02:00.0/net/enp2s0/enp2s0-0::lan
lrwxrwxrwx 1 root root 0 May  8 06:20 enp2s0-1::lan -> ../../devices/pci0000:00/0000:00:13.1/0000:02:00.0/net/enp2s0/enp2s0-1::lan
lrwxrwxrwx 1 root root 0 May  8 06:20 enp2s0-2::lan -> ../../devices/pci0000:00/0000:00:13.1/0000:02:00.0/net/enp2s0/enp2s0-2::lan

... and it does look like at least some of the GPIO control is available with the stock Ubuntu 24.04 kernel:

# ls -l /sys/class/gpio/
total 0
--w------- 1 root root 4096 May  9 06:21 export
lrwxrwxrwx 1 root root    0 May  8 06:20 gpiochip512 -> ../../devices/platform/INT3452:00/gpio/gpiochip512
lrwxrwxrwx 1 root root    0 May  8 06:20 gpiochip590 -> ../../devices/platform/INT3452:01/gpio/gpiochip590
lrwxrwxrwx 1 root root    0 May  8 06:20 gpiochip667 -> ../../devices/platform/INT3452:02/gpio/gpiochip667
lrwxrwxrwx 1 root root    0 May  8 06:20 gpiochip714 -> ../../devices/platform/INT3452:03/gpio/gpiochip714
--w------- 1 root root 4096 May  9 06:21 unexport

Right now, I'm only looking to get basic ON / OFF support working - but it would likely be good to register them as normal LEDs to allow some of the effects to work...

# ls -l /dev/mmc*
brw-rw---- 1 root disk 179,  0 May  8 06:20 /dev/mmcblk2
brw-rw---- 1 root disk 179,  8 May  8 06:20 /dev/mmcblk2boot0
brw-rw---- 1 root disk 179, 16 May  8 06:20 /dev/mmcblk2boot1
brw-rw---- 1 root disk 179,  1 May  8 06:20 /dev/mmcblk2p1
brw-rw---- 1 root disk 179,  2 May  8 06:20 /dev/mmcblk2p2
brw-rw---- 1 root disk 179,  3 May  8 06:20 /dev/mmcblk2p3
crw------- 1 root root 241,  0 May  8 06:20 /dev/mmcblk2rpmb

If I hard power off the device, then power it up again, the storage will be back to mmcblk0. After a reboot, this will then become mmcblk1 and another reboot to mmcblk2 etc.

Is this a BIOS issue?

From dmidecode:

BIOS Information
        Vendor: American Megatrends Inc.
        Version: UPAPBM12
        Release Date: 12/21/2022

No answer from the UP Shop, does anyone know is there some default password and what that might be?

I was trying to set a gpio pin to output high through c++ code using the mraa library. and I had so much trouble finding the right pin number to use to set the good pin.
the pin number has 2 gpio number asssociated.

in my BIOS, the pin is GPIO15 (pin 37) and setting it to output high really worked. but with the mraa library I had to do

mraa::Gpio gpio_1(26, true, true);
gpio_1.dir(mraa::DIR_OUT);
gpio_1.write(1);

for make it working.

maybe the third argument to gpio at true makes the numbering different, but puting false did that no pins where accepted so I had no choice.

In the document of my up4000:

the pin is numbered like in the BIOS, while the wiki schema:

uses the gpio26 number instead, the only constant being the pin number 37.

so I want to set the GPIO19 (pin 16) in my BIOS to output because my SPI_CLK isn't working if I don't do that. will this work if I use mraa with gpio23 instead because the wiki says so.

why is this so confusing. This other wiki page: https://github.com/up-board/up-community/wiki/Pinout even has different numbering