Difference between revisions of "DESK-XZ7-L/Development/Synchronizing git repositories"
| Line 8: | Line 8: | ||
|style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#edf8fb; padding:5px; color:#000000"|2022/11/22 | |style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#edf8fb; padding:5px; color:#000000"|2022/11/22 | ||
|style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#edf8fb; padding:5px; color:#000000"|DESK-XZ7-L-1.0.0-rc1 release | |style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#edf8fb; padding:5px; color:#000000"|DESK-XZ7-L-1.0.0-rc1 release | ||
| + | |- | ||
| + | !style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#ededed; padding:5px; color:#000000"|2024/01/12 | ||
| + | !style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#ededed; padding:5px; color:#000000"|DESK-XZ7-L-1.0.1 release | ||
|- | |- | ||
|} | |} | ||
| Line 28: | Line 31: | ||
|Petalinux | |Petalinux | ||
|<code>git@git.dave.eu:desk-xz-l/petalinux.git </code> | |<code>git@git.dave.eu:desk-xz-l/petalinux.git </code> | ||
| − | |||
| − | |||
| − | |||
|- | |- | ||
|U-Boot | |U-Boot | ||
| Line 56: | Line 56: | ||
Please note that git fetch doesn't merge the commits on the current branch. To do that, the developer should run the <code>git merge</code> command or replace the ''fetch-merge'' process with a single <code>git pull</code> command. Please note that the recommended method is the ''fetch-merge'' process. For further information on Git, please refer to the official [http://git-scm.com Git Documentation] | Please note that git fetch doesn't merge the commits on the current branch. To do that, the developer should run the <code>git merge</code> command or replace the ''fetch-merge'' process with a single <code>git pull</code> command. Please note that the recommended method is the ''fetch-merge'' process. For further information on Git, please refer to the official [http://git-scm.com Git Documentation] | ||
| − | + | <section end=Body/> | |
[[Category:BORA]] | [[Category:BORA]] | ||
Revision as of 10:48, 18 January 2024
| HOME | SOMs | SBCs | ToloMEO Embedded Assistant |  GET A QUOTE
|
 ONLINE HELPDESK
|
| Roadmap | IoT Services | ML/AI services | Embedded Design Services |
| History | |||
|---|---|---|---|
| Issue Date | Notes | ||
| 2022/11/22 | DESK-XZ7-L-1.0.0-rc1 release | ||
| 2024/01/12 | DESK-XZ7-L-1.0.1 release | ||
Synchronizing the repository[edit | edit source]
In DESK-XZ7-L, the following source trees are clones of the correspondent DAVE Embedded Systems git repositories:
| Component | GIT Remote |
|---|---|
| Vivado | git@git.dave.eu:desk-xz-l/vivado.git
|
| Petalinux | git@git.dave.eu:desk-xz-l/petalinux.git
|
| U-Boot | git@git.dave.eu:desk-xz-l/u-boot-xlnx.git
|
There are two main repositories to:
- track and reproduce hardware design with Vivado
- track and reproduce Petalinux/Yocto build
Additional repositories will be used to track other piece of software that requires customization (e.g. U-Boot bootloader, Linux kernel, sample application and so on)
Access to DAVE Embedded Systems' git repositories is granted to the development kit's owners only. Please refer to this page for detailed instructions on how to get access.
Instructions[edit | edit source]
The components listed in the table above can be kept in sync and up to date with DAVE Embedded Systems' repositories.
Once the git account has been enabled, the developer can:
- clone the repository with the
git clone <git_remote_repository>command - synchronize a source tree entering the repository directory and launching the
git fetch origincommand.
Please note that git fetch doesn't merge the commits on the current branch. To do that, the developer should run the git merge command or replace the fetch-merge process with a single git pull command. Please note that the recommended method is the fetch-merge process. For further information on Git, please refer to the official Git Documentation
