一.實(shí)現(xiàn)multbin?
1.首先修改config.bib?

比如:
#elif defined IMGMULTIBIN
;? NAME? ? ? ? ? START ADDR? ? SIZE? ? ? TYPE
;? ----------------------------------------------------------------
NK? ? ? ? ? ? 80220000? ? ? 007DE000? RAMIMAGE??
SHELL? ? ? ? 809FE000? ? ? 00100000? RAMIMAGE??
APPS? ? ? ? ? 80AFE000? ? ? 00100000? RAMIMAGE??
CHAIN? ? ? ? 80BFE000? ? ? 00002000? RESERVED ; XIP chain info
RAM? ? ? ? ? 80C00000? ? ? 01000000? RAM? ? ? ??
pdwXIPLoc? ? 00000000? ? ? 80BFE000? FIXUPVAR? ; XIP pTOC

AUTOSIZE=ON? ? ? ? ? ;自動(dòng)調(diào)整RAM 起始地址到 最近的 XIP region的末尾
ROM_AUTOSIZE=ON? ? ? ；每個(gè)分隔的XIP regin 的大小自動(dòng)調(diào)整
DLLADDR_AUTOSIZE=ON? ；自動(dòng)調(diào)整 dll地址空間大小根據(jù) multiple XIP regions.?
XIPSCHAIN=80bfe000? ? ; 指定CHAIN region 在內(nèi)存段的地址.?
Note? This address is applicable for the example provided in the previous step of this procedure.?
If you use a customized address for the CHAIN region or a different BSP, you will have to?
update this variable to match your settings?



pdwXIPLoc 必須定義START ADDR =00000000 SIZE=CHAIN的START ADDR
CHAIN 用來保存多個(gè)bin的chain info,CHAIN的位置和你bootloader代碼有關(guān),(cepc一般放在 NK region 后面)
所有的RAMIMAGE 必須在物理,虛擬地址上都連續(xù)
經(jīng)驗(yàn)上每個(gè)bin 加32K (msdn：As a good practice, add the sizes of all files for a given region,?
and then add an extra 32K as a buffer. Adding this extra amount provides room for the files to?
reduce and expand as they change between each successive build)


2.修改platform.bib,把不同的部分放入到不動(dòng)的region中 (其他bib也可以修改的)
比如
if IMGMULTIBIN
shell.exe? $(_FLATRELEASEDIR)\shell.exe? SHELL? SH
filesys.exe $(_FLATRELEASEDIR)\filesys.exe SHELL? SH
#else
shell.exe? $(_FLATRELEASEDIR)\shell.exe? NK? SH
filesys.exe $(_FLATRELEASEDIR)\filesys.exe NK? SH
#endif

表示把文件系統(tǒng), shell放到 SHELL regin (shell.bin)


3.設(shè)置: 環(huán)境變量IMGMULTIBIN =1


4.在cfw.c中的OEMInit中的最后加上對(duì)InitRomChain的調(diào)用，來連接各個(gè)bin,最后連接到OEMRomChain 上!!!

void InitRomChain(void)
{
static? ROMChain_t s_pNextRom[MAX_ROM] = {0};
DWORD? dwRomCount = 0;
DWORD? ? ? dwChainCount = 0;
DWORD? *pdwCurXIP;
DWORD? ? ? dwNumXIPs;
PXIPCHAIN_ENTRY pChainEntry = NULL;

if(pdwXIPLoc == NOT_FIXEDUP)
{
return;? //pdwXIPLoc 必須是 FIXUPVAR ,否則表示沒有chain或者設(shè)置不對(duì)
}

// set the top bit to mark it as a virtual address
pdwCurXIP = (DWORD*)(((DWORD)pdwXIPLoc) | 0x80000000);

// first DWORD is number of XIPs
dwNumXIPs = (*pdwCurXIP);??

if(dwNumXIPs > MAX_ROM)
{
lpWriteDebugStringFunc(TEXT("ERROR: Number of XIPs exceeds MAX\n"));
return;
}

pChainEntry = (PXIPCHAIN_ENTRY)(pdwCurXIP + 1);? //其實(shí)就是指向CHAIN 中chain info的相關(guān)信息

while(dwChainCount < dwNumXIPs)
{
if ((pChainEntry->usFlags & ROMXIP_OK_TO_LOAD) &&? // flags indicates valid XIP
*(LPDWORD)(((DWORD)(pChainEntry->pvAddr)) + ROM_SIGNATURE_OFFSET) == ROM_SIGNATURE)
{
s_pNextRom[dwRomCount].pTOC = *(ROMHDR **)(　　((DWORD)(pChainEntry->pvAddr)) + ROM_SIGNATURE_OFFSET + 4　　);
s_pNextRom[dwRomCount].pNext = NULL;

if (dwRomCount != 0)
{
s_pNextRom[dwRomCount-1].pNext = &s_pNextRom[dwRomCount];
}
else
{
OEMRomChain = s_pNextRom;
}
dwRomCount++;
}
else
{
lpWriteDebugStringFunc( _T("Invalid XIP found\n") );
}

++pChainEntry;
dwChainCount++;
}
}




