EFI BIOS Concept

[圖文] LINE原創貼圖

2015-07-10T09:39:00.002-07:00

最近畫了一組LINE原創貼圖，經過審查通過，在LINE正式上架了。
原創貼圖連結 http://line.me/S/sticker/1160144
希望大家可以多多支持Icey Creamy!

以下是貼圖內容

BIOS該怎麼換SCI的IRQ9變成IRQ11呢?

2012-03-27T04:44:00.001-07:00

預設值SCI是透過IRQ9，

如何去改IRQ9到IRQ11呢?

要修改三個部分

1. BIOS部分是透過EFI CODE這部分可以去參考Intel的南橋spec的[SCI_IRQ_SEL].

2. ASL CODE 這部分可以去參考ACPI spec的[FADT SCT_INT] 從9設成11

3. ASL CODE 這部分可以去參考ACPI spec的[MADT EFI_ACPI_2_0_INTERRUPT_SOURCE_OVERRIDE]也是從9設成11

這樣就可以改用IRQ11去發SCI了。

How to create EDK2 enviornment?

2012-03-06T01:32:00.000-08:00

以下是我個人電腦的設定，依據不同環境需要自行調整。

使用TortoiseSVN軟體download 位址https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2的source code

預設會下載到C:\EDK2的資料夾裡。

開啟Visual Studio 2008 Command Prompt

到指定的目錄夾，C:\EDK2

鍵入edksetup.bat

C:\EDK2\edksetup.bat

然後再到Conf的資料夾

C:\EDK2\Conf\

鍵入edit target.txt

C:\EDK2\Conf\edit target.txt

ACTIVE_PLATFORM = Nt32Pkg/Nt32Pkg.dsc

TARGET = DEBUG

TARGET_ARCH = IA32

TOOL_CHAIN_CONF = Conf/toos_def.txt

TOOL_CHAIN_TAG = MYTOOLS

#MAX_CONCURRENT_THREAD_NUMBER = 1

MAX_CONCURRENT_THREAD_NUMBER = 8 # My CPU is Quad Core

BUILD_RULE_CONF = Conf/build_rule.txt

Build完後，可以到

C:\EDK2\Build\NT32\DEBUG_MYTOOLS\IA32

鍵入secmain.exe

C:\EDK2\Build\NT32\DEBUG_MYTOOLS\IA32\SecMain.exe

即可進入EDK2的模擬環境

PS2 Keyboard Malfunction Sometimes

2011-11-30T18:42:00.000-08:00

最近遇到一個在POST過程中，隨意按鍵，有機率性的PS2 internal keyboard不能動的問題，所以為了解決這個問題，在BIOS logo出來時，去發一個keyboard reset給KBC controller。

以下的程式碼就是發keyboard reset給KBC controller

VOID
KeyBoardReset(
VOID
)
{
UINT8 Data;

//
// Clear Output Buffer data
//
Data = IoInput8(0x64);
while (Data & 0x01) {
Data = IoInput8(0x60);
Data = IoInput8(0x64);
}

//
// Disalbe Aux Device
//
IoOutput8 (0x64, 0xA7);
while (Data & 0x02) {
Data = IoInput8(0x64);
}

//
// Disalbe Keyboard
//
IoOutput8 (0x64, 0xAD);
while (Data & 0x02) {
Data = IoInput8(0x64);
}

//
// Reset keyboard.
//
IoOutput8 (0x60, 0xFF);
Data = IoInput8(0x64);
while (!(Data & 0x01)) {
Data = IoInput8(0x64);
}
Data = IoInput8(0x60);
Data = IoInput8(0x64);
while (!(Data & 0x01)) {
Data = IoInput8(0x64);
}
Data = IoInput8(0x60);
}

Kindle Touch 連不上Wi-Fi?

2011-11-28T23:34:00.000-08:00

在剛開始使用Kindle Touch時，有遇到無法透過家中的無線分享器連上Wi-Fi，怎麼會這樣子呢?上網找各種solution，使用了以下的方式，讓Kindle Touch可以順利連上Wi-Fi。

需求：一台安裝有Windows 7的電腦加上有一張無線網卡(若是筆電就是內建配備；
桌上型電腦的話，可能要再買一張USB無線網卡)
軟體：額外安裝Connectify(用谷歌可以搜尋的到)

