| Summary: | PnP target QA | ||
|---|---|---|---|
| Product: | [QA/Testing] Runtime Testing | Reporter: | Armin Kuster <akuster> |
| Component: | general | Assignee: | Unassigned <unassigned> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | randy.macleod, richard.purdie |
| Version: | 2.7 | ||
| Target Milestone: | 5.99 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
As discussed in today's bug triage meeting. What we guess is asked is for Yocto to build the tools necessary to flash/debug the board at the same time it builds the image. For example : * STM32MP1 BSP layer build openocd-native (JTAG debugger tool) with the image : https://github.com/STMicroelectronics/meta-st-stm32mp/blob/ca501bd7dbe023682903ceedddaacd940b0898f4/conf/machine/include/st-machine-common-stm32mp.inc#L362-L368 * Atmel BSP layer had a tool to flash the board : https://github.com/linux4sam/meta-atmel/commit/9da3978412adc4f9f9fb5f1633de1d322a76c2eb and https://github.com/linux4sam/meta-atmel/commit/aabcfa27791b2d49550b527237dcbe8126b06597 "AT91Bootstrap: remove at91bootstrap-sam-ba recipe" ... but, these tools might be better suited for the specific BSP layers than OE-Core (since they can't realistically be common enough to be shared) Bulk move from 4.99 or 0.00 to 5.99 Not detailed enough and kind of out of scope. |
Can we create some mechanism to allow easier end developer testing on real hardware ('plug a board into their laptop and go')?