Skip to content

Add the tezi-custom sources - #373

Merged
daniel-rossier merged 1 commit into
mainfrom
feat/tezi-custom
Nov 7, 2026
Merged

daniel-rossier merged 1 commit into
mainfrom
feat/tezi-custom

Conversation

@daniel-rossier

Copy link
Copy Markdown
Contributor

scripts/recovery-edgem.sh needs scripts/tezi-custom/tezi.itb, and tells the user to run scripts/tezi-custom/build.sh, but that directory was never imported. So the script could not work, and flashing a Verdin needed a manual tezictl feed-add on the serial console, lost at every reboot.

This adds build.sh, patch_fit.py and rc.local.append.in, identical to edgem1 and to infrabase#69. They only patch the Toradex installer, so they depend on neither Torizon nor the capsules. The board then registers the feed that deploy.sh publishes on port 8080 by itself.

tezi-feed-serve.sh gets the comment edgem1 carries, tying its host IP selection to build.sh, and .gitignore covers what the build generates.

Only checked for syntax (bash -n): the build was not run and nothing was tested on a Verdin board.

recovery-edgem.sh runs the installer that scripts/tezi-custom/build.sh
produces, but that directory was never imported: the script could not
work, and a Verdin flash needed a manual tezictl feed-add on the serial
console, lost at every reboot.

Take the sources from Infrabase and edgem1. They patch the Toradex
installer only, so nothing here depends on Torizon or the capsules, and
the board finds the feed deploy.sh publishes on IB_HTTP_FEED_PORT by
itself. Ignore what the build leaves next to them.
@daniel-rossier
daniel-rossier merged commit df109c4 into main Nov 7, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant