OMAP-L138_FlashAndBootUtils_2_29.tar.gz_FlashAndBootUtils_omap_o

/*************************************************************** * TI OMAP-L138 AIS Utilities * * (C) 2009-2010 Texas Instruments, Inc. * * * ***************************************************************/ This directory contains the source and build files for various utilities associated with booting flashing the OMAP-L138 SoC device. These utilities include HexAIS - Command-line AIS generation utility for non-secure OMAP-L138 devices UartHost - GUI application to boot non-secure AIS images over the serial port Running ======= These applications are built on the Microsoft's .Net framework. To use them, you must run them on a system that has the Microsoft .Net framework v3.5 installed. Alternatively, you can run them using the open-source Mono framework v2.4 or later. This may allow the applications to be run under Linux, since Mono exists and runs on that platform. NOTE: On windows, using the mono framework requires you to use the mono executable. With Mono in your path, the usage is as follows: mono <ApplicationName> <ApplicationParams> If the mono command is left off, the Microsoft framework will be used instead. HexAIS tool =========== The HexAIS and tool relies on its input parameters to be provided in INI files, example of which are included in the package. The ini files are processed in order and are primarily used to specify what AIS Function Execute commands you want to use to initialize the system. The comments in the INI file themselves provide a rough documentation. The tools have a number of options that can be specified on the command line. You can run the program with the -h option to see the help screen for each program. Command Syntax ============== HexAIS_OMAP-L138 [Options] [Input File Names] <Option> can be any of the following: -h Show this help screen. -entrypoint <Addr> Force specified entry point for AIS boot image. -ini <INI file name> Specify the ini file (default is OMAP-L138.ini). -otype <Output Type> Specify type of output file, from following:. binary Create a binary AIS file (.bin), default. carray Create a text file with AIS data in a C array (.c). srecord@addr Create a Motorola S-record format (.srec) at addr. text Create a text file with AIS data as ASCII text (.txt). -o <Output File Name> Explicitly specify the output filename. Default is input file name with extension based on output type. Input files (ELF or COFF object files OR Binary files) can be supplied on the command line or via the INI file. Binary files must be supplied with a load address, so they are specified in the following manner: <Binary File Name>@<Hex Load Address> It is recommended to use the INI file syntax for placing and including files since that provides greater flexibility (see below). Complete INI Syntax =================== The INI file consists of a collection of INI sections. Except for the [General] sections, which describe configuration information for the AIS file, the INI sections are processed in order and result in contents being added to the generated AIS output. Each INI section contains a collection of fields which are described below: Configuration ------------- [GENERAL] ; Can be 8 or 16 - used in emifa (NOR boot mode) busWidth=8 ; SPIMASTER,I2CMASTER,EMIFA,NAND,EMAC,UART,PCI,HPI,USB,MMC_SD,VLYNQ,RAW BootMode=Specify boot mode (typically use NONE). Some boot modes can require certain extra information beyond the actual AIS data. The tools may support generating this information depending on the boot mode selection. ; TRUE/ON or FALSE/OFF seqReadEn=Specify that sequential read should be used for I2C or SPI master modes. This is equivalent to using the [AIS_SeqReadEnable] section (see below). Include a file -------------- The INPUTFILE section allows including a binary or object file into the AIS boot image. The result of this INI section will be one or more AIS SectionLoad or EncryptedSectionLoad commands inserted into the AIS output. Note that input files can be specified on the command line, but using individual [INPUTFILE] sections offer more control over placement and content. [INPUTFILE] FILENAME=Filename of the binary or object file to include in the AIS iamge LOADADDRESS=Address to which file contents are loaded. If specified, input file is treated as a binary file. For object files, the load address for loadable sections is embedded in the object file itself. ENTRYPOINTADDRESS=Allows specifying the entry point for this module. This is typically used with binary files since object files embed the entry point. USEENTRYPOINT=Set to YES or TRUE to ensure that the entrypoint is taken from this input file for the JUMP_CLOSE command Insert ROM Function Calls (AIS Function Execute) ------------------------------------------------ These INI sections are used to insert specific AIS Function Execute commands into the AIS output. ; This section allows setting the PLL0 system clock with a ; specified multiplier and divider as shown. The clock source ; can also be chosen for internal or external. ; |------24|------16|-------8|-------0| ; PLL0CFG0: | CLKMODE| PLLM | PREDIV | POSTDIV| ; PLL0CFG1: | RSVD | PLLDIV1| PLLDIV3| PLLDIV7| [PLL0CONFIG] PLL0CFG0= PLL0CFG1= ; This section allows setting up the PLL1. Usually this will ; take place as part of the EMIF3a DDR setup. The format of ; the input args is as follows: ; |------24|------16|-------8|-------0| ; PLL1CFG0: | PLLM| POSTDIV| PLLDIV1| PLLDIV2| ; PLL1CFG1: | RSVD | PLLDIV3| [PLL1CONFIG] PLL1CFG0= PLL1CFG1= ; This section lets us configure the peripheral interface ; of the current booting peripheral (I2C, SPI, or UART). ; Use with caution. The format of the PERIPHCLKCFG field ; is as follows: ; SPI: |------24|------16|-------8|-------0| ; | RSVD |PRESCALE| ; ; I2C: |------24|------16|-------8|-------0| ; | RSVD |PRESCALE| CLKL | CLKH | ; ; UART: |------24|------16|-------8|-------0| ; | RSVD | OSR | DLH | DLL | [PERIPHCLKCFG] PERIPHCLKCFG= ; This section can be used to configure the PLL1 and the EMIF3a registers ; for starting the DDR2 interface. ; See PLL1CONFIG section for the format of the PLL1CFG fields. ; |------24|------16|-------8|-------0| ; PLL1CFG0: | PLL1CFG | ; PLL1CFG1: | PLL1CFG | ; DDRPHYC1R: | DDRPHYC1R | ; SDCR: | SDCR | ; SDTIMR: | SDTIMR | ; SDTIMR2: | SDTIMR2 | ; SDRCR: | SDRCR | ; CLK2XSRC: | CLK2XSRC | [EMIF3DDR] PLL1CFG0= PLL1CFG1= DDRPHYC1R= SDCR= SDTIMR= SDTIMR2= SDRCR= CLK2XSRC= ; This section can be used to configure the EMIFA to use ; CS0 as an SDRAM interface. The fields required to do this ; are given below.