//在romldr.h中　定義了上面的相關(guān)的
typedef struct _XIPCHAIN_ENTRY {
LPVOID? pvAddr;? ? ? ? ? ? ? ? // address of the XIP
DWORD? dwLength;? ? ? ? ? ? ? // the size of the XIP
DWORD? dwMaxLength;? ? ? ? ? ? // the biggest it can grow to
USHORT? usOrder;? ? ? ? ? ? ? ? // where to put into ROMChain_t
USHORT? usFlags;? ? ? ? ? ? ? ? // flags/status of XIP
DWORD? dwVersion;? ? ? ? ? ? ? // version info
CHAR? ? szName[XIP_NAMELEN];? ? // Name of XIP, typically the bin file''s name, w/o .bin
DWORD? dwAlgoFlags;? ? ? ? ? ? // algorithm to use for signature verification
DWORD? dwKeyLen;? ? ? ? ? ? ? // length of key in byPublicKey
BYTE? ? byPublicKey[596];? ? ? // public key data
} XIPCHAIN_ENTRY, *PXIPCHAIN_ENTRY;

#define ROMXIP_OK_TO_LOAD? ? ? 0x0001
#define ROMXIP_IS_SIGNED? ? ? ? 0x0002

#define ROM_SIGNATURE_OFFSET 64　　　//0x40
#define ROM_SIGNATURE 0x43454345? ? //cece 4byte? ? =>ROMHDR 在0x44偏移處,
//每個(gè)bin 都有個(gè)pToc指向ROMHDR開頭的地址,看下面的bin 文件結(jié)構(gòu),在0x44offset處地址里面放的是ROMHDR地址,開始是-1,由romimage.exe來設(shè)置的


//有點(diǎn)糊涂了 再分析下bin文件的結(jié)構(gòu)
struct BinFile{?
BYTE signature[7]; // = { ''''B'''', ''''0'''', ''''0'''', ''''0'''', ''''F'''', ''''F'''', ''''\a'''' }?
DWORD ImageStart?
DWORD ImageLength?
Record ImageRecords[RecordNum]?
};?


struct Record{?
DWORD address;?
DWORD length;?
DWORD chksum;?
};?
在文件的最開端，會(huì)放置一個(gè)BinFile結(jié)構(gòu)，imageStart和ImageLength分別對(duì)應(yīng)鏡像展開后在內(nèi)存中存放的首地址和長度。
該結(jié)構(gòu)中的RecordNum為不確定的，通常在最后一個(gè)記錄之后增加一個(gè)address和Chksum都為0的紀(jì)錄表示結(jié)束，
而這個(gè)表示結(jié)束的結(jié)構(gòu)中的Length則標(biāo)示其實(shí)際入口點(diǎn)。?
可以用viewbin -r 去看下nk.bin:
Image Start = 0x8C200000, length = 0x00E158C8
Start address = 0x8C201000
Checking record #22 for potential TOC (ROMOFFSET = 0xFF446658)
Checking record #177 for potential TOC (ROMOFFSET = 0x00000000)
Found pTOC? = 0x8d013950
ROMOFFSET = 0x00000000

ROMHDR ----------------------------------------
DLL First? ? ? ? ? : 0x01E401E7??
DLL Last? ? ? ? ? ? : 0x02000000??
Physical First? ? ? : 0x8C200000??
Physical Last? ? ? : 0x8D0158C8??
RAM Start? ? ? ? ? : 0x8E600000??
RAM Free? ? ? ? ? ? : 0x8E629000??
RAM End? ? ? ? ? ? : 0x8FF00000??
Kernel flags? ? ? ? : 0x00000002??
Prof Symbol Offset? : 0x00000000??
Num Copy Entries? ? :? ? ? ? ? 1? ??
Copy Entries Offset : 0x8CC7AE8C??
Num Modules? ? ? ? :? ? ? ? 166? ??
Num Files? ? ? ? ? :? ? ? ? 95? ??
Kernel Debugger? ? :? ? ? ? No
CPU? ? ? ? ? ? ? ? :? ? 0x01c2 (Thumb)
Extensions? ? ? ? ? : 0x8C20266C

