15 Dec, 2018

1 commit


20 Oct, 2018

1 commit


04 Aug, 2018

1 commit

  • The "Beaglebone Enhanced" by Sancloud is based on the Beaglebone Black,
    but with the following differences:

    * Gigabit capable PHY
    * Extra USB hub, optional i2c control
    * lps3331ap barometer connected over i2c
    * MPU6050 6 axis MEMS accelerometer/gyro connected over i2c
    * 1GiB DDR3 RAM
    * RTL8723 Wifi/Bluetooth connected over USB

    Signed-off-by: Koen Kooi
    Reviewed-by: Tom Rini

    Koen Kooi
     

12 Apr, 2018

1 commit


09 Apr, 2018

2 commits


07 Apr, 2018

1 commit

  • Texas Instruments AM3358 based low-cost board using Octavo Systems OSD3358 SIP
    with built-in TPS65217 PMIC and 512MB DDR3. Board features small 35mm x
    55mm size, high-speed USB OTG, microSD and 72 0.1" expansion header
    pins with 2xSPI, 2xI2C, 2xUART, USB, 8xADC, up-to-44 GPIO, PRU pins and much more.

    https://beagleboard.org/pocket

    This was tested using the am335x_evm_usbspl_defconfig.

    Note that MII pins are enabled despite not having Ethernet on this
    board. This avoids an issue where otherwise many timeout errors would be
    generated. See https://e2e.ti.com/support/arm/sitara_arm/f/791/t/298976
    for some related discussion.

    Signed-off-by: Jason Kridner
    Cc: Tom Rini
    Reviewed-by: Tom Rini

    Jason Kridner
     

05 Mar, 2018

1 commit


24 Feb, 2018

1 commit


15 Feb, 2018

