[cip-dev] B@D: iwg20m support

[cip-dev] B@D: iwg20m support

[Daniel Sangorrin]

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.org/cip-core/iwg20m/core-image-minimal-iwg20m.cpio.gz
https://s3-us-west-2.amazonaws.com/download.cip-project.org/cip-core/iwg20m/r8a7743-iwg20d-q7.dtb
https://s3-us-west-2.amazonaws.com/download.cip-project.org/cip-core/iwg20m/uImage

You will need to patch the master branch of the B at D git
repository with the next three patches. Please re-install
from the latest code just to make sure we are on the same page.
Robert: please, could you ask Tom to merge them?

[PATCH 1/3] Vagrantfile: support the http proxy plugin
[PATCH 2/3] iwg20m: add device type and dictionary template
[PATCH 3/3] iwg20m: add a test that boots a cip-core ramdisk

Making it work is a bit complicated so I have prepared a guide
for you. Check it below and make sure you don't skip any step or
modify any file without a reason.

Regards,
Daniel

Enabling Renesas board
======================

Prepare your IP Power 9258 PDU
    - Set the password
    - Set the IP address to 192.168.11.68

Virtualbox serial port (ser2net) setup
    host$ sudo apt install virtualbox-ext-pack
    host$ sudo adduser <user> vboxusers
    - Oracle VM Virtualbox manager
        Settings > USB > add the device USB-UART device
        (/dev/ttyUSB1 on the host will become /dev/ttyUSB0 inside the VM)

Prepare network interfaces for tftp and for controlling the remote power switch (PDU)
    host$ vagrant up
    host$ vagrant ssh
    vagrant$ sudo -s
    vagrant# ifconfig eth1:1 192.168.11.76/24 <-- PDU ip: 192.168.11.68
    vagrant# export no_proxy="192.168.11.68, $no_proxy"
    vagrant# curl http://admin:<password>@192.168.11.68/set.cmd?cmd=setpower+p61=1 (switch on)
    vagrant# curl http://admin:<password>@192.168.11.68/set.cmd?cmd=setpower+p61=0 (switch off)

Check ser2net is working
    vagrant# curl http://admin:<password>@192.168.11.68/set.cmd?cmd=setpower+p61=1 (switch on)
    vagrant# telnet localhost 8020
        [IMP] you should be able to see u-boot and kernel messages
        [Note] to quit: Ctrl-] and quit

Prepare the tftp server
    host$ sudo service tftpd-hpa stop <-- to avoid conflicts

Check the status of the device
    - make sure that your device type definitions are updated
        vagrant# less /etc/lava-server/dispatcher-config/device-types/renesas-iwg20m.jinja2 <-- renesas-iwg20m.jinja2
        vagrant# less /etc/lava-server/dispatcher-config/devices/iwg20m01.jinja2 <-- myiwg20m.jinja2
    - check the workers
        vagrant# lava-server manage workers list
            Workers:
                * stretch.localdomain (3 devices) (master) <-- hostname --long
    - check the device list
        vagrant# lava-server manage device-types list
            * beaglebone-black (1 devices)
            * qemu (1 devices)
            * renesas-iwg20m (1 devices)

Changing SERVER_IP so that the target downloads from the proper address
    - SERVER_IP corresponds to the address of the dispatcher
    - LAVA V2 settings
        Ref: https://validation.linaro.org/static//docs/v2/pipeline-admin.html#extra-dispatcher-configuration
        vagrant# cp /usr/share/lava-dispatcher/dispatcher.yaml /etc/lava-server/dispatcher.d/stretch.localdomain.yaml <-- the name of the worker!!
        vagrant# vi /etc/lava-server/dispatcher.d/stretch.localdomain.yaml
            dispatcher_ip: 192.168.1.66
        vagrant# ifconfig eth1:2 192.168.1.66/24
        vagrant# service lava-server restart
        vagrant# service lava-slave restart
        vagrant# service tftpd-hpa restart

Add binaries to the kernel-ci storage server
    host$ cp -rf path/to/binaries board-at-desk-single-dev/
        [Note] The binaries must be as follows (see test definition):
            - iwg20m/r8a7743-iwg20d-q7.dtb (rename from uImage-r8a7743-iwg20d-q7.dtb)
            - iwg20m/uImage
            - iwg20m/core-image-minimal-iwg20m.cpio.gz
        [Note] You can download them from here
            https://s3-us-west-2.amazonaws.com/download.cip-project.org/cip-core/iwg20m/core-image-minimal-iwg20m.cpio.gz
            https://s3-us-west-2.amazonaws.com/download.cip-project.org/cip-core/iwg20m/r8a7743-iwg20d-q7.dtb
            https://s3-us-west-2.amazonaws.com/download.cip-project.org/cip-core/iwg20m/uImage
    host$ cd board-at-desk-single-dev/
    host$ vagrant rsync
    vagrant# cp -r /vagrant/binaries/iwg20m/ /var/www/images/kernel-ci/
    vagrant# ls /var/www/images/kernel-ci/iwg20m/
        core-image-minimal-iwg20m.cpio.gz  r8a7743-iwg20d-q7.dtb  uImage
        [Note] Use http://localhost:8010/iwg20m/ in the tests
    vagrant# service nginx restart

Login into LAVA
    host$ firefox http://localhost:8080/
        lavauser:mylava1234
        Scheduler > Submit job
            - Copy and paste tests/iwg20m-test-ramdisk.yaml
            - It should work as follows:
                + LAVA causes the board to switch on
                + LAVA downloads the kernel/dt/ramdisk from the storage server
                  and overlays necessary LAVA binaries
                + LAVA interrupts u-boot and executes 'run bootcmd'
                + The board downloads the files by TFTPBOOT
                + LAVA detects the login prompt and logs in
                + LAVA detects the shell prompt and executes its test (uname -a)
                + LAVA causes the board to switch off
                (IT WORKS)

[cip-dev] [PATCH 1/3] Vagrantfile: support the http proxy plugin

[Daniel Sangorrin]

The proxy settings are collected from the environment.

Signed-off-by: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>
---
 Vagrantfile | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/Vagrantfile b/Vagrantfile
index 2771600..1e1a491 100644
--- a/Vagrantfile
+++ b/Vagrantfile
@@ -23,6 +23,11 @@ SCRIPT
 Vagrant.configure(2) do |config|
   config.vm.provider :virtualbox do |vbox, override|
     config.vm.box = "debian/stretch64"
+    if Vagrant.has_plugin?("vagrant-proxyconf")
+      config.proxy.http     = ENV["http_proxy"]
+      config.proxy.https    = ENV["https_proxy"]
+      config.proxy.no_proxy = ENV["no_proxy"]
+    end
     
     vbox.customize ["modifyvm", :id, "--vram", "12"]
     vbox.customize ["modifyvm", :id, "--memory", "2048"]
-- 
2.7.4

[cip-dev] [PATCH 2/3] iwg20m: add device type and dictionary template

[Daniel Sangorrin]

The user will have to modify myiwg20m.jinja2 according
to its environment (ip address, PDU, etc)

Signed-off-by: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>
---
 device-dictionary/myiwg20m.jinja2     |  9 +++++++++
 device-types/renesas-iwg20m.jinja2    | 15 +++++++++++++++
 integration-scripts/configure_lava.sh |  6 ++++++
 3 files changed, 30 insertions(+)
 create mode 100644 device-dictionary/myiwg20m.jinja2
 create mode 100644 device-types/renesas-iwg20m.jinja2

