linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: monstr@monstr.eu (Michal Simek)
To: linux-arm-kernel@lists.infradead.org
Subject: remoteproc: Load coprocessor code to the specific main memory location
Date: Tue, 06 Mar 2012 16:22:06 +0100	[thread overview]
Message-ID: <4F562B9E.7060302@monstr.eu> (raw)
In-Reply-To: <CAK=Wgbaa9rv1pg19sWYFVX_Dvt0J0AzbRtKhPVnhP6WGdMeT9A@mail.gmail.com>

Hi Ohad,

Ohad Ben-Cohen wrote:
> On Wed, Feb 22, 2012 at 2:10 PM, Michal Simek <monstr@monstr.eu> wrote:
>> That will be great to get it. Please let me know when you have them.
> 
> Will do.

I have got the pandaboard (revision A3). u-boot and linux is running on it.
I just need to compile ducati-m3-core0.xem3

I have found the manual at https://github.com/GAnthony/syslink3

In sysbios-rpmsg readme I have found some TI tools which are required
and there is any compilation failure. I think it is because of missing CGT tools

        3) CGT TMS470: 4.9.0
           Public Links:-
             TMS470 Compiler is not available for free publicly. Please contact your TI representative.

Is it possible to compile firmware with this compiler?


I have also tried your bios version at
git://github.com/ohadbc/sysbios-rpmsg.git
branch: rpmsg_3.3_rc1_TLV

compilation passed but it doesn't generate bin file. :-(
I will investigate it tmr.

I would like to compile that bin file myself to be able to add some debug messages.

Thanks for your help,
Michal


-- 
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian

  reply	other threads:[~2012-03-06 15:22 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4F1EE861.4030405@monstr.eu>
2012-01-25 11:42 ` remoteproc: Load coprocessor code to the specific main memory location Ohad Ben-Cohen
2012-01-25 12:41   ` Michal Simek
2012-01-25 13:45     ` Ohad Ben-Cohen
2012-01-25 14:19       ` Michal Simek
2012-01-25 16:24         ` Ohad Ben-Cohen
2012-01-26 10:44           ` Michal Simek
2012-01-27 10:06             ` Michal Simek
2012-01-27 11:38             ` Ohad Ben-Cohen
2012-02-13 14:20               ` Michal Simek
2012-02-14 16:28                 ` Ohad Ben-Cohen
2012-02-15 12:47                   ` Michal Simek
2012-02-15 14:36                     ` Michal Simek
2012-02-16  9:12                       ` Michal Simek
2012-02-16 11:28                         ` Ohad Ben-Cohen
2012-02-16 13:07                           ` Michal Simek
2012-02-16 13:22                             ` Michal Simek
2012-02-16 17:34                               ` Ohad Ben-Cohen
     [not found]                                 ` <CAHTX3dJ4PruKO-wJLJU8W0boHFL0f6eoF+QNaoNjm5hu26YEow@mail.gmail.com>
2012-02-17  1:55                                   ` Ohad Ben-Cohen
2012-02-20 14:22                                     ` Michal Simek
2012-02-20 20:11                                       ` Ohad Ben-Cohen
2012-02-22 12:10                                         ` Michal Simek
2012-02-22 12:59                                           ` Ohad Ben-Cohen
2012-03-06 15:22                                             ` Michal Simek [this message]
2012-03-06 16:26                                               ` Ohad Ben-Cohen
2012-02-16 17:27                             ` Ohad Ben-Cohen

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=4F562B9E.7060302@monstr.eu \
    --to=monstr@monstr.eu \
    --cc=linux-arm-kernel@lists.infradead.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 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).