Running PSP Components on OMAP-L137

Booting U-Boot

U-Boot is an open source boot loader and is responsible for booting the Linux kernel.

Connect a serial cable from the serial port on the EVM to the COM port on the host machine. Set up the serial terminal software as described in Booting the EVM out of the box.
Note: Boot images may not have been pre-flashed on the EVM for all boot modes. In this case, follow the procedures in Flashing images to flash the required boot images.

Booting from SPI Flash

• Set the SW2 switch on the DSK board as follows. (X indicates the setting is 'don't care')

Pin#	7	2	1	0	3
Position	0	1	0	1	X

Booting from NAND Flash

• Set the SW2 switch on the DSK board as follows. (X indicates the setting is 'don't care')

Pin#	7	2	1	0	3
Position	0	1	1	1	X

On the User Interface card, set the SW1 switch as follows:

Pin #	1	2	3	4
Position	1	0	1	1

Flashing images to SPI flash using Serial Flasher

The following software supports the OMAP-L137 families of devices.

This package contains a set of utilities running from the command-line on Windows for flashing the various flash types on the OMAP-L137 EVM via the serial port.

The Serial Flashing Host Utility executable is called sfh_OMAP-L137.exe.

These programs each encapsulate a distinct binary UBL which is transferred via the UART. This implies that the chip must be operating in the UART boot mode, showing the BOOTME prompt.

Obtaining the flashing software

The latest source code and binaries are present in package here under host-tools.

Compiling

Please refer here for instructions to build the flashing software.

Running

Under Windows This utility can be run from the command line under Windows with the .Net Framework 2.0 or later installed through the following steps:

1. Set the boot pins of the EVM to UART2 boot mode. This is done by setting boot switches on the OMAP-L137 or DA830 EVM according to the following table:
   Note: DA830 and DA830 Wi-Fi EVMs use the 'revisions after B' configuration
   For all revisions after B:

   Pin#	7	2	1	0	3
   Position	ON	OFF	ON	OFF	OFF

   For revisions A and B:

   Pin#	7	2	1	0	3
   Position	ON	OFF	ON	OFF	ON

2. Connect a serial cable from the host computer to the OMAP-L137 or DA830 EVM. Note that for OMAPL137_v1 the host computer must be able to run at a UART baud rate of 230400.
3. Test your UART connection by opening HyperTerminal and connecting to the correct COM port at 115200 (or 230400). When the reset button is pressed on the EVM, the words "BOOTME" should appear on the terminal. If not, recheck the cable connection, baud settings, and boot pins of the EVM. Please note that many PC serial ports do not support a baud rate of 230400. In these cases, a USB->Serial adapter should be used.
4. Disconnect from HyperTerminal.
5. Open a command prompt on the host computer and change directory to where the flashing utility was saved (ex. c:\flasher).
6. Run the flashing utility with this command:
   • C:\flasher>sfh_OMAP-L137.exe [options]
7. Reset the board

Under Linux

The serial flasher can be run on a Linux machine with the latest open-source Mono Framework installed. The steps are identical to the Windows environment except the command:

• mono ./sfh_OMAP-L137.exe [options]

Serial Flasher Options

There are four modes for using the serial flasher:

1. Erase the target flash type - This will erase the entire contents of the flash.
   • C:\flasher>sfh_OMAP-L137.exe -erase
2. Flash the memory with a single application image - This will place an application image at address 0x0 of the flash.
   • C:\flasher>sfh_OMAP-L137.exe -flash_noubl <binary application file>
3. Flash the memory with a UBL and application image placing the UBL at address 0x0 and an application image, such as u-boot, at address 0x10000 by default. This is used for the AM1707 device.
   • C:\flasher>sfh_OMAP-L137.exe -flash <UBL binary file> <binary application file>
   • Note: If one of the following target types is specified on the command line, the corresponding load addresses are used by the utility:
     • targetType = DA830: DSP+ARM UBL placed as 0x0 and application image placed at 0x8000 (allows for separate DSP image load)
     • targetType = DA830_pa_boot: DSP+ARM UBL combined with DSP image placed at 0x0 and application image placed at 0xA0000
     • targetType = DA830WIFI: DSP+ARM UBL placed as 0x0 and application image placed at 0x8000
4. Flash the memory with a DSP UBL, ARM UBL, and application image - This will place a DSP AIS file at address 0x0 of the flash, an ARM UBL at address 0x2000, and an application image, such as u-boot, at address 0x8000. This is used for the OMAPL137_v1 and OMAPL137_v2 devices.
   • C:\flasher>sfh_OMAP-L137.exe -flash_dsp <DSP UBL AIS file> <ARM UBL binary file> <binary application file>

Additional options are shown below:

  -targetType         : Specifies exact target type within OMAP-L137 (OMAPL137_v2 [default], OMAPL137_v1, C6747, AM1707) 
                        or DA830 (DA830, DA830_pa_boot, DA830WIFI) families
  -flashType          : Specifies exact flash type (default SPI_MEM)
  -p <COM PORT NAME>  : Allows specifying com port other than default 'COM1' or '/dev/ttyS0'.
  -h                  : Show help text.
  -v                  : See verbose output from OMAP-L137.
  -baud <BAUD RATE>   : Allows specifying baud rate other than default (115200)
  -APPStartAddr       : Changes entry point of application (default 0xC1080000)
  -APPLoadAddr        : Changes load address of application (default 0xC1080000)
  -APPFlashBlock      : Changes the block to flash the image into (only for -flash_noubl and -flash modes)

Once any command is run, the "Waiting for BOOTME..." prompt shows. Power cycle the board or press the reset button to continue.

Please note, for the AM1707, the ARM UBL must come from the /gnu/ubl/ directory of this release (i.e. ubl_AM1707_SPI_MEM.bin). The serial flasher is not compatible with the UBLs found in the PSP release.

For the OMAPL137_v1 and OMAPL137_v2, the DSP and ARM UBLs should come from the PSP release directory.

Restoring the OMAP-L137 EVM SPI Flash

If the contents of the OMAP-L137 SPI flash become corrupted, they can be restored through the following steps:

1. Set the boot pins to UART2 boot mode. This is done by setting the boot switches on the OMAP-L137 EVM according to the following table:

   Pin#	7	2	1	0	3
   Position	ON	OFF	ON	OFF	OFF

2. Obtain the DSP UBL AIS file (dsp-spi-ais.bin), the ARM UBL binary file (ubl-spi.bin), and the u-boot binary file (u-boot.bin).
   • Pre-built images are located in the "images" directory of the PSP installation
3. Run the following command to flash the UBL and u-boot binary files:
   • C:\flasher>sfh_OMAP-L137.exe -spiflash_dsp <DSP UBL AIS file> <ARM UBL binary file> <u-boot binary file>
4. Reset the board
5. After the UBL and u-boot files have been flashed, set the boot pins to SPI0 boot mode and reboot the board. This is done by setting the boot switches on the OMAP-L137 EVM according to the following table:

   Pin#	7	2	1	0	3
   Position	OFF	ON	OFF	ON	OFF

6. One u-boot has loaded, follow the instructions in the Getting Started Guide to copy the Linux kernel and filesystem to the SPI flash.
   • Updating the Kernel Image

Restoring the DA830 or DA830 Wi-Fi EVMs SPI Flash

If the contents of the DA830 or DA830 Wi-Fi EVMs SPI flash become corrupted, they can be restored through the following steps:

1. Set the boot pins to UART2 boot mode. This is done by setting the boot switches on the EVM according to the following table:

   Pin#	7	2	1	0	3
   Position	ON	OFF	ON	OFF	OFF

2. Obtain the DSP+ARM UBL file and the u-boot binary file.
3. Run the following command to flash the UBL and u-boot binary files:
   • da830-evm
   C:\flasher>sfh_OMAP-L137.exe -flash <DSP+ARM UBL file> <u-boot binary file> -targetType <DA830> -appFlashBlock <48>
   • da830-WiFi
   C:\flasher>sfh_OMAP-L137.exe -flash <DSP+ARM UBL file> <u-boot binary file> -targetType <DA830WIFI>
4. Reset the board
5. After the UBL and u-boot files have been flashed, set the boot pins to SPI0 boot mode and reboot the board. This is done by setting the boot switches on the EVM according to the following table:

   Pin#	7	2	1	0	3
   Position	OFF	ON	OFF	ON	OFF

6. Once u-boot has loaded, follow the instructions in the Getting Started Guide to copy the Linux kernel and filesystem to the SPI flash.
   • Updating the Kernel Image

Flashing images to SPI Flash using CCS

1. Setup the EVM in "emulation debug" mode by setting SW2 switch as follows:
   
   

   For EVM revisions A and B:

   Pin #	7	2	1	0	3
   Position	1	1	1	1	1

   
   
   

   For EVM revisions after B:

   Pin #	7	2	1	0	3
   Position	1	1	1	1	0

   
   

2. Start CCStudio and connect to the DSP. Once done, connect to the ARM. Ensure that you have the latest DSP GEL file from Spectrum Digital Support site correctly specified.
3. Load the SPI flasher tool on to the ARM. You can either use the pre-built binary shipped in the images/utils/da830-evm/ or images/utils/da830-wifi/ directory of the PSP installation (DA830_spiWriter.out) according to board getting used, or you can build your own by following the steps in the section on Rebuilding the SPI Flash writer
4. Run the SPI flasher program. You will be prompted for the input file paths. Two files are required: DSP+ARM AIS and U-Boot.
   • To burn these two files, When prompted for a dspais file name, provide the path to pa_ubl-spi.bin file. A pre-built image is located in the images/boot-strap/da830-evm/ or images/boot-strap/da830-wifi/directory of the PSP installation according to board getting used. When prompted for a u-boot file name, provide the path to the u-boot.bin file. A pre-built image is located in the images/u-boot/da830-wifi/ or images/u-boot/da830-evm/ directory of the PSP installation according to board getting used.
5. Once the SPI flash has been written with the all the required files, disconnect CCStudio and power off the EVM. Proceed to Booting from SPI Flash.