From: Kylo Ginsberg <kylo@kylo•net>
To: Fahd Abidi <fabidi@ultsol•com>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: bdi2000 + mpc8560ads, very early breakpoints
Date: Wed, 13 Apr 2005 11:59:15 -0700 [thread overview]
Message-ID: <425D6C03.1070805@kylo.net> (raw)
In-Reply-To: <81C69D96BDD30640952C7A404004AA25018DB9@ultsol01.tewks.ultsol.local>
Thanks; that was instructive. I hadn't read up on the 85xx debug
exceptions yet.
For posterity, my issue was that even though the code is running out of
ddr at this stage, u-boot has left the IVPR pointed at flash. So once
head_e500.S invalidated the tlb entry for the flash region, the debug
exception vector was inaccessible and a breakpoint sent the processor
off the road. As a workaround, I modified u-boot to re-point IVPR when
it relocates itself into ddr.
Cheers,
Kylo
Fahd Abidi wrote:
>Try the suggestions pointed out in here:
>
>http://www.ultsol.com/faq-P308.htm
>
>This is based off suggestions from another customer. Let me know if this
>works for you or not.
>
>Fahd
>
>-----Original Message-----
>From: Kylo Ginsberg [mailto:kylo@veriwave•com]
>Sent: Tuesday, April 12, 2005 3:21 PM
>To: linuxppc-embedded@ozlabs•org
>Subject: bdi2000 + mpc8560ads, very early breakpoints
>
>I'm running a bdi2000 (with mpc85xx-gdb f/w 1.03) with a mpc8560ads
>target, and I'm trying to set breakpoints early on in linux startup (in
>the head_e500.S code that sets up tlb's). I'm setting the breakpoints
>from within the bdi telnet interface.
>
>I can:
>--succesfully hit a breakpoint set up to any instruction <= the address
>of the first 'tlbwe'.
>--single step (with the bdi "TI" command) past that 'tlbwe' as far as
>I've cared to try
>
>I cannot:
>--hit a breakpoint once the first 'tlbwe' has executed. If I attempt to
>
>do so, linux startup doesn't proceed, I lose further communication with
>the target and the BDI claims "COP Freeze" and I have to reset the
>target.
>
>Btw, the 'tlbwe' in question marks invalid the first tlb1 entry setup by
>
>u-boot, which pointed at flash address space. Code is running out of
>ram at this point.
>
>I'm probably missing something very basic here. Any ideas?
>
>Thanks,
>Kylo
>
>_______________________________________________
>Linuxppc-embedded mailing list
>Linuxppc-embedded@ozlabs•org
>https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>_______________________________________________
>Linuxppc-embedded mailing list
>Linuxppc-embedded@ozlabs•org
>https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>
>
next prev parent reply other threads:[~2005-04-13 19:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-13 13:37 bdi2000 + mpc8560ads, very early breakpoints Fahd Abidi
2005-04-13 18:59 ` Kylo Ginsberg [this message]
2005-04-13 19:37 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2005-04-12 19:21 Kylo Ginsberg
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=425D6C03.1070805@kylo.net \
--to=kylo@kylo$(echo .)net \
--cc=fabidi@ultsol$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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