TI DM3730 EBOOT analysis (I)

The main function of EBOOT calls BootLoaderMain (). Microsoft has fixed it. The development of EBoot mainly improves several functions called by BootLoaderMain.

1. relocate globals to RAM
KernelRelocate (pTOC)

2. Init debug support. We can use OEMWriteDebugString afterward.
OEMDebugInit ()

3. initialize platform (clock, drivers, transports, etc)

OEMPlatformInit ()

 

4. call OEM specific pre-download function

OEMPreDownload

5 (1). download image
If (! DownloadImage (& dwImageStart, & dwImageLength, & dwLaunchAddr ))

5 (2). final call to launch the image. never returned
OEMLaunch (dwImageStart, dwImageLength, dwLaunchAddr, (const ROMHDR *) dwpToc );

OEMPlatformInit initialization platform, there is nothing to say, because 35 series and 37 series BSP are integrated, so first judge the CPU model, and then initialize the corresponding processing.

 

Let's take A look at the OEMPreDownload function. The first three tasks are called PreDownload to prepare A, B, and C.

A. BLReserveBootBlocks. Check the implementation function. Nothing to do... it's so shameless... let's continue.

BOOL BLReserveBootBlocks (
BOOT_CFG * pBootCfg
)
{
UNREFERENCED_PARAMETER (pBootCfg );
// Nothing to do...
Return TRUE;
}

B. BLReadBootCfg (& g_bootCfg): Read the configuration parameters of boot. If reading fails, load the default value. You can use the default value if you are not familiar with the configuration information.

C. BLConfigureFlashPartitions (FALSE); this function is important. Let's take a look at FMD_Init, BP_Init, BP_OpenPartition, and BP_LowLevelFormat.

Familiar functions. For a brief explanation, we mainly obtain information about flash memory partitions, boot, OS, and file system partitions. If there is no such information, flash memory will be formatted here,

It is dangerous to generate new partition information. If one attempt to read the information fails, it will all be formatted. Oh, the system information is gone. Be careful when using this information.