Is there a BIOS for UP Xtreme i11 0001 with SOF key enabled?

nashif
nashif New Member Posts: 1

Revision 0000 bios version 1.4 introduced SOF key, does the 0001 version have a BIOS that has this key enabled as well?

From 1.4 release notes:

Add SOF key for cAvsImage0Manifest

Best Answer

Answers

  • fredoh
    fredoh New Member Posts: 13
    edited September 21

    Dear Aaron admin, I have both 0000 and 0001 and I'm actively working on SOF project also. I'm so happy with Up series. Unluckily TGL UP Xtreme i11 HW 0001 doesn't have SOF community key, I failed to boot SOF key signed firmwares. Can you double check this? This is critical to us to maximize test coverage of TGL platforms. I have two 0001 HW already and eventually we need to buy more.

    I'm running Linux/Ubuntu on it.

  • fredoh
    fredoh New Member Posts: 13
    edited September 21

    @nashif did you verify that SOF key is working with HW 0001? it didn't work for me. Tested on two 0001.

    @rogertsai(AAEON) If you want to test with my HW by release engineering BIOS, I'm happy to test/support that. I'm really eager to see 0001 HW is working with SOF project.

  • rogertsai(AAEON)
    rogertsai(AAEON) New Member Posts: 350 ✭✭✭

    @fredoh
    Have you tried clearing the CMOS data? if not, you can clear the CMOS values by removing the battery, this action will clear the board BIOS data and it will be restored to default settings.
    or try to update your BIOS to R1.1 on 0001 board
    0001 bios version 1.1

  • fredoh
    fredoh New Member Posts: 13

    Thanks. I will try your suggestion and new BIOS shortly. Will update here by today

  • fredoh
    fredoh New Member Posts: 13

    I upgraded to R1.1 BIOS. I need to use HD-Audio mode, so no need to change any BIOS setting. I don't have any luck. Still intel signed FW works.
    I tired to remove the coin battery for +10 seconds and reconnected and try again. I have same error.

    [ 6.692850] snd_sof_intel_hda_common:hda_dsp_stream_trigger: sof-audio-pci-intel-tgl 0000:00:1f.3: FW Poll Status: reg[0x160]=0x140000 successful
    [ 6.692854] sof-audio-pci-intel-tgl 0000:00:1f.3: ------------[ DSP dump start ]------------
    [ 6.692857] sof-audio-pci-intel-tgl 0000:00:1f.3: Firmware download failed
    [ 6.692860] sof-audio-pci-intel-tgl 0000:00:1f.3: fw_state: SOF_FW_BOOT_IN_PROGRESS (2)
    [ 6.692865] sof-audio-pci-intel-tgl 0000:00:1f.3: 0x80000012: module: ROM, state: CSE_VALIDATE_IMAGE_REQUEST, not running
    [ 6.692870] sof-audio-pci-intel-tgl 0000:00:1f.3: error code: 0x2c (error: signature verification failed)
    [ 6.692883] sof-audio-pci-intel-tgl 0000:00:1f.3: extended rom status: 0x80000012 0x2c 0x0 0x0 0x0 0x0 0x2510113 0x0
    [ 6.692886] sof-audio-pci-intel-tgl 0000:00:1f.3: ------------[ DSP dump end ]------------
    [ 6.692906] sof-audio-pci-intel-tgl 0000:00:1f.3: Failed to start DSP
    [ 6.692909] sof-audio-pci-intel-tgl 0000:00:1f.3: error: failed to boot DSP firmware -110
    [ 6.692912] snd_sof:sof_set_fw_state: sof-audio-pci-intel-tgl 0000:00:1f.3: fw_state change: 2 -> 3

  • rogertsai(AAEON)
    rogertsai(AAEON) New Member Posts: 350 ✭✭✭

    @fredoh
    It’s quite weird that the 0001 did not remove the SOF in BIOS, but the key failed to boot.
    Please share both 0000 and 0001 logs with us. Also provide your application environment, tools and test steps for further clarity.

  • fredoh
    fredoh New Member Posts: 13
    edited September 28

    Yes, It’s quite weird, I have a team in Shanghai, they have two 0001 HW. I tested with one of them. It has R1.0 BIOS(it came with it, no update was required), it works fine with same build and same test.

    I have no idea, how come two of my 0001 devices don't support SOF key. I will let you know if I find any clue.

  • fredoh
    fredoh New Member Posts: 13
    edited September 28

    Narrowing down to ME update problem. This is last screen of BIOS upgrade.
    Verifying Boot Block ... Done is last print and it automatically reboot. Is this right? I don't remember TGL 0000 case, but WHL Up Xtreme stays in the shell. And last messages are 'Loading ME data to BIOS ... done'
    Automatic reboot is normal and can I belive my BIOS upgrade is successful?


    I think I'm pretty familiar with BIOS upgrade procedure. If I miss any step, please educate me.

    • Login with admin access level
    • CRB Setup → PCH-FW Configuration → Firmware Update Configuration
    • Enable 'Me FW Image Re-Flash' (default is Disabled)
    • Set Boot to Internal EFI Shell
    • Save and reboot
    • Boot to EFI Shell
    • FS0: (this is my case)
    • go.nsh
  • fredoh
    fredoh New Member Posts: 13
    edited September 29

    Comparing my BIOS settings again. One of my 0001, when it has R1.0
    ME Firmware Status 2 = 0x80100106

    After upgrading to R1.1
    ME Firmware Status 2 = 0x89100106

    I checked on same value on the other device which has R1.1 as well.
    ME Firmware Status 2 = 0x80100106
    Other values are matching but this Status 2 is different from the other identical device.
    Apparently both have same problem, so Status 2 may not be the problem.

    Is there any way I can check ME is updated properly?

  • fredoh
    fredoh New Member Posts: 13
    edited October 14

    I was able to upgrade to R1.6 BIOS on another TGL UP Xtreme 0000. So my BIOS upgrade skill is not doubtable, :)

    While the BIOS Upgrading, it shows "ME loading" and it didn't reboot automatically. My 0001 devices are rebooting without having ME upgrade done. I think it crashes at ME upgrade stage. Just rebooting without throwing errors is too bad. It hides so many problems.

  • fredoh
    fredoh New Member Posts: 13

    After flashing 100 times of BIOS, T.T, found the problem and fixed it myself.

    Aaeon didn't include ME update option in default BIOS upgrading script. My case, it come with ME block broken, without loading ME again it always fails.

    I was worry about automatic reboot but it was due to the option /REBOOT, not a critical problem.

    This is my command to flash the BIOS, after flashing the BIOS. SOF Community is working fine.
    AfuEfix64_5.14.03.0039.efi V04Z3M11.bin /P /N /R /B /ME

    You can close this issue.