public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Elad Yosef <elad.yosef@gmail.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Flash Driver and Cache in MIPS32
Date: Fri, 01 Jul 2011 12:22:00 -0000	[thread overview]
Message-ID: <BANLkTinz4yKYOici5YQW70TfgRUm6dcFUg@mail.gmail.com> (raw)

Hi,
My RedBoot text is located in cached segment (called Kseg0)
My RedBoot data+bss are located in un-cached segment (called Kseg1)
(Due to the RAM limitations I can't refer my RAM as cached)
My flash driver's code is located in the RAM.

When I try to access my flash driver for format/program.
I need to manipulate the flash HW API and while doing so the flash is
an unavailable for reading!!!
(Need to do write enable and send other commands to the flash)
It is HW SPI core that enables me to refer the flash as memory mapped
for reading actions.

I have a problem to format my driver. I get an exception during the
format command.
Since my exception base is mapped to a flash address my RedBoot crash
(infinite exceptions loop) from obvious reason -
the flash is unavailable for reading!!!

I linked my RedBoot data+bss into cached segment (which I can't normally use)
And my flash driver works perfectly.

Is there a methodology to to jump between cached and un-cached code execution?
There are macro's inside I/O package for such cases but I'm sure they
fit my target.

Thanks
Elad

-- 
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:[~2011-07-01 12:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=BANLkTinz4yKYOici5YQW70TfgRUm6dcFUg@mail.gmail.com \
    --to=elad.yosef@gmail.com \
    --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).