1. 15 Apr, 2021 1 commit
  2. 14 Apr, 2021 6 commits
  3. 13 Apr, 2021 1 commit
  4. 09 Apr, 2021 1 commit
  5. 08 Apr, 2021 7 commits
  6. 07 Apr, 2021 2 commits
  7. 06 Apr, 2021 2 commits
    • stevanradakovic's avatar
      Merge branch 'docker-install' into 'master' · 8429aae3
      stevanradakovic authored
      doc: install latest version docker and docker-compose
      
      See merge request !1471
      8429aae3
    • Chase Qi's avatar
      doc: install latest version docker and docker-compose · 941acad6
      Chase Qi authored
      The current version '18.09.1' docker installed via 'apt install
      docker.io' doesn't work with 'lava-docker-worker'. The below error
      returned.
      
      ```
      docker: Error response from daemon: OCI runtime create failed:
      container_linux.go:344: starting container process caused "exec:
      \"/dev/init\": stat /dev/init: no such file or directory": unknown.
      ```
      
      While the '20.10.5' version from Docker's official repo works well with
      'lava-docker-worker'
      
      Old version docker-compose also is problematic in some cases.
      Signed-off-by: default avatarChase Qi <chase.qi@amd.com>
      941acad6
  8. 03 Apr, 2021 1 commit
  9. 01 Apr, 2021 3 commits
  10. 26 Mar, 2021 4 commits
  11. 24 Mar, 2021 4 commits
    • Antonio Terceiro's avatar
      dispatcher: fvp: emulate DockerRun container naming · 60f39786
      Antonio Terceiro authored
      This makes it possible to start a docker test shell container that
      shares the network stack of a fvp container.
      60f39786
    • Antonio Terceiro's avatar
      dispatcher: docker: support sharing network stacks · c2c35554
      Antonio Terceiro authored
      Every usage of docker that is backed by lava_dispatcher.utils.docker now
      supports sharing networking stacks between container. You need to start
      a long-running container, say, a QEMU device that is using docker, and
      specify a name for it using the `container_name` key in the job
      definition. Later in the job definition, when defining another
      container, say a docker test shell one, you reference the name used for
      the first container in the `network_from` key. For example:
      
      - In the QEMU boot action:
      
        docker:
          image: foo/bar
          container_name: qemu
      
      - In a docker test shell after that:
      
        docker:
          image: something/else
          network_from: qemu
      
      Note that this is only supported if the original container is a
      long-running container that stays running in the background after the
      action where it started finishes, e.g. a QEMU device container.
      
      We have to drop support for container hostname because that conflicts
      with the --network option. Also it's pointl...
      c2c35554
    • Antonio Terceiro's avatar
      test_fvp: drop unused monkey patching · 5bf5c395
      Antonio Terceiro authored
      5bf5c395
    • Paul Sokolovsky's avatar
      doc/v2/actions-boot: pyocd: Describe device type level config options · 38f70c57
      Paul Sokolovsky authored
      Prompted by the addition of new "connect_before_flash" option which should
      be set in device type template. To make it less confusing, describe other
      device type level options too: "command" and "options". This is still
      seems like first time such options are described for a boot method, but
      hopefully this will set a positive example to extend to other methods.
      Signed-off-by: default avatarPaul Sokolovsky <paul.sokolovsky@linaro.org>
      38f70c57
  12. 23 Mar, 2021 2 commits
    • Paul Sokolovsky's avatar
      lpcxpresso55s69: Add support for "pyocd" boot method. · d3503065
      Paul Sokolovsky authored
      Uses "connect_before_flash" method param recently added to "pyocd" boot
      method, to avoid losing serial output immediately after flashing.
      Signed-off-by: default avatarPaul Sokolovsky <paul.sokolovsky@linaro.org>
      d3503065
    • Paul Sokolovsky's avatar
      boot/pyocd: Allow to connect to device before flashing · 214166d8
      Paul Sokolovsky authored
      This will allow to capture serial output appearing immediately after
      flashing. Specific reason for this change is lpcxpresso55s69 board,
      which doesn't support reset-using-uart-break feature. In other words,
      how we dealt re: this problem with other boards is that we flashed it
      (and it started executing, which is not good), then connected to it,
      which caused reset and executing from start, and that's how we were
      able to capture the full output (but potentially with extra output
      in the beginning, which is again not good).
      
      That way doesn't work with lpcxpresso55s69 - as there's no reset,
      we lose some initial output, and capture only tail of it. This problem
      however doesn't happen with "jlink" boot method, and the difference
      is exactly that it first issues ConnectDevice sub-action, and then
      Flash() action. Looking at the other boot actions, that's also how
      most of them do either. "cmsis-dap" and "pyocd" for about the only
      clear exceptions.
      
      Given that, it would be tempting to just swap the order unconditionally.
      However, detailed gitlog review shows that such a change was already
      made on 2018-07-31 in commit 4efd8586, just to be reverted the
      same day in 610b8e58. Sadly, the revert doesn't include reasons
      for it, by I was able to find the related dicussion at
      https://review.linaro.org/c/lava/lava/+/27685. Quoting:
      
      > There's a very specific reason this code was written how it was.
      > On some pyocd devices the serial connection doesn't exist until
      > the board is flashed, or the flashing process resets the serial
      > connection so if already connected it will be closed.
      > This change will mean they simply no longer work.
      
      Specific boards weren't named, but it's easily to believe that could
      happen, given all the variability in board behavior we see.
      So instead (and as suggested in the review discussion by the link
      above), a "connect_before_flash" boot method param is introduced,
      and the default is kept the same as before (i.e.
      connect_before_flash = False). For now, it will be set to True for
      lpcxpresso55s69, and then other boards can be tested with that setting
      as time permits.
      Signed-off-by: default avatarPaul Sokolovsky <paul.sokolovsky@linaro.org>
      214166d8
  13. 22 Mar, 2021 3 commits
  14. 19 Mar, 2021 2 commits
  15. 18 Mar, 2021 1 commit