On 9/11/14, 12:06 PM, "Robert Nelson" <robertcnel...@gmail.com> wrote:

>On Thu, Sep 11, 2014 at 1:57 PM, Jason Kridner <jkrid...@gmail.com> wrote:
>>
>>
>> On Thursday, September 11, 2014 10:39:25 AM UTC-4, RobertCNelson wrote:
>>>
>>> On Thu, Sep 11, 2014 at 9:23 AM, Tom Rini <tom.r...@gmail.com> wrote:
>>> > On Friday, September 5, 2014 1:39:04 PM UTC-4, RobertCNelson wrote:
>>> >>
>>> >> On Fri, Sep 5, 2014 at 12:32 PM, Gerald Coley
>>><ger...@beagleboard.org>
>>> >> wrote:
>>> >> > SW is supposed to set it to 1.35V. Sounds like it got dropped
>>> >> > somewhere
>>> >> > because initially it did.. It was designed this way because when
>>>it
>>> >> > was
>>> >> > designed, the PMIC defaulted to 1.5V. Since the design there is a
>>> >> > TPS65217D
>>> >> > that was release later that supports the 1.35V initial setting.
>>> >>
>>> >> It should be set here:
>>> >>
>>> >>
>>> >>
>>> >> 
>>>http://git.denx.de/?p=u-boot.git;a=blob;f=board/ti/am335x/board.c;h=0739
>>>e6021a21e71d7d0f5c840b793ce7fdf98fae;hb=HEAD#l275
>>> >>
>>> >> 269                 /*
>>> >> 270                  * Increase USB current limit to 1300mA or
>>>1800mA
>>> >> and
>>> >> set
>>> >> 271                  * the MPU voltage controller as needed.
>>> >> 272                  */
>>> >> 273                 if (dpll_mpu_opp100.m == MPUPLL_M_1000) {
>>> >> 274                         usb_cur_lim =
>>> >> TPS65217_USB_INPUT_CUR_LIMIT_1800MA;
>>> >> 275                         mpu_vdd = TPS65217_DCDC_VOLT_SEL_1325MV;
>>> >> 276                 } else {
>>> >> 277                         usb_cur_lim =
>>> >> TPS65217_USB_INPUT_CUR_LIMIT_1300MA;
>>> >> 278                         mpu_vdd = TPS65217_DCDC_VOLT_SEL_1275MV;
>>> >> 279                 }
>>> >>
>>> >>
>>> >> But that only happens if you have the "beaglebone black" header in
>>> >> eeprom:
>>> >>
>>> >> 262                 /*
>>> >> 263                  * Override what we have detected since we know
>>>if
>>> >> we
>>> >> have
>>> >> 264                  * a Beaglebone Black it supports 1GHz.
>>> >> 265                  */
>>> >> 266                 if (board_is_bone_lt(&header))
>>> >>
>>> >> So you'll have to override that check.
>>> >
>>> >
>>> > Note that the question was about DCDC1 and DDR voltage not DCDC2/3
>>>(CORE
>>> > and
>>> > MPU) voltage.  I don't know what initial bring-up U-Boot was whacking
>>> > DCDC1
>>> > but it never reached the rest of the world so it's more a happy
>>>accident
>>> > that should be corrected (and wouldn't be too hard to do, if anyone
>>>out
>>> > there is looking for a reason to get their feet wet ).
>>>
>>> Well, the original v2013.04 patchset can be seen here:
>>>
>>>
>>> 
>>>https://github.com/beagleboard/meta-beagleboard/tree/master/common-bsp/r
>>>ecipes-bsp/u-boot/u-boot-denx
>>>
>>> The only thing that touches the pmic, is this hack:
>>>
>>>
>>> 
>>>https://github.com/beagleboard/meta-beagleboard/blob/master/common-bsp/r
>>>ecipes-bsp/u-boot/u-boot-denx/0004-beaglebone-HACK-raise-USB-current-lim
>>>it.patch
>>>
>>> I don't have my tps decoder ring, so i'm not sure if that address is
>>> more then just the usb current setting..
>>
>>
>> I believe the equivalent hack to set DCDC1 to 1.35V is
>>
>>
>> +/* 0x24 is the address of the PMIC */
>> +/* 0x0b is the password register */
>> +/* 0x0e is the DEFDCDC1 register */
>> +/* 0x73 is the password (register 0x0e ^ 0x7d) */
>> +/* 0x12 sets the DCDC1 to 1.35V */
>> +/* Sequence must be repeated twice for password protection */
>>  #define CONFIG_BOOTCOMMAND \
>> +       "i2c mw 0x24 0x0b 0x73; " \
>> +       "i2c mw 0x24 0x0e 0x12; " \
>> +       "i2c mw 0x24 0x0b 0x73; " \
>> +       "i2c mw 0x24 0x0e 0x12; " \
>>
>> I'm just about to try this out, but don't mind if someone beats me to
>>it.
>> :-)
>
>Is there an easy to access ddr3_vdd test point?
Probably the best place is L1 or R6 which is on the bottom of the board
close to the 5V connector

Regards,
John
>
>Regards,
>
>-- 
>Robert Nelson
>http://www.rcn-ee.com/
>
>-- 
>For more options, visit http://beagleboard.org/discuss
>--- 
>You received this message because you are subscribed to the Google Groups
>"BeagleBoard" group.
>To unsubscribe from this group and stop receiving emails from it, send an
>email to beagleboard+unsubscr...@googlegroups.com.
>For more options, visit https://groups.google.com/d/optout.


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to