1. 31 Jul, 2019 3 commits
    • Sam Protsenko's avatar
      configs: am57xx_evm_defconfig: Enable 'bcb' command · 29e783d6
      Sam Protsenko authored
      
      
      It is essential to have an access to BCB area of 'misc' partition on
      Android devices [1]. For BeagleBoard X15 the 'bcb' command will be
      further used for reboot reason implementation and booting to recovery.
      It can be also used for debugging reasons, like checking RescueParty
      messages in BCB area.
      
      [1] doc/android/bcb.txt
      Signed-off-by: default avatarSam Protsenko <semen.protsenko@linaro.org>
      29e783d6
    • Sam Protsenko's avatar
      omap: Correct the fastboot product var · 4347b0b0
      Sam Protsenko authored
      
      
      "fastboot flashall" expects "fastboot getvar product" value to be one of
      values provided in android-info.txt file (in AOSP), from "require
      board=" list. Before this patch, "am57xx" is returned for all AM57xx
      based boards, as it's set in $board env var from SYS_BOARD in
      board/ti/am57xx/Kconfig file, which is used for default implementation
      of "fastboot getvar product".
      
      In order to fix that inconsistency, let's do next:
        1. In U-Boot: override fastboot.product, reusing the value from
           $board_name
        2. In AOSP: provide values for all AM57xx boards we can use to
           device/ti/beagle_x15/board-info.txt file
      
      This way requirements check in "fastboot flashall" will work as
      expected, verifying that user tries to flash images to the board which
      those images were built for.
      Signed-off-by: default avatarSam Protsenko <semen.protsenko@linaro.org>
      Acked-by: default avatarAndrew F. Davis <afd@ti.com>
      4347b0b0
    • Sam Protsenko's avatar
      env: ti: boot: Handle reboot reason from BCB · 3db0989e
      Sam Protsenko authored
      In case of Android boot, reboot reason can be written into BCB (usually
      it's an area in 'misc' partition). U-Boot then can obtain that reboot
      reason from BCB and handle it accordingly to achieve correct Android
      boot flow, like it was suggested in [1]:
        - if it's empty: perform normal Android boot from eMMC
        - if it contains "bootonce-bootloader": get into fastboot mode
        - if it contains "boot-recovery": perform recovery boot
      
      The latter is not implemented yet, as it depends on some features that
      are not implemented on TI platforms yet (in AOSP and in U-Boot).
      
      [1] https://marc.info/?l=u-boot&m=152508418909737&w=2
      
      Signed-off-by: default avatarSam Protsenko <semen.protsenko@linaro.org>
      3db0989e
  2. 30 Jul, 2019 31 commits
  3. 29 Jul, 2019 6 commits