(toppers-users 4491) Re: English Version of target SoCFPGA

[Jonathan Sherman]

Thank you for your response,

>From my understanding, I should be able to get Android + SafeG 1.0 working
on my Xilinx ZC702 Board.  First I Should get Android working on the board,
and then patch the linux kernel? and then install Safe-G 1.0 onto the same
partition as Android?

On Thu, Jan 14, 2016 at 5:22 AM, Daniel Sangorrin <
daniel.sangorrin ＠ gmail.com> wrote:

> Hi Jonathan,
>
> > From my understanding, It is only possible to get Android running using
> the
> > newest SafeG version?
>
> No, not at all. You can run Android with mostly any version of SafeG
> if it supports your board.
>
> > I also have a Xilinx ZC702 Board running SafeG-1.0,
> > there's no way SafeG can work for that board?
>
> Yes, there is. You can run SafeG 1.0 on Xilinx ZC702 and Zedboard. If
> you have any problem let me know. In fact, that is the latest version
> that supports the ZC702 SoC. You can also run SafeG 1.0 on QEMU which
> is useful for debugging.
>
> Thanks,
> Daniel
>
> > On Wed, Jan 13, 2016 at 6:06 AM, Daniel Sangorrin
> > <daniel.sangorrin ＠ gmail.com> wrote:
> >>
> >> Hi Jonathan,
> >>
> >> I will assume that you are talking about
> >> "safeg/doc/jp/socfpga/README.txt".
> >> # Perhaps professor Honda can confirm whether there is an English
> >> version or not.
> >>
> >> If you take a look at the document the important information is already
> >> written in English (just skip the Japanese). For small details, please
> use
> >> Google translate or ask here.
> >>
> >> I'd suggest you to start with the prebuilt binaries. Prepare your SDCard
> >> as
> >> indicated in the following site:
> >>
> >>
> >>
> http://www.rocketboards.org/foswiki/Documentation/AlteraSoCDevelopmentBoardSoftwareGettingStarted
> >>
> >> Then copy the prebuilt binaries from
> >> http://toppers.jp/download.cgi/safeg_socfpga-20131203.tar.gz
> >>
> >> Follow the README.txt included with the prebuilt binary package to
> >> load them into
> >> memory (see below).
> >>
> >> Case 1) Trust FMP kernel vs Non-Trusted FMP kernel
> >>
> >>  mmc rescan
> >>  fatload mmc 0:1 0x3f000000 monitor.bin
> >>  fatload mmc 0:1 0x3f100000 fmp_t_sample1.bin
> >>  fatload mmc 0:1 0x01000040 fmp_nt_sample1.bin
> >>  go 0x3f000000
> >>
> >> Case 2) Trust FMP kernel vs Non-Trusted Linux
> >>
> >>  mmc rescan
> >>  fatload mmc 0:1 0x3f000000 monitor.bin
> >>  fatload mmc 0:1 0x3f100000 fmp_t_com.bin
> >>  fatload mmc 0:1 0x01000040 u-boot_nt.bin
> >>  go 0x3f000000
> >>
> >> [Note] Use these commands on the non-trust u-boot:
> >>
> >> mmc rescan;
> >> fatload mmc 0:1 0x7fc0 uImage_nt;
> >> fatload mmc 0:1 0x00000100 socfpga.dtb;
> >> setenv bootargs console=ttyS0,57600 mem=1000M root=/dev/mmcblk0p2 rw
> >> rootwait;
> >> bootm 0x7fc0 - 0x00000100
> >>
> >>
> >> Regarding Android documentation, SafeG only cares about the kernel. It's
> >> mostly
> >> agnostic to the userland binaries that you run (e.g. dalvik or
> >> zygote). The Linux kernel needs
> >> to be patched so that some configuration is done in Trust mode. You can
> >> see the
> >> patches for the kernel version 3.10.31
> >> (http://git.rocketboards.org/linux-socfpga.git)
> >> under the directory "safeg/patches/target/socfpga/"
> >>
> >> - 1_NT_linux_l2.patch (Required)
> >> - 2_NT_linux_com.patch (Optional, only if you want COM the dual-OS
> >> communications module)
> >>
> >> So basically, you would have to first get Android running on your board,
> >> and
> >> then patch its kernel with 1_NT_linux_l2.patch.
> >>
> >> Thanks,
> >> Daniel
> >>
> >>
> >>
> >> On Wed, Jan 13, 2016 at 1:16 PM, Jonathan Sherman
> >> <jonmsherman08 ＠ gmail.com> wrote:
> >> > I was wondering if there was an english version for the target
> >> > README.txt
> >> > file for the Altera SoCFPGA?  Also, is there any documentation
> regarding
> >> > Android?
> >
> >
>
-------------- next part --------------
HTML$B$NE:IU%U%!%$%k$rJ]4I$7$^$7$?(B...
URL: <http://www.toppers.jp/pipermail/users/attachments/20160114/2e110aae/attachment.html>