FreeCalypso > hg > fc-magnetite
view src/condat2/frame/config/gprsinit.c @ 600:8f50b202e81f
board preprocessor conditionals: prep for more FC hw in the future
This change eliminates the CONFIG_TARGET_FCDEV3B preprocessor symbol and
all preprocessor conditionals throughout the code base that tested for it,
replacing them with CONFIG_TARGET_FCFAM or CONFIG_TARGET_FCMODEM. These
new symbols are specified as follows:
CONFIG_TARGET_FCFAM is intended to cover all hardware designs created by
Mother Mychaela under the FreeCalypso trademark. This family will include
modem products (repackagings of the FCDEV3B, possibly with RFFE or even
RF transceiver changes), and also my desired FreeCalypso handset product.
CONFIG_TARGET_FCMODEM is intended to cover all FreeCalypso modem products
(which will be firmware-compatible with the FCDEV3B if they use TI Rita
transceiver, or will require a different fw build if we switch to one of
Silabs Aero transceivers), but not the handset product. Right now this
CONFIG_TARGET_FCMODEM preprocessor symbol is used to conditionalize
everything dealing with MCSI.
At the present moment the future of FC hardware evolution is still unknown:
it is not known whether we will ever have any beyond-FCDEV3B hardware at all
(contingent on uncertain funding), and if we do produce further FC hardware
designs, it is not known whether they will retain the same FIC modem core
(triband), if we are going to have a quadband design that still retains the
classic Rita transceiver, or if we are going to switch to Silabs Aero II
or some other transceiver. If we produce a quadband modem that still uses
Rita, it will run exactly the same fw as the FCDEV3B thanks to the way we
define TSPACT signals for the RF_FAM=12 && CONFIG_TARGET_FCFAM combination,
and the current fcdev3b build target will be renamed to fcmodem. OTOH, if
that putative quadband modem will be Aero-based, then it will require a
different fw build target, the fcdev3b target will stay as it is, and the
two targets will both define CONFIG_TARGET_FCFAM and CONFIG_TARGET_FCMODEM,
but will have different RF_FAM numbers. But no matter which way we are
going to evolve, it is not right to have conditionals on CONFIG_TARGET_FCDEV3B
in places like ACI, and the present change clears the way for future
evolution.
author | Mychaela Falconia <falcon@freecalypso.org> |
---|---|
date | Mon, 01 Apr 2019 01:05:24 +0000 |
parents | 93999a60b835 |
children |
line wrap: on
line source
/* +----------------------------------------------------------------------------- | Project : | Modul : +----------------------------------------------------------------------------- | Copyright 2002 Texas Instruments Berlin, AG | All rights reserved. | | This file is confidential and a trade secret of Texas | Instruments Berlin, AG | The receipt of or possession of this file does not convey | any rights to reproduce or disclose its contents or to | manufacture, use, or sell anything it may describe, in | whole, or in part, without the specific written consent of | Texas Instruments Berlin, AG. +----------------------------------------------------------------------------- | Purpose : Nucleus Entry Function Application_Initialize() +----------------------------------------------------------------------------- */ #ifndef _TARGET_ #define NEW_ENTITY #endif /*==== INCLUDES ===================================================*/ #ifdef _TARGET_ #include "uart/serialswitch.h" #endif #include "nucleus.h" #include "typedefs.h" #include "os.h" #include "vsi.h" #include "os_types.h" #include "pcon.h" #include "p_mem.h" /*==== CONSTANTS ==================================================*/ /*==== TYPES ======================================================*/ /*==== EXTERMALS ==================================================*/ #ifndef _TARGET_ extern void GpInitTarget (void); extern void Cust_Init_Layer1 (void); extern void GpUnmaskInterrupts (void); extern void GpInitExternalDevices (void); #endif /*==== PROTOTYPES =================================================*/ short StartFrame (void); /*==== VARIABLES ==================================================*/ T_PCON_PROPERTIES *pcon = NULL; T_MEM_PROPERTIES *mem = NULL; /*==== FUNCTIONS ==================================================*/ #ifdef _TARGET_ void DummyCallback ( void ) { } #endif /* +--------------------------------------------------------------------+ | PROJECT : GSM-PS (6147) MODULE : GPRSINIT | | STATE : code ROUTINE : Application_Initialize | +--------------------------------------------------------------------+ PURPOSE : Main entry function for NUCLEUS */ /* * NOTE: Application_Initalize() must not be used when compiling for target, * because it is already defined in a TI lib (as of TI 5.1.1). */ #ifndef _TARGET_ void Application_Initialize (void *first_available_memory) { #ifdef _TARGET_ GpInitTarget (); Cust_Init_Layer1 (); GpInitExternalDevices (); SER_tr_Init ( 0, 2, DummyCallback ); #endif StartFrame(); #ifdef _TARGET_ GpUnmaskInterrupts (); #endif } #endif /* !_TARGET_ */ /* +----------------------------------------------------------------------+ | PROJECT : xxx MODULE : GPRSINIT | | STATE : code ROUTINE : InitializeApplication | +----------------------------------------------------------------------+ PURPOSE : General initialization function to be filled with application specific initializations. Function is called by the frame after creation of all tasks prior to the starting of the tasks. */ void InitializeApplication ( void ) { /* * It has to defined if the allocated partition memory shall be * initialized with a dedicated pattern. Select * ENABLE_PARTITON_INIT or DISABLE_PARTITON_INIT * and a pattern to be used for initialization */ #ifdef _TARGET_ vsi_m_init ( DISABLE_PARTITON_INIT, (char)0x00 ); #else vsi_m_init ( ENABLE_PARTITON_INIT, (char)0x00 ); #endif #ifdef _TARGET_ /* * The RTOS tick has to be set.Currently it can be set to * SYSTEM_TICK_TDMA_FRAME for the TDMA frame system tick of 4.615ms * or * SYSTEM_TICK_10_MS for the 10ms tick used for UMTS */ os_set_tick ( SYSTEM_TICK_TDMA_FRAME ); #endif }