ROMHDR Extensions -----------------------------
PID[0] = 0x00000000
PID[1] = 0x00000000
PID[2] = 0x00000000
PID[3] = 0x00000000
PID[4] = 0x00000000
PID[5] = 0x00000000
PID[6] = 0x00000000
PID[7] = 0x00000000
PID[8] = 0x00000000
PID[9] = 0x00000000
Next: 00000000

COPY Sections ---------------------------------
Src: 0x8CD18DA8? Dest: 0x8E606000? CLen: 0x228? ? ? DLen: 0x22B4C?

MODULES ---------------------------------------
11/20/2006? 03:20:28? ? ? 268800? nk.exe?
11/20/2006? 03:25:22? ? ? 550400? coredll.dll?
11/20/2006? 03:25:22? ? ? 205824? filesys.exe?
11/20/2006? 03:25:22? ? ? 723968? gwes.exe?
11/20/2006? 03:09:08? ? ? 25600? device.exe?
.......................
.......................
FILES ----------------------------------------
11/20/2006? 03:10:42? C_R_? ? ? 2897? ? ? 12461? ? ? ? ? ? ? ? ceconfig.h (ROM 0x8C55E4AC)
11/20/2006? 03:25:18? _HRS? ? ? ? ? 0? ? 694654? ? ? ? ? ? ? ? wince.nls (ROM 0x8CE36984)
5/09/2007? 14:06:14? CHRS? ? ? 3427? ? ? 20574? ? ? ? ? ? ? initobj.dat (ROM 0x8C730280)
.......................
.......................
done.

分布結(jié)構(gòu):
Image :
Offset -----------?
0x00 | ImageStart?
|?
|?
0x40 | Rom Signature { 0x43454345 }?
0x44 | Pointer to the ROMHDR for this Region?
|?
|?
0x???? | ROMHDR{ 　　　　　　　　　　　　　　　<-pToc所指
| };?
|?


Chain file?
struct _XIPCHAIN_ENTRY {?
LPVOID pvAddr; // address of the XIP?
DWORD dwLength; // the size of the XIP?
DWORD dwMaxLength; // the biggest it can grow to?
USHORT usOrder; // where to put into ROMChain_t?
USHORT usFlags; // flags/status of XIP?
DWORD dwVersion; // version info?
CHAR szName[XIP_NAMELEN]; // Name of XIP, typically the bin file''''s name, w/o .bin?
DWORD dwAlgoFlags; // algorithm to use for signature verification?
DWORD dwKeyLen; // length of key in byPublicKey?
BYTE byPublicKey[596]; // public key data?
};?


Offset --------------------------?
0x00 | DWORD Count;?
0x04 | XIPCHAIN_ENTRY[1]{?
| };?
| XIPCHAIN_ENTRY[2]{?
| };?
| ...?


二.關(guān)于OEMMultiBINNotify ,他是被blcommon 來調(diào)用，來讓我們獲得一個(gè)或多個(gè) BIN regions的信息的
比如
用結(jié)構(gòu)
typedef struct _MultiBINInfo_
{
DWORD dwNumRegions;
RegionInfo Region[BL_MAX_BIN_REGIONS];
} MultiBINInfo, *PMultiBINInfo;

定義一個(gè)MultiBINInfo? ? g_BINRegionInfo;全局變量在OEMMultiBINNotify中獲得每個(gè)bin regins的信息

ReginInfo結(jié)構(gòu):
typedef struct _RegionInfo_
{
DWORD dwRegionStart;
DWORD dwRegionLength;
} RegionInfo, *PRegionInfo;