它的運作模式就是將你的電腦透過無線網卡，變成一個Hot Spot，讓你的Wi-Fi裝置可以透過它連上網路。簡單的方式就是，請記得密碼設定成10碼，編碼模式設成WEP。不然Kindle Touch可能會無法連上Wi-Fi。

Kindle Touch 開箱文

2011-11-28T05:41:00.000-08:00

期待已久的Kindle Touch WiFi 廣告版總算是入手了! 接下來就讓我來開箱吧。

簡單又環保的設計採破壞式開箱方式，我想這樣才會願意把盒子拿去回收吧(笑)

主角登場了!!! 伴隨著淡淡的紙盒香味飄出~在Kindle Touch的螢幕上有讓人有看來像是擺上一張紙的感覺，但那其實就是電子紙的魔力啊!!!在Kindle Touch螢幕下方有四條線(好在不是設計成三條線冏rz)，那就是Home鍵，在機身下方由左至右有micro USB孔、耳機孔、和開關鍵。

側身設計很薄

躺在Kindle Touch正下方的就是傳輸以及充電的micro USB線

準備插上USB線來大展身手囉。

可以看到插上USB線後，橘燈亮起，它就自動開機了...

接下來就會看到一連串的Kindle Touch的自我介紹。若迫不及待，可以按下方四條横線的Home鍵開始設定Kindle Touch吧。

最重要的就是設定Kindle Touch的Wi-Fi，讓它連上網路。

連上Wi-Fi後，就會看到有Wi-Fi字樣出現在右上角

設成完成後就註冊Amazon的帳號準備買書吧。

背面的設計也是很有質感的。

Kindle Touch優點：
1. 以觸控的電子書來說，紅外線觸控方式在Kindle Touch表現的很不錯
2. 即時英文長押螢幕單字來查詢，非常適合學習英文
3. 大小和重量適中，很適合帶出門喝咖啡邊看書，多愜意啊
4. 翻頁的反應速度似乎有比前一代進步
5. 由於是電子紙，電池續航力最長可以到兩個月
6. 最大優點是電子紙螢幕看再久，眼睛也不會痠

Kindle Touch缺點：
1. 資料夾管理系統不是很方便
2. 如果將機身横擺，也沒辦法將文件橫向顯示
3. 手指要乾淨，才不會把螢幕弄髒(笑)

Set PS2 KB LED Status (Num Lock/Cap Lock/Scroll Lock) in Code

2011-11-21T20:05:00.000-08:00

1. Send keyboard command 0xED to KBC command port 0x64
2. Wait for the response 0xFA value from KBC data port 0x60
3. Send keyboard LED status command to KBC command port 0x64
     EDh nn      write LEDs. nn=
                                                b2      Caps Lock
                                                 b1      Num Lock
                                                 b0      Scroll Lock
     Ex. 0x05 means Caps Lock and Scroll Lock is enabled, Num Lock is disabled
4. Wait for the response 0xFA value from KBC data port 0x60

Trigger SMI to Do CpuIo Cause System Hangs Up Under Windows

2011-11-01T00:18:00.000-07:00

We would like to use CpuIo protocol and must locate it first.

Status = gBS->LocateProtocol (&gEfiCpuIoProtocolGuid, NULL, &CpuIo);
There is a question here, system is entered windows that has exited boot service.
Therefore, we locate this protocol will cause system hangs up.
To avoid this, we should create a global variable to save the CpuIo pointer when system during POST phase.

EFI_CPU_IO_PROTOCOL   *mCpuIo = NULL;

EFI_DRIVER_ENTRY_POINT (SctCpuIoPointSave)
EFI_STATUS
SctCpuIoPointSave (
IN EFI_HANDLE ImageHandle,
IN EFI_SYSTEM_TABLE *SystemTable
)
{
EFI_STATUS Status;
EFI_HANDLE Handle;
DxeInitializeDriverLib (ImageHandle, SystemTable);

//
// Locate CpuIo protocol.
//
Status = gBS->LocateProtocol ( &gEfiCpuIoProtocolGuid, NULL, &mCpuIo ) ;

return Status;
} // EnteyPoint.

Just need to call your function in SMI code to use CpuIo.
For example,

VOID
ShowPort80 (VOID)
{
EFI_STATUS    Status ;
UINT8                Data ;
  Data = 0x99;
Status = mCpuIo->Io.Write (
                        mCpuIo,
                        EfiCpuIoWidthUint8,
                        0x80,
                        1,
                        &Data);
ASSERT_EFI_ERROR (Status);
}

