linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: Eugeniu Rosca <erosca@de.adit-jv.com>,
	Marek Vasut <marek.vasut+renesas@gmail.com>,
	Kieran Bingham <kieran.bingham@ideasonboard.com>,
	Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
Cc: u-boot@lists.denx.de, linux-renesas-soc@vger.kernel.org,
	Michael Dege <michael.dege@renesas.com>,
	Gotthard Voellmeke <gotthard.voellmeke@renesas.com>,
	Adam Bass <adam.bass@renesas.com>,
	Bastian Farkas <bfarkas@de.adit-jv.com>,
	Tobias Franzen <tfranzen@de.adit-jv.com>,
	Philipp Ahmann <pahmann@de.adit-jv.com>,
	Simon Maleyka <smaleyka@de.adit-jv.com>,
	Eugeniu Rosca <roscaeugeniu@gmail.com>
Subject: Re: Automated/remote flashing of R-Car3
Date: Tue, 7 May 2019 15:23:12 +0200	[thread overview]
Message-ID: <79ae01fb-6945-05c5-a08d-92aaffeaa6f0@gmail.com> (raw)
In-Reply-To: <20190507104115.GA27355@vmlxhi-102.adit-jv.com>

On 5/7/19 12:41 PM, Eugeniu Rosca wrote:
> Dear Marek, dear Kieran,

Hi,

[...]

> 1.c Use OpenOCD
> + Presumably same advantages as using a Lauterbach
> + Based on Kieran's https://github.com/kbingham/renesas-jtag
>   and on Adam's https://github.com/ntfreak/openocd/commit/1afec4f561392
>   the solution is currently in use.
> ? Any ideas on the model/price of the JTAG adapter?

Any FT2232H (the H is important, due to MPSSE) works.
I like Flyswatter2 from TinCanTools.

> ? Not tested. Any patches needed on top of vanilla OpenOCD?

http://openocd.zylin.com/5149 and related ones, it adds RPC HF support.
However, there are two problems with this:
1) Even with buffered write, the programming is slow
   - This could be improved by running code on one of the Gen3 CPUs
     instead of whacking registers via JTAG adapter. I believe that's
     what lauterbach and everyone else does too. The data upload to
     SRAM/DRAM is fast via JTAG, register IO is not great.
2) LifeC locks the RPC HF access
   - This is a problem, since the JTAG probe cannot access it once
     it's locked. There might be a way around it, but it's rather
     nasty -- use boundary scan test mode to either flip MD pins or
     access the HF bus directly and bitbang at least erase command
     to wipe the first few sectors, then reset the CPU and have it
     drop to SCIF loader mode, then stop the CPU and reprogram the
     HF (since the SCIF loader runs in EL3 and does not touch the
     lifec settings.

Neither of 1) and 2) is implemented, but can be implemented if there is
interest.

> 1.d. Use CPLD Configurator
> + H3_M3_StarterKit_Configurator.exe is a Windows tool shipped by
>   Renesas, hence readily available, which allows to modify the MD
>   pins, to conveniently switch between QSPI/Hyperflash/SCIF
>   boot mode from a GUI
> + Most of the advantages pointed out above
> - ULCB-only solution (i.e. does not apply to Salvator-X)
> - Requires a Windows host

Where can I obtain this and are there sources / documentation available?

-- 
Best regards,
Marek Vasut

  reply	other threads:[~2019-05-07 13:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-07 10:41 Automated/remote flashing of R-Car3 Eugeniu Rosca
2019-05-07 13:23 ` Marek Vasut [this message]
2019-05-07 15:53   ` Eugeniu Rosca
2019-05-07 16:09     ` Marek Vasut
2019-05-08  9:32       ` Eugeniu Rosca
2019-05-08 11:30         ` Marek Vasut
2019-05-08 12:07       ` Michael Dege
2019-05-08 13:51       ` Eugeniu Rosca
2019-05-08 15:11         ` Marek Vasut

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=79ae01fb-6945-05c5-a08d-92aaffeaa6f0@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=adam.bass@renesas.com \
    --cc=bfarkas@de.adit-jv.com \
    --cc=erosca@de.adit-jv.com \
    --cc=gotthard.voellmeke@renesas.com \
    --cc=kieran.bingham+renesas@ideasonboard.com \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=marek.vasut+renesas@gmail.com \
    --cc=michael.dege@renesas.com \
    --cc=pahmann@de.adit-jv.com \
    --cc=roscaeugeniu@gmail.com \
    --cc=smaleyka@de.adit-jv.com \
    --cc=tfranzen@de.adit-jv.com \
    --cc=u-boot@lists.denx.de \
    /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;
as well as URLs for NNTP newsgroup(s).