public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jesper Skov <jskov@redhat.com>
To: "Jurica Baricevic" <jura@INTESIS.hr>
Cc: "Ecos" <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] Stand-alone application working from RAM
Date: Wed, 19 Jul 2000 23:48:00 -0000	[thread overview]
Message-ID: <otya2xb8kv.fsf@thinktwice.zoftcorp.dk> (raw)
In-Reply-To: <001a01bff19e$7874cab0$6b00a8c0@JURA>

>>>>> "Jurica" == Jurica Baricevic <jura@INTESIS.hr> writes:

Jurica> forgot to write it?). So, now I am going to link my
Jurica> application to 0x80000000 (my rom_vectors section is at the
Jurica> beginning of code) and hope that it will work.  Otherwise, I
Jurica> will have to go deeper into HAL...  Anyway, I wonder is there
Jurica> maybe anything else that I should care about?

Yes, that might do it.

Alternatively have the hal_memc_init macro copy the vectors there. I
have the below (in a still not published platform HAL):

(from platform.inc)

#if !defined(CYG_HAL_STARTUP_RAM) || !defined(CYGSEM_HAL_USE_ROM_MONITOR)
        .macro  hal_memc_init
        <possibly init memory controllers here!>
#if !defined(CYGSEM_HAL_USE_ROM_MONITOR)
        // If we don't play nice with a ROM monitor, copy the required
        // vectors into the proper location.
        la      t0,0x80000000           # dest addr
        la      t1,utlb_vector          # source addr
        la      t3,utlb_vector_end      # end dest addr
1:      
        lw      v0,0(t1)                # get word
        addi    t1,t1,4
        sw      v0,0(t0)                # write word
        addi    t0,t0,4
        bne     t1,t3,1b
        nop

        la      t0,0x80000180           # dest addr
        la      t1,other_vector         # source addr
        la      t3,other_vector_end     # end dest addr
1:      
        lw      v0,0(t1)                # get word
        addi    t1,t1,4
        sw      v0,0(t0)                # write word
        addi    t0,t0,4
        bne     t1,t3,1b
        nop
#endif
        .endm
#define CYGPKG_HAL_MIPS_MEMC_DEFINED        
#endif


Jesper

  reply	other threads:[~2000-07-19 23:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-19  9:29 Jurica Baricevic
2000-07-19 23:48 ` Jesper Skov [this message]
2000-07-20  7:52   ` Jurica Baricevic
2000-07-20  9:00     ` Jesper Skov

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=otya2xb8kv.fsf@thinktwice.zoftcorp.dk \
    --to=jskov@redhat.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=jura@INTESIS.hr \
    /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).