FreeCalypso > hg > fc-magnetite
view cdg3/sap/tra.pdf @ 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 | c15047b3d00d |
children |
line wrap: on
line source
;******************************************************************************** ;*** File : tra.pdf ;*** Creation : Wed Mar 11 09:58:53 CST 2009 ;*** XSLT Processor : Apache Software Foundation / http://xml.apache.org/xalan-j / supports XSLT-Ver: 1 ;*** Copyright : (c) Texas Instruments AG, Berlin Germany 2002 ;******************************************************************************** ;*** Document Type : Service Access Point Specification ;*** Document Name : tra ;*** Document No. : 8411.106.98.101 ;*** Document Date : 2002-06-10 ;*** Document Status: BEING_PROCESSED ;*** Document Author: TVO ;******************************************************************************** PRAGMA SRC_FILE_TIME "Thu Nov 29 09:55:46 2007" PRAGMA LAST_MODIFIED "2002-06-10" PRAGMA ID_AND_VERSION "8411.106.98.101" VALTAB VAL_entity_name VAL 6 TRA_ENTITY_NAME_LEN "Max name length" VALTAB VAL_ack_flg VAL 0 TRA_ACK "acknowledged" VAL 1 TRA_NAK "not acknowledged" VALTAB VAL_dti_direction VAL 0 TRA_DTI_NORMAL "DTI used normally" VAL 1 TRA_DTI_INVERTED "DTI is inverted" VALTAB VAL_dti_conn VAL 0 TRA_CONNECT_DTI "Connect DTI to TRA" VAL 1 TRA_DISCONNECT_DTI "Connect DTI to upper layer" VAR entity_name "name of an neighbour entity" B VAL @p_tra - VAL_entity_name@ VAR ack_flg "acknowledge flag" B VAL @p_tra - VAL_ack_flg@ VAR link_id "link identifier" L VAR dti_direction "DTI direction" B VAL @p_tra - VAL_dti_direction@ VAR dti_conn "DTI connect" B VAL @p_tra - VAL_dti_conn@ ; TRA_ACTIVATE_REQ 0x80000019 ; TRA_ACTIVATE_CNF 0x80004019 ; TRA_DEACTIVATE_REQ 0x80010019 ; TRA_DEACTIVATE_CNF 0x80014019 ; TRA_DTI_REQ 0x80020019 ; TRA_DTI_CNF 0x80024019 ; TRA_DTI_IND 0x80034019 PRIM TRA_ACTIVATE_REQ 0x80000019 { } PRIM TRA_ACTIVATE_CNF 0x80004019 { ack_flg ; acknowledge flag } PRIM TRA_DEACTIVATE_REQ 0x80010019 { } PRIM TRA_DEACTIVATE_CNF 0x80014019 { } PRIM TRA_DTI_REQ 0x80020019 { dti_conn ; DTI connect link_id ; Link identifier of DTI entity_name [TRA_ENTITY_NAME_LEN] ; Communication entity name dti_direction ; DTI direction } PRIM TRA_DTI_CNF 0x80024019 { dti_conn ; DTI connect link_id ; Link identifier } PRIM TRA_DTI_IND 0x80034019 { link_id ; link identifier }