public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Rohit Pandita <pandi008@umn.edu>
To: Gary Thomas <gary@mlbassoc.com>
Cc: ecos-discuss@sourceware.org
Subject: Re: [ECOS] processor hangs at 'hal_mon_init'
Date: Wed, 28 Jun 2006 19:47:00 -0000	[thread overview]
Message-ID: <44A2DCA4.8060403@umn.edu> (raw)
In-Reply-To: <W790762629185061151479637@webmail6>

bob.koninckx@o-3s.com wrote:
>> -----Original Message-----
>> From: Rohit Pandita [mailto:pandi008@umn.edu]
>> Sent: Tuesday, June 27, 2006 05:36 PM
>> To: 'Gary Thomas'
>> Cc: ecos-discuss@sourceware.org
>> Subject: Re: [ECOS] processor hangs at 'hal_mon_init'
>>
>> Gary Thomas wrote:
>>> Rohit Pandita wrote:
>>>> Hi all,
>>>>
>>>> While trying to singlestep through RedBoot in ROM (platform 
>>>> PhyCore555), processor hangs at 'hal_mon_init' routine. Any clues 
>>>> would be appreciated.
>>> What are you using to single step the code?  That macro fiddles with
>>> the MSR (Machine State Register) and it might do something that confuses
>>> your debug environment.
>>>
>> Im using P&E Micro's BDM interface(usb-ml-ppcbdm) and debugger(icdppcz). 
>> Thanks.
> 
> Most BDMs exploit the MPC555 hardware to step instruction by instruction, so I doubt that could be the cause of your problem. It is more likely that something is wrong with your configuration. Which startup type do you use (ROM or RAM), is CYGSEM_HAL_USE_ROM_MONITOR defined ? Do you have any idea where exactly in hal_mon_init things go wrong ? What's the contents of the different processor registers right before it locks up ? Does it actually lock up, or is a processor exception raised (e.g. illegal instruction or memory protection) that does not bring the processor back into BDM mode ?
> 
> Bob
> 
Hi,
- using ROM startup, CYGSEM_HAL_USE_ROM_MONITOR not included (RedBoot 
set to behave as ROM monitor)
- error occurs at instruction 'STWU R0,0004(R4)' in hal_mon_init.
Before execution: R0=7C71 43A6, R4=FFFF FFFC
After: -no change-

Why is it trying to write to a ROM location (0000 0000) when VSR table 
should be copied to RAM, if I understand correctly

- execution halts with a debugger msg 'waiting for a keystroke or 
breakpoint'

I can send across the configuration(.ecc) file or anything else that 
might help. Thanks in advance.

Rohit

>> -- 
>> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
>> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>>
>>
> 
> 


-- 

Rohit Pandita
Graduate Student

Office:
    15, Akerman Hall
Mail address:
    107, Akerman Hall
    Department of Aerospace Engineering and Mechanics
    University of Minnesota
    110, Union Street S.E.
    Minneapolis, MN 55455
Tel: 1-612-625-6561
Fax: 1-612-625-1558


-- 
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:[~2006-06-28 19:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-28  7:27 bob.koninckx
2006-06-28 19:47 ` Rohit Pandita [this message]
2006-06-29 21:28   ` Bob Koninckx
2006-07-03 17:42     ` Rohit Pandita
  -- strict thread matches above, loose matches on Subject: below --
2006-07-04  7:11 bob.koninckx
2006-06-27 19:06 Rohit Pandita
2006-06-27 20:32 ` Gary Thomas
2006-06-27 21:37   ` Rohit Pandita

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=44A2DCA4.8060403@umn.edu \
    --to=pandi008@umn.edu \
    --cc=ecos-discuss@sourceware.org \
    --cc=gary@mlbassoc.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).