public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: James Bowman <james.bowman@ftdichip.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH, FT32] gdb and sim support
Date: Thu, 26 Mar 2015 07:10:00 -0000	[thread overview]
Message-ID: <20150326071024.GB12423@vapier> (raw)
In-Reply-To: <CA9BBF0458F83C4F9051448B941B57D117234AD6@glaexch1>

[-- Attachment #1: Type: text/plain, Size: 1598 bytes --]

On 23 Mar 2015 19:20, James Bowman wrote:
> +/*
> + * FT32 is a Harvard architecture: RAM and code occupy
> + * different address spaces.
> + *
> + * sim and gdb model FT32 memory by adding 0x800000 to RAM
> + * addresses. This means that sim/gdb can treat all addresses
> + * similarly.
> + * 
> + * The address space looks like:
> + *
> + *    00000   start of code memory
> + *    3ffff   end of code memory
> + *   800000   start of RAM
> + *   80ffff   end of RAM
> + */

do they actually occupy different address spaces ?  that is to say, if you put 
address 0 into a register and try to do a data load/store, does it throw an 
exception ?  or is it transparently routed to 800000 ?

Blackfin cpus are described as Harvard because it has on-chip memory that can 
only be accessed either as insn or as data, but it's a unified memory map.  for 
example, if you were to execute (jump to) 0xffa00000, it'd work, but if you 
tried to do a load/store with 0xffa00000, the hardware would throw an exception.  
if you were to execute (jump to) 0xff800000, the hardware would throw an 
exception, but you could do a load/store just fine.

i'm not sure gdb or the sim generally support processors with overlapping 
memory.  i.e. a $pc of 0 is completely different from a $r0 (data register) with 
the address of 0.

i tried to grab some datasheets from ftdichip.com, but (1) couldn't seem to find 
anything on the architecture (just datasheets for specific parts which covered 
more system devices than the ISA/core) and (2) it's crazy slow to download from.
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-03-26  7:10 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-03  4:06 James Bowman
2015-02-10  6:27 ` James Bowman
2015-02-17 10:21   ` Mike Frysinger
2015-02-19  7:06 ` Mike Frysinger
     [not found] ` <ORIGINAL-RELEASE-1424557036-20150219070610.GI544@vapier>
2015-02-23 10:40   ` James Bowman
2015-02-24  4:52     ` Mike Frysinger
2015-03-10 16:56       ` James Bowman
2015-03-16  8:25         ` Mike Frysinger
2015-03-19 15:26           ` James Bowman
2015-03-19 18:52             ` Mike Frysinger
2015-03-20  2:57               ` James Bowman
2015-03-20  5:18                 ` Mike Frysinger
2015-03-20  5:19                   ` Mike Frysinger
2015-03-23 19:21                     ` James Bowman
2015-03-26  7:10                       ` Mike Frysinger [this message]
2015-03-26 19:05                         ` James Bowman
2015-03-16 16:38         ` Mike Frysinger
2015-03-17 17:36         ` Joel Brobecker
2015-03-19 15:21           ` James Bowman
2015-03-19 18:54             ` Mike Frysinger
2015-03-20  3:01               ` James Bowman
2015-03-20  3:47                 ` Mike Frysinger
2015-03-20 12:46                 ` Joel Brobecker
2015-03-20 15:47                   ` Mike Frysinger
2015-03-20 15:50                     ` Joel Brobecker
2015-03-22 22:33                       ` Mike Frysinger
2015-03-23 12:36                         ` Joel Brobecker
2015-03-23 19:15                           ` James Bowman
2015-03-23 23:04                             ` Joel Brobecker
2015-03-28  6:21 ` Mike Frysinger

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=20150326071024.GB12423@vapier \
    --to=vapier@gentoo.org \
    --cc=gdb-patches@sourceware.org \
    --cc=james.bowman@ftdichip.com \
    /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).