How do I hide the "Devices and Printers" of hardware component in Windows 7

2011-10-26T19:31:00.000-07:00

For example: want to remove the camera device in devices and printers

Just need to add red part in device ASL code.

Device(PRT3) {

Name(_ADR, 0x00000003)

Name(_UPC, package() {

0x00,

0xFF,

0x00000000,

0x00000000

})

// Using method _RMV remove component

Method(_RMV,0)

{

Return(0x00) // 0 : Unremovable 1: Removable

}

Deep S3

2011-08-25T22:48:00.000-07:00

Why do we need deep S3?
A: Deep S3 can save more power consumption for notebook battery life.

How does the deep S3 work?
A: Deep S3 will automatically activate when notebook only attach the battery without AC plug-in and during S3. System goes to sleep to S3 will check the AC adapt is present or not. If AC is plug-in, the system will enter normal S3. If system without AC plug-in, the system will enter deep S3.

More information can refer to "Intel Deep S3 Implementation Guide".

AMD UMI and PCIe Bridge Register Access Method

2011-08-21T23:31:00.001-07:00

If we want to access the UMI and the FCH/GPP link interface could through the following register spaces: ABCFG, AXCFG, AXINDC, AXINDP, RCINDC, and RCINDP

Change the register spaces must through the AB_INDX/AB_DATA register pair. You can get the AB_INDX through PM_REG that IO index port 0xCD6 and IO data port 0xCD7 offset 0xE0 register.

For example, if the PM_REG offset 0xE0 is 0xCD8 that means the AB_INDX is 0xCD8 and AB_DATA is equal to AB_INDX + 4.

========================================

AXINDC Registers:

AX_INDXC 0x30

AX_DATAC 0x34

Example 1: For Write Temp to AXINDC 20h

Out CD8h, 00000030h

Out CDCh, 00000020h

Out CD8h, 00000034h

Out CDCh, Temp

=========================================

AXINDP Registers:

AX_INDXP 0x38

AX_DATAP 0x3C

Example 2: For Write Temp to AXINDP 20h

Out CD8h, 40000030h

Out CDCh, 00000020h

Out CD8h, 40000034h

Out CDCh, Temp

=========================================

AXCFG Registers:

Example 3: For Write Temp to AXCFG 03h

Out CD8h, 80000003h

Out CDCh, Temp

=========================================

ABCFG Registers:

Example 4: For Write 0xFFFFFFFF to ABCFG 04h

Out CD8h, C0000004h

Out CDCh, FFFFFFFFh

=========================================

RCINDC Registers:

Example 5: For Write Temp to RCINDC 14h

Out CD8h, 20000014h

Out CDCh, Temp

=========================================

RCINDP Registers:

Example 6: For Write Temp to RCINDP A0h(PortB)

Out CD8h, 610000A0h

Out CDCh, Temp

How to know the notebook panel resolution during POST

2011-08-10T19:31:00.000-07:00

The horizontal can get from EDID table bytes 0x38(lower 8 bits) and 0x3A(Upper 4:4 bits).
For example:
Bytes   Value
0x38      0xA0
0x3A     0x50

Horizotal = (Offset (0x3A) & 0xF0 << 4) + Offset (0x38)
               = (0x50 << 4) + 0xA0
               = 0x5A0 (Hex)
               = 1440 (Dec)

The vertical can get from EDID table bytes 0x3B(lower 8 bits) and 0x3D(Upper 4:4 bits).
For example:
Bytes   Value
0x3B      0x84
0x3D     0x30

Vertical = (Offset (0x3D) & 0xF0 << 4) + Offset (0x3B)
             = (0x30 << 4) + 0x84
             = 0x384 (Hex)
             = 900 (Dec)

Therefore, we can know the panel resoultion is 1440 * 900 for this example.

Library Compiler Error - don't know how to make

2011-06-29T08:07:00.000-07:00

遇到 don't know how to make LibraryX.lib 的情況，可以用以下的方式排除
1. 確定LibraryX.lib 在 AAA.dsc裡面有去定義這個AAA.inf
2. 若在build這個AAA.inf的library的時候就遇到compiler error，請先解決這個compiler error (可能是LibraryX建的方式有問題，可以參照其他現成的library做法)
3. 若你在BBB的檔案要引用這個LibraryX的時候，請先確定在build出來的temp目錄層底下，有長出LibraryX.lib的檔案。
4. 若有，請在BBB.inf裡確定以下兩點
[includes.common]
$(EFI_SOURCE)\(Library_ROOT) //要指定路徑在library那一層
[libraries.common]
LibraryX
5.記住呼叫的Libray名字不要打錯，不然就會造成complier "don't know how to make" 的error

SATA及USB介面傳輸速度比較表

2011-06-27T08:08:00.001-07:00

SATA版本	頻寬	速度傳輸一部6G高清電影
SATA 3.0	6Gb/s	600MB 約10秒 (理想值)
SATA 2.0	3Gb/s	300MB 約20秒 (理想值)
SATA 1.0	1.5Gb/s	150MB 約40秒 (理想值)

USB版本	頻寬	速度傳輸一部6G高清電影
USB 3.0	5 Gb/s	500MB 約12秒 (理想值)
USB 2.0	480Mb/s	48MB 約125秒 (理想值)
USB 1.1	120Mb/s	1.2MB 約5000秒 (理想值)

USB 1.0 1.5Mb/s 150KB 約40000秒 (理想值)

How to make an EFI library?

2011-06-22T23:57:00.000-07:00

1. 在inf檔裡修改
[defines]
BASE_NAME       = HelloLib
COMPONENT_TYPE = LIBRARY

[sources.common]
Hello\Hello.c
Hello\Hello.h

2. 把你需要的library function加到hello.c及hello.h裡

3.在EFI driver去引用HelloLib的時候要去修改以下的檔案
   AbcDriver.inf
   AbcDriver.c

4.AbcDriver.c要加入
   #include "Hello.h"

   用extern的方式加入library的function名字
   並在你的function去呼叫你要用的library function即可

5.AbcDriver.inf要加入
[includes.common]
$(EFI_SOURCE)\Library\Hello <== 指到放Hello.h的那一層目錄

[libraries.common]
   HelloLib

INT 15h E820 Query Memory Map Use Debug32.exe

2011-05-30T03:41:00.000-07:00

;Input:
;       eax   - function code 0E820H
;       ebx   - continuation code, zero for first call
;       es:di - buffer pointer , point to an buffer for BIOS to fill in.
;       ecx   - buffer size , minimum is 20 bytes
;       edx   - signature 'SMAP'

C:\debug32
-r32
-a
mov eax, 0000e820
mov ebx, 0
mov ecx, 14
mov edx, 534d4150
mov di, 200
int 15
int 3
p
-go

;Output:
;       CF    - non-carry indicates no error
;       eax   - signature return 'SMAP'
;       es:di - buffer pointer, same as input
;       ecx   - real buffer size return
;       ebx   - continuation code , zero return if last run occured

ACPI can't recogize OS type with Ubuntu operating system

2011-05-26T02:42:00.000-07:00

ACPI can't recogize OS type with Ubuntu operating system

Remove "Linux" from supported _OSI strings.
The Linux OS no longer wants to respond true for this string.
The only safe strings are windows-related as they represent the tested path through the BIOS-provided ASL.
===========================================================================

現在Ubuntu不支援用_OSI strings的方式來回報OS類型

A20 Gate

2011-05-23T01:33:00.000-07:00

1. 在8086的系統，當初只設計20根位址線。透過Segment + Offset的方式來定址，Ex. F000 : 0010h = F0000+ 0010h = F0010h 那衍生了一個問題就是當CS : IP的值為FFFF : FFFFh = FFFF0 + FFFFh = 10FFEFh = 1M + 64K – 16 Bytes 但系統只能存取到1M以下，這該如何是好? 所以大於1M，系統會直接回繞。

2.   在80286的系統，位址線變成了24根，但又要向下相容，就衍生了A20的模式，當A20是disable，就等同於8086的架構，若A20 Enable，系統就可以存取到2 ^ 24次方 = 16M byte，也就是Segment變成最大值為FFFFFh 而不是FFFFh

3.   開啟A20 Gate的方法，最簡單就是對IO Port 92h 的bit 1給設起來；反之關閉A20 Gate的方法，就是清掉IO Port 92h 的bit 1。

enable_A20:
        cli

        call    a20wait
        mov     al,0xAD ; Disable Keyboard
        out     0x64,al

        call    a20wait
        mov     al,0xD0
        out     0x64,al

        call    a20wait2
        in      al,0x60
        push    eax

        call    a20wait
        mov     al,0xD1
        out     0x64,al

        call    a20wait
        pop     eax
        or      al,2
        out     0x60,al

        call    a20wait
        mov     al,0xAE   ; Enable Keyboard
        out     0x64,al

        call    a20wait
        sti
        ret

a20wait:
        in      al,0x64
        test    al,2
        jnz     a20wait
        ret

a20wait2:
        in      al,0x64
        test    al,1
        jz      a20wait2
        ret

8259 Control Word

2011-05-18T22:57:00.001-07:00

RTC Lost Power

2011-05-18T02:25:00.000-07:00

After remove RTC coin battery, system plug-in RTC coin battery the CMOS register 0xE access by (index port 0x70/ data port 0x71) bit 7 will be set. After check this bit, we also need to clear this bit by code.

============================================================================

在移除RTC水銀電池後，然後再次插上，這時後CMOS register offset 0xE的位址，在(使用index port 0x70/ data port 0x71)方式存取，這時候的0xE的bit 7會被設起來，在code裡面，一檢查完，就需要清掉這個位元。

About IO Decode (AMD Chipset)

2011-05-17T21:55:00.000-07:00

1.Set IO base address in south bridge register
2.Enable Alternative Wide IO Range in south bridge register
3.Enable Wide IO Port in south bridge register
if system still can't open IO decode, we need to check is occupied by another device using the same IO resource or not. We can check the value in each of PCI bridge offset 0x1C.PCI bridger IO resource is aligned to a 4KB boundary.

============================================================================

1.設定要做IO decode去設定南橋暫存器的IO Base Adress
2.開啟南橋暫存器的Alternative Wide IO Range
3.開啟南橋暫存器的Wide IO Port
若還是無法開啟IO decode，這時候就要檢查是否有別的device佔用到相同的IO decode的位址，可以先檢查每個PCI bridge的offset 0x1C的值，PCI bridge一次就是佔4K的IO resource。

The Different Between LegacyBiosInt86 And LegacyBiosFarCall86

2011-05-16T07:37:00.000-07:00

When we wanna issue a software interrupt, we need to call LegacyBiosInt86 thunk function call.
When we wanna jump to OPROM or other legacy address, we need to call LegacyBiosFarCall86 thunk function call.

========================================================================

LegacyBiosInt86是我們需要使用程式去呼叫INT時所使用到的thunk function ，像是CALL INT10...
LegacyBiosFarCall86是我們需要跳到option ROM address所需要用到的thunk function

Bring Up BIOS

2011-05-10T20:48:00.000-07:00

1. Modify GPIO that depends on platform design
2. Modify FDLA (Firmware Device Linear Address)
3. Change VBIOS
4. Change SPI ROM size
5. Disable KSC

===========================================================================

做一個Bring-up BIOS主要的工作如下：
1. 依照platform的layout去修改GPIO
2. 修改FDLA (Firmware Device Linear Address)
3. 換掉VBIOS
4. 依照platform的設計改變SPI ROM大小
5. 移除KSC

Software SMI Behavior

2011-05-06T21:15:00.000-07:00

ACPI Enable and Disable Behavior

2011-05-06T20:23:00.000-07:00

ACPI Enable
OSPM performs this transition by writing the ACPI_ENABLE value to the SMI_CMD, which generates an event to the hardware to transition the platform into ACPI mode. When hardware has finished the transition, it sets the SCI_EN bit and returns control back to OSPM.

ACPI Disable
While in the G0 “working state,” OSPM can request a transition to Legacy mode by writing the ACPI_DISABLE value to the SMI_CMD register, which results in the hardware going into legacy mode and resetting the SCI_EN bit LOW.

=======================================================================

ACPI Enable
由OS去寫ACPI_ENABLE的值到SMI_CMD port，會由BIOS所註冊的ACPI Enable的SMI handler去處理將SCI_EN bit設起來，在這handler裡，OEM可以自行加入程式碼以達到一些特殊的需求，再將控制權交還給BIOS。

ACPI Disable
在ACPI_ENABLE下，也可由OS去寫ACPI_DISABLE的值到SMI_CMD port，會由BIOS所註冊的ACPI Disable的SMI handler去處理將SCI_EN bit清為零。