| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The upstream NRF-SDK download url and zip archive filename changed,
which was fixed with https://github.com/InfiniTimeOrg/InfiniTime/pull/2270
But the archive contents stayed the same, with the "old" folder name.
After #2270 we have basically the same docker-container as before the PR,
but the `GetNrfSdk` function of the `build.sh` script is called again during
firmware build time as the expected foldername for the SDK isn't the same as
the zip filename:
```sh
[ ! -d "$TOOLS_DIR/$NRF_SDK_VER" ] && GetNrfSdk
```
Then during the build the `buils.sh` script tries to execute `GetNrfSdk` again,
which fails as the files already exist resulting in the following error:
```
replace /opt/nRF5_SDK_15.3.0_59ac345/components/802_15_4/api/HAL/hal_atomic.h? [y]es, [n]o, [A]ll, [N]one, [r]ename: NULL
```
Fix this by reverting the `NRF_SDK_VER` to the folder name in the zip
archive and by some character replacement generate the download URL from
the above (the download is in lower-case without the `_` and `.`
characters).
Furthermore add safeguards to check after the `GetNrfSdk` call if the
expected folder is really created. Then we have an error early during
container image creation if the contents of the zip-archive are
unexpected.
|
| |
|
| |
nRF has moved the download to a new location- Update the build script to fetch from the same URL the download website currently provides.
|
| | |
|
| |
|
|
| |
This reverts commit 35654fbd982e27383ffc15446d9ab0a8606ae29d.
|
| |
|
|
| |
This reverts commit 7103f9d8063431b778df83244de5862d963e1ce8.
|
| |
|
| |
Co-authored-by: NeroBurner <pyro4hell@gmail.com>
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Return the build status as return code from the `main` helper function.
In the process convert the handling if the file was sourced or directly
executed into an explicit if/else statement to make the intent clearer.
In case of an build error the error is now reported at the build step,
where the error happened.
Fixes: https://github.com/InfiniTimeOrg/InfiniTime/issues/1292
|
| |
|
|
| |
the debugging environment (USE_JLINK, USE_OPENOCD and USE_GDB_CLIENT).
|
| |
|
|
| |
Add lv_img_conf in Docker image to build resources at build time.
|
| |
|
|
|
|
| |
This is because of this bug:
https://community.arm.com/support-forums/f/compilers-and-libraries-forum/52623/gcc-11-2-arm-none-eabi-internal-compiler-error-illegal-instruction
It is causing some of the GitHub Actions builds to fail.
|
| |
|
|
|
|
| |
Updates the buildAndProgram doc and the docker
image, which means GitHub Actions will also use
the new toolchain.
|
| |
|
|
|
|
| |
docker image to build the firmware. This allows to avoid the duplication of the build logic in Docker and Github workflow format.
The Dockerfile has been slightly adapted (remove the USER instructions). Docker images are now published in DockerHub (jf002/infinitime-build).
|
| | |
|
| |
|
|
| |
adafruit-nrfutil on the build machine) : BUILD_DFU (disabled by default, enabled in docker build).
|
| | |
|
| |
|
|
| |
Added some extra dir names to gitignore
|
| |
|
|
| |
Also fixed a bug with empty quoted strings
|
| |
|
|
| |
Script is written to handle it's own dependencies so it can be used within Docker or on the host system
|
| |
|
|
| |
and post_build.sh that is generated by cmake build.sh
|
| |
|
|
|
|
|
| |
in their filename.
Update Docker build script accordingly.
Also fix permission issue with docker build (all files belonged to root).
|
|
|
arm64 arch.
|