From: Ash C. <ash...@gm...> - 2013-06-26 19:16:24
|
In general, SPL only initializes hardware for devices it might use to boot. A number of defines in the code #CONFIG_SPL_*_SUPPORT configure what hardware blocks actually get enabled. Also, you might find the control flow in arch/arm/cpu/armv7/omap3/board.c void s_init(void) useful. --Ash On Thu, Jun 20, 2013 at 7:22 AM, Andy Walls <an...@si...> wrote: > Hi, > > I'm trying to set the PADCONF registers in the U-Boot SPL sensibly, to > avoid any floating inputs on the Overo's OMAP and on my external level > converters. > > I'm using most of the pins on the Tobi's 40 pin header: > SPI1 (all pins, as a master) > GPIO_114 (input) > UART1 (both Tx and Rx) > GPIO_31 (input) > GPIO_186 (input) > GPIO_10 (input) > GPIO_170 (output) > GPIO_163 (output) > PWM11 (event input) > PWM10 (output) > GPIO_147 (output) > GPIO_144 (output) > > Which of the functional blocks (UART1, SPI1, GPTimer10, GPTimer11, > GPIOn) are activated by the U-boot SPL (a.k.a. MLO)? > > Reading the source checked out using yocto, I'm pretty sure UART1 is > initialized in the SPL. > > If something like PWM10 or GPIO_170 isn't driving a line because the > GPTimers or GPIO blocks are powered down or not configured as outputs, > then I need to set the PADCONFs differently to prevent float. > > Thanks, > Andy > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |