public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Agus Ariffianto <aariffianto@s.ee.itb.ac.id>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] error: no memory region specified for loadable '.ram_vectors'
Date: Tue, 30 May 2006 11:19:00 -0000	[thread overview]
Message-ID: <20060530111849.GM2876@lunn.ch> (raw)
In-Reply-To: <02bc01c683cc$5abbc520$6c44cda7@aariffianto>

On Tue, May 30, 2006 at 04:35:14PM +0700, Agus Ariffianto wrote:
> >>>>>My guess is you have the interface to Redboot enabled, but the current
> >>>>>leon port does not support this.
> >>>
> >>>Try turning off:
> >>>
> >>>CYGPKG_HAL_ROM_MONITOR
> >>>CYGSEM_HAL_VIRTUAL_VECTOR_SUPPORT
> >>>
> >>>       Andrew
> >>
> >>Dear Andrew,
> >>the option CYGSEM_HAL_VIRTUAL_VECTOR_SUPPORT couldn't be disable. Thank 
> >>you
> >
> >Ah, O.K. I did not read the cdl closely enough.
> >
> >You want this either disabled, or not active.
> >
> >It is active if CYGINT_HAL_VIRTUAL_VECTOR_SUPPORT is 1 or more. What
> >value does it have for you? If it is 1 or more what implements it?
> >
> >     Andrew
> >
> 
> Property        Value
> Macro            CYGSEM_HAL_VIRTUAL_VECTOR_SUPPORT
> Enabled        True
> Activelf        CYGINT_HAL_VIRTUAL_VECTOR_SUPPORT
> Calculated    1
> Compile        hal_if.c    hal_misc.c

You need to start understanding things for yourself. Why is
CYGINT_HAL_VIRTUAL_VECTOR_SUPPORT 1? It is an interface, so something
must be implementing it. What? Is it possible to disable what is
implementing the interface?

You will probably find this documentation useful. It tells you all
about the cdl language.

http://ecos.sourceware.org/docs-latest/cdl-guide/cdl-guide.html

        Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2006-05-30 11:19 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-29  9:20 Agus Ariffianto
2006-05-29  9:44 ` Andrew Lunn
2006-05-29 10:40   ` Agus Ariffianto
2006-05-29 12:20     ` Andrew Lunn
2006-05-30  4:00       ` Agus Ariffianto
2006-05-30  7:28         ` AW: " Ram Sudhir Tadavarthi
2006-05-30  7:38           ` Andrew Lunn
2006-05-30 11:49           ` Agus Ariffianto
2006-05-30 12:02             ` Andrew Lunn
2006-05-30 12:40               ` Agus Ariffianto
2006-05-30 12:59                 ` Andrew Lunn
2006-05-30 13:02               ` Agus Ariffianto
2006-05-30 13:18                 ` Andrew Lunn
2006-05-30 13:28                   ` Agus Ariffianto
2006-06-13  9:31                   ` [ECOS] error: no memory region specified for loadable '.ram_vectors' => Now it works Agus Ariffianto
2006-05-30  4:06       ` [ECOS] error: no memory region specified for loadable '.ram_vectors' Agus Ariffianto
2006-05-30  7:43         ` Andrew Lunn
2006-05-30  9:36           ` Agus Ariffianto
2006-05-30 11:19             ` Andrew Lunn [this message]
2006-05-29  9:38 Agus Ariffianto
2006-05-29 11:21 Agus Ariffianto

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=20060530111849.GM2876@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=aariffianto@s.ee.itb.ac.id \
    --cc=ecos-discuss@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).