[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [microblaze-uclinux] RE: Problem with Petalinux booting with lltemac
Hi Rick,
it is hard for us to help you.
Please post more relevant information like
Petalinux version?
MMU/noMMU
kernel log
If you see heartbeat you use any noMMU a little bit changed version.
Do you use any ref board? Do you have the same problem on it too?
Regards,
Michal
Rick Hunnicutt wrote:
> Further information on this... The heartbeat function shows the kernel is running. I can manually output data to the uart through the xmd console. I thought maybe this was similar to the uart lite hanging that Olof was working through. I put the CONFIG_HZ param up to 200 then 300 but still the same results (besides very fast blinking LED's). Since the prints aren't working, my debugging efforts are crippled.
>
> Again, any ideas or help would be appreciated.
>
> Thanks,
> Rick
>
>> -----Original Message-----
>> From: owner-microblaze-uclinux@xxxxxxxxxxxxxx [mailto:owner-microblaze-
>> uclinux@xxxxxxxxxxxxxx] On Behalf Of Rick Hunnicutt
>> Sent: Wednesday, December 10, 2008 2:50 PM
>> To: microblaze-uclinux@xxxxxxxxxxxxxx
>> Subject: [microblaze-uclinux] Problem with Petalinux booting with
>> lltemac
>>
>> I am working with a custom board with a virtex-5 running petalinux.
>> Everything boots fine when I have the system fully setup without the
>> lltemac IP included. When it is included, the kernel boots and it
>> starts mounting file systems and such but then the output on the
>> terminal stops. I have put strategic prints in the kernel and it seems
>> it makes it to the schedule task and then stop, but not really.
>> Normally, the prints would just fly off the page as the scheduler is
>> called repeatedly. I left the system on over the weekend and found that
>> the system is indeed running, just extremely, extremely slow. The
>> system made it through the scheduler call about once per day...
>>
>> The kernel does not have the lltemac driver or even network support
>> built in at this point and it behaves the same. We have used chip scope
>> with the plb bus analyzer module to snoop the plb bus but haven't seen
>> anything that we can call helpful.
>>
>> Any ideas or help would be appreciated.
>>
>>
>>
>> Thanks,
>>
>> Rick
>>
>> ___________________________
>> 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/
>
>
___________________________
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/