Basic recipe for Boundary Devices Nitrogen6SoloX board #18
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This drops the rpi specifics and adapts the basic stuff to the Boundary Devices Nitrogen6SoloX board.
Use the imx-specific device node name for the console argument.
We'll replace the extlinux specifics with something more similar to what flash-kernel does which seems more suitable.
The gen-bootscript.sh was copied verbatim from wandboard recipe. Note that nitrogen6sx is not part of debian u-boot-imx package and not even in upstream u-boot (yet). It will need to be built from the boundarydevices u-booti-imx6 fork.
The nit6sx support is not yet in upstream u-boot. We thus use boundarys official u-boot binary https://boundarydevices.com/wiki/u-boot/ says: > Where to get the latest binary for my platform? > > Our build server automatically generates and uploads all the latest binaries to this address: > > http://linode.boundarydevices.com/u-boot-images/ > > The README file contains the exact commit ID of this build images. The source for it is at https://github.com/boundarydevices/u-boot-imx6
The ramdiskaddr variable was not set in the built-in environment variables, so set it when needed. Also: - update comments to be in line with what's in the environment for this u-boot binary. - Replace mentions of wandboard with nit6sx.
andhe
commented
Nov 25, 2020
| - action: raw | ||
| description: Write u-boot binary to raw image load addr | ||
| origin: bootloader | ||
| source: . |
There was a problem hiding this comment.
See go-debos/debos#77 (downloaded is a file which should be used directly, not an archive.)
andhe
commented
Nov 25, 2020
| description: Write u-boot binary to raw image load addr | ||
| origin: bootloader | ||
| source: . | ||
| offset: 1024 |
There was a problem hiding this comment.
(Note to self: This could also be written as {{ sector 2 }}.)
This allows setting which mmc device u-boot should load kernel, dtb, initrd from when building the recipe. eg. debos -t mmcbootdev:1 nit6sx/debimage-nit6sx.yaml
Use correct syntax with setenv and use correct variable name when reading the variable.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
I made a basic recipe for the nit6sx board from Boundary Devices in case anyone is interested.
It uses a pre-built u-boot binary because the board is only supported in boundary devices u-boot fork and not in upstream u-boot.
Testing this is limited to 'it boots' (for now).
It is based on and similar to the wandboard recipe, but with the file structure updated to match the latest style recipes.
PS. debos assumption that all downloads basically are archives and that both origin and source is required arguments for raw action causes the quite ugly "source: ." workaround to be used. Possibly this is an area for improvement in debos.