From: daniel.wagner@siemens.com (Daniel Wagner)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] B@D: iwg20m support
Date: Mon, 18 Dec 2017 12:36:21 +0100 [thread overview]
Message-ID: <8334d32c-edfb-76dd-3246-dca7cd9a9d62@siemens.com> (raw)
In-Reply-To: <1513231035-42479-1-git-send-email-daniel.sangorrin@toshiba.co.jp>
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
next prev parent reply other threads:[~2017-12-18 11:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 5:57 [cip-dev] B@D: iwg20m support Daniel Sangorrin
2017-12-14 5:57 ` [cip-dev] [PATCH 1/3] Vagrantfile: support the http proxy plugin Daniel Sangorrin
2017-12-14 5:57 ` [cip-dev] [PATCH 2/3] iwg20m: add device type and dictionary template Daniel Sangorrin
2017-12-14 6:06 ` Daniel Sangorrin
2017-12-14 5:57 ` [cip-dev] [PATCH 3/3] iwg20m: add a test that boots a cip-core ramdisk Daniel Sangorrin
2017-12-18 11:36 ` Daniel Wagner [this message]
2017-12-19 1:40 ` [cip-dev] B@D: iwg20m support Daniel Sangorrin
2018-01-02 9:37 ` Trung. Huynh
2018-01-09 8:40 ` Daniel Sangorrin
2018-01-09 10:40 ` Trung. Huynh
2018-01-09 23:55 ` Daniel Sangorrin
2018-01-10 4:04 ` Trung. Huynh
2018-01-10 5:25 ` Daniel Sangorrin
2018-01-10 6:58 ` Trung. Huynh
2018-01-11 5:49 ` Daniel Sangorrin
2018-01-12 2:16 ` Trung. Huynh
2018-03-23 14:34 ` Tram Quynh Thi. Nguyen
2018-03-26 1:08 ` Daniel Sangorrin
2018-03-26 7:54 ` Zoran S
2018-03-26 8:39 ` Tram Quynh Thi. Nguyen
2018-03-26 8:45 ` Daniel Sangorrin
2018-03-26 8:53 ` Tram Quynh Thi. Nguyen
2018-03-26 8:59 ` Daniel Sangorrin
2018-03-28 11:19 ` Tram Quynh Thi. Nguyen
2018-03-28 11:52 ` Zoran S
2018-03-29 3:37 ` Tram Quynh Thi. Nguyen
2018-03-29 8:23 ` Zoran S
2018-03-28 23:23 ` Daniel Sangorrin
2018-01-02 9:45 ` [cip-dev] FW: " Trung. Huynh
2018-01-02 11:26 ` [cip-dev] " Daniel Wagner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8334d32c-edfb-76dd-3246-dca7cd9a9d62@siemens.com \
--to=daniel.wagner@siemens.com \
--cc=cip-dev@lists.cip-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox