Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Vermeulen Jan <Jan.Vermeulen@siemens.atea.be>
To: "'gdb@sources.redhat.com'" <gdb@sources.redhat.com>
Subject: powerpc simulator questions
Date: Thu, 01 Nov 2001 15:25:00 -0000	[thread overview]
Message-ID: <E76F715C0429D5118F2100508BB9EDEE0261359D@hrtades7.atea.be> (raw)

Hello everybody,

I'm already subscribed to the crossgcc list for some time now, so i thought
"why not venture into the gdb-world as well?" :)

I noticed that you have the option of stepping through your code by means of
a simulator. Whoever invented that: hats off :) It's really usefull. (if i
ever get it working... hehe)

However, being a complete n00b on the gdb-topic, I compiled/installed
Insight-5.0 with the "--target=powerpc-eabi" option.

I made a little test program, called 'destest' which simply encrypts and
decrypts an 8 byte value. No include files are used, there is only destest.c

I compiled it with "powerpc-eabi-gcc -g -Wl,-Tmylink.ld -o destest
destest.c".

mylink.ld:
OUTPUT_ARCH(powerpc)   /* Specify the output machine architecture */

ENTRY(main);

/*
MEMORY
{
  vects (rx): ORIGIN = 0x0,  LENGTH = 1023 
  rom1 (rx): ORIGIN = 0x400, LENGTH= 511K
  ramcode (rwx): ORIGIN = 0x800000, LENGTH = 2048K
  ramdata (rw): ORIGIN = 0x0A00000, LENGTH = 2048K
}
*/

SECTIONS {
  . = 0x0;
  .vector0 :
    {
      LONG(ABSOLUTE( main ))
    }
  . = 0x400;
  .text :
    { 
    *(.text)
    }
  . = 0xA00000;
  .data : 
    {
    *(.data)
    }
  .bss  :
    { 
    *(.bss)
      end = ALIGN(0x8);
    }
}

Then i ran insight, did "target sim", "load" and it spit out something like
/openprom/init/load-binary: broken transfer.

I have no clue as to what's going on.
I first made the directory 'openprom' under root, but i have a hunch that's
not really what i should be doing. My guess is that /openprom is something
in memory being used by powerpc-eabi-gdb.

Can anybody help me? Or point me to a HOWTO/FAQ/manual?
I read the gdb manual and the psim manual, but no real step-by-step
(holding-the-newbie's-hand) procedure is explained there. :-)

Thank you in advance,
Jan


             reply	other threads:[~2001-11-13 10:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-01 15:25 Vermeulen Jan [this message]
2001-11-01 16:30 ` Andrew Cagney
2001-11-01 16:43 ` Frank Ch. Eigler
2001-11-02 18:33 Vermeulen Jan
2001-11-27 20:39 ` Andrew Cagney
2001-11-18 11:45   ` Andrew Cagney

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=E76F715C0429D5118F2100508BB9EDEE0261359D@hrtades7.atea.be \
    --to=jan.vermeulen@siemens.atea.be \
    --cc=gdb@sources.redhat.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