g_BINRegionInfo 被WriteRegionsToBootMedia　寫regions到flash用到,
我用的是nandflash,
WriteRegionsToBootMedia中這段
// Look in the kernel region''s extension area for a multi-BIN extension descriptor.
// This region, if found, details the number, start, and size of each BIN region.
//
//for (nCount = 0, dwNumExts = 0 ; (nCount < g_BINRegionInfo.dwNumRegions) && !pChainInfo ; nCount++)
for (nCount = 0, dwNumExts = 0 ; (nCount < g_BINRegionInfo.dwNumRegions); nCount++)
{
// Does this region contain nk.exe and an extension pointer?
//
pExt = (EXTENSION *)GetKernelExtPointer(g_BINRegionInfo.Region[nCount].dwRegionStart,
g_BINRegionInfo.Region[nCount].dwRegionLength );
if ( pExt != NULL)
{
// If there is an extension pointer region, walk it until the end.
//
while (pExt)
{
DWORD dwBaseAddr = g_BINRegionInfo.Region[nCount].dwRegionStart;
pExt = (EXTENSION *)OEMMapMemAddr(dwBaseAddr, (DWORD)pExt);
EdbgOutputDebugString("INFO: OEMLaunch: Found chain extenstion: ''%s'' @ 0x%x\r\n", pExt->name, dwBaseAddr);
if ((pExt->type == 0) && !strcmp(pExt->name, "chain information"))
{
pChainInfo = (PXIPCHAIN_SUMMARY) OEMMapMemAddr(dwBaseAddr, (DWORD)pExt->pdata);
dwNumExts = (pExt->length / sizeof(XIPCHAIN_SUMMARY));
EdbgOutputDebugString("INFO: OEMLaunch: Found ''chain information'' (pChainInfo=0x%x? Extensions=0x%x).\r\n", (DWORD)pChainInfo, dwNumExts);
break;
}
pExt = (EXTENSION *)pExt->pNextExt;
}
}
else {
//? Search for Chain region. Chain region doesn''t have the ROMSIGNATURE set
DWORD? dwRegionStart = g_BINRegionInfo.Region[nCount].dwRegionStart;
DWORD? dwSig = *(LPDWORD) OEMMapMemAddr(dwRegionStart, dwRegionStart + ROM_SIGNATURE_OFFSET);

if ( dwSig != ROM_SIGNATURE) {
//? It is the chain
dwChainStart = dwRegionStart;
dwChainLength = g_BINRegionInfo.Region[nCount].dwRegionLength;
EdbgOutputDebugString("Found the Chain region: StartAddress: 0x%X; Length: 0x%X\n", dwChainStart, dwChainLength);
}
}
}

// nk.exe and an extension pointer? 這個(gè)是什么意思，就是說nk.exe　包含一個(gè)擴(kuò)展point是派什么用處的，那位知道告訴我


感覺是一個(gè)是bootlaod時(shí)的概念，一個(gè)是運(yùn)行是的概念
bootlaoder時(shí)　：通過OEMMultiBINNotify　獲得的信息來進(jìn)行下載等應(yīng)用

運(yùn)行時(shí)，是根據(jù)config.bib中CHAIN的關(guān)于regions的信息,通過InitRomChain　來把他串起來，



三.toc block ,是和nand boot有關(guān)的東西

typedef struct _TOC {
DWORD? ? ? ? ? ? ? dwSignature;
// How to boot the images in this TOC.
// This could be moved into the image descriptor if desired,
// but I prefer to conserve space.
BOOT_CFG? ? ? ? ? ? BootCfg;

// Array of Image Descriptors.
IMAGE_DESCRIPTOR? ? id[MAX_TOC_DESCRIPTORS];

//? ? UCHAR Pad[12];? ? ? // align on SECTOR_SIZE
CHAININFO? ? ? ? ? chainInfo;
} TOC, *PTOC;? ? ? ? ? // 512 bytes


typedef struct _IMAGE_DESCRIPTOR {

// File version info
DWORD dwVersion;? ? ? ? ? ? ? ? ? ? // e.g: build number
DWORD dwSignature;? ? ? ? ? ? ? ? ? // e.g: "EBOT", "CFSH", etc
UCHAR ucString[IMAGE_STRING_LEN];? // e.g: "PocketPC_2002"

DWORD dwImageType;? ? ? // IMAGE_TYPE_ flags
DWORD dwTtlSectors;? ? // TTL image size in sectors.
// We store size in sectors instead of bytes
// to simplify sector reads in Nboot.

DWORD dwLoadAddress;? ? // Virtual address to load image (ImageStart)
DWORD dwJumpAddress;? ? // Virtual address to jump (StartAddress/LaunchAddr)

// This array equates to a sector-based MXIP MultiBINInfo in blcommon.
// Unused entries are zeroed.
// You could chain image descriptors if needed.
SG_SECTOR sgList[MAX_SG_SECTORS];

// BinFS support to load nk region only
//struct
//{
ULONG dwStoreOffset;? ? // byte offset - not needed - remove!
//ULONG RunAddress;? ? // nk dwRegionStart address
//ULONG Length;? ? ? ? // nk dwRegionLength in bytes
//ULONG LaunchAddress;? // nk dwLaunchAddr
//} NKRegion;

} IMAGE_DESCRIPTOR, *PIMAGE_DESCRIPTOR;

這些信息被寫入block 1,
為nboot啟動(dòng)　nk,或 eboot提供信息的

總結(jié)

以上是生活随笔為你收集整理的关于mult-xip bin的一些资料整理的全部內(nèi)容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網(wǎng)站內(nèi)容還不錯(cuò)，歡迎將生活随笔推薦給好友。