[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [microblaze-uclinux] pid X: failed 256 WAS: problems booting kernel
even though, it is somewhat of a new problem, I thought I'd post this
under the same thread, since I'm still working with the same hardware.
I've created a user application, basically "hello, world", using
printf, added it to the /user/ tree, and it seems to get built just
fine, but when I run it on the sh shell I get back:
pid X: failed 256
where X is an integer value that keeps increasing and increasing.
I've noticed this is happening with several other /bin programs:
typing "kill" gives:
BusyBox v1.00 (2004.11.17-01:49+0000) multi-call binary
pid 68: failed 256
I'm guessing these programs are crashing, and this is just sash's way
of telling us, but I have feeling this is some omission on my part.
It does with or without printf. It does it returning void or int.
I looked around, but this is a tough one to search on. Any ideas?
On Mon, 22 Nov 2004 23:45:55 -0500, John Carter <email@example.com> wrote:
> that is quite true. It is definately quite amazing that you emailed
> me a processor, and that it took a blink of an eye to download. (and
> it works!)
> it is quite possible that those lines got taken out of the mhs file,
> though I used the makefile for mb_vanilla. In the next few days, once
> I get a better install on the windows side of things, I'm going to
> resynthesize it. I used the linux version for the broken file, but I
> don't think we had all the EDK updates. If I can pin it down to
> something specific, I'll make sure to follow up.
> thanks again,
> On Tue, 23 Nov 2004 11:27:46 +1000, John Williams
> <firstname.lastname@example.org> wrote:
> > Hi John,
> > John Carter wrote:
> > > hi, thanks for your help. The processor you sent is working, and I
> > > was just able to boot the kernel I compiled. I cannot overstate how
> > > excited I was to see the boot up screen. It seems I have issues with
> > > my EDK, or need to modify something within the mb_vanilla package to
> > > get it to synthesize properly.
> > OK, so at least we're narrowing it down a little.
> > I should be used to it by now, but the idea of *emailing* you a
> > linux-capable microprocessor system still amazes me!
> > > these lines upon connection are new:
> > >
> > > Instruction Cache Base Address.....0x80000000
> > > Instruction Cache High Address.....0x81ffffff
> > >
> > > and:
> > >
> > > Data Cache Base Address...0x80000000
> > > Data Cache High Address...0x81ffffff
> > >
> > > I'm going to look into this a bit further, but thanks so much for your help.
> > Hmm, suggests maybe you'd removed the cache definition lines from your
> > local system.mhs?
> > John
> > ___________________________
> > microblaze-uclinux mailing list
> > email@example.com
> > Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
> > Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
> /* John Carter, BCS
> * MSc Student (CIS) - University of Guelph
> * firstname.lastname@example.org
> * site=http://www.jcarter.ca */
/* John Carter, BCS
* MSc Student (CIS) - University of Guelph
* site=http://www.jcarter.ca */
microblaze-uclinux mailing list
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/