[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [microblaze-uclinux] kernel won't boot



I should add that I did follow the tutorial precisely several times.  I also downloaded the demo and the image.bin that came with the demo worked fine on the bitstream generated in my BSB project.

I have 2.4.32-uc0 version of the kernel.

I had the same problem of no kernel boot output with both the microblaze-elf-tools-20050830 build and the microblaze-elf-tools-20051121 build.

After failing several times to boot, I noticed in the make menuconfig that you could select a modularized version of RAM/ROM/Flash chip drivers-> Support for Intel/Sharp flash chips as well as Mapping drivers for chip access-> Generic uClinux RAM/ROM filesystem support.

From the beginning I had clicked space to bring up the asterisk next to this option.  But I also noticed that if you hit space only once, or typed M, it would put in an M in the brackets instead of the asterisk... indicating a module.  I didn't really know what this meant but it seemed like a remote possibility that the documentation could be slightly off on this aspect.  Anyway I recompiled everything and the kernel actually booted.  I have no idea why.  But there were also errors:

...
Support for command set 0001 not present
gen_probe: No supported Vendor Command Set found
...
JEDEC: Found no Flash device at location zero
...
flatfsd: Nonexistent or bad flatfs (-48), creating new one...
flatfsd: Failed to write flatfs (-48(: No such device
flatfsd: Created 3 configuration files (176 bytes)

Hopefully this information isn't too random... and can help someone else get some insight.
Jim

On 3/28/06, jim bo <jamesd.snyder@xxxxxxxxx> wrote:
I'm experiencing the same problems described by Daniel and Eric.

Was a resolution ever found?


On 2/12/06, Eric Lynum < elynum@xxxxxxx> wrote:


I haven't modified any of the pcores. I'm able to when I write mwr
0x30000058 0x55aa55aa get the 0x55aa55aa back. And it looks like I'm able to
write at any address in that sdram block and get back what I wrote.

Also when I use the random.bin file I get back everything I write except and
this might be correct but it's byte swapped.

After I do my hexdump and place it in a file.  I look at the file and in the
file if I have 00000000 and the data is dfb5fe00 I get back B5df00fe from
xmd.  But I think that's correct.

The only thing I can do is go back through the tutorial and see if I'm doing
sommething wrong because it looks like I can read and write blocks of data
to the ram correctly.



-----Original Message-----
From: owner-microblaze-uclinux@xxxxxxxxxxxxxx
[mailto: owner-microblaze-uclinux@xxxxxxxxxxxxxx ] On Behalf Of John Williams
Sent: Sunday, February 12, 2006 6:59 PM
To: microblaze-uclinux@xxxxxxxxxxxxxx
Subject: Re: [microblaze-uclinux] kernel won't boot

Eric,

Eric Lynum wrote:
> I did a mb-objdump on my kernel and the data on the address after 30000058
> is not the same that is actually being written into the sdram.
> For instance
> At 30000054 I have a561e000 which is what I have in the sdram
> At 30000058 I have b000300a but I have b000300d in the sdram
> After that it looks like every thing is moved to the left by 2 spaces for
> instance at 30000068  it should be b0003009 but I get in the sdram
f0b00030.

It looks then like a problem with your memory and/or interfacing.

Do some more tests to confirm.  e.g.

What happens if you use XMD to write words into the DDR

mwr 0x30000058 0x55aa55aa
mrd 0x30000058

????

Other addresses?

Create a 1MB file of random numbers:

$ dd if=/dev/urandom of=random.bin bs=1k count=1k

download it in XMD

% dow -data random.bin 0x30000000

read it back, and compare to the original contents

$ hexdump random.bin

Once you are sure that what you upload, doesn't match what's in the
memory, time to start finding out why.

Did you follow the tutorial closely?

Have you done anything silly like make custom modifications to Xilinx
pcores (it happens!)

If all else fails, ask someone to post working ML401 bitstream and
kernel images, try them on your setup.

I'm really not sure what else to suggest.

Regards,

John
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive :
http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/

___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/