view src/cs/services/cst/cus_cst.h @ 629:3231dd9b38c1

armio.c: make GPIOs 8 & 13 outputs driving 1 on all "classic" targets Calypso GPIOs 8 & 13 are pinmuxed with MCUEN1 & MCUEN2, respectively, and on powerup these pins are MCUEN, i.e., outputs driving 1. TI's code for C-Sample and earlier turns them into GPIOs configured as outputs also driving 1 - so far, so good - but TI's code for BOARD 41 (which covers D-Sample, Leonardo and all real world Calypso devices derived from the latter) switches them from MCUEN to GPIOs, but then leaves them as inputs. Given that the hardware powerup state of these two pins is outputs driving 1, every Calypso board design MUST be compatible with such driving; typically these GPIO signals will be either unused and unconnected or connected as outputs driving some peripheral. Turning these pins into GPIO inputs will result in floating inputs on every reasonably-wired board, thus I am convinced that this configuration is nothing but a bug on the part of whoever wrote this code at TI. This floating input bug had already been fixed earlier for GTA modem and FCDEV3B targets; the present change makes the fix unconditional for all "classic" targets. The newly affected targets are D-Sample, Leonardo, Tango and GTM900.
author Mychaela Falconia <falcon@freecalypso.org>
date Thu, 02 Jan 2020 05:38:26 +0000
parents 945cf7f506b2
children
line wrap: on
line source

/*
+--------------------------------------------------------------------+
| PROJECT : XXX                        SOURCE : CUS_CST.H            |
| AUTHOR  : XXX                        VERSION: 1.0                  |
| CREATED : 01.02.99                   STATE  : code                 |
+--------------------------------------------------------------------+

   MODULE  : CUS_CST

   PURPOSE : Custom dependent definitions for the CST entity of the
             mobile station.

             Use this header for definitions to integrate the protocol
             stack entity CST in your target system.
*/

#ifndef CUS_CST_H
#define CUS_CST_H


/*==== CONSTANTS ==================================================*/
/*
 * TIMER_VALUES
 *
 * Description :  The constants define the timer values for the CST
 *                timer TXXX depending on the various channel types
 *                and service access point identifiers.
 *
 *                If your target system uses other units please
 *                change the values.
 */

/*
 * Unit is 1 ms 
 */
#define T_RX_VALUE              1000
#define TICS_PER_DECIHOURS      (1000*60*6)


/*
 * MAX_CST_TIMER
 *
 * Description :  The constant define the number of timer available
 *                in the timer pool.
 */
#define MAX_CST_TIMER 4

/*
 * VERSION
 *
 * Description :  The constants define the type and the value of a
 *                version identification. The version is part of the
 *                monitor struct.
 */
#define T_VERSION   char
#define VERSION_CST  "CST 1.0"

/*
 * VSI_CALLER
 *
 * Description :  For multithread applications the constant VSI_CALLER
 *                must be defined to identify the calling thread of the
 *                VSI-Interface. This must be done correponding to the
 *                type of T_VSI_CALLER in VSI.H. The comma symbol is
 *                neccessary because the vsi-functions are called
 *                like this vsi_xxx (VSI_CALLER par2, par3 ...)
 */

#ifdef OPTION_MULTITHREAD
#define VSI_CALLER cst_handle,
#define VSI_CALLER_SINGLE cst_handle
#else
#define VSI_CALLER
#define VSI_CALLER_SINGLE
#endif

#endif // CUS_CST_H