AMiRo-OS

* You should have received a copy of the GNU General Public License along with OpenBLT.

* If not, see <http://www.gnu.org/licenses/>.

*

* proprietary components. The exception text is included at the bottom of the license

* file <license.html>.

* \endinternal

****************************************************************************************/

#ifndef BLT_CONF_H

*   C P U   D R I V E R   C O N F I G U R A T I O N

****************************************************************************************/

/* To properly initialize the baudrate clocks of the communication interface, typically

 * needed. Set these through configurables BOOT_CPU_XTAL_SPEED_KHZ and

 * BOOT_CPU_SYSTEM_SPEED_KHZ, respectively. To enable data exchange with the host that is

 * big endian mode.

 * Set BOOT_CPU_USER_PROGRAM_START_HOOK to 1 if you would like a hook function to be

 * called the moment the user program is about to be started. This could be used to

 * de-initialize application specific parts, for example to stop blinking an LED, etc.

/** \brief Frequency of the external crystal oscillator. */

#define BOOT_CPU_XTAL_SPEED_KHZ         (8000)

/** \brief Desired system speed. */

 * have to be controlled by this bootloader. Additionally the bootloader should be able

 * to send program code of user programs for other devices.

 * Make sure that one of the communication interfaces is the gateway!

/** \brief Bootloader of main device. */

#define BOOTLOADER_OF_MAIN_DEVICE       (0)

/****************************************************************************************

*   C O M M U N I C A T I O N   I N T E R F A C E   C O N F I G U R A T I O N

****************************************************************************************/

 * configurable to 1. Configurable BOOT_COM_CAN_BAUDRATE selects the communication speed

 * message identifier for sending data from the target to the host is configured with

 * BOOT_COM_CAN_TXMSG_ID. The one for receiving data from the host is configured with

 * BOOT_COM_CAN_RX_MAX_DATA, respectively. It is common for a microcontroller to have more

 * than 1 CAN controller on board. The zero-based BOOT_COM_CAN_CHANNEL_INDEX selects the

 * CAN controller channel.

 */

/** \brief Enable/disable CAN transport layer. */

#define BOOT_COM_CAN_ENABLE             (1)

/** \brief Configure the desired CAN baudrate. */

/** \brief Configure CAN message ID target->host. */

/** \brief Configure number of bytes in the target->host CAN message. */

#define BOOT_COM_CAN_TX_MAX_DATA        (255)

/** \brief Configure CAN message ID host->target. */

/** \brief Configure number of bytes in the host->target CAN message. */

#define BOOT_COM_CAN_RX_MAX_DATA        (255)

/** \brief Select the desired CAN peripheral as a zero based index. */

#define BOOT_COM_CAN_CHANNEL_INDEX      (0)

 * configurable to 1. Configurable BOOT_COM_UART_BAUDRATE selects the communication speed

 * respectively. It is common for a microcontroller to have more than 1 UART interface

 * on board. The zero-based BOOT_COM_UART_CHANNEL_INDEX selects the UART interface.

 */

/** \brief Enable/disable UART transport layer. */

#define BOOT_COM_UART_ENABLE            (1)

/** \brief Configure the desired communication speed. */

/** \brief Configure number of bytes in the target->host data packet. */

#define BOOT_COM_UART_TX_MAX_DATA       (255)

/** \brief Configure number of bytes in the host->target data packet. */

*   F I L E   S Y S T E M   I N T E R F A C E   C O N F I G U R A T I O N

****************************************************************************************/

/* The file system interface is selected by setting the BOOT_FILE_SYS_ENABLE configurable

 * together with one of the remote communication interfaces such as UART, CAN or USB.

 *

 * Set BOOT_FILE_LOGGING_ENABLE to 1 if you would like log messages to be created during

 * additional information on the error cause.

 *

 * Set BOOT_FILE_STARTED_HOOK_ENABLE to 1 if you would like to be informed when a new

 *

 * Set BOOT_FILE_COMPLETED_HOOK_ENABLE to 1 if you would like to be informed when a

 */

/** \brief Enable/disable support for firmware updates from a locally attached storage.*/

#define BOOT_FILE_SYS_ENABLE            (0)

/** \brief Enable/disable logging messages during firmware updates. */

#define BOOT_FILE_LOGGING_ENABLE        (1)

/** \brief Enable/disable a hook function that is called upon detection of an error. */

/** \brief Enable/disable a hook function that is called at the start of the update. */

/** \brief Enable/disable a hook function that is called at the end of the update. */

/****************************************************************************************

*   B A C K D O O R   E N T R Y   C O N F I G U R A T I O N

****************************************************************************************/

/* It is possible to implement an application specific method to force the bootloader to

 * stay active after a reset. Such a backdoor entry into the bootloader is desired in

 * reactivate the bootloader. By enabling these hook functions, the application can

 * implement the backdoor, which overrides the default backdoor entry that is programmed

 * into the bootloader. When desired for security purposes, these hook functions can

*   S E E D / K E Y   S E C U R I T Y   C O N F I G U R A T I O N

****************************************************************************************/

/* A security mechanism can be enabled in the bootloader's XCP module by setting configu-

 * During the unlock sequence, Microboot requests a seed from the bootloader, which is in

 * bootloader then verifies this key to determine if programming and erase operations are

 * permitted.

 * After enabling this feature the hook functions XcpGetSeedHook() and XcpVerifyKeyHook()