public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Kurt Siedenburg <kurt.siedenburg@vicom.com>
To: Les Miklosy <lgm0@verizon.net>,
	"ecos-discuss@ecos.sourceware.org"
	<ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] RedBoot hits fetch instruction trap
Date: Wed, 30 Jul 2014 06:36:00 -0000	[thread overview]
Message-ID: <279D77960F36224FAA5BAC312F54F6F73712AA9C@AUSP01DAG0302.collaborationhost.net> (raw)
In-Reply-To: <53D8804D.2050404@verizon.net>

I once had a similar problem which turned out to be unaligned instructions.
Source was an assembly file with embedded strings which didn't contain proper alignment directives.
Thus a modified string now contained an odd number of characters.  And the instructions after that string all became unaligned.

Please note that I never dealt with Sparc - only with ARM and MIPS and some x86.  So I don't know if the above applies in your case.

If you want to follow up on this you can look at your map file.
Check if the addresses for _timer_poll, do_idle, and net_io_test happens to be odd (with DEBUG disabled).
Possibly with DEBUG enabled the addresses could be aligned again.

Good luck,
  Kurt

-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org [mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of Les Miklosy
Sent: Tuesday, July 29, 2014 10:19 PM
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] RedBoot hits fetch instruction trap

During execution of RedBoot configured for a  Sparc Leon3 IP core the process hits a trap on instruction fetch in the RedBoot routine _timer_poll(). The debugger history and assembly are attached. The process will execute RedBoot commands at the command prompt and otherwise behave normally until a branch instruction to do_idle and subsequently net_io_test(), that is where execution eventually fails.

Oddly the process runs without fault when DEBUG command options are selected during configuration of the build with configtool, trouble begins when the DEBUG options are again removed. The DEBUG instructions appear in the ethernet modules and in RedBoot's net_io. If this is a timing issue can someone please suggest what parameters can be tweeked to resolve the traps, or if a memory alignment problem can someone offer a memory map and alignment parameters? Are there configuration selections in the amba bus header file, those might be helpful too.

The compiler is sparc-elf-gcc-3.4.4  I'm using two additional compilation flags  -msoft-float and D-ECOS. The system configuration is also attached to this email.  Thank you for directions. -Les

--
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:[~2014-07-30  6:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-30  5:24 Les Miklosy
2014-07-30  6:36 ` Kurt Siedenburg [this message]
2014-07-30 21:25   ` Les Miklosy
2014-07-31  6:22   ` Les Miklosy
2014-07-31  9:08     ` Kurt Siedenburg

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=279D77960F36224FAA5BAC312F54F6F73712AA9C@AUSP01DAG0302.collaborationhost.net \
    --to=kurt.siedenburg@vicom.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=lgm0@verizon.net \
    /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).