2 commits

  • This converts the following to Kconfig:
    CONFIG_BOOTCOUNT_LIMIT

    Signed-off-by: Lukasz Majewski
    Tested-by: Alex Kiernan
    Reviewed-by: Hannes Schmelzer
    Acked-by: Hannes Schmelzer

    Lukasz Majewski
     
  • >From DFU_ALT_INFO_EMMC (include/environment/ti/dfu.h) we can see that
    rootfs will be flashed to second partition on eMMC. But at the moment we
    have only one partition in $partitions environment variable. Let's add
    "bootloader" partition prior to "rootfs", so that DFU works correctly.
    This also fixes eMMC boot, which looks for rootfs on second partition.

    "bootloader" partition start corresponds to "u-boot.img.raw" in DFU
    eMMC info, which is 0x300 sector (384 KiB offset from eMMC start).

    rootfs start address can be also found from DFU eMMC info.
    bootloader-related area is finished at 0x1500 sector (2688 KiB offset
    from eMMC start). This should be the start address for rootfs in
    $partitions environment variable.

    While at it, fix U-Boot environment address to be the same as for
    AM57x EVM, so that it doesn't clash with other partitions.

    So now eMMC layout looks like this:

    ===============================================================

    0 +------------------------+
    | MBR/GPT header | 128 -
    128 +------------------------+
    | MLO | 256 -
    384 +------------------------+
    | u-boot.img | 1792 bootloader
    2176 +------------------------+
    | //////// hole //////// | 256 -
    2432 +------------------------+
    | U-Boot environment | 128 -
    2560 +------------------------+
    | U-Boot environment | 128 -
    | (redundant) |
    2688 +------------------------+
    | rootfs | remaining rootfs
    end +------------------------+

    ===============================================================

    "hole" area can be used further for storing U-Boot environment (like
    it's done in AM57x EVM config file) or for increasing u-boot.img area
    (in case u-boot.img size increased, e.g. if new dtbs were added).

    This commit conforms with Linux partition table from f6d245b8c56c
    ("arm: am57xx: Fix Linux boot from eMMC") commit, making things in
    uniform way.

    Signed-off-by: Sam Protsenko
    Reviewed-by: Lokesh Vutla
    Reviewed-by: Tom Rini

    Sam Protsenko
     

11 Feb, 2018

1 commit

  • On the NIOS2 and Xtensa architectures, we do not have
    CONFIG_SYS_TEXT_BASE set. This is a strict migration of the current
    values into the defconfig and removing them from the headers.

    I did not attempt to add more default values in and for now will leave
    that to maintainers.

    Signed-off-by: Tom Rini

    Tom Rini
     

23 Jan, 2018

1 commit


19 Dec, 2017

1 commit

  • Use dfu_alt_info_emmc variable from include/environment/ti/dfu.h file.
    It was probably overlooked when extracting DFU variables to mentioned
    file.

    This patch fixes DFU on BeagleBone Black, so that we can use commands
    like ones below to upgrade various images on eMMC:

    => setenv dfu_alt_info $dfu_alt_info_emmc
    => dfu 0 mmc 1

    $ dfu-util -D MLO -a MLO.raw
    $ dfu-util -D u-boot.img -a u-boot.img.raw

    Without this patch, the user is forced to assign the value to
    dfu_alt_info_emmc manually, which contradicts with instructions [1].

    [1] http://processors.wiki.ti.com/index.php/Linux_Core_U-Boot_User%27s_Guide

    Signed-off-by: Sam Protsenko
    Reviewed-by: Lokesh Vutla
    Reviewed-by: Lukasz Majewski

    Sam Protsenko
     

18 Nov, 2017

1 commit

  • We first introduce CONFIG_USE_BOOTCOMMAND, similar to
    CONFIG_USE_BOOTARGS. We then migrate CONFIG_BOOTCOMMAND for most
    CONFIG_DISTRO_DEFAULT users. In some cases platforms have a complex
    scheme around this usage, and these have been defered for the moment so
    that platform maintainers can work on a migration plan.

    Signed-off-by: Tom Rini
    Reviewed-by: Lukasz Majewski

    Tom Rini
     

06 Nov, 2017

1 commit


21 Oct, 2017

1 commit

  • This converts the following to Kconfig:
    CONFIG_NAND_MXC
    CONFIG_NAND_OMAP_GPMC
    CONFIG_NAND_OMAP_GPMC_PREFETCH
    CONFIG_NAND_OMAP_ELM
    CONFIG_SPL_NAND_AM33XX_BCH
    CONFIG_SPL_NAND_SIMPLE
    CONFIG_SYS_NAND_BUSWIDTH_16BIT

    Signed-off-by: Adam Ford
    Reviewed-by: Heiko Schocher
    [trini: Finish migration of CONFIG_SPL_NAND_SIMPLE, fix some build issues,
    add CONFIG_NAND_MXC so we can do CONFIG_SYS_NAND_BUSWIDTH_16BIT]
    Signed-off-by: Tom Rini

    Adam Ford
     

04 Oct, 2017

3 commits


02 Sep, 2017

1 commit


17 Aug, 2017

1 commit


13 Aug, 2017

1 commit


12 Aug, 2017

2 commits


09 Aug, 2017

1 commit


08 Aug, 2017

1 commit


31 Jul, 2017

1 commit


26 Jul, 2017

4 commits

  • This converts the following to Kconfig:
    CONFIG_ENV_IS_IN_FAT

    Signed-off-by: Simon Glass

    Simon Glass
     
  • This converts the following to Kconfig:
    CONFIG_ENV_IS_IN_SPI_FLASH

    Signed-off-by: Simon Glass

    Simon Glass
     
  • This converts the following to Kconfig:
    CONFIG_ENV_IS_IN_FLASH

    Signed-off-by: Simon Glass

    Simon Glass
     
  • This converts the following to Kconfig:
    CONFIG_ENV_IS_IN_MMC
    CONFIG_ENV_IS_IN_NAND
    CONFIG_ENV_IS_IN_UBI
    CONFIG_ENV_IS_NOWHERE

    In fact this already exists for sunxi as a 'choice' config. However not
    all the choices are available in Kconfig yet so we cannot use that. It
    would lead to more than one option being set.

    In addition, one purpose of this series is to allow the environment to be
    stored in more than one place. So the existing choice is converted to a
    normal config allowing each option to be set independently.

    There are not many opportunities for Kconfig updates to reduce the size of
    this patch. This was tested with

    ./tools/moveconfig.py -i CONFIG_ENV_IS_IN_MMC

    And then manual updates. This is because for CHAIN_OF_TRUST boards they
    can only have ENV_IS_NOWHERE set, so we enforce that via Kconfig logic
    now.

    Signed-off-by: Simon Glass
    Signed-off-by: Tom Rini

    Simon Glass
     

25 Jul, 2017

1 commit


12 Jul, 2017

1 commit

  • When CONFIG_CMD_FASTBOOT or CONFIG_USB_FUNCTION_FASTBOOT are defined
    in am335x_evm.h, a dependency on g_dnl.c is created. This in turn
    creates a dependency on having USB gadget enabled.
    As a result we can't create configs with USB gadget disabled.

    Since these CONFIG_ variables are now part of kconfig, move them to
    the board defconfigs, and out of am335x_evm.h. This both preserves
    current defaults, and allows creating configs with USB gadget off.

    Signed-off-by: Alexandru Gagniuc
    Reviewed-by: Tom Rini

    Alexandru Gagniuc
     

22 May, 2017

1 commit

  • This converts the following to Kconfig:
    CONFIG_CMD_EEPROM
    CONFIG_CMD_EEPROM_LAYOUT
    CONFIG_EEPROM_LAYOUT_HELP_STRING

    Signed-off-by: Simon Glass
    Reviewed-by: Tom Rini
    [trini: Rework Kconfig logic slightly, define EEPROM location on TI eval
    platforms]
    Signed-off-by: Tom Rini

    Simon Glass
     

15 May, 2017

1 commit


12 May, 2017

2 commits


09 Apr, 2017

1 commit

  • Introduce include/environment/ti/mmc.h that
    consolidates environment variable definitions
    for various TI boards that support MMC/SD.

    This allows reuse of same environment variables
    on non-ARMv7 TI platforms like OMAP-L138 for
    example.

    While at it, move DFU-related environment variable
    includes to only non-SPL builds for AM335x and
    AM437x since they are not really used for SPL
    today.

    Signed-off-by: Sekhar Nori
    Reviewed-by: Lukasz Majewski
    Reviewed-by: Tom Rini

    Sekhar Nori
     

08 Apr, 2017

1 commit

  • BeagleBone Blue is next grenation of boards from BeagleBoard.org, focusing
    on robotics with a TI wl1835 wireless module for connectivity.

    This board can be indentified by the BLAx value after A335BNLT (BBB)
    in the at24 eeprom:
    BLAx: [aa 55 33 ee 41 33 33 35 42 4e 4c 54 42 4c 41 30 |.U3.A335BNLTBLA2|]

    http://beagleboard.org/blue
    https://github.com/beagleboard/beaglebone-blue

    firmware: https://github.com/beagleboard/beaglebone-black-wireless/tree/master/firmware
    wl18xx mac address: /proc/device-tree/ocp/ethernet@4a100000/slave@4a100200/mac-address

    Signed-off-by: Robert Nelson
    CC: Tom Rini
    CC: Jason Kridner
    CC: Will Newton
    Reviewed-by: Tom Rini

    robertcnelson@gmail.com