FreeCalypso > hg > fc-magnetite
view src/cs/riviera/rvm/rvm_ext_priorities.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
/************************************************************************************* * * * Name rvm_ext_priorities.h * * * * Function this file priorities defintitions for basic SWEs * * It includes a file * * * * Version 0.1 * * * * Date Modification * * ------------------------------------ * * 10/11/2000 Create * * * * Author Cristian Livadiotti (c-livadiotti@ti.com) * * * * (C) Copyright 2000 by Texas Instruments Incorporated, All Rights Reserved * * * * --------------------------------------------------------------------------------- * * * * History: * * * * 10/18/2001 - Updated for R2D by Christophe Favergeon * * * *************************************************************************************/ #ifndef __RVM_EXT_PRIORITIES_H_ #define __RVM_EXT_PRIORITIES_H_ /* PRIORITIES SETTING: */ /* All user priority should be set under 250: */ /* Higher values are reserved */ /* ** External Priority definitions ** Note that RVM_EXPL_TASK_PRIORITY is used for testing purpose (refer to RTEST). ** Hence, users have to make sure that such a priority is lower than the software ** entity under test, not to starve the system. */ #define RVM_EXPL_TASK_PRIORITY (242) #define RVM_RGUI_TASK_PRIORITY (240) #define RVM_R2D_TASK_PRIORITY (239) #define RVM_DEV1_TASK_PRIORITY (245) #define RVM_DEV2_TASK_PRIORITY (245) #define RVM_DEV3_TASK_PRIORITY (245) #define RVM_UVM_TASK_PRIORITY (245) #define RVM_BTU_TASK_PRIORITY (248) /* was 240 */ #define RVM_BTUI_TASK_PRIORITY (240) #define RVM_BTA_TASK_PRIORITY (248) /* rl: was 200 */ #define RVM_BTH_TASK_PRIORITY (200) #endif /* __RVM_EXT_PRIORITIES_H_ */