[cip-dev] B@D: iwg20m support

[tram.nguyen.xw@rvc.renesas.com (Tram Quynh Thi. Nguyen)]

Hi Daniel,

Thank you for your support.

Hi Zoran,

Thank you for your support.

I followed this guide to build for Renesas iwg20m board and got the results without errors: 
https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-cip-iwg20m/README.IWG20M.txt

Daniel got my idea.
In our environment, we use different SDK to compile c source to binary. 
That a reason why I asked for SDK.

Best regards,
Tram Nguyen

-----Original Message-----
From: Zoran S [mailto:zoran.stojsavljevic.de at gmail.com] 
Sent: Monday, March 26, 2018 2:55 PM
To: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>
Cc: Tram Quynh Thi. Nguyen <tram.nguyen.xw@rvc.renesas.com>; O365-Anh The. Tran <anh.tran.jc@renesas.com>; O365-Yasushi Onishi <yasushi.onishi.xc@renesas.com>; O365-Yoshinori Kaneko <yoshinori.kaneko.xg@renesas.com>; cip-dev at lists.cip-project.org; Binh Thanh. Nguyen <binh.nguyen.uw@rvc.renesas.com>; O365-Minh Thuy Dinh. Tran <minh.tran.xc@renesas.com>; O365-Chan Duc. Vu <chan.vu.xv@renesas.com>
Subject: Re: [cip-dev] B at D: iwg20m support

Hello Tram,

I have no idea what you are talking here (which problem with iwg20m), but if you (as Daniel mentioned) are dealing with YOCTO build, I finally (after in total 3 days of struggle) built one on Saturday (on my home network). I am just about (today) to test out of CIP YOCTO kernel 4.4.-x, initramfs.gpio.gz and .dtb.

It has nothing to do with Daniel's Sangorrin kas script (which is based upon configuration tool called kas - Siemens based - authors Jan Kiszka, Daniel Wagner and Henning Schill):
Kas iwg20d script is here:
https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-cip-bbb/kas-bbb.yml
.

I was NOT able to build it, due to the following error:
https://www.mail-archive.com/yocto at yoctoproject.org/msg39512.html

Rather, my YOCTO build has everything to do with:
https://elinux.org/RZ-G/Boards/Yocto_2.0

I compiled it... And have created loads for core-image-minimal and core-image-weston (weston is Wayland compositor, behind Wayland server protocol).

It is a bit peculiar environment required to build the outdated YOCTO... ;-)

Zoran
_______

