Re: Xilinx BSP for linux 2.6

Re: Xilinx BSP for linux 2.6

[Ameet Patil]

Its the same link as before! I just updated the file!
http://www.cs.york.ac.uk/rtslab/demos/amos/xupv2pro/patches/linuxppc-2.6.17_sysace.patch

-Ameet

Ming Liu wrote:
> Dear Ameet,
> Could you please give me a copy of your new driver for SystemACE?
> Regards
> Ming
> 
> 
>> From: Ameet Patil <ammubhai@gmail.com>
>> To: Ming Liu <eemingliu@hotmail.com>
>> Subject: Re: Xilinx BSP for linux 2.6
>> Date: Fri, 07 Jul 2006 15:17:31 +0100
>>
>> Thats right! Sorry about the error! :-)
>>
>> Good luck with TEMAC!
>>
>> -Ameet
>>
>> Ming Liu wrote:
>> > Dear Ameet,
>> > OK. I found the problem. tts/0 should be a char device, not a block 
> one.
>> > so it should be c not b. I neglected that and just copied your 
> commands. :)
>> >
>> > Next, I will try to implement the Temac driver. If any information, I
>> > will let you know.
>> >
>> > Regards
>> > Ming
>> >
>> >
>> >> From: Ameet Patil <ammubhai@gmail.com>
>> >> To: Ming Liu <eemingliu@hotmail.com>
>> >> CC: linuxppc-embedded@ozlabs.org
>> >> Subject: Re: Xilinx BSP for linux 2.6
>> >> Date: Fri, 07 Jul 2006 13:42:42 +0100
>> >>
>> >> Hi Ming,
>> >>
>> >> Excellent News!
>> >>
>> >> Don't worry... the problem you are facing could be because of missing
>> >> device files in your /dev folder.
>> >>
>> >> Do as follows:
>> >> mount the CF card onto your PC and then goto the /dev folder on your
>> >> root filesystem in the card. Here run the following commands as root:
>> >> # mknod -m 660 console c 5 1
>> >> # mknod -m 660 xsa b 254 0
>> >> # mknod -m 660 xsa1 b 254 1
>> >> # mknod -m 660 xsa2 b 254 2
>> >> # mknod -m 660 xsa3 b 254 3
>> >> Now there should be a directory tts in your dev. If not create one
>> >> "mkdir tts". Then do this in the dev/tts folder,
>> >> # mknod -m 660 0 b 4 64
>> >>
>> >> > Also, when I compile the kernel, there is a error. That's in 
> adapter.c
>> >> > file, undefined reference to "XAssert". I checked the source code 
> and
>> >> I think you have the old patch. If you download the new one, the
>> >> compilation problem should not occur. But you resolved it yourself,...
>> >> which is good.
>> >>
>> >> Let me know if this works. I shall add this stuff in PART II of the
>> > article.
>> >>
>> >> -Ameet
>> >>
>> >> Ming Liu wrote:
>> >> > Dear Ameet,
>> >> > A good news is that now my 2.6 kernel is running in my ML403 board!
>> >> > According your guidance, first I made the kernel as simple as 
> possible
>> >> > and it works well. Then I included the patch for SystemACE and here 
> is
>> >> > the information shown on the hyper teminal:
>> >> >
>> >> >
>> >> > Linux/PPC load: console=ttyS0,9600 root=/dev/xsa3 [    0.000148]
>> >> > Console: colour dummy device 80x25
>> >> > [    0.000919] Dentry cache hash table entries: 16384 (order: 4, 
> 65536
>> >> > bytes)
>> >> > [    0.002277] Inode-cache hash table entries: 8192 (order: 3, 32768
>> > bytes)
>> >> > [    0.012802] Memory: 63104k available (1340k kernel code, 384k 
> data,
>> >> > 76k init,
>> >> > 0k highmem)
>> >> > [    0.230310] Mount-cache hash table entries: 512
>> >> > [    0.238305] VFS: Disk quotas dquot_6.5.1
>> >> > [    0.238516] Dquot-cache hash table entries: 1024 (order 0, 4096
>> > bytes)
>> >> > [    0.238817] JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc.
>> >> > [    0.239435] JFS: nTxBlock = 493, nTxLock = 3944
>> >> > [    0.241883] Initializing Cryptographic API
>> >> > [    0.241940] io scheduler noop registered (default)
>> >> > [    0.322864] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, 
> IRQ
>> >> > sharing
>> >> > disabled
>> >> > [    0.324759] serial8250.0: ttyS0 at MMIO 0x40401003 (irq = 1) is a
>> > 16550A
>> >> > [    1.653644] RAMDISK driver initialized: 16 RAM disks of 65536K 
> size
>> >> > 1024 bloc
>> >> > ksize
>> >> > [    1.745079] loop: loaded (max 8 devices)
>> >> > [    1.793392]  xsa: xsa1 xsa2 xsa3
>> >> > [    1.839262] mice: PS/2 mouse device common for all mice
>> >> > [    1.935059] VFS: Mounted root (ext2 filesystem) readonly.
>> >> > [    2.000037] Freeing unused kernel memory: 76k init
>> >> > [    2.075656] Warning: unable to open an initial console.
>> >> >
>> >> > I use xsa3 as the partition to store the file system. Now the file
>> >> > system is the old one for my 2.4 kernel generated by busybox. Then I
>> >> > think that's why the problem "unable to open an initial console" is
>> >> > generated. Do you have some suggestion on how to solve it? Thanks 
> for
>> >> > your opinion.
>> >> > Also, when I compile the kernel, there is a error. That's in 
> adapter.c
>> >> > file, undefined reference to "XAssert". I checked the source code 
> and
>> >> > found that the function of XAssert is defined in the file
>> >> > xbasic_types.c, not the xbasic_types.h. So it cannot be included 
> into
>> >> > adapter.c. And also in the makefile there is no dependency on
>> >> > xbasic_types.c. So I added the defination for this function in
>> >> > adapter.c, copying it from xbasic_types.c. It then worked well.
>> >> > Waiting for your guidance. You know, an expert's opinion is always
>> >> > useful for a novice, like me. :)
>> >> >
>> >> > Regards
>> >> > Ming
>> >> >
>> >> > _________________________________________________________________
>> >> > 免费下载 MSN Explorer:   http://explorer.msn.com/lccn/
>> >> >
>> >
>> > _________________________________________________________________
>> > 享用世界上最大的电子邮件系统― MSN Hotmail。  http://www.hotmail.com
>> >
> 
> _________________________________________________________________
> 免费下载 MSN Explorer:   http://explorer.msn.com/lccn 
> 

Kernel hangs after "Now booting the kernel".

[Ming Liu]

Dear Ameet,
I really feel so sorry to take away much time from you. However, there are 
really so many strange problems for my system.

I tried to implement the Temac option and recompiled the kernel. Then when 
I boot the kernel from CF card, after the information "Now booting the 
kernel", it hangs. I canceled the Temac again and recompiled the kernel, 
restoring the former condition, this problem still existed. It's so 
strange.

Any suggestion to solve this? Of course, suggestions from other friends are 
also appreciated.

Thanks a lot again for your great help!

Regards
Ming

_________________________________________________________________
与联机的朋友进行交流，请使用 MSN Messenger:  http://messenger.msn.com/cn  

Re: Kernel hangs after "Now booting the kernel".

[Ameet Patil]

Hi Ming,
   Check if the kernel boot options are set right? (ie.
console=ttyS0,9600 root=/dev/xsa3). Sometimes the configuration is lost.
If this is intact, then another thing to try is to start from the
beginning: make mrproper and then make menuconfig, etc.

I have not looked into TEMAC patch yet, but don't think it would affect
your serial output messages. Double check the boot options and whether
you have included support for legacy serial device/ console on serial
deivce.

-Ameet

Ming Liu wrote:
> Dear Ameet,
> I really feel so sorry to take away much time from you. However, there 
> are really so many strange problems for my system.
> 
> I tried to implement the Temac option and recompiled the kernel. Then 
> when I boot the kernel from CF card, after the information "Now booting 
> the kernel", it hangs. I canceled the Temac again and recompiled the 
> kernel, restoring the former condition, this problem still existed. It's 
> so strange.
> 
> Any suggestion to solve this? Of course, suggestions from other friends 
> are also appreciated.
> 
> Thanks a lot again for your great help!
> 
> Regards
> Ming
> 
> _________________________________________________________________
> 与联机的朋友进行交流，请使用 MSN Messenger:  http://messenger.msn.com/cn 
> 

Kernel hangs after "Now booting the kernel"

[Brian Rutledge]

[-- Attachment #1: Type: text/plain, Size: 1550 bytes --]

Hi



            I am using an Embedded Planet 852T board with a planet core

bootloader. I am trying to boot the kernel (2.6) and the boot sequence

gets as far as:



 



>go



[Go 00200000]





loaded at:     00200000 0030A160



relocated to:  00400000 0050A160



board data at: 00508124 00508140



relocated to:  004050B4 004050D0



zimage at:     004058FD 0050704A



avail ram:     0050B000 01000000



 





Linux/PPC load: console=ttyS0,9600 console=tty0 root=/dev/ram0

init=/linuxrc rw



Uncompressing Linux...done.



Now booting the kernel



 



 



            After which nothing happens.



 



            Does the kernel try an set up the serial port at this point

or can I assume that the serial is operational based on the output up to

this point?



 



            Are there any other areas I should be looking at?



 



            Thanks Brian





Legal Disclaimer:

The information contained in this message may be privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete or destroy any copy of this message


[-- Attachment #2: Type: text/html, Size: 8196 bytes --]