Skip to content
Snippets Groups Projects
Select Git revision
0 results
Search by author
  • Any Author
0 authors
  1. Sep 27, 2022
  3. Sep 22, 2022
  5. Sep 20, 2022
  7. Sep 16, 2022
    • GitBot's avatar
      Integrate uboot-imx-kuk/add_boot_bus_check · d369a378
      GitBot authored 
      --

Commit: seco-ne/3rd-party/kuk/uboot-imx-kuk@c432389c

Removed rearrangement of the USDHC busses

The USDHC busses had been rearranged, because we have a different pin mapping
on the MC3 (as compared to the Trizeps modules and the DE).
We now have a boot bus detection, which sets the correct bus for the boot
scripts. This makes the rearrangement obsolete.
Removing the rearrangement also fixes an error in the save function for the
environment, which mixes the boot bus with the device tree definitions.

BCS 746-000814

--

Commit: seco-ne/3rd-party/kuk/uboot-imx-kuk@fb5fcbc7

cmd:guf: Added boot bus detection to guf sub-system

The boot bus detection sets an environment variable that contains the USDHC
bus, from which U-Boot was started. The variable is used in the search for the
boot scripts and prevents U-Boot from mixing up the eMMC and SD-Card.

BCS 746-000814
      d369a378
  9. Sep 14, 2022
  11. Sep 12, 2022
  13. Sep 09, 2022
  15. Sep 07, 2022
    • GitBot's avatar
      Integrate linux-imx-kuk/tanaro_add_scx1001255ggu06_dunfell · 39856480
      GitBot authored 
      --

Commit: seco-ne/kernel/linux-imx-kuk@df93942a

arm64: dts: tanaro: Add device tree for scx1001255ggu06

Add the device tree for the touch display set SCX1001255GGU06 including
the LCD panel FG1001L0DSSWMG01 and an SIS touch.
The panel is connected via LVDS.

The current state does not work as expected. It seems the MIPI signals
are not clocked out correctly. So we use a reduced pixel clock to get a
working display. This results in a reduced frame rate of ~42 fps.
      39856480
  17. Sep 06, 2022
  19. Sep 05, 2022
  21. Aug 31, 2022
  23. Aug 30, 2022
  25. Aug 29, 2022
  27. Aug 25, 2022
  29. Aug 22, 2022
  31. Aug 12, 2022
  33. Aug 11, 2022
  35. Aug 02, 2022
  37. Aug 01, 2022
  39. Jul 29, 2022
  41. Jul 20, 2022
  43. Jul 15, 2022
  45. Jul 13, 2022
    • GitBot's avatar
      Integrate gitlab-ci/add-test-reporting-to-test-jobs · e57f3fce
      GitBot authored 
      --

Commit: seco-ne/yocto/infrastructure/gitlab-ci@52bae4a1

Lava Testreporting: Add script to generate markdown report for given jobids

Adds scripts for mark down generation.
Adds scripts for lava test result queries.
Adds script to generate a mark down report from this data
Call script from submit_test to generate a report directly
after the testrun.
      e57f3fce
    • GitBot's avatar
      Integrate gitlab-ci/run-test-from-gitlab-directly · 83d6e0db
      GitBot authored 
      --

Commit: seco-ne/yocto/infrastructure/gitlab-ci@ab09db0b

CI: Lava Test: Allow to install test image directly from gitlab

The images from the build job can be directly installed from gitlab.
To achive this some changes in the complete pipeline have been needed.

1. The variables used in the build job, like CI_PARAM_IMAGE, ... and
   related variables like BUILDPATH are only valid in the build job now.
2. The build job writes every variable needed in a follow up job into
   build.env. This also includes the url to the fng-install.sh of the
   final image.
3. The build.env file is used as dotenv artifact, as well as normal
   file artifact.
   The dotenv make the written variables automatically available in
   follow up jobs, that are using the aritfacts, like the deploy job.
   The normal file artifact is available via artifact download.
   (I did't found a way to download the dotenv file instead)
4. Some scripts have been added:
   - Find a job inside the pipeline by name, as the id is not known in
     advance.
   - Download all artifacts or one file of the artifacts from a given
     job
   - Download one file of the latest job by name
5. The scripts are used to download the build.env into the test job
   (where not artifacts are needed anymore)
6. The script is sourced and all variables are available inside the
   script.

Additionally this adds a fake build job to the ci-test pipeline, that
copies an image from srv73 and stores it as artifact in a way that a
test-job can run on it, like in the normal yocto pipeline.
      83d6e0db
  47. Jul 12, 2022
    • GitBot's avatar
      Integrate gitlab-ci/share-build-and-test-job-basics · b7c8ae9f
      GitBot authored 
      --

Commit: seco-ne/yocto/infrastructure/gitlab-ci@075aeccb

Refactoring: share build and test job basics for ci-test and Yocto

This shares YAML code for the following procedures:
- Build environment
- Source code checkout via repo
- SSH key and known hosts setup
- LAVA test submission
- Docker check if build folder is empty
      b7c8ae9f
    • GitBot's avatar
      Integrate linux-imx-kuk/rtc_overlays · 24345722
      GitBot authored 
      --

Commit: seco-ne/kernel/linux-imx-kuk@11963a85

tanaro:rtcs: Fix to RTC overlay mechanism

The first approach of selecting a RTC didn't work as expected.
The active RTC must reside on the rtc0 alias because otherwise
the hwclock utilities can't access the RTC.
For this to work, we now have a placeholder in the main device tree
that is filled with the actual values in one of the two overlays.
This breaks with the naming conventions for I2C bus devices, but
right now, we don't have a better solution.

BCS 746-000877
      24345722
  49. Jul 08, 2022
  51. Jul 07, 2022
  53. Jul 06, 2022
    • GitBot's avatar
      Integrate gf-emc-test-suite/rs485echo_fix_transmission_behavior · 56adf752
      GitBot authored 
      --

Commit: seco-ne/tools/gf-emc-test-suite@113135af

rs485echo: Fix RS485 transmission delays

Before, the delay_rts_before_send delay_rts_after_send fields were not
explicitly initialized. This led to a erroneous transmission behaviour.
Now the RS485 port settings are read before the half duplex
configuration is done. This ensures that the delays are set to 0 or to
a predefined value (device tree).

BCS 746-000908
      56adf752
    • GitBot's avatar
      Integrate gitlab-ci/CI-variable-scope-for-CI_PARAM_IMAGE-and-more · eba8f16e
      GitBot authored 
      --

Commit: seco-ne/yocto/infrastructure/gitlab-ci@c503a6d4

CI: pipeline yocto: Change scope of CI_PARAM_IMAGE, ... to fix fngsystem build

The variables CI_PARAM_IMAGE, CI_PARAM_DISTRO, CI_MACHINE have been
defined outside the job in the '.gitlab-ci.yml' file. This has a lower
precedence then variables defined inside the job, but it seems that
these variables are used in the scope of 'Trigger variables' when
available in the trigger job. These override the value set in the
template. As main results this made FNGSystem jobs build the normal
yocto.
      eba8f16e