diff --git a/device-dictionary/myiwg20m.jinja2 b/device-dictionary/myiwg20m.jinja2
new file mode 100644
index 0000000..fc0de62
--- /dev/null
+++ b/device-dictionary/myiwg20m.jinja2
@@ -0,0 +1,9 @@
+{% extends 'renesas-iwg20m.jinja2' %}
+{% set connection_command = 'telnet localhost 8020' %}
+{% set power_on_command = 'curl http://admin:<password>@<ip>/set.cmd?cmd=setpower+p61=1' %}
+{% set power_off_command = 'curl http://admin:<password>@<ip>/set.cmd?cmd=setpower+p61=0' %}
+{% set hard_reset_command = 'curl http://admin:<password>@<ip>/set.cmd?cmd=setpower+p61=0; curl http://admin:12345678 at 192.168.11.68/set.cmd?cmd=setpower+p61=1' %}
+{% set test_delay = 500 %}
+{% set uboot_ipaddr_cmd = 'setenv ipaddr 192.168.1.55' %}
+{% set base_ip_args = 'ip=192.168.1.55' %}
+{% set extra_kernel_args = 'ignore_loglevel vmalloc=384M' %}
diff --git a/device-types/renesas-iwg20m.jinja2 b/device-types/renesas-iwg20m.jinja2
new file mode 100644
index 0000000..f1506ae
--- /dev/null
+++ b/device-types/renesas-iwg20m.jinja2
@@ -0,0 +1,15 @@
+{% extends 'base-uboot.jinja2' %}
+
+{% set console_device = console_device|default('ttySC0') %}
+{% set baud_rate = baud_rate|default(115200) %}
+{% set device_type = "renesas-iwg20m" %}
+{% set bootloader_prompt = bootloader_prompt|default('iWave-G20M >') %}
+{% set kernel_file = kernel_file | default('uImage') %}
+{% set dtb_file = dtb_file | default('r8a7743-iwg20d-q7.dtb') %}
+{% set bootm_kernel_addr = '0x40007fc0' %}
+{% set bootm_ramdisk_addr = '0x41000000' %}
+{% set bootm_dtb_addr = '0x40f00000' %}
+{% set bootz_kernel_addr = '0x40007fc0' %}
+{% set bootz_ramdisk_addr = '0x81600000' %}
+{% set bootz_dtb_addr = '0x40f00000' %}
+{% set uboot_mkimage_arch = 'arm' %}
diff --git a/integration-scripts/configure_lava.sh b/integration-scripts/configure_lava.sh
index 8d75b76..b13acdd 100755
--- a/integration-scripts/configure_lava.sh
+++ b/integration-scripts/configure_lava.sh
@@ -51,6 +51,12 @@ sudo DEBIAN_FRONTEND=noninteractive cp mybbb.dat /etc/lava-server/dispatcher-con
 sudo DEBIAN_FRONTEND=noninteractive chown lavaserver.lavaserver /etc/lava-server/dispatcher-config/devices/*
 # lava-tool device-dictionary --update mybbb.dat http://lavauser at localhost:8080/RPC2 bbb01
 
+# Renesas iwg20m
+sudo DEBIAN_FRONTEND=noninteractive cp -v /vagrant/device-types/renesas-iwg20m.jinja2 /etc/lava-server/dispatcher-config/device-types/
+sudo DEBIAN_FRONTEND=noninteractive lava-server manage device-types add renesas-iwg20m
+sudo DEBIAN_FRONTEND=noninteractive lava-server manage devices add --device-type renesas-iwg20m --worker $(hostname --long) iwg20m01
+sudo DEBIAN_FRONTEND=noninteractive cp -v /vagrant/device-dictionary/myiwg20m.jinja2 /etc/lava-server/dispatcher-config/devices/iwg20m01.jinja2
+
 # Change the default shutdown message for kernel v4.4 - comment these lines out if using older kernel with a Shutdown message of "The system is going down for reboot NOW"
 cd /usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/utils/
 sudo DEBIAN_FRONTEND=noninteractive sed -ie "/SHUTDOWN_MESSAGE/s/The system is going down for reboot NOW/Restarting system/" constants.py
-- 
2.7.4

[cip-dev] [PATCH 2/3] iwg20m: add device type and dictionary template

[Daniel Sangorrin]

> -----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: Thursday, December 14, 2017 2:57 PM
> To: cip-dev at lists.cip-project.org
> Subject: [cip-dev] [PATCH 2/3] iwg20m: add device type and dictionary template
> 
> The user will have to modify myiwg20m.jinja2 according
> to its environment (ip address, PDU, etc)
> 
> Signed-off-by: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>
> ---
>  device-dictionary/myiwg20m.jinja2     |  9 +++++++++
>  device-types/renesas-iwg20m.jinja2    | 15 +++++++++++++++
>  integration-scripts/configure_lava.sh |  6 ++++++
>  3 files changed, 30 insertions(+)
>  create mode 100644 device-dictionary/myiwg20m.jinja2
>  create mode 100644 device-types/renesas-iwg20m.jinja2
> 
> diff --git a/device-dictionary/myiwg20m.jinja2 b/device-dictionary/myiwg20m.jinja2
> new file mode 100644
> index 0000000..fc0de62
> --- /dev/null
> +++ b/device-dictionary/myiwg20m.jinja2
> @@ -0,0 +1,9 @@
> +{% extends 'renesas-iwg20m.jinja2' %}
> +{% set connection_command = 'telnet localhost 8020' %}
> +{% set power_on_command = 'curl http://admin:<password>@<ip>/set.cmd?cmd=setpower+p61=1' %}
> +{% set power_off_command = 'curl http://admin:<password>@<ip>/set.cmd?cmd=setpower+p61=0' %}
> +{% set hard_reset_command = 'curl http://admin:<password>@<ip>/set.cmd?cmd=setpower+p61=0; curl
> http://admin:12345678 at 192.168.11.68/set.cmd?cmd=setpower+p61=1' %}

Sorry, please change "12345678" to <password>

> +{% set test_delay = 500 %}
> +{% set uboot_ipaddr_cmd = 'setenv ipaddr 192.168.1.55' %}
> +{% set base_ip_args = 'ip=192.168.1.55' %}
> +{% set extra_kernel_args = 'ignore_loglevel vmalloc=384M' %}
> diff --git a/device-types/renesas-iwg20m.jinja2 b/device-types/renesas-iwg20m.jinja2
> new file mode 100644
> index 0000000..f1506ae
> --- /dev/null
> +++ b/device-types/renesas-iwg20m.jinja2
> @@ -0,0 +1,15 @@
> +{% extends 'base-uboot.jinja2' %}
> +
> +{% set console_device = console_device|default('ttySC0') %}
> +{% set baud_rate = baud_rate|default(115200) %}
> +{% set device_type = "renesas-iwg20m" %}
> +{% set bootloader_prompt = bootloader_prompt|default('iWave-G20M >') %}
> +{% set kernel_file = kernel_file | default('uImage') %}
> +{% set dtb_file = dtb_file | default('r8a7743-iwg20d-q7.dtb') %}
> +{% set bootm_kernel_addr = '0x40007fc0' %}
> +{% set bootm_ramdisk_addr = '0x41000000' %}
> +{% set bootm_dtb_addr = '0x40f00000' %}
> +{% set bootz_kernel_addr = '0x40007fc0' %}
> +{% set bootz_ramdisk_addr = '0x81600000' %}
> +{% set bootz_dtb_addr = '0x40f00000' %}
> +{% set uboot_mkimage_arch = 'arm' %}
> diff --git a/integration-scripts/configure_lava.sh b/integration-scripts/configure_lava.sh
> index 8d75b76..b13acdd 100755
> --- a/integration-scripts/configure_lava.sh
> +++ b/integration-scripts/configure_lava.sh
> @@ -51,6 +51,12 @@ sudo DEBIAN_FRONTEND=noninteractive cp mybbb.dat /etc/lava-server/dispatcher-con
>  sudo DEBIAN_FRONTEND=noninteractive chown lavaserver.lavaserver /etc/lava-server/dispatcher-config/devices/*
>  # lava-tool device-dictionary --update mybbb.dat http://lavauser at localhost:8080/RPC2 bbb01
> 
> +# Renesas iwg20m
> +sudo DEBIAN_FRONTEND=noninteractive cp -v /vagrant/device-types/renesas-iwg20m.jinja2 /etc/lava-server/dispatcher-
> config/device-types/
> +sudo DEBIAN_FRONTEND=noninteractive lava-server manage device-types add renesas-iwg20m
> +sudo DEBIAN_FRONTEND=noninteractive lava-server manage devices add --device-type renesas-iwg20m --worker $(hostname --
> long) iwg20m01
> +sudo DEBIAN_FRONTEND=noninteractive cp -v /vagrant/device-dictionary/myiwg20m.jinja2 /etc/lava-server/dispatcher-
> config/devices/iwg20m01.jinja2
> +
>  # Change the default shutdown message for kernel v4.4 - comment these lines out if using older kernel with a Shutdown message of
> "The system is going down for reboot NOW"
>  cd /usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/utils/
>  sudo DEBIAN_FRONTEND=noninteractive sed -ie "/SHUTDOWN_MESSAGE/s/The system is going down for reboot NOW/Restarting
> system/" constants.py
> --
> 2.7.4
> 
> 
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev

[cip-dev] [PATCH 3/3] iwg20m: add a test that boots a cip-core ramdisk

[Daniel Sangorrin]

Signed-off-by: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>
---
 tests/iwg20m-test-ramdisk.yaml | 76 ++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 76 insertions(+)
 create mode 100644 tests/iwg20m-test-ramdisk.yaml

diff --git a/tests/iwg20m-test-ramdisk.yaml b/tests/iwg20m-test-ramdisk.yaml
new file mode 100644
index 0000000..f016ea7
--- /dev/null
+++ b/tests/iwg20m-test-ramdisk.yaml
@@ -0,0 +1,76 @@
+# Copyright (C) 2017, Codethink, Ltd., Robert Marshall <robert.marshall@codethink.co.uk>
+# Copyright (C) 2017, Toshiba corp., Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>
+# SPDX-License-Identifier:	AGPL-3.0
+# This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, version 3.
+# This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details.
+
+# You should have received a copy of the GNU Affero General Public License along with this program. If not, see <http://www.gnu.org/licenses/>.
+
+device_type: renesas-iwg20m
+job_name: Kernel version test
+timeouts:
+  job:
+    minutes: 10
+  action:
+    minutes: 5
+  connection:
+    minutes: 2
+priority: medium
+visibility: public
+
+
+# ACTION_BLOCK
+actions:
+- deploy:
+    timeout:
+      minutes: 4
+    to: tftp
+    os: oe
+    kernel:
+      url: http://localhost:8010/iwg20m/uImage
+      type: uImage
+    ramdisk:
+      url: http://localhost:8010/iwg20m/core-image-minimal-iwg20m.cpio.gz
+      compression: gz
+      # the bootloader needs a u-boot header on the modified ramdisk
+      add-header: u-boot
+    #modules:
+    #  url: http://localhost:8010/iwg20m/modules-iwg20m.tgz
+    #  compression: gz
+    dtb:
+      url: http://localhost:8010/iwg20m/r8a7743-iwg20d-q7.dtb
+
+# BOOT_BLOCK
+- boot:
+    auto_login:
+      login_prompt: '\(none\) login: '
+      username: root
+    prompts:
+      - 'cip# '
+    method: u-boot
+    commands: ramdisk
+    type: uimage
+    timeout:
+      minutes: 1
+
+# TEST_BLOCK
+- test:
+    timeout:
+      minutes: 5
+    definitions:
+    - repository:
+        metadata:
+          format: Lava-Test Test Definition 1.0
+          name: kernel-version-basic
+          version: "1.0"
+          description: "check kernel version"
+          os:
+            - oe
+          scope:
+            - functional
+        run:
+          steps:
+            - lava-test-case uname --shell uname -a
+      from: inline
+      name: kernel-version-inline
+      path: inline/kernel-version-basic.yaml
-- 
2.7.4

[cip-dev] B@D: iwg20m support

[Daniel Wagner]

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.org/cip-core/iwg20m/core-image-minimal-iwg20m.cpio.gz
> https://s3-us-west-2.amazonaws.com/download.cip-project.org/cip-core/iwg20m/r8a7743-iwg20d-q7.dtb
> https://s3-us-west-2.amazonaws.com/download.cip-project.org/cip-core/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/kas-bbb.yml
https://github.com/igaw/cip-rt-misc/blob/master/docs/kas-minnowboard.yml

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.

Thanks,
Daniel

[cip-dev] B@D: iwg20m support

[Daniel Sangorrin]

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.org/cip-core/iwg20m/core-image-minimal-iwg20m.cpio.gz
> > https://s3-us-west-2.amazonaws.com/download.cip-project.org/cip-core/iwg20m/r8a7743-iwg20d-q7.dtb
> > https://s3-us-west-2.amazonaws.com/download.cip-project.org/cip-core/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/kas-bbb.yml
> https://github.com/igaw/cip-rt-misc/blob/master/docs/kas-minnowboard.yml
> 
> 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/civilinfrastructureplatform/cip-core-quickstart
https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-cip-iwg20m/README.IWG20M.txt
https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-cip-iwg20m/kas-iwg20m.yml

An overview of the CIP Core is here:
https://wiki.linuxfoundation.org/civilinfrastructureplatform/cip-core
https://gitlab.com/cip-project/cip-core/blob/master/deby/README.md

For the BBB please check this other Readme and kas file:
https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-cip-bbb/README.BBB.txt
https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-cip-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] B@D: iwg20m support

[Trung. Huynh]

Dear Daniel,

One important thing is how big is root fs size get maximal? Is it limited?
Your configuration on iwg20m is to assign 8 ramdisks with enlargement of each block 100MB approx:

CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=8
CONFIG_BLK_DEV_RAM_SIZE=102400
CONFIG_EXT4_FS=y
CONFIG_EXT4_USE_FOR_EXT2=y
CONFIG_USB_XHCI_RCAR=n

If we try to test more function as our wish (more dependencies in ramdisk), assuming that the root fs size could be 150MB.
For G1M 1GB of RAM, just increase CONFIG_BLK_DEV_RAM_SIZE to 250000 and reduce CONFIG_BLK_DEV_RAM_COUNT to 4 iWave.

-> Output is booting failed, attachment to show what occurring.

Regards,
Trung

-----Original Message-----
From: cip-dev-bounces@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.org/cip-core
> > /iwg20m/core-image-minimal-iwg20m.cpio.gz
> > https://s3-us-west-2.amazonaws.com/download.cip-project.org/cip-core
> > /iwg20m/r8a7743-iwg20d-q7.dtb 
> > https://s3-us-west-2.amazonaws.com/download.cip-project.org/cip-core
> > /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/kas-bbb.yml
> https://github.com/igaw/cip-rt-misc/blob/master/docs/kas-minnowboard.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/civilinfrastructureplatform/cip-core-quickstart
https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-cip-iwg20m/README.IWG20M.txt
https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-cip-iwg20m/kas-iwg20m.yml

An overview of the CIP Core is here:
https://wiki.linuxfoundation.org/civilinfrastructureplatform/cip-core
https://gitlab.com/cip-project/cip-core/blob/master/deby/README.md

For the BBB please check this other Readme and kas file:
https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-cip-bbb/README.BBB.txt
https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-cip-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] B@D: iwg20m support

[Daniel Sangorrin]

Dear Trung san,

First of all, please could you give me some feedback about the LAVA configuration files and AWS links that I sent to the list before holidays?. Did you try them and did they work for you?.

See my answers below.

> -----Original Message-----
> From: Trung. Huynh [mailto:trung.huynh.uw at rvc.renesas.com]
> Sent: Tuesday, January 02, 2018 6:37 PM
> To: Daniel Sangorrin
> Cc: cip-dev at lists.cip-project.org; O365-Chan Duc. Vu; O365-Minh Thuy Dinh. Tran; O365-Anh The. Tran; Binh Thanh. Nguyen; O365-
> Yoshinori Kaneko; O365-Yasushi Onishi
> Subject: RE: [cip-dev] B at D: iwg20m support
> 
> Dear Daniel,
> 
> One important thing is how big is root fs size get maximal? Is it limited?
> Your configuration on iwg20m is to assign 8 ramdisks with enlargement of each block 100MB approx:
> 
> CONFIG_BLK_DEV_RAM=y
> CONFIG_BLK_DEV_RAM_COUNT=8
> CONFIG_BLK_DEV_RAM_SIZE=102400
> CONFIG_EXT4_FS=y
> CONFIG_EXT4_USE_FOR_EXT2=y
> CONFIG_USB_XHCI_RCAR=n

Currently, "my configuration" is just the mainstream shmobile_defconfig (as suggested by Chris if I remember correctly). If you need to change the default
configuration on cip-core upstream, please send me a defconfig (make savedefconfig) or a list of configuration options that
should be added to shmobile_defconfig. However, in this case I think those options are very dependent on what you are putting on your filesystem so it might
be a better idea if you create your own private branch and change the configuration as you need.

If you actually plan to submit the tests/dependencies to cip-core then adding those config options to cip-core would actually make sense. Is this your plan?

> If we try to test more function as our wish (more dependencies in ramdisk), assuming that the root fs size could be 150MB.
> For G1M 1GB of RAM, just increase CONFIG_BLK_DEV_RAM_SIZE to 250000 and reduce CONFIG_BLK_DEV_RAM_COUNT to 4 iWave.

By the way, you might also need to modify the u-boot settings so that the ramdisk does not overlap with the kernel or the device tree. And the LAVA configuration files.

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.org/cip-core
> > > /iwg20m/core-image-minimal-iwg20m.cpio.gz
> > > https://s3-us-west-2.amazonaws.com/download.cip-project.org/cip-core
> > > /iwg20m/r8a7743-iwg20d-q7.dtb
> > > https://s3-us-west-2.amazonaws.com/download.cip-project.org/cip-core
> > > /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/kas-bbb.yml
> > https://github.com/igaw/cip-rt-misc/blob/master/docs/kas-minnowboard.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/civilinfrastructureplatform/cip-core-quickstart
> https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-cip-iwg20m/README.IWG20M.txt
> https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-cip-iwg20m/kas-iwg20m.yml
> 
> An overview of the CIP Core is here:
> https://wiki.linuxfoundation.org/civilinfrastructureplatform/cip-core
> https://gitlab.com/cip-project/cip-core/blob/master/deby/README.md
> 
> For the BBB please check this other Readme and kas file:
> https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-cip-bbb/README.BBB.txt
> https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-cip-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] B@D: iwg20m support

[Trung. Huynh]

Dear Daniel,

Yes, I tried it and working well, but I want to custom some devices under kernel layer to execute our test cases as well as packing some dependencies
To do that I must expand file system that why I got this issue.

Regards,
Trung

-----Original Message-----
From: Daniel Sangorrin [mailto:daniel.sangorrin at toshiba.co.jp] 
Sent: Tuesday, January 9, 2018 3:41 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,

First of all, please could you give me some feedback about the LAVA configuration files and AWS links that I sent to the list before holidays?. Did you try them and did they work for you?.

See my answers below.

> -----Original Message-----
> From: Trung. Huynh [mailto:trung.huynh.uw at rvc.renesas.com]
> Sent: Tuesday, January 02, 2018 6:37 PM
> To: Daniel Sangorrin
> Cc: cip-dev at lists.cip-project.org; O365-Chan Duc. Vu; O365-Minh Thuy 
> Dinh. Tran; O365-Anh The. Tran; Binh Thanh. Nguyen; O365- Yoshinori 
> Kaneko; O365-Yasushi Onishi
> Subject: RE: [cip-dev] B at D: iwg20m support
> 
> Dear Daniel,
> 
> One important thing is how big is root fs size get maximal? Is it limited?
> Your configuration on iwg20m is to assign 8 ramdisks with enlargement of each block 100MB approx:
> 
> CONFIG_BLK_DEV_RAM=y
> CONFIG_BLK_DEV_RAM_COUNT=8
> CONFIG_BLK_DEV_RAM_SIZE=102400
> CONFIG_EXT4_FS=y
> CONFIG_EXT4_USE_FOR_EXT2=y
> CONFIG_USB_XHCI_RCAR=n

Currently, "my configuration" is just the mainstream shmobile_defconfig (as suggested by Chris if I remember correctly). If you need to change the default configuration on cip-core upstream, please send me a defconfig (make savedefconfig) or a list of configuration options that should be added to shmobile_defconfig. However, in this case I think those options are very dependent on what you are putting on your filesystem so it might be a better idea if you create your own private branch and change the configuration as you need.

If you actually plan to submit the tests/dependencies to cip-core then adding those config options to cip-core would actually make sense. Is this your plan?

> If we try to test more function as our wish (more dependencies in ramdisk), assuming that the root fs size could be 150MB.
> For G1M 1GB of RAM, just increase CONFIG_BLK_DEV_RAM_SIZE to 250000 and reduce CONFIG_BLK_DEV_RAM_COUNT to 4 iWave.

By the way, you might also need to modify the u-boot settings so that the ramdisk does not overlap with the kernel or the device tree. And the LAVA configuration files.

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.org/cip-co
> > > re /iwg20m/core-image-minimal-iwg20m.cpio.gz
> > > https://s3-us-west-2.amazonaws.com/download.cip-project.org/cip-co
> > > re
> > > /iwg20m/r8a7743-iwg20d-q7.dtb
> > > https://s3-us-west-2.amazonaws.com/download.cip-project.org/cip-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/kas-bbb.yml
> > https://github.com/igaw/cip-rt-misc/blob/master/docs/kas-minnowboard
> > .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/civilinfrastructureplatform/cip-core-
> quickstart 
> https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-cip
> -iwg20m/README.IWG20M.txt 
> https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-cip
> -iwg20m/kas-iwg20m.yml
> 
> An overview of the CIP Core is here:
> https://wiki.linuxfoundation.org/civilinfrastructureplatform/cip-core
> https://gitlab.com/cip-project/cip-core/blob/master/deby/README.md
> 
> For the BBB please check this other Readme and kas file:
> https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-cip
> -bbb/README.BBB.txt 
> https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-cip
> -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] B@D: iwg20m support

[Daniel Sangorrin]

Dear Trung san,

> -----Original Message-----
> From: Trung. Huynh [mailto:trung.huynh.uw at rvc.renesas.com]
> Sent: Tuesday, January 09, 2018 7:41 PM
> Dear Daniel,
> 
> Yes, I tried it and working well, but I want to custom some devices under kernel layer to execute our test cases as well as packing
> some dependencies
> To do that I must expand file system that why I got this issue.

Please could you read my e-mail  and answer my question about your plan?. 

Thanks,
Daniel

> -----Original Message-----
> From: Daniel Sangorrin [mailto:daniel.sangorrin at toshiba.co.jp]
> Sent: Tuesday, January 9, 2018 3:41 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,
> 
> First of all, please could you give me some feedback about the LAVA configuration files and AWS links that I sent to the list before
> holidays?. Did you try them and did they work for you?.
> 
> See my answers below.
> 
> > -----Original Message-----
> > From: Trung. Huynh [mailto:trung.huynh.uw at rvc.renesas.com]
> > Sent: Tuesday, January 02, 2018 6:37 PM
> > To: Daniel Sangorrin
> > Cc: cip-dev at lists.cip-project.org; O365-Chan Duc. Vu; O365-Minh Thuy
> > Dinh. Tran; O365-Anh The. Tran; Binh Thanh. Nguyen; O365- Yoshinori
> > Kaneko; O365-Yasushi Onishi
> > Subject: RE: [cip-dev] B at D: iwg20m support
> >
> > Dear Daniel,
> >
> > One important thing is how big is root fs size get maximal? Is it limited?
> > Your configuration on iwg20m is to assign 8 ramdisks with enlargement of each block 100MB approx:
> >
> > CONFIG_BLK_DEV_RAM=y
> > CONFIG_BLK_DEV_RAM_COUNT=8
> > CONFIG_BLK_DEV_RAM_SIZE=102400
> > CONFIG_EXT4_FS=y
> > CONFIG_EXT4_USE_FOR_EXT2=y
> > CONFIG_USB_XHCI_RCAR=n
> 
> Currently, "my configuration" is just the mainstream shmobile_defconfig (as suggested by Chris if I remember correctly). If you need
> to change the default configuration on cip-core upstream, please send me a defconfig (make savedefconfig) or a list of configuration
> options that should be added to shmobile_defconfig. However, in this case I think those options are very dependent on what you are
> putting on your filesystem so it might be a better idea if you create your own private branch and change the configuration as you need.
> 
> If you actually plan to submit the tests/dependencies to cip-core then adding those config options to cip-core would actually make
> sense. Is this your plan?
> 
> > If we try to test more function as our wish (more dependencies in ramdisk), assuming that the root fs size could be 150MB.
> > For G1M 1GB of RAM, just increase CONFIG_BLK_DEV_RAM_SIZE to 250000 and reduce CONFIG_BLK_DEV_RAM_COUNT to 4
> iWave.
> 
> By the way, you might also need to modify the u-boot settings so that the ramdisk does not overlap with the kernel or the device tree.
> And the LAVA configuration files.
> 
> 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.org/cip-co
> > > > re /iwg20m/core-image-minimal-iwg20m.cpio.gz
> > > > https://s3-us-west-2.amazonaws.com/download.cip-project.org/cip-co
> > > > re
> > > > /iwg20m/r8a7743-iwg20d-q7.dtb
> > > > https://s3-us-west-2.amazonaws.com/download.cip-project.org/cip-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/kas-bbb.yml
> > > https://github.com/igaw/cip-rt-misc/blob/master/docs/kas-minnowboard
> > > .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/civilinfrastructureplatform/cip-core-
> > quickstart
> > https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-cip
> > -iwg20m/README.IWG20M.txt
> > https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-cip
> > -iwg20m/kas-iwg20m.yml
> >
> > An overview of the CIP Core is here:
> > https://wiki.linuxfoundation.org/civilinfrastructureplatform/cip-core
> > https://gitlab.com/cip-project/cip-core/blob/master/deby/README.md
> >
> > For the BBB please check this other Readme and kas file:
> > https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-cip
> > -bbb/README.BBB.txt
> > https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-cip
> > -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] B@D: iwg20m support

[Trung. Huynh]

Dear Daniel,

-----Original Message-----
From: Daniel Sangorrin [mailto:daniel.sangorrin at toshiba.co.jp] 
Sent: Wednesday, January 10, 2018 6:55 AM
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]
> Sent: Tuesday, January 09, 2018 7:41 PM Dear Daniel,
> 
> Yes, I tried it and working well, but I want to custom some devices 
> under kernel layer to execute our test cases as well as packing some 
> dependencies To do that I must expand file system that why I got this issue.

Please could you read my e-mail  and answer my question about your plan?. 

Thanks,
Daniel

> -----Original Message-----
> From: Daniel Sangorrin [mailto:daniel.sangorrin at toshiba.co.jp]
> Sent: Tuesday, January 9, 2018 3:41 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,
> 
> First of all, please could you give me some feedback about the LAVA 
> configuration files and AWS links that I sent to the list before holidays?. Did you try them and did they work for you?.
> 
> See my answers below.
> 
> > -----Original Message-----
> > From: Trung. Huynh [mailto:trung.huynh.uw at rvc.renesas.com]
> > Sent: Tuesday, January 02, 2018 6:37 PM
> > To: Daniel Sangorrin
> > Cc: cip-dev at lists.cip-project.org; O365-Chan Duc. Vu; O365-Minh Thuy 
> > Dinh. Tran; O365-Anh The. Tran; Binh Thanh. Nguyen; O365- Yoshinori 
> > Kaneko; O365-Yasushi Onishi
> > Subject: RE: [cip-dev] B at D: iwg20m support
> >
> > Dear Daniel,
> >
> > One important thing is how big is root fs size get maximal? Is it limited?
> > Your configuration on iwg20m is to assign 8 ramdisks with enlargement of each block 100MB approx:
> >
> > CONFIG_BLK_DEV_RAM=y
> > CONFIG_BLK_DEV_RAM_COUNT=8
> > CONFIG_BLK_DEV_RAM_SIZE=102400
> > CONFIG_EXT4_FS=y
> > CONFIG_EXT4_USE_FOR_EXT2=y
> > CONFIG_USB_XHCI_RCAR=n
> 
> Currently, "my configuration" is just the mainstream 
> shmobile_defconfig (as suggested by Chris if I remember correctly). If 
> you need to change the default configuration on cip-core upstream, 
> please send me a defconfig (make savedefconfig) or a list of configuration options that should be added to shmobile_defconfig. However, in this case I think those options are very dependent on what you are putting on your filesystem so it might be a better idea if you create your own private branch and change the configuration as you need.
> 
> If you actually plan to submit the tests/dependencies to cip-core then 
> adding those config options to cip-core would actually make sense. Is this your plan?

Yes, we would like to submit those configurations to cip-core upstream then everyone can use it as a baseline.
Before doing it, I want to make sure on which I've already done will be ok.
Of course the new configuration get branch as an option to do our test cases if it's passed through

Regarding shmobile_defconfig, attachment shows up for you.
Thank you.

> 
> > If we try to test more function as our wish (more dependencies in ramdisk), assuming that the root fs size could be 150MB.
> > For G1M 1GB of RAM, just increase CONFIG_BLK_DEV_RAM_SIZE to 250000 
> > and reduce CONFIG_BLK_DEV_RAM_COUNT to 4
> iWave.
> 
> By the way, you might also need to modify the u-boot settings so that the ramdisk does not overlap with the kernel or the device tree.
> And the LAVA configuration files.
> 
> 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.org/cip-
> > > > co re /iwg20m/core-image-minimal-iwg20m.cpio.gz
> > > > https://s3-us-west-2.amazonaws.com/download.cip-project.org/cip-
> > > > co
> > > > re
> > > > /iwg20m/r8a7743-iwg20d-q7.dtb
> > > > https://s3-us-west-2.amazonaws.com/download.cip-project.org/cip-
> > > > 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/kas-bbb.yml
> > > https://github.com/igaw/cip-rt-misc/blob/master/docs/kas-minnowboa
> > > 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/civilinfrastructureplatform/cip-cor
> > e-
> > quickstart
> > https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-c
> > ip
> > -iwg20m/README.IWG20M.txt
> > https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-c
> > ip
> > -iwg20m/kas-iwg20m.yml
> >
> > An overview of the CIP Core is here:
> > https://wiki.linuxfoundation.org/civilinfrastructureplatform/cip-cor
> > e https://gitlab.com/cip-project/cip-core/blob/master/deby/README.md
> >
> > For the BBB please check this other Readme and kas file:
> > https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-c
> > ip
> > -bbb/README.BBB.txt
> > https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/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
> 
> 



-------------- next part --------------
A non-text attachment was scrubbed...
Name: shmobile_defconfig
Type: application/octet-stream
Size: 105521 bytes
Desc: shmobile_defconfig
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20180110/80f6a0ec/attachment-0001.obj>

[cip-dev] B@D: iwg20m support

[Daniel Sangorrin]

Dear Trung san

> -----Original Message-----
> From: Trung. Huynh [mailto:trung.huynh.uw at rvc.renesas.com]
> Sent: Wednesday, January 10, 2018 1:05 PM
...
> > Currently, "my configuration" is just the mainstream
> > shmobile_defconfig (as suggested by Chris if I remember correctly). If
> > you need to change the default configuration on cip-core upstream,
> > please send me a defconfig (make savedefconfig) or a list of configuration options that should be added to shmobile_defconfig.
> However, in this case I think those options are very dependent on what you are putting on your filesystem so it might be a better idea
> if you create your own private branch and change the configuration as you need.
> >
> > If you actually plan to submit the tests/dependencies to cip-core then
> > adding those config options to cip-core would actually make sense. Is this your plan?
> 
> Yes, we would like to submit those configurations to cip-core upstream then everyone can use it as a baseline.
> Before doing it, I want to make sure on which I've already done will be ok.
> Of course the new configuration get branch as an option to do our test cases if it's passed through

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.

> 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

Thanks,
Daniel

> Thank you.
> 
> >
> > > If we try to test more function as our wish (more dependencies in ramdisk), assuming that the root fs size could be 150MB.
> > > For G1M 1GB of RAM, just increase CONFIG_BLK_DEV_RAM_SIZE to 250000
> > > and reduce CONFIG_BLK_DEV_RAM_COUNT to 4
> > iWave.
> >
> > By the way, you might also need to modify the u-boot settings so that the ramdisk does not overlap with the kernel or the device
> tree.
> > And the LAVA configuration files.
> >
> > 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.org/cip-
> > > > > co re /iwg20m/core-image-minimal-iwg20m.cpio.gz
> > > > > https://s3-us-west-2.amazonaws.com/download.cip-project.org/cip-
> > > > > co
> > > > > re
> > > > > /iwg20m/r8a7743-iwg20d-q7.dtb
> > > > > https://s3-us-west-2.amazonaws.com/download.cip-project.org/cip-
> > > > > 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/kas-bbb.yml
> > > > https://github.com/igaw/cip-rt-misc/blob/master/docs/kas-minnowboa
> > > > 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/civilinfrastructureplatform/cip-cor
> > > e-
> > > quickstart
> > > https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-c
> > > ip
> > > -iwg20m/README.IWG20M.txt
> > > https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-c
> > > ip
> > > -iwg20m/kas-iwg20m.yml
> > >
> > > An overview of the CIP Core is here:
> > > https://wiki.linuxfoundation.org/civilinfrastructureplatform/cip-cor
> > > e https://gitlab.com/cip-project/cip-core/blob/master/deby/README.md
> > >
> > > For the BBB please check this other Readme and kas file:
> > > https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-c
> > > ip
> > > -bbb/README.BBB.txt
> > > https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/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] B@D: iwg20m support

[Trung. Huynh]

Dear Daniel,

> -----Original Message-----
> From: Daniel Sangorrin [mailto:daniel.sangorrin at toshiba.co.jp] 
> Sent: Wednesday, January 10, 2018 12:26 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]
> > Sent: Wednesday, January 10, 2018 1:05 PM
>...
> > > Currently, "my configuration" is just the mainstream 
> > > shmobile_defconfig (as suggested by Chris if I remember correctly). 
> > > If you need to change the default configuration on cip-core 
> > > upstream, please send me a defconfig (make savedefconfig) or a list of configuration options that should be added to shmobile_defconfig.
> > However, in this case I think those options are very dependent on what 
> > you are putting on your filesystem so it might be a better idea if you create your own private branch and change the configuration as you need.
> > >
> > > If you actually plan to submit the tests/dependencies to cip-core 
> > > then adding those config options to cip-core would actually make sense. Is this your plan?
> > 
> > Yes, we would like to submit those configurations to cip-core upstream then everyone can use it as a baseline.
> > Before doing it, I want to make sure on which I've already done will be ok.
> > Of course the new configuration get branch as an option to do our test 
> > cases if it's passed through
>
> 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

>
> > 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.

>
> Thanks,
> Daniel
>
> > Thank you.
> > 
> > >
> > > > If we try to test more function as our wish (more dependencies in ramdisk), assuming that the root fs size could be 150MB.
> > > > For G1M 1GB of RAM, just increase CONFIG_BLK_DEV_RAM_SIZE to 
> > > > 250000 and reduce CONFIG_BLK_DEV_RAM_COUNT to 4
> > > iWave.
> > >
> > > By the way, you might also need to modify the u-boot settings so 
> > > that the ramdisk does not overlap with the kernel or the device
> > tree.
> > > And the LAVA configuration files.
> > >
> > > 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.org/ci
> > > > > > p- co re /iwg20m/core-image-minimal-iwg20m.cpio.gz
> > > > > > https://s3-us-west-2.amazonaws.com/download.cip-project.org/ci
> > > > > > p-
> > > > > > co
> > > > > > re
> > > > > > /iwg20m/r8a7743-iwg20d-q7.dtb
> > > > > > https://s3-us-west-2.amazonaws.com/download.cip-project.org/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/kas-bbb.yml
> > > > > https://github.com/igaw/cip-rt-misc/blob/master/docs/kas-minnowb
> > > > > 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/civilinfrastructureplatform/cip-c
> > > > or
> > > > e-
> > > > quickstart
> > > > https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta
> > > > -c
> > > > ip
> > > > -iwg20m/README.IWG20M.txt
> > > > https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta
> > > > -c
> > > > ip
> > > > -iwg20m/kas-iwg20m.yml
> > > >
> > > > An overview of the CIP Core is here:
> > > > https://wiki.linuxfoundation.org/civilinfrastructureplatform/cip-c
> > > > or e 
> > > > https://gitlab.com/cip-project/cip-core/blob/master/deby/README.md
> > > >
> > > > For the BBB please check this other Readme and kas file:
> > > > https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta
> > > > -c
> > > > ip
> > > > -bbb/README.BBB.txt
> > > > https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/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] B@D: iwg20m support

[Daniel Sangorrin]

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?

I have added your kernel configuration changes:
https://gitlab.com/cip-project/cip-core/commit/c1efa6325909815731abe0b69ec7e19e2e56aee7
Please let me know if that works for you.

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? 

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.org/ci
> > > > > > > p- co re /iwg20m/core-image-minimal-iwg20m.cpio.gz
> > > > > > > https://s3-us-west-2.amazonaws.com/download.cip-project.org/ci
> > > > > > > p-
> > > > > > > co
> > > > > > > re
> > > > > > > /iwg20m/r8a7743-iwg20d-q7.dtb
> > > > > > > https://s3-us-west-2.amazonaws.com/download.cip-project.org/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/kas-bbb.yml
> > > > > > https://github.com/igaw/cip-rt-misc/blob/master/docs/kas-minnowb
> > > > > > 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/civilinfrastructureplatform/cip-c
> > > > > or
> > > > > e-
> > > > > quickstart
> > > > > https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta
> > > > > -c
> > > > > ip
> > > > > -iwg20m/README.IWG20M.txt
> > > > > https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta
> > > > > -c
> > > > > ip
> > > > > -iwg20m/kas-iwg20m.yml
> > > > >
> > > > > An overview of the CIP Core is here:
> > > > > https://wiki.linuxfoundation.org/civilinfrastructureplatform/cip-c
> > > > > or e
> > > > > https://gitlab.com/cip-project/cip-core/blob/master/deby/README.md
> > > > >
> > > > > For the BBB please check this other Readme and kas file:
> > > > > https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta
> > > > > -c
> > > > > ip
> > > > > -bbb/README.BBB.txt
> > > > > https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/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] B@D: iwg20m support

[Trung. Huynh]

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/c1efa6325909815731abe0b69ec7e19e2e56aee7
> 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/kas-bbb
> > > > > > > .yml 
> > > > > > > https://github.com/igaw/cip-rt-misc/blob/master/docs/kas-min
> > > > > > > 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/civilinfrastructureplatform/c
> > > > > > ip-c
> > > > > > or
> > > > > > e-
> > > > > > quickstart
> > > > > > https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/
> > > > > > meta
> > > > > > -c
> > > > > > ip
> > > > > > -iwg20m/README.IWG20M.txt
> > > > > > https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/
> > > > > > meta
> > > > > > -c
> > > > > > ip
> > > > > > -iwg20m/kas-iwg20m.yml
> > > > > >
> > > > > > An overview of the CIP Core is here:
> > > > > > https://wiki.linuxfoundation.org/civilinfrastructureplatform/c
> > > > > > ip-c
> > > > > > or e
> > > > > > https://gitlab.com/cip-project/cip-core/blob/master/deby/READM
> > > > > > E.md
> > > > > >
> > > > > > For the BBB please check this other Readme and kas file:
> > > > > > https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/
> > > > > > meta
> > > > > > -c
> > > > > > ip
> > > > > > -bbb/README.BBB.txt
> > > > > > https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/
> > > > > > 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] B@D: iwg20m support

[Tram Quynh Thi. Nguyen]

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.

Best regards,
Tram Nguyen

-----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/c1efa6325909815731abe0b
> 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/kas-b
> > > > > > > bb
> > > > > > > .yml
> > > > > > > https://github.com/igaw/cip-rt-misc/blob/master/docs/kas-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/civilinfrastructureplatform
> > > > > > /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/civilinfrastructureplatform
> > > > > > /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] B@D: iwg20m support

[Daniel Sangorrin]

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/c1efa6325909815731abe0b
> > 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/kas-b
> > > > > > > > bb
> > > > > > > > .yml
> > > > > > > > https://github.com/igaw/cip-rt-misc/blob/master/docs/kas-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/civilinfrastructureplatform
> > > > > > > /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/civilinfrastructureplatform
> > > > > > > /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] B@D: iwg20m support

[Zoran S]

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/c1efa6325909815731abe0b
>> > 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/kas-b
>> > > > > > > > bb
>> > > > > > > > .yml
>> > > > > > > > https://github.com/igaw/cip-rt-misc/blob/master/docs/kas-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/civilinfrastructureplatform
>> > > > > > > /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/civilinfrastructureplatform
>> > > > > > > /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

[cip-dev] B@D: iwg20m support

[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

[cip-dev] B@D: iwg20m support

[Daniel Sangorrin]

Hi Tram,

> -----Original Message-----
> From: Tram Quynh Thi. Nguyen [mailto:tram.nguyen.xw at rvc.renesas.com]
> Sent: Monday, March 26, 2018 5:40 PM
> To: Zoran S <zoran.stojsavljevic.de@gmail.com>; Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>
> Cc: 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
> 
> 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.

If you are allowed, could you give me some information about your SDK?
For example, the one in CIP core uses the "cortexa15" tuning, but yours maybe using "cortexa15hf" for example.

Also, if your tests are using dynamic linking then you need to make sure that your SDK library headers are the same
version as the libraries on the target as well. If you use static linking I think it should not matter.

Thanks,
Daniel

> -----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

[cip-dev] B@D: iwg20m support

[Tram Quynh Thi. Nguyen]

Hi Daniel,

I got it. Thank you for your information.
Our SDK information: "cortexa15hf"

Best regards,
Tram Nguyen

-----Original Message-----
From: Daniel Sangorrin [mailto:daniel.sangorrin at toshiba.co.jp] 
Sent: Monday, March 26, 2018 3:45 PM
To: Tram Quynh Thi. Nguyen <tram.nguyen.xw@rvc.renesas.com>; 'Zoran S' <zoran.stojsavljevic.de@gmail.com>
Cc: 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

Hi Tram,

> -----Original Message-----
> From: Tram Quynh Thi. Nguyen [mailto:tram.nguyen.xw at rvc.renesas.com]
> Sent: Monday, March 26, 2018 5:40 PM
> To: Zoran S <zoran.stojsavljevic.de@gmail.com>; Daniel Sangorrin 
> <daniel.sangorrin@toshiba.co.jp>
> Cc: 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
> 
> 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.

If you are allowed, could you give me some information about your SDK?
For example, the one in CIP core uses the "cortexa15" tuning, but yours maybe using "cortexa15hf" for example.

Also, if your tests are using dynamic linking then you need to make sure that your SDK library headers are the same version as the libraries on the target as well. If you use static linking I think it should not matter.

Thanks,
Daniel

> -----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/c1efa6325909815731
> >> > ab
> >> > 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/civilinfrastructurepla
> >> > > > > > > tf
> >> > > > > > > orm
> >> > > > > > > /c
> >> > > > > > > ip-c
> >> > > > > > > or
> >> > > > > > > e-
> >> > > > > > > quickstart
> >> > > > > > > https://gitlab.com/cip-project/cip-core/blob/master/deb
> >> > > > > > > y/
> >> > > > > > > pok
> >> > > > > > > y/
> >> > > > > > > meta
> >> > > > > > > -c
> >> > > > > > > ip
> >> > > > > > > -iwg20m/README.IWG20M.txt 
> >> > > > > > > https://gitlab.com/cip-project/cip-core/blob/master/deb
> >> > > > > > > y/
> >> > > > > > > pok
> >> > > > > > > y/
> >> > > > > > > meta
> >> > > > > > > -c
> >> > > > > > > ip
> >> > > > > > > -iwg20m/kas-iwg20m.yml
> >> > > > > > >
> >> > > > > > > An overview of the CIP Core is here:
> >> > > > > > > https://wiki.linuxfoundation.org/civilinfrastructurepla
> >> > > > > > > tf
> >> > > > > > > orm
> >> > > > > > > /c
> >> > > > > > > ip-c
> >> > > > > > > or e
> >> > > > > > > https://gitlab.com/cip-project/cip-core/blob/master/deb
> >> > > > > > > y/
> >> > > > > > > REA
> >> > > > > > > DM
> >> > > > > > > E.md
> >> > > > > > >
> >> > > > > > > For the BBB please check this other Readme and kas file:
> >> > > > > > > https://gitlab.com/cip-project/cip-core/blob/master/deb
> >> > > > > > > y/
> >> > > > > > > pok
> >> > > > > > > y/
> >> > > > > > > meta
> >> > > > > > > -c
> >> > > > > > > ip
> >> > > > > > > -bbb/README.BBB.txt
> >> > > > > > > https://gitlab.com/cip-project/cip-core/blob/master/deb
> >> > > > > > > y/
> >> > > > > > > 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

[cip-dev] B@D: iwg20m support

[Daniel Sangorrin]

Hi Tram,

> -----Original Message-----
> From: Tram Quynh Thi. Nguyen [mailto:tram.nguyen.xw at rvc.renesas.com]
> Sent: Monday, March 26, 2018 5:54 PM
> To: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>; 'Zoran S' <zoran.stojsavljevic.de@gmail.com>
> Cc: 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
> 
> Hi Daniel,
> 
> I got it. Thank you for your information.
> Our SDK information: "cortexa15hf"

If you want you can rebuild cip core with cortexa15hf tuning.

$ vi conf/machine/iwg20m.conf
DEFAULTTUNE ?= cortexa15hf

Then you _may_ be able to use your SDK as it is.

Maybe I will set it as default.

Best regards
Daniel

> 
> Best regards,
> Tram Nguyen
> 
> -----Original Message-----
> From: Daniel Sangorrin [mailto:daniel.sangorrin at toshiba.co.jp]
> Sent: Monday, March 26, 2018 3:45 PM
> To: Tram Quynh Thi. Nguyen <tram.nguyen.xw@rvc.renesas.com>; 'Zoran S' <zoran.stojsavljevic.de@gmail.com>
> Cc: 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
> 
> Hi Tram,
> 
> > -----Original Message-----
> > From: Tram Quynh Thi. Nguyen [mailto:tram.nguyen.xw at rvc.renesas.com]
> > Sent: Monday, March 26, 2018 5:40 PM
> > To: Zoran S <zoran.stojsavljevic.de@gmail.com>; Daniel Sangorrin
> > <daniel.sangorrin@toshiba.co.jp>
> > Cc: 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
> >
> > 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.
> 
> If you are allowed, could you give me some information about your SDK?
> For example, the one in CIP core uses the "cortexa15" tuning, but yours maybe using "cortexa15hf" for example.
> 
> Also, if your tests are using dynamic linking then you need to make sure that your SDK library headers are the same version as the
> libraries on the target as well. If you use static linking I think it should not matter.
> 
> Thanks,
> Daniel
> 
> > -----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/c1efa6325909815731
> > >> > ab
> > >> > 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/civilinfrastructurepla
> > >> > > > > > > tf
> > >> > > > > > > orm
> > >> > > > > > > /c
> > >> > > > > > > ip-c
> > >> > > > > > > or
> > >> > > > > > > e-
> > >> > > > > > > quickstart
> > >> > > > > > > https://gitlab.com/cip-project/cip-core/blob/master/deb
> > >> > > > > > > y/
> > >> > > > > > > pok
> > >> > > > > > > y/
> > >> > > > > > > meta
> > >> > > > > > > -c
> > >> > > > > > > ip
> > >> > > > > > > -iwg20m/README.IWG20M.txt
> > >> > > > > > > https://gitlab.com/cip-project/cip-core/blob/master/deb
> > >> > > > > > > y/
> > >> > > > > > > pok
> > >> > > > > > > y/
> > >> > > > > > > meta
> > >> > > > > > > -c
> > >> > > > > > > ip
> > >> > > > > > > -iwg20m/kas-iwg20m.yml
> > >> > > > > > >
> > >> > > > > > > An overview of the CIP Core is here:
> > >> > > > > > > https://wiki.linuxfoundation.org/civilinfrastructurepla
> > >> > > > > > > tf
> > >> > > > > > > orm
> > >> > > > > > > /c
> > >> > > > > > > ip-c
> > >> > > > > > > or e
> > >> > > > > > > https://gitlab.com/cip-project/cip-core/blob/master/deb
> > >> > > > > > > y/
> > >> > > > > > > REA
> > >> > > > > > > DM
> > >> > > > > > > E.md
> > >> > > > > > >
> > >> > > > > > > For the BBB please check this other Readme and kas file:
> > >> > > > > > > https://gitlab.com/cip-project/cip-core/blob/master/deb
> > >> > > > > > > y/
> > >> > > > > > > pok
> > >> > > > > > > y/
> > >> > > > > > > meta
> > >> > > > > > > -c
> > >> > > > > > > ip
> > >> > > > > > > -bbb/README.BBB.txt
> > >> > > > > > > https://gitlab.com/cip-project/cip-core/blob/master/deb
> > >> > > > > > > y/
> > >> > > > > > > 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
> 

[cip-dev] B@D: iwg20m support

[Tram Quynh Thi. Nguyen]

Hi Daniel,

I'm sorry for late reply.
After rebuilding cip core with cortexa15hf tuning, I can run binary files successfully.

Thank you and best regards,
Tram Nguyen

-----Original Message-----
From: Daniel Sangorrin [mailto:daniel.sangorrin at toshiba.co.jp] 
Sent: Monday, March 26, 2018 3:59 PM
To: Tram Quynh Thi. Nguyen <tram.nguyen.xw@rvc.renesas.com>; 'Zoran S' <zoran.stojsavljevic.de@gmail.com>
Cc: 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

Hi Tram,

> -----Original Message-----
> From: Tram Quynh Thi. Nguyen [mailto:tram.nguyen.xw at rvc.renesas.com]
> Sent: Monday, March 26, 2018 5:54 PM
> To: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>; 'Zoran S' 
> <zoran.stojsavljevic.de@gmail.com>
> Cc: 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
> 
> Hi Daniel,
> 
> I got it. Thank you for your information.
> Our SDK information: "cortexa15hf"

If you want you can rebuild cip core with cortexa15hf tuning.

$ vi conf/machine/iwg20m.conf
DEFAULTTUNE ?= cortexa15hf

Then you _may_ be able to use your SDK as it is.

Maybe I will set it as default.

Best regards
Daniel

> 
> Best regards,
> Tram Nguyen
> 
> -----Original Message-----
> From: Daniel Sangorrin [mailto:daniel.sangorrin at toshiba.co.jp]
> Sent: Monday, March 26, 2018 3:45 PM
> To: Tram Quynh Thi. Nguyen <tram.nguyen.xw@rvc.renesas.com>; 'Zoran S' 
> <zoran.stojsavljevic.de@gmail.com>
> Cc: 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
> 
> Hi Tram,
> 
> > -----Original Message-----
> > From: Tram Quynh Thi. Nguyen [mailto:tram.nguyen.xw at rvc.renesas.com]
> > Sent: Monday, March 26, 2018 5:40 PM
> > To: Zoran S <zoran.stojsavljevic.de@gmail.com>; Daniel Sangorrin 
> > <daniel.sangorrin@toshiba.co.jp>
> > Cc: 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
> >
> > 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-c
> > ip
> > -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.
> 
> If you are allowed, could you give me some information about your SDK?
> For example, the one in CIP core uses the "cortexa15" tuning, but yours maybe using "cortexa15hf" for example.
> 
> Also, if your tests are using dynamic linking then you need to make 
> sure that your SDK library headers are the same version as the libraries on the target as well. If you use static linking I think it should not matter.
> 
> Thanks,
> Daniel
> 
> > -----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-c
> > ip
> > -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/c1efa63259098157
> > >> > 31
> > >> > ab
> > >> > 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/doc
> > >> > > > > > > > s/
> > >> > > > > > > > ka
> > >> > > > > > > > s-b
> > >> > > > > > > > bb
> > >> > > > > > > > .yml
> > >> > > > > > > > https://github.com/igaw/cip-rt-misc/blob/master/doc
> > >> > > > > > > > s/
> > >> > > > > > > > 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/civilinfrastructurep
> > >> > > > > > > la
> > >> > > > > > > tf
> > >> > > > > > > orm
> > >> > > > > > > /c
> > >> > > > > > > ip-c
> > >> > > > > > > or
> > >> > > > > > > e-
> > >> > > > > > > quickstart
> > >> > > > > > > https://gitlab.com/cip-project/cip-core/blob/master/d
> > >> > > > > > > eb
> > >> > > > > > > y/
> > >> > > > > > > pok
> > >> > > > > > > y/
> > >> > > > > > > meta
> > >> > > > > > > -c
> > >> > > > > > > ip
> > >> > > > > > > -iwg20m/README.IWG20M.txt 
> > >> > > > > > > https://gitlab.com/cip-project/cip-core/blob/master/d
> > >> > > > > > > eb
> > >> > > > > > > y/
> > >> > > > > > > pok
> > >> > > > > > > y/
> > >> > > > > > > meta
> > >> > > > > > > -c
> > >> > > > > > > ip
> > >> > > > > > > -iwg20m/kas-iwg20m.yml
> > >> > > > > > >
> > >> > > > > > > An overview of the CIP Core is here:
> > >> > > > > > > https://wiki.linuxfoundation.org/civilinfrastructurep
> > >> > > > > > > la
> > >> > > > > > > tf
> > >> > > > > > > orm
> > >> > > > > > > /c
> > >> > > > > > > ip-c
> > >> > > > > > > or e
> > >> > > > > > > https://gitlab.com/cip-project/cip-core/blob/master/d
> > >> > > > > > > eb
> > >> > > > > > > y/
> > >> > > > > > > REA
> > >> > > > > > > DM
> > >> > > > > > > E.md
> > >> > > > > > >
> > >> > > > > > > For the BBB please check this other Readme and kas file:
> > >> > > > > > > https://gitlab.com/cip-project/cip-core/blob/master/d
> > >> > > > > > > eb
> > >> > > > > > > y/
> > >> > > > > > > pok
> > >> > > > > > > y/
> > >> > > > > > > meta
> > >> > > > > > > -c
> > >> > > > > > > ip
> > >> > > > > > > -bbb/README.BBB.txt
> > >> > > > > > > https://gitlab.com/cip-project/cip-core/blob/master/d
> > >> > > > > > > eb
> > >> > > > > > > y/
> > >> > > > > > > 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-de
> > >> > > > > > > v
> > >> > > > > >
> > >> > > > > >
> > >> > > > >
> > >> > > > >
> > >> > >
> > >> > >
> > >> >
> > >
> > >
> > > _______________________________________________
> > > cip-dev mailing list
> > > cip-dev at lists.cip-project.org
> > > https://lists.cip-project.org/mailman/listinfo/cip-dev
> 

[cip-dev] B@D: iwg20m support

[Zoran S]

Hello Tram,

Could you, please, do me a favour?

Could you, please, find for me the kernel tree after you did build
your kas SDK (supposed to be 4.4.-x) tree, and from there to retrieve
for me the following .dts files:

path: kernel-top-dir/arch/arm/boot/dts, the files:

r8a7743.dtsi
r8a7743-iwg20d-q7.dts
r8a7743-iwg20m.dtsi

And, please, attach them for me to the email for inspection?

Thank you,
Zoran
_______

[cip-dev] B@D: iwg20m support

[Tram Quynh Thi. Nguyen]

Hello Zoran,

Yes. Please refer attached files for your information.

Best regards,
Tram Nguyen

-----Original Message-----
From: Zoran S [mailto:zoran.stojsavljevic.de at gmail.com] 
Sent: Wednesday, March 28, 2018 6:52 PM
To: Tram Quynh Thi. Nguyen <tram.nguyen.xw@rvc.renesas.com>
Cc: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>; 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,

Could you, please, do me a favour?

Could you, please, find for me the kernel tree after you did build your kas SDK (supposed to be 4.4.-x) tree, and from there to retrieve for me the following .dts files:

path: kernel-top-dir/arch/arm/boot/dts, the files:

r8a7743.dtsi
r8a7743-iwg20d-q7.dts
r8a7743-iwg20m.dtsi

And, please, attach them for me to the email for inspection?

Thank you,
Zoran
_______
-------------- next part --------------
A non-text attachment was scrubbed...
Name: r8a7743.dtsi
Type: application/octet-stream
Size: 30990 bytes
Desc: r8a7743.dtsi
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20180329/d81bca32/attachment-0003.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: r8a7743-iwg20d-q7.dts
Type: application/octet-stream
Size: 1015 bytes
Desc: r8a7743-iwg20d-q7.dts
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20180329/d81bca32/attachment-0004.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: r8a7743-iwg20m.dtsi
Type: application/octet-stream
Size: 1060 bytes
Desc: r8a7743-iwg20m.dtsi
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20180329/d81bca32/attachment-0005.obj>

[cip-dev] B@D: iwg20m support

[Zoran S]

Hello Tram,

I just checked the dtb/ with v4.4.120-cip20-rt13, and there, these are
the exact same files.

Since I am not at all able to make working example out of YOCTO (I do
not have SDK). I use:
https://elinux.org/RZ-G/Boards/Yocto_2.0

I even followed what you all did:
TUNE_FEATURES     = "arm armv7a vfp neon callconvention-hard cortexa15hf"

I have the very last ask: when you bring up the iwg20m SDK image from
U-boot to the Linux kernel, what will be the root prompt (so I can
exercise some more Lava iwg20m use cases)?

Should be: [root at iwg20m]#, but this does not play well with Lava (it
reports to me: invalid prompt)?!

Thank you,
Zoran
_______

On Thu, Mar 29, 2018 at 5:37 AM, Tram Quynh Thi. Nguyen
<tram.nguyen.xw@rvc.renesas.com> wrote:
> Hello Zoran,
>
> Yes. Please refer attached files for your information.
>
> Best regards,
> Tram Nguyen
>
> -----Original Message-----
> From: Zoran S [mailto:zoran.stojsavljevic.de at gmail.com]
> Sent: Wednesday, March 28, 2018 6:52 PM
> To: Tram Quynh Thi. Nguyen <tram.nguyen.xw@rvc.renesas.com>
> Cc: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>; 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,
>
> Could you, please, do me a favour?
>
> Could you, please, find for me the kernel tree after you did build your kas SDK (supposed to be 4.4.-x) tree, and from there to retrieve for me the following .dts files:
>
> path: kernel-top-dir/arch/arm/boot/dts, the files:
>
> r8a7743.dtsi
> r8a7743-iwg20d-q7.dts
> r8a7743-iwg20m.dtsi
>
> And, please, attach them for me to the email for inspection?
>
> Thank you,
> Zoran
> _______

[cip-dev] B@D: iwg20m support

[Daniel Sangorrin]

Thanks for the feedback Tram.
I will set the cortexa15hf tuning as default.

Thanks,
Daniel

> -----Original Message-----
> From: Tram Quynh Thi. Nguyen [mailto:tram.nguyen.xw at rvc.renesas.com]
> Sent: Wednesday, March 28, 2018 8:19 PM
> To: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>; 'Zoran S' <zoran.stojsavljevic.de@gmail.com>
> Cc: 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
> 
> Hi Daniel,
> 
> I'm sorry for late reply.
> After rebuilding cip core with cortexa15hf tuning, I can run binary files successfully.
> 
> Thank you and best regards,
> Tram Nguyen
> 
> -----Original Message-----
> From: Daniel Sangorrin [mailto:daniel.sangorrin at toshiba.co.jp]
> Sent: Monday, March 26, 2018 3:59 PM
> To: Tram Quynh Thi. Nguyen <tram.nguyen.xw@rvc.renesas.com>; 'Zoran S' <zoran.stojsavljevic.de@gmail.com>
> Cc: 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
> 
> Hi Tram,
> 
> > -----Original Message-----
> > From: Tram Quynh Thi. Nguyen [mailto:tram.nguyen.xw at rvc.renesas.com]
> > Sent: Monday, March 26, 2018 5:54 PM
> > To: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>; 'Zoran S'
> > <zoran.stojsavljevic.de@gmail.com>
> > Cc: 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
> >
> > Hi Daniel,
> >
> > I got it. Thank you for your information.
> > Our SDK information: "cortexa15hf"
> 
> If you want you can rebuild cip core with cortexa15hf tuning.
> 
> $ vi conf/machine/iwg20m.conf
> DEFAULTTUNE ?= cortexa15hf
> 
> Then you _may_ be able to use your SDK as it is.
> 
> Maybe I will set it as default.
> 
> Best regards
> Daniel
> 
> >
> > Best regards,
> > Tram Nguyen
> >
> > -----Original Message-----
> > From: Daniel Sangorrin [mailto:daniel.sangorrin at toshiba.co.jp]
> > Sent: Monday, March 26, 2018 3:45 PM
> > To: Tram Quynh Thi. Nguyen <tram.nguyen.xw@rvc.renesas.com>; 'Zoran S'
> > <zoran.stojsavljevic.de@gmail.com>
> > Cc: 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
> >
> > Hi Tram,
> >
> > > -----Original Message-----
> > > From: Tram Quynh Thi. Nguyen [mailto:tram.nguyen.xw at rvc.renesas.com]
> > > Sent: Monday, March 26, 2018 5:40 PM
> > > To: Zoran S <zoran.stojsavljevic.de@gmail.com>; Daniel Sangorrin
> > > <daniel.sangorrin@toshiba.co.jp>
> > > Cc: 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
> > >
> > > 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-c
> > > ip
> > > -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.
> >
> > If you are allowed, could you give me some information about your SDK?
> > For example, the one in CIP core uses the "cortexa15" tuning, but yours maybe using "cortexa15hf" for example.
> >
> > Also, if your tests are using dynamic linking then you need to make
> > sure that your SDK library headers are the same version as the libraries on the target as well. If you use static linking I think it should
> not matter.
> >
> > Thanks,
> > Daniel
> >
> > > -----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-c
> > > ip
> > > -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/c1efa63259098157
> > > >> > 31
> > > >> > ab
> > > >> > 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/doc
> > > >> > > > > > > > s/
> > > >> > > > > > > > ka
> > > >> > > > > > > > s-b
> > > >> > > > > > > > bb
> > > >> > > > > > > > .yml
> > > >> > > > > > > > https://github.com/igaw/cip-rt-misc/blob/master/doc
> > > >> > > > > > > > s/
> > > >> > > > > > > > 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/civilinfrastructurep
> > > >> > > > > > > la
> > > >> > > > > > > tf
> > > >> > > > > > > orm
> > > >> > > > > > > /c
> > > >> > > > > > > ip-c
> > > >> > > > > > > or
> > > >> > > > > > > e-
> > > >> > > > > > > quickstart
> > > >> > > > > > > https://gitlab.com/cip-project/cip-core/blob/master/d
> > > >> > > > > > > eb
> > > >> > > > > > > y/
> > > >> > > > > > > pok
> > > >> > > > > > > y/
> > > >> > > > > > > meta
> > > >> > > > > > > -c
> > > >> > > > > > > ip
> > > >> > > > > > > -iwg20m/README.IWG20M.txt
> > > >> > > > > > > https://gitlab.com/cip-project/cip-core/blob/master/d
> > > >> > > > > > > eb
> > > >> > > > > > > y/
> > > >> > > > > > > pok
> > > >> > > > > > > y/
> > > >> > > > > > > meta
> > > >> > > > > > > -c
> > > >> > > > > > > ip
> > > >> > > > > > > -iwg20m/kas-iwg20m.yml
> > > >> > > > > > >
> > > >> > > > > > > An overview of the CIP Core is here:
> > > >> > > > > > > https://wiki.linuxfoundation.org/civilinfrastructurep
> > > >> > > > > > > la
> > > >> > > > > > > tf
> > > >> > > > > > > orm
> > > >> > > > > > > /c
> > > >> > > > > > > ip-c
> > > >> > > > > > > or e
> > > >> > > > > > > https://gitlab.com/cip-project/cip-core/blob/master/d
> > > >> > > > > > > eb
> > > >> > > > > > > y/
> > > >> > > > > > > REA
> > > >> > > > > > > DM
> > > >> > > > > > > E.md
> > > >> > > > > > >
> > > >> > > > > > > For the BBB please check this other Readme and kas file:
> > > >> > > > > > > https://gitlab.com/cip-project/cip-core/blob/master/d
> > > >> > > > > > > eb
> > > >> > > > > > > y/
> > > >> > > > > > > pok
> > > >> > > > > > > y/
> > > >> > > > > > > meta
> > > >> > > > > > > -c
> > > >> > > > > > > ip
> > > >> > > > > > > -bbb/README.BBB.txt
> > > >> > > > > > > https://gitlab.com/cip-project/cip-core/blob/master/d
> > > >> > > > > > > eb
> > > >> > > > > > > y/
> > > >> > > > > > > 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-de
> > > >> > > > > > > v
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > >
> > > >> > > > >
> > > >> > >
> > > >> > >
> > > >> >
> > > >
> > > >
> > > > _______________________________________________
> > > > cip-dev mailing list
> > > > cip-dev at lists.cip-project.org
> > > > https://lists.cip-project.org/mailman/listinfo/cip-dev
> >
> 
> 

[cip-dev] FW: B@D: iwg20m support

[Trung. Huynh]

Dear Daniel,

Some troubles with email so I re-send the output log in attachment.
Sorry for inconvenience.

Regards,
Trung

> -----Original Message-----
> From: Trung. Huynh 
> Sent: Tuesday, January 2, 2018 4:37 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,
>
> One important thing is how big is root fs size get maximal? Is it limited?
> Your configuration on iwg20m is to assign 8 ramdisks with enlargement of each block 100MB approx:
>
> CONFIG_BLK_DEV_RAM=y
> CONFIG_BLK_DEV_RAM_COUNT=8
> CONFIG_BLK_DEV_RAM_SIZE=102400
> CONFIG_EXT4_FS=y
> CONFIG_EXT4_USE_FOR_EXT2=y
> CONFIG_USB_XHCI_RCAR=n
>
> If we try to test more function as our wish (more dependencies in ramdisk), assuming that the root fs size could be 150MB.
> For G1M 1GB of RAM, just increase CONFIG_BLK_DEV_RAM_SIZE to 250000 and reduce CONFIG_BLK_DEV_RAM_COUNT to 4.
>
> -> Output is booting failed, attachment to show what occurring.
>
> Regards,
> Trung

> -----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.org/cip-core
> > > /iwg20m/core-image-minimal-iwg20m.cpio.gz
> > > https://s3-us-west-2.amazonaws.com/download.cip-project.org/cip-core
> > > /iwg20m/r8a7743-iwg20d-q7.dtb
> > > https://s3-us-west-2.amazonaws.com/download.cip-project.org/cip-core
> > > /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/kas-bbb.yml
> > https://github.com/igaw/cip-rt-misc/blob/master/docs/kas-minnowboard.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/civilinfrastructureplatform/cip-core-quickstart
> https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-cip-iwg20m/README.IWG20M.txt
> https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-cip-iwg20m/kas-iwg20m.yml
>
> An overview of the CIP Core is here:
> https://wiki.linuxfoundation.org/civilinfrastructureplatform/cip-core
> https://gitlab.com/cip-project/cip-core/blob/master/deby/README.md
>
> For the BBB please check this other Readme and kas file:
> https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-cip-bbb/README.BBB.txt
> https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-cip-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
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 250MB_ramdisk_boot.txt
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20180102/b8be8b58/attachment-0001.txt>

[cip-dev] B@D: iwg20m support

[Daniel Wagner]

Hi Daniel,

On 12/19/2017 02:40 AM, Daniel Sangorrin wrote:
> 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.org/cip-core/iwg20m/core-image-minimal-iwg20m.cpio.gz
>>> https://s3-us-west-2.amazonaws.com/download.cip-project.org/cip-core/iwg20m/r8a7743-iwg20d-q7.dtb
>>> https://s3-us-west-2.amazonaws.com/download.cip-project.org/cip-core/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/kas-bbb.yml
>> https://github.com/igaw/cip-rt-misc/blob/master/docs/kas-minnowboard.yml
>>
>> 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/civilinfrastructureplatform/cip-core-quickstart
> https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-cip-iwg20m/README.IWG20M.txt
> https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-cip-iwg20m/kas-iwg20m.yml
> 
> An overview of the CIP Core is here:
> https://wiki.linuxfoundation.org/civilinfrastructureplatform/cip-core
> https://gitlab.com/cip-project/cip-core/blob/master/deby/README.md
> 
> For the BBB please check this other Readme and kas file:
> https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-cip-bbb/README.BBB.txt
> https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-cip-bbb/kas-bbb.yml
> 
> You can add the packages "openssh nfs-utils rt-tests strace procps", they are available in meta-debian.

Thanks a lot for all the pointers. Very useful!

Happy to see that kas works for you :)

> 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).

I don't think I need meta-qt5, I just used the default settings I found.
So far I am happy with the rootfs I have. Maybe if I need more stuff I
switch over to deby.

Thanks,
Daniel