Re: Unable to access toaster server - Regarding

["Reyna, David" <david.reyna@windriver.com>]

[-- Attachment #1: Type: text/plain, Size: 8830 bytes --]

Hi Surendra ,

> "I'm able to see only the Jethro and Krogoth builds in my toaster interfaces"

It is obvious from the screen shot that you are working with an old version of YP. That explains why your git branch error was against "Krogoth" which is YP-2.1 (April 2016), where we are currently at YP-2.4.

Unless you have a business reason to use that old release, I strongly recommend using the current version.


  $ git clone git://git.yoctoproject.org/poky && cd poky
  $ . oe-init-build-env
  $ . toaster start webport=0.0.0.0:8000

If you are required to use Krogoth, then we need to do deeper debugging. For example, I would need the "toaster_runbuilds.log" file in the project directory to see exactly the layer that does seem to have the branch that you are trying to pull.

- David

From: Ponguru Surendranath [mailto:Ponguru.S@nestgroup.net]
Sent: Friday, October 20, 2017 6:31 AM
To: Reyna, David
Cc: toaster@yoctoproject.org
Subject: RE: Unable to access toaster server - Regarding

Hello David,

Thank you for your wonderful help.

After exploring a little, I tired adding a custom layer to the image on a different build (Krogoth) on Toaster. I've imported the layer gpsnavi-agl as a custom layer.
As suggested from the video to create custom layer<https://www.youtube.com/watch?v=QJzaE_XjX5c> that is referenced<http://www.yoctoproject.org/docs/latest/toaster-manual/toaster-manual.html#web-interface-videos> in Toaster user manual v2.4, I figured out that navi_0.0.7.bb and navidata_0.0.7.bb are the recipes available in the layer. I get the error mentioned in the screenshot attached. I followed the same steps, but this time for Krogoth build, as I've mentioned in the previous mails. Please help me to correct this.

On the other hand, I'm able to see only the Jethro and Krogoth builds in my toaster interfaces; the screenshot is attached (Printscreen is unable to capture the pulldown menu!). Can you suggest me how to cope up with the master branch, if possible?

Happy Weekend!!



Regards,
Surendra.
Siliconupdates<siliconupdates.blogspot.com>




From: Reyna, David [mailto:david.reyna@windriver.com]
Sent: Friday, October 20, 2017 4:18 AM
To: Ponguru Surendranath
Cc: toaster@yoctoproject.org<mailto:toaster@yoctoproject.org>
Subject: RE: Unable to access toaster server - Regarding

Hi Surendra,

1. "Toaster is now working fine. Instead of pip3, I used pip and this resolved the issue."

I am glad that it is working now. The resolution is interesting. With YP-2.2 we all moved to Python3, which is why we now use pip3 instead of just pip. I wonder what host and version you have.

2. "My requirement is to build agl-demo-platform image. But, I couldn't find it in the image recipes"

When I just now created a project against project against "Rocko" I did not see the image recipe "agl-demo-platform image", but when I create it against "master" I do!

It is often the case that all these layers take a while to get the latest and greatest branches configured. So, I recommend working with "master" until things stabilize more for Rocko.

- David

From: Ponguru Surendranath [mailto:Ponguru.S@nestgroup.net]
Sent: Thursday, October 19, 2017 4:35 AM
To: Reyna, David
Cc: toaster@yoctoproject.org<mailto:toaster@yoctoproject.org>
Subject: RE: Unable to access toaster server - Regarding

Thank you very much, David, for the prompt reply.


1.       Toaster is now working fine. Instead of pip3, I used pip and this resolved the issue.

2.       Yes, toaster server has connected once. When I clicked on 'New Project' button, I got the error mentioned in the previous screenshot.

3.       After I used pip, I'm able to clone all the versions.

After creating a new project in Toaster, I've added the required meta layers and configured the Bitbake variables as you see the attachment.
My requirement is to build agl-demo-platform image. But, I couldn't find it in the image recipes. So, for time being, I tried building core-image-minimal, for which I go the error attached. Please help.
Also, if there are any beginner mistakes, please suggest how to correct them.


Regards,
Surendra.
Siliconupdates<siliconupdates.blogspot.com>



From: Reyna, David [mailto:david.reyna@windriver.com]
Sent: Thursday, October 19, 2017 1:00 PM
To: Ponguru Surendranath
Cc: toaster@yoctoproject.org<mailto:toaster@yoctoproject.org>
Subject: RE: Unable to access toaster server - Regarding

Hi Surendra,

I have not seen this bug before.

1) Try these exact instructions to start Toaster, in case there is something lost in translation. This will start Toaster in the default ".../poky/build" directory.


$ cd poky

$ source oe-init-build-env

$ source toaster start

2) It appears that you got Toaster to connect, but then when you tried to create a new project you got the error in the screen shot?

3) Do you get the same problem if you clone against Pyro?

I will re-test Toaster against Rocko just in case some last minute fix broke something.


- David


From: toaster-bounces@yoctoproject.org<mailto:toaster-bounces@yoctoproject.org> [mailto:toaster-bounces@yoctoproject.org] On Behalf Of Ponguru Surendranath
Sent: Wednesday, October 18, 2017 10:40 PM
To: toaster@yoctoproject.org<mailto:toaster@yoctoproject.org>
Subject: [Toaster] Unable to access toaster server - Regarding

Hi there,

I'm a beginner for toaster. The following are the steps I've followed to use toaster.


*         sudo apt-get install python3-pip

*         git clone -b rocko git://git.yoctoproject.org/poky.git

*         cd poky

*         sudo pip3 install -r /home/ntp-152/surendra/poky/bitbake/toaster-requirements.txt

*         source /path/to/oe-init-build-env /path/to/build/dir

*         source toaster start
After this I opened the URL http://localhost:8000. But, I'm see an error on this and the screenshot of error is attached. Also, the toaster-requirements.txt is also attached. Please help.




Regards,
Surendra.
Siliconupdates<siliconupdates.blogspot.com>

________________________________

Confidentiality Statement / Disclaimer : This message and any attachments is intended for the sole use of the intended recipient. It may contain confidential information. Any unauthorized use, dissemination or modification is strictly prohibited. If you are not the intended recipient, please notify the sender immediately then delete it from all your systems, and do not copy, use or print. Internet communications are not secure and it is the responsibility of the recipient to make sure that it is virus/malicious code exempt.

The company/sender cannot be responsible for any unauthorized alterations or modifications made to the contents. If you require any form of confirmation of the contents, please contact the company/sender. The company/sender is not liable for any errors or omissions in the content of this message.

________________________________
________________________________

Confidentiality Statement / Disclaimer : This message and any attachments is intended for the sole use of the intended recipient. It may contain confidential information. Any unauthorized use, dissemination or modification is strictly prohibited. If you are not the intended recipient, please notify the sender immediately then delete it from all your systems, and do not copy, use or print. Internet communications are not secure and it is the responsibility of the recipient to make sure that it is virus/malicious code exempt.

The company/sender cannot be responsible for any unauthorized alterations or modifications made to the contents. If you require any form of confirmation of the contents, please contact the company/sender. The company/sender is not liable for any errors or omissions in the content of this message.

________________________________
________________________________

Confidentiality Statement / Disclaimer : This message and any attachments is intended for the sole use of the intended recipient. It may contain confidential information. Any unauthorized use, dissemination or modification is strictly prohibited. If you are not the intended recipient, please notify the sender immediately then delete it from all your systems, and do not copy, use or print. Internet communications are not secure and it is the responsibility of the recipient to make sure that it is virus/malicious code exempt.

The company/sender cannot be responsible for any unauthorized alterations or modifications made to the contents. If you require any form of confirmation of the contents, please contact the company/sender. The company/sender is not liable for any errors or omissions in the content of this message.

________________________________

[-- Attachment #2: Type: text/html, Size: 26540 bytes --]