On Mon, Mar 26, 2018 at 3:08 AM, Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp> wrote:
> Dear Tram,
>
>> -----Original Message-----
>> From: Tram Quynh Thi. Nguyen [mailto:tram.nguyen.xw at rvc.renesas.com]
>> Sent: Friday, March 23, 2018 11:34 PM
>> To: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>
>> Cc: cip-dev at lists.cip-project.org; O365-Chan Duc. Vu 
>> <chan.vu.xv@renesas.com>; O365-Minh Thuy Dinh. Tran 
>> <minh.tran.xc@renesas.com>; O365-Anh The. Tran 
>> <anh.tran.jc@renesas.com>; Binh Thanh. Nguyen 
>> <binh.nguyen.uw@rvc.renesas.com>; O365-Yoshinori Kaneko 
>> <yoshinori.kaneko.xg@renesas.com>; O365-Yasushi Onishi 
>> <yasushi.onishi.xc@renesas.com>
>> Subject: RE: [cip-dev] B at D: iwg20m support
>>
>> Dear Daniel-san,
>> CC all,
>>
>> Currently, I found below issue when running Test Cases on your environment or newest cip-core environment:
>> - Cannot run any binary files.
>> Reason: We use our SDK to build the binary files.
>>
>> Could you please share how to compile binary to run on this envionment?
>> Thank you for your support.
>
> To build the SDK use "bitbake meta-toolchain".
>
> Thanks,
> Daniel
>
>> -----Original Message-----
>> From: Trung. Huynh
>> Sent: Friday, January 12, 2018 9:16 AM
>> To: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>
>> Cc: cip-dev at lists.cip-project.org; O365-Chan Duc. Vu 
>> <chan.vu.xv@renesas.com>; O365-Minh Thuy Dinh. Tran 
>> <minh.tran.xc@renesas.com>; O365-Anh The. Tran 
>> <anh.tran.jc@renesas.com>; Binh Thanh. Nguyen 
>> <binh.nguyen.uw@rvc.renesas.com>; O365-Yoshinori Kaneko 
>> <yoshinori.kaneko.xg@renesas.com>; O365-Yasushi Onishi 
>> <yasushi.onishi.xc@renesas.com>; Tram Quynh Thi. Nguyen 
>> <tram.nguyen.xw@rvc.renesas.com>
>> Subject: RE: [cip-dev] B at D: iwg20m support
>>
>> Dear Daniel
>>
>> > -----Original Message-----
>> > From: Daniel Sangorrin [mailto:daniel.sangorrin at toshiba.co.jp]
>> > Sent: Thursday, January 11, 2018 12:50 PM
>> > To: Trung. Huynh <trung.huynh.uw@rvc.renesas.com>
>> > Cc: cip-dev at lists.cip-project.org; O365-Chan Duc. Vu 
>> > <chan.vu.xv@renesas.com>; O365-Minh Thuy Dinh. Tran 
>> > <minh.tran.xc@renesas.com>; O365-Anh The. Tran 
>> > <anh.tran.jc@renesas.com>; Binh Thanh. Nguyen 
>> > <binh.nguyen.uw@rvc.renesas.com>; O365-Yoshinori Kaneko 
>> > <yoshinori.kaneko.xg@renesas.com>; O365-Yasushi Onishi 
>> > <yasushi.onishi.xc@renesas.com>
>> > Subject: RE: [cip-dev] B at D: iwg20m support
>> >
>> > Dear Trung san,
>> >
>> > > -----Original Message-----
>> > > From: Trung. Huynh [mailto:trung.huynh.uw at rvc.renesas.com]
>> > ..
>> > > >
>> > > > Please let me confirm just in case. Am I right if I say that 
>> > > > you plan to you submit not only the kernel configuration flags 
>> > > > but also test dependency definitions to cip core, and the
>> corresponding yaml files for B at D?.
>> > > > If that's correct I will be glad to accept them.
>> > >
>> > > Yes, we would love to be apart in B at D with our contribution for who need to take our test suites as a testing plan.
>> > > We do not promise this is to become excellent suites but we do 
>> > > our best to have a good things that somebody to think about at 
>> > > first
>> >
>> > OK, that's great!
>> >
>> > > > > Regarding shmobile_defconfig, attachment shows up for you.
>> > > >
>> > > > Thanks, you only changed these flags right?
>> > > > CONFIG_BLK_DEV_RAM_SIZE=250000
>> > > > CONFIG_BLK_DEV_RAM_COUNT=4
>> > >
>> > > You're right, the cip-core I pulled down from global site without 
>> > > changing anything, it just be changed those flags and built under standalone of Linaro's cross compiler.
>> >
>> > I just realized that you might be using the wrong branch of cip-core. You should be using the "master" branch not the "jethro"
>> > one which was used and frozen for the cip-core release and the quickstart wiki page (the master branch depends on "morty").
>> > The jethro branch was using a non-official CIP kernel repository 
>> > (https://github.com/renesas-rz/renesas-cip) but on the master
>> branch we are using the official CIP kernel.  For that reason, 
>> shmobile_defconfig on the main branch is different and some drivers have not been merged yet.
>> > Please could you check which branch you are using?
>>
>> Is v4.4.55-cip3 the "Jethro" one? Because I saw this is the build I was use.
>>
>> >
>> > I have added your kernel configuration changes:
>> > https://gitlab.com/cip-project/cip-core/commit/c1efa6325909815731ab
>> > e0b
>> > 69ec7e19e2e56aee7 Please let me know if that works for you.
>>
>> Anyway, let get back to master branch with flags from your suggestion, the issue seems get to worse than previous one:
>> After uboot pull necessary packages on RAM up, it get stuck at:
>>
>> Starting kernel ...
>>
>> Nothing print out after this, so we didn't explore what occurring I 
>> also tried to test with v4.4.83-cip8 if any possibility to solve the 
>> problem but same things
>>
>> >
>> > Could you show me how you built cip-core using Linaro's cross compiler?
>> > By the way, cip-core builds its own toolchain, are you using Linaro's to reduce build time?
>>
>> In circle development process, we build up our target packages by 
>> Yocto But for this cip-core testing with B at D, I'm using the compiler which to be installed via Ubuntu's repository:
>> gcc version 4.8.4 (Ubuntu/Linaro 4.8.4-2ubuntu1~14.04.1)
>>
>> >
>> > Thanks,
>> > Daniel
>> >
>> > > > > > > -----Original Message-----
>> > > > > > > From: cip-dev-bounces at lists.cip-project.org
>> > > > > > > [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf 
>> > > > > > > Of Daniel Sangorrin
>> > > > > > > Sent: Tuesday, December 19, 2017 8:40 AM
>> > > > > > > To: 'Daniel Wagner' <daniel.wagner@siemens.com>
>> > > > > > > Cc: cip-dev at lists.cip-project.org
>> > > > > > > Subject: Re: [cip-dev] B at D: iwg20m support
>> > > > > > >
>> > > > > > > Dear Daniel Wagner,
>> > > > > > >
>> > > > > > > > -----Original Message-----
>> > > > > > > > From: Daniel Wagner [mailto:daniel.wagner at siemens.com]
>> > > > > > > > Sent: Monday, December 18, 2017 8:36 PM
>> > > > > > > > To: Daniel Sangorrin
>> > > > > > > > Cc: cip-dev at lists.cip-project.org
>> > > > > > > Subject: Re: [cip-dev] B at D: iwg20m support
>> > > > > > > >
>> > > > > > > > Hi Daniel,
>> > > > > > > >
>> > > > > > > > On 12/14/2017 06:57 AM, Daniel Sangorrin wrote:
>> > > > > > > > > Hi Trung-san, Robert and all
>> > > > > > > > >
>> > > > > > > > > I received the AWS credentials from Agustin and 
>> > > > > > > > > uploaded the cip-core binaries for the Renesas iwg20m board.
>> > > > > > > > >
>> > > > > > > > > https://s3-us-west-2.amazonaws.com/download.cip-project.
>> > > > > > > > > or
>> > > > > > > > > g/ci
>> > > > > > > > > p- co re /iwg20m/core-image-minimal-iwg20m.cpio.gz
>> > > > > > > > > https://s3-us-west-2.amazonaws.com/download.cip-project.
>> > > > > > > > > or
>> > > > > > > > > g/ci
>> > > > > > > > > p-
>> > > > > > > > > co
>> > > > > > > > > re
>> > > > > > > > > /iwg20m/r8a7743-iwg20d-q7.dtb 
>> > > > > > > > > https://s3-us-west-2.amazonaws.com/download.cip-project.
>> > > > > > > > > or
>> > > > > > > > > g/ci
>> > > > > > > > > p-
>> > > > > > > > > co
>> > > > > > > > > re
>> > > > > > > > > /iwg20m/uImage
>> > > > > > > >
>> > > > > > > > Just out of curiosity: how did you build the root fs? 
>> > > > > > > > The naming indicates that you used Yocto. I am still 
>> > > > > > > > setting up my test environment for rt testing and wrote two kas files to create me a root fs:
>> > > > > > > >
>> > > > > > > > https://github.com/igaw/cip-rt-misc/blob/master/docs/ka
>> > > > > > > > s-b
>> > > > > > > > bb
>> > > > > > > > .yml
>> > > > > > > > https://github.com/igaw/cip-rt-misc/blob/master/docs/ka
>> > > > > > > > s-m
>> > > > > > > > in
>> > > > > > > > nowb
>> > > > > > > > oa
>> > > > > > > > rd
>> > > > > > > > .y
>> > > > > > > > ml
>> > > > > > > >
>> > > > > > > > They are not self contained yet. Will fixed that right now.
>> > > > > > > > The idea that you can write
>> > > > > > > >
>> > > > > > > >         kas build kas-bbb.yml
>> > > > > > > >
>> > > > > > > > and you get a root fs for testing.
>> > > > > > >
>> > > > > > > The CIP Core rootfs was built using Deby (poky build 
>> > > > > > > system
>> > > > > > > + meta-debian). You can see a tutorial in the CIP wiki and a more up-to- date README and kas file in the source code.
>> > > > > > >
>> > > > > > > https://wiki.linuxfoundation.org/civilinfrastructureplatf
>> > > > > > > orm
>> > > > > > > /c
>> > > > > > > ip-c
>> > > > > > > or
>> > > > > > > e-
>> > > > > > > quickstart
>> > > > > > > https://gitlab.com/cip-project/cip-core/blob/master/deby/
>> > > > > > > pok
>> > > > > > > y/
>> > > > > > > meta
>> > > > > > > -c
>> > > > > > > ip
>> > > > > > > -iwg20m/README.IWG20M.txt 
>> > > > > > > https://gitlab.com/cip-project/cip-core/blob/master/deby/
>> > > > > > > pok
>> > > > > > > y/
>> > > > > > > meta
>> > > > > > > -c
>> > > > > > > ip
>> > > > > > > -iwg20m/kas-iwg20m.yml
>> > > > > > >
>> > > > > > > An overview of the CIP Core is here:
>> > > > > > > https://wiki.linuxfoundation.org/civilinfrastructureplatf
>> > > > > > > orm
>> > > > > > > /c
>> > > > > > > ip-c
>> > > > > > > or e
>> > > > > > > https://gitlab.com/cip-project/cip-core/blob/master/deby/
>> > > > > > > REA
>> > > > > > > DM
>> > > > > > > E.md
>> > > > > > >
>> > > > > > > For the BBB please check this other Readme and kas file:
>> > > > > > > https://gitlab.com/cip-project/cip-core/blob/master/deby/
>> > > > > > > pok
>> > > > > > > y/
>> > > > > > > meta
>> > > > > > > -c
>> > > > > > > ip
>> > > > > > > -bbb/README.BBB.txt
>> > > > > > > https://gitlab.com/cip-project/cip-core/blob/master/deby/
>> > > > > > > pok
>> > > > > > > y/
>> > > > > > > meta
>> > > > > > > -c
>> > > > > > > ip
>> > > > > > > -bbb/kas-bbb.yml
>> > > > > > >
>> > > > > > > You can add the packages "openssh nfs-utils rt-tests strace procps", they are available in meta-debian.
>> > > > > > >
>> > > > > > > Unfortunately, you cannot simply add "meta-qt5" because 
>> > > > > > > it may conflict with meta-debian. Instead you would need 
>> > > > > > > to use meta- debian qt5 recipes (only if you really need 
>> > > > > > > qt5 for
>> testing RT).
>> > > > > > >
>> > > > > > > Thanks,
>> > > > > > > Daniel Sangorrin
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > _______________________________________________
>> > > > > > > cip-dev mailing list
>> > > > > > > cip-dev at lists.cip-project.org 
>> > > > > > > https://lists.cip-project.org/mailman/listinfo/cip-dev
>> > > > > >
>> > > > > >
>> > > > >
>> > > > >
>> > >
>> > >
>> >
>
>
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev