From: Jan Siegmund <jan.siegmund0@hm.edu>
To: Alan Tull <atull@kernel.org>
Cc: "u-boot@lists.denx.de" <u-boot@lists.denx.de>,
"linux-fpga@vger.kernel.org" <linux-fpga@vger.kernel.org>,
matthew.gerlach@linux.intel.com
Subject: Re: Linux hang
Date: Thu, 7 Dec 2017 21:14:54 +0100 [thread overview]
Message-ID: <889a3fd6-5935-899c-a1da-ee974aa6e30e@hm.edu> (raw)
In-Reply-To: <CANk1AXSJc88PcVpDsipDr+1PMjJkCxdnyPfsOGqfuzz2zEWb5Q@mail.gmail.com>
Am 07.12.2017 um 20:19 schrieb Alan Tull:
> On Thu, Dec 7, 2017 at 5:00 AM, Siegmund, Jan <jan.siegmund0@hm.edu> wrote:
>
> Hi SIegmund,
>
>> Hi all,
>> does anybody have an idea for the following problem?
>>
>> * FPGA is programmed using an overlay
>> * FPGA writes to SDRAM via the FPGA2SDRAM-bridge
>> * Linux hangs and the watchdog resets the board (the FPGA stays programmed)
>> * After the reset and boot, the FPGA is reprogrammed using the same overlay
>> * Now, the FPGA can write to the SDRAM without a problem
>>
>> The environment:
>>
>> *Board: DE0-NANO-SoC
>> *U-Boot: 2017.11
>> *Kernel: 4.14.0-rc7 (review-v4.14-rc7-non-dt-support-v5.1 branch)
>>
>> The overlay:
>>
>> /dts-v1/;
>> /plugin/;
>>
>> / {
>> fragment@0 {
>> target-path = "/soc/base_fpga_region";
>> #address-cells = <1>;
>> #size-cells = <1>;
>> __overlay__ {
>> #address-cells = <1>;
>> #size-cells = <1>;
>> fpga-bridges = <&fpga_bridge0 &fpga_bridge1>;
>> firmware-name = "foo_base.rbf";
>>
>> fpga-bridge@ffc25080 {
>> compatible = "altr,socfpga-fpga2sdram-bridge";
>> reg = <0xffc25080 0x4>;
>> bridge-enable = <1>;
>> };
>
> It's been a while since I've touched that bridge, but here's what I
> can think of, hope it helps.
>
> This overlay will add the bridge after programming. It looks like it
> should enable it since you have bridge-enable = <1>, so I'm not sure
> why that's not working.
>
> Would it make sense to add the f2s bridge before doing the fpga
> programming? You could add the f2s bridge in the base device tree and
> add it to your fpga-bridges list so that that bridge is enabled after
> the fpga is programmed.
Hi Alan,
this might be worth a try.
Thanks,
Jan
>
> Alan
>
>>
>> foo@ff200000 {
>> compatible= "altr,bar";
>> interrupt-parent = <&intc>;
>> interrupts = <0 40 4>;
>> };
>>
>> };
>> };
>> };
>>
>> Thanks
>
next prev parent reply other threads:[~2017-12-07 20:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 17:02 Linux hang Siegmund, Jan
2017-12-07 11:00 ` WG: " Siegmund, Jan
2017-12-07 14:01 ` AW: " Goldschmidt Simon
2017-12-07 19:58 ` [U-Boot] " Jan Siegmund
2017-12-07 19:19 ` Alan Tull
2017-12-07 20:14 ` Jan Siegmund [this message]
2017-12-08 13:52 ` Anatolij Gustschin
2017-12-11 16:23 ` Jan Siegmund
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=889a3fd6-5935-899c-a1da-ee974aa6e30e@hm.edu \
--to=jan.siegmund0@hm.edu \
--cc=atull@kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=matthew.gerlach@linux.intel.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).