On 25/07/2016 16:58, Tim Sander wrote:
Hi Phil
Am Montag, 25. Juli 2016, 16:47:22 schrieb Phil Reid:
On 25/07/2016 15:09, Teoh Choon Zone wrote:
    Whats in brgmodrst (0xFFD0501C)?

    0xFF401FD0 is the lw hps2fpga bridge.

    0xC000000D looks a bit odd for lw hps2fpga bridge devices.
    That should be for the high speed hps2fpga bridge.

    lw hps2fpga is at base 0xFF200000

root@linaro-developer:~/test# devmem2 0xFFD0501C
/dev/mem opened.
Memory mapped at address 0xb6fa4000.
Value at address 0xFFD0501C (0xb6fa401c): 0x0

Ya, you're right. My FPGA design utilise both the LW and H2F bridges. LW
bridge is working as I can see the interrupts coming from FPGA. Only the
H2F is not working, I couldn't read whatever register from the FPGA side
although I've mmaped 0xC0000000. This is strange right? Is this related
to the privileged access issue as in Arria device?

Hmm I haven't used the h2f bridge for a while and just checked, and have
problems. I currently got  lw h2f for register control and f2h for IP cores
to access the HPS DDR working fine.

My system hangs and reboots after a read to 0xc0000000 (which is a 0.5G DDR3
device connected to the FPGA's hard DDR controller). Tested using uboot
2016.01 and read / write to this address 0xc0000000  via h2f window works
fine. Reset are all enabled under Linux.

So looks like possible fpga region is not getting mapped correctly and I'm
not sure where this is done. New one for me. The fpga-region stuff may be
related:

base_fpga_region {
        compatible = "fpga-region";
        fpga-mgr = <&fpga_mgr>;
        fpga-bridges = <&fpga_bridge0>, <&fpga_bridge1>;

        #address-cells = <0x1>;
        #size-cells = <0x1>;
        ranges = <0 0xff200000 0x100000>;

Shouldn't this look like this:
                        ranges = <0 0x0 0xc0000000 0x20000000>,
                                <1 0x0 0xff200000 0x00200000>;

or if you would like to keep your indexes:
                        ranges = <0 0x0 0xff200000 0x00200000>,
                                         <1 0x0 0xc0000000 0x20000000>;

};

The dtsi only reference the lw h2f range, not sure if that's related.
Someone with a bit more knowledge may be able to offer some advice.
I am currently still chewing on the configs you sent me...


Yeap that worked for me. I can now 'devmem2 0xc0000000' and get something 
meaningful.
Thanks for the suggestion.


--
Regards
Phil Reid

ElectroMagnetic Imaging Technology Pty Ltd
Development of Geophysical Instrumentation & Software
www.electromag.com.au

3 The Avenue, Midland WA 6056, AUSTRALIA
Ph: +61 8 9250 8100
Fax: +61 8 9250 7100
Email: pr...@electromag.com.au
_______________________________________________
Rfi mailing list
Rfi@lists.rocketboards.org
http://lists.rocketboards.org/cgi-bin/mailman/listinfo/rfi

Reply via email to