Bug 13017 - PnP target QA
Summary: PnP target QA
Status: RESOLVED INVALID
Alias: None
Product: Runtime Testing
Classification: QA/Testing
Component: general (show other bugs)
Version: 2.7
Hardware: x86 Multiple
: Medium normal
Target Milestone: 5.99
Assignee: Unassigned
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2018-11-11 19:52 UTC by Armin Kuster
Modified: 2026-01-29 16:19 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Armin Kuster 2018-11-11 19:52:32 UTC
Can we create some mechanism to allow easier end developer testing on
real hardware ('plug a board into their laptop and go')?
Comment 1 Yoann Congal 2023-02-02 16:51:24 UTC
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)
Comment 2 Randy MacLeod 2023-10-24 14:24:56 UTC
Bulk move from 4.99 or 0.00 to 5.99
Comment 3 Randy MacLeod 2026-01-29 16:19:30 UTC
Not detailed enough and kind of out of scope.