From: "Tales Toledo" <toledo.tales@gmail.com>
To: "Gary Thomas" <gary@mlbassoc.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] PowerPC Redboot porting problems
Date: Thu, 21 Jun 2007 11:44:00 -0000 [thread overview]
Message-ID: <2308fb0f0706201347i7a8e01fx7ec2baf0b69f13f6@mail.gmail.com> (raw)
In-Reply-To: <46798E18.9010204@mlbassoc.com>
Hi,
I see some progress now.
I was downloading .bin file to 0x0 (the same procedure I was using
before when I tried to download code to RAM an programming to flash).
I decide to move from .bin to .elf and voilá...
Now I have a new message
--------------------------------------------------------------
Program received signal SIGINT, Interrupt.
CR := (CR0|4CR1|8CR2|12CR3|16CR4|20CR5|24CR6|28CR7)
SPR 2:Condition Register, UM140
CR = 0x2042488d =
(CR0=0x2|CR1=0x0|CR2=0x4|CR3=0x2|CR4=0x4|CR5=0x8|CR6=0x8|CR7=0xd)
ICR := (|RST|CHSTP|MCI||6EXTI|ALI|PRI|FPUVI|DECI||13SYSI|TR||17SEI|ITLBMS|DTBLMS|ITLBER|DTLBER||28LBRK|IBRK|EBRK|DPI)
SPR 148:Interrupt Cause Register, UM994
ICR = 0x00004000 = (SEI)
0x4b6c0 in hal_hardware_init ()
---------------------------------------------------------------
looking at disassembled file
---------------------------------------------------------------
4b6b8: 90 64 01 74 stw r3,372(r4)
4b6bc: 3c 60 40 00 lis r3,16384
4b6c0: 60 63 08 01 ori r3,r3,2049
4b6c4: 3c a0 ff 80 lis r5,-128
4b6c8: 60 a5 07 74 ori r5,r5,1908
4b6cc: 90 64 01 00 stw r3,256(r4)
4b6d0: 90 a4 01 04 stw r5,260(r4)
4b6d4: 3c 60 00 00 lis r3,0
4b6d8: 60 63 00 81 ori r3,r3,129
4b6dc: 3c a0 ff 80 lis r5,-128
4b6e0: 60 a5 0e 00 ori r5,r5,3584
4b6e4: 90 64 01 08 stw r3,264(r4)
4b6e8: 90 a4 01 0c stw r5,268(r4)
---------------------------------------------------------------
seems that the exception occurs when I'm programming BR0/OR0
-------------------------------------------
/*
* Base Register initialization.
*/
/* BOOT ROM */
lwi r3,0x40000801 # 16-bit, GPCM
lwi r5,0xFF800774 # 7 wait states, up to 8MB
stw r3,BR0(r4)
stw r5,OR0(r4)
/* ONBOARD SDRAM */
lwi r3,0x00000081 # 32-bit, UPMA
lwi r5,0xFF800E00
stw r3,BR1(r4)
stw r5,OR1(r4)
-----------------------------------------------
I didn't see the problem yet. Any idea.
Thanks,
TT.
On 6/20/07, Gary Thomas <gary@mlbassoc.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Tales Toledo wrote:
> > Hi,
> >
> > I'm facing some problems trying to port redboot to MPC885...
> > I have tried to follow the steps suggested at porting guide. I'm using only
> > RAM as a first step but unfortunately I can get success. I'm using
> > Viper files as reference.
> >
> > I'm using gdb with mpcbdm and get always the same exception when
> > running it from RAM.
>
> Look carefully - this is failing on the first instruction you downloaded,
> so it most certainly has nothing to do with porting eCos.
> * Have you verified the code that was downloaded correctly?
> * Have you successfully executed any code on this platform using these tools?
>
> - --
> - ------------------------------------------------------------
> Gary Thomas | Consulting for the
> MLB Associates | Embedded world
> - ------------------------------------------------------------
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
>
> iD8DBQFGeY4YmaKbSsQGV8ARAirMAJ9xEKtFrDXYOh5jB59disiPExgbUgCgjT0j
> xmJBNpW1xfQruVljpMs/JrY=
> =/UuG
> -----END PGP SIGNATURE-----
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2007-06-20 20:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-20 21:46 Tales Toledo
2007-06-21 3:48 ` Gary Thomas
2007-06-21 11:44 ` Tales Toledo [this message]
2007-06-24 9:15 ` Tales Toledo
2007-06-27 21:21 ` Tales Toledo
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=2308fb0f0706201347i7a8e01fx7ec2baf0b69f13f6@mail.gmail.com \
--to=toledo.tales@gmail.com \
--cc=ecos-discuss@ecos.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).