public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Purna Chandra Mandal <purna.mandal@microchip.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] drivers: mtd: add Microchip PIC32 internal non-CFI flash driver.
Date: Fri, 11 Mar 2016 14:11:46 +0530	[thread overview]
Message-ID: <56E284CA.9040307@microchip.com> (raw)
In-Reply-To: <56E1796E.5090707@openedev.com>

On 03/10/2016 07:11 PM, Jagan Teki wrote:
> On Thursday 10 March 2016 06:42 PM, Purna Chandra Mandal wrote:
>> PIC32 embedded flash banks are memory mapped, directly read by CPU,
>> and programming (erase followed by write) operation on them are
>> handled by on-chip NVM controller.
>
> Can you please add some more description to understand bit more, which kind of flash it is, parallel NOR?
>
Jagan,

These are parallel NOR flash divided into number of banks to allow
erase/programming in one while fetch/execution continues from other.
As the flash is memory-mapped code stored can be directly executed
from flash (XIP), also there is additional hardware logic to prefetch
and cache contents to improve code execution. These flash can also
be used to store user data.

In PIC32 there are two sets of embedded flash memory of same type -
boot flash, and program flash; early-boot-code executes from
boot-flash and one bank of program-flash is used for u-boot, other
bank for environment.

> thanks!
> -- 
> Jagan.

  reply	other threads:[~2016-03-11  8:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-10 13:12 [U-Boot] [PATCH] drivers: mtd: add Microchip PIC32 internal non-CFI flash driver Purna Chandra Mandal
2016-03-10 13:41 ` Jagan Teki
2016-03-11  8:41   ` Purna Chandra Mandal [this message]
2016-03-14 12:43 ` Daniel Schwierzeck
2016-03-14 13:30   ` Purna Chandra Mandal
2016-03-14 13:46     ` Jagan Teki
2016-03-14 14:07       ` Purna Chandra Mandal
2016-03-15 12:05         ` Jagan Teki
2016-03-16 11:07           ` Purna Chandra Mandal
2016-03-16 14:25             ` Jagan Teki

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=56E284CA.9040307@microchip.com \
    --to=purna.mandal@microchip.com \
    --cc=u-boot@lists.denx.de \
    /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