device: add shikra-evk Jinja2 device templates#69
Conversation
mwasilew
left a comment
mwasilew
left a comment
There was a problem hiding this comment.
I would prefer Shikra to be based on qdl deployment, not flasher.
Do we need to create qdl Jinja template similar to flasher? |
|
Yes, here is an example job o Glymur: https://lava-staging.infra.foundries.io/scheduler/job/4232. It might take a few iterations to get it right. So if Shikra is very urgent we can go with flasher and update later. |
If it works, let's go with the flasher for now. Meanwhile I'll create another PR to add qdl jinja based on the yaml available on the job. |
Add base device definition and meta-qcom project override for shikra-evk, a new device type with its own LAVA device type identifier, boot prompt, and flasher configuration. Signed-off-by: Anil Yadav <anilyada@qti.qualcomm.com>
qcom-anilyada
force-pushed
the
test/add-shikra
branch
from
62bec9e to
4bf516f
Compare
|
Given there are no devices to test with and I'm planning to roll-out deploy-to-qdl this week, maybe flasher is not the best approach. |
|
We have connected one shikra device to worker-10, can be used as staging. |
2 participants
Add base device definition and meta-qcom project override for shikra-evk, a new device type with its own LAVA device type identifier, boot prompt, and flasher configuration.
Created a Draft PR, please ignore this for now:
Dependency on https://jira-dc4.qualcomm.com/jira/browse/OSTT-674 and device onboarding in LAVA pool.
Currently, checking if the received devices are booting up properly.
Signed-off-by: Anil Yadav anilyada@qti.qualcomm.com