[yocto] using Hob to run images on a custom simulator, other than qemu

[Mirela Rabulea]

Hi Belén,
Thanks for the info on the tests, I'll check on that.
In the meantime, please find attached my proposal for the new GUI options. Basically, if an image is qemu-compatible, already there was a "Run image" button displayed. I let the button be named "Run qemu image", while if a non qemu-compatible image is selected, the same button shows up with the name "Run custom image", and besides that, an option shows-up to allow the selection of the custom script (by default it points out to runqemu script) to be used for launching this custom image.
I also attached my original versus changed python scripts, for more clarity.
Looking forward for your feedback.

And...Merry Christmas :)

Regards,
Mirela


-----Original Message-----
From: Barros Pena, Belen [mailto:belen.barros.pena at intel.com] 
Sent: Wednesday, December 23, 2015 12:21 PM
To: Mirela Rabulea <mirela.rabulea at nxp.com>; Mirela Rabulea <Mirela.Rabulea at freescale.com>; yocto at yoctoproject.org; poky at yoctoproject.org
Cc: Nicolae Manescu <nicu.manescu at nxp.com>; Georgescu, Alexandru C <alexandru.c.georgescu at intel.com>
Subject: Re: [yocto] using Hob to run images on a custom simulator, other than qemu



On 22/12/2015 11:35, "Mirela Rabulea" <mirela.rabulea at nxp.com> wrote:

>Hi Belén,
>Thanks for the answer. Is there a set of tests that would ensure there 
>are no regressions? Where can it be found?

These are the test cases I can find in Testopia:

https://bugzilla.yoctoproject.org/tr_list_cases.cgi?searchstr=hob&current_t
ab=case&summary_type=anywordssubstr&summary=hob&field-1-0-0=summary&type-1-
0-0=anywordssubstr&value-1-0-0=hob

Hopefully someone from QA can provide more details on how to run them.

If you want any input on how to present the new options in the UI, let me know. I'll be happy to help.

Cheers

Belén

>
>Thanks,
>Mirela
>
>-----Original Message-----
>From: Barros Pena, Belen [mailto:belen.barros.pena at intel.com]
>Sent: Monday, December 21, 2015 1:26 PM
>To: Mirela Rabulea <Mirela.Rabulea at freescale.com>; 
>yocto at yoctoproject.org; poky at yoctoproject.org
>Cc: nicolae.manescu at nxp.com
>Subject: Re: [yocto] using Hob to run images on a custom simulator, 
>other than qemu
>
>
>
>On 18/12/2015 16:05, "yocto-bounces at yoctoproject.org on behalf of 
>Mirela Rabulea" <yocto-bounces at yoctoproject.org on behalf of 
>Mirela.Rabulea at freescale.com> wrote:
>
>>
>>
>>Hello yocto world
>>J
>>
>> 
>>
>>This is my first message on any yocto list, I¹m not sure which list to 
>>address, so I choose the ones which seemed the most generic and suited 
>>to my purpose. Please redirect me if a more specific list is better 
>>suited to ask this question.
>>
>> 
>>
>>The problem I see at present is: there is one single button in Hob, 
>>³Run Image², which is active only for qemu images, and it is 
>>triggering the execution of the ³poky\scripts\runqemu² script. Please 
>>scroll down to the picture at end of this email to see what I¹m talking about.
>>
>> 
>>
>>The question I want to ask is if it would be acceptable to add more 
>>buttons to the ³Image details² dialog (or a new dialog to pop-up when 
>>³Run Image² is clicked), in order to allow the customization of the 
>>simulator to be launched, basically to specify the location & command 
>>line of such custom simulator. Who may advise in this matter? I am 
>>willing to contribute with changes.
>
>Hi Mirela,
>
>I have asked a few people about this, because Hob is pretty much 
>deprecated at this point (it's being replaced by a web interface called 
>Toaster). They replied they would be willing to merge changes to Hob, 
>as long as they can be sure they won't cause any regressions.
>
>I hope this helps.
>
>Cheers
>
>Belén
>
>>
>> 
>>
>>The changes I anticipate would be necessary are:
>>
>>1.      
>>Changes in the GUI, somewhere in the python scripts from 
>>³poky\bitbake\lib\bb\ui\crumbs\², especially in imagedetailspage.py, 
>>maybe in builder.py
>>
>>2.      
>>Be more permissive with the types of images that are allowed to run.
>>Currently, there are these restrictions related to the name and 
>>extension of the image in ³poky\meta\classes\ image_types.bbclass², 
>>these need to be extended/customized:
>>
>>RUNNABLE_IMAGE_TYPES ?= "ext2 ext3"
>>
>>RUNNABLE_MACHINE_PATTERNS ?= "qemu"
>>
>>
>> 
>>
>>BTW, here is how Hob ³Image details² dialog currently looks like, see 
>>attached picture, note that the highlighted ³Run Image² button shows 
>>up only for qemu images.
>> 
>>
>>Regards,
>>
>>Mirela
>>
>> 
>>
>>
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: hob_run_custom_image_proposal.png
Type: image/png
Size: 111492 bytes
Desc: hob_run_custom_image_proposal.png
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20151224/f56a8f3b/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: builder.py
Type: application/octet-stream
Size: 68713 bytes
Desc: builder.py
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20151224/f56a8f3b/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: builder_____original.py
Type: application/octet-stream
Size: 65989 bytes
Desc: builder_____original.py
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20151224/f56a8f3b/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imagedetailspage_____original.py
Type: application/octet-stream
Size: 28935 bytes
Desc: imagedetailspage_____original.py
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20151224/f56a8f3b/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imagedetailspage.py
Type: application/octet-stream
Size: 31074 bytes
Desc: imagedetailspage.py
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20151224/f56a8f3b/attachment-0003.obj>