106 lines
4.4 KiB
C
106 lines
4.4 KiB
C
/****************************************************************************
|
|
* config/launchxl-tms57004/src/moxart_boot.c
|
|
*
|
|
* Copyright (C) 2015 Gregory Nutt. All rights reserved.
|
|
* Author: Gregory Nutt <gnutt@nuttx.org>
|
|
*
|
|
* Redistribution and use in source and binary forms, with or without
|
|
* modification, are permitted provided that the following conditions
|
|
* are met:
|
|
*
|
|
* 1. Redistributions of source code must retain the above copyright
|
|
* notice, this list of conditions and the following disclaimer.
|
|
* 2. Redistributions in binary form must reproduce the above copyright
|
|
* notice, this list of conditions and the following disclaimer in
|
|
* the documentation and/or other materials provided with the
|
|
* distribution.
|
|
* 3. Neither the name NuttX nor the names of its contributors may be
|
|
* used to endorse or promote products derived from this software
|
|
* without specific prior written permission.
|
|
*
|
|
* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
|
|
* "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
|
|
* LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
|
|
* FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
|
|
* COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
|
|
* INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
|
|
* BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
|
|
* OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
|
|
* AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
|
|
* ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
|
* POSSIBILITY OF SUCH DAMAGE.
|
|
*
|
|
****************************************************************************/
|
|
|
|
/****************************************************************************
|
|
* Included Files
|
|
****************************************************************************/
|
|
|
|
#include <nuttx/config.h>
|
|
|
|
#include <nuttx/board.h>
|
|
|
|
#include <arch/board/board.h>
|
|
|
|
#include "launchxl-tms57004.h"
|
|
|
|
/****************************************************************************
|
|
* Public Functions
|
|
****************************************************************************/
|
|
|
|
/****************************************************************************
|
|
* Name: tms570_boardinitialize
|
|
*
|
|
* Description:
|
|
* All TMS570 architectures must provide the following entry point. This
|
|
* function is called near the beginning of _start. This function is
|
|
* called after clocking has been configured but before caches have been
|
|
* enabled and before any devices have been initialized. .data/.bss
|
|
* memory may or may not have been initialized (see the "special
|
|
* precautions" below).
|
|
*
|
|
* This function must perform low level initialization including
|
|
*
|
|
* - Initialization of board-specific memory resources (e.g., SDRAM)
|
|
* - Configuration of board specific resources (GPIOs, LEDs, etc).
|
|
* - Setup of the console UART. This UART done early so that the serial
|
|
* console is available for debugging very early in the boot sequence.
|
|
*
|
|
* Special precautions must be taken if .data/.bss lie in SRAM. in that
|
|
* case, the boot logic cannot initialize .data or .bss. The function
|
|
* must then:
|
|
*
|
|
* - Take precautions to assume that logic does not access any global
|
|
* data that might lie in SDRAM.
|
|
* - Call the function arm_data_initialize() as soon as SDRAM has been
|
|
* properly configured for use.
|
|
*
|
|
****************************************************************************/
|
|
|
|
void tms570_board_initialize(void)
|
|
{
|
|
}
|
|
|
|
/****************************************************************************
|
|
* Name: board_initialize
|
|
*
|
|
* Description:
|
|
* If CONFIG_BOARD_INITIALIZE is selected, then an additional
|
|
* initialization call will be performed in the boot-up sequence to a
|
|
* function called board_initialize(). board_initialize() will be
|
|
* called immediately after up_initialize() is called and just before the
|
|
* initial application is started. This additional initialization phase
|
|
* may be used, for example, to initialize board-specific device drivers.
|
|
*
|
|
****************************************************************************/
|
|
|
|
#ifdef CONFIG_BOARD_INITIALIZE
|
|
void board_initialize(void)
|
|
{
|
|
/* Perform application level board initialization */
|
|
|
|
tms570_bringup();
|
|
}
|
|
#endif
|