FreeCalypso > hg > fc-magnetite
view src/cs/drivers/drv_app/fchg/fchg_func_i.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 | 0df0668f8bea |
children |
line wrap: on
line source
/* * Declarations of internal functions live here. */ #ifndef __FCHG_FUNC_I #define __FCHG_FUNC_I #include "fchg/fchg_messages.h" void pwr_init_discharge(void); void pwr_load_ffs_batt_table(void); void pwr_load_ffs_charging_config(void); void pwr_set_default_batt_table(void); void pwr_process_message(T_RV_HDR *msg_ptr); void pwr_process_adc(struct pwr_adc_ind_s *msg); void pwr_handle_timer(void); void pwr_charger_plug(void); void pwr_charger_unplug(void); void pwr_charge_start_req(void); void pwr_charge_stop_req(void); #endif /* include guard */