From: Chris.Paterson2@renesas.com (Chris Paterson)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [isar-cip-core] iwg20m: temporary patch for review
Date: Tue, 4 Jun 2019 09:17:09 +0000 [thread overview]
Message-ID: <TYAPR01MB22856FCFA39D3863764C781EB7150@TYAPR01MB2285.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <TY2PR01MB3323A8D6687CA6A6167A4D01D0150@TY2PR01MB3323.jpnprd01.prod.outlook.com>
Hello Daniel,
> From: daniel.sangorrin at toshiba.co.jp <daniel.sangorrin@toshiba.co.jp>
> Sent: 04 June 2019 09:51
>
> Hello Chris,
>
> > From: Chris Paterson <Chris.Paterson2@renesas.com>
> <snip>
> > > +# Boot partition files
> > > +DTB_FILE = "r8a7743-iwg20d-q7.dtb"
> >
> > I wonder if it is better to use r8a7743-iwg20d-q7-dbcm-ca.dtb instead. This
> does the same as
> > r8a7743-iwg20d-q7.dtb but also enables the add-on board that comes with
> most iwg20d kits.
> > The add-on board adds HDMI output, CAN bus and various SCIF interfaces.
>
> OK, I will use that one then.
>
> > > +# [Note] u-boot is in an SPI flash memory and needs a JTAG debugger to
> re-
> > > flash
> >
> > It is also possible to write to the SPI from Linux, but having JTAG as backup
> is recommended as there is no backup
> > SPI if the write goes wrong.
>
> Yeah, it's a bit risky.
> By the way, the u-boot in the board is from 2013. Is it possible to use a newer
> one? If yes, do you know the name of the configuration file/entrypoint?
Alas no. The u-boot provided by the Renesas RZ/G1 BSP [1] is still only based on v2013.01.01.
[1] https://github.com/renesas-rz/meta-renesas/blob/certified-linux-v2.1.1/meta-rzg1/recipes-bsp/u-boot/u-boot_2013.01.01.bb
Kind regards, Chris
>
> Thanks,
> Daniel
>
>
>
>
> >
> > Kind regards, Chris
> >
> > > +
> > > +# SDCard Boot partition (copies files in IMAGE_BOOT_FILES)
> > > +part /boot --source bootimg-partition --ondisk mmcblk0 --fstype vfat --
> label
> > > boot --align 1 --size 32M --extra-space 0
> > > +
> > > +# Rootfs partition
> > > +part / --source rootfs --ondisk mmcblk0 --fstype ext4 --label root --align
> > > 1024 --size 2G --active
> > > +
> > > +bootloader --append "rootwait console=ttySC0,115200"
> > > --
> > > 2.17.1
> > >
> > > _______________________________________________
> > > cip-dev mailing list
> > > cip-dev at lists.cip-project.org
> > > https://lists.cip-project.org/mailman/listinfo/cip-dev
prev parent reply other threads:[~2019-06-04 9:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 6:14 [cip-dev] [isar-cip-core] iwg20m: temporary patch for review Daniel Sangorrin
2019-06-04 6:19 ` Jan Kiszka
2019-06-04 7:05 ` Chris Paterson
2019-06-04 8:51 ` daniel.sangorrin at toshiba.co.jp
2019-06-04 9:17 ` Chris Paterson [this message]
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=TYAPR01MB22856FCFA39D3863764C781EB7150@TYAPR01MB2285.jpnprd01.prod.outlook.com \
--to=chris.paterson2@renesas.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.