Need help booting linux on my 8265 board
Hi, I have problem booting linux on my 8265 board. Both u-boot and ppcboot run well, but when I boot the linux kernel, the board be dead. At this time the registers look like to be some default values(use powertap pro). I try u-boot1.1, ppcboot1.1.5; linux kernel 2.4.4 2.4.18 2.4.20. (1)about compile kernel vim Makefile,arch=ppc CROSS_COMPILE=ppc_82xx- vim arch/ppc/platforms/ads826x.h, IMAP_ADDR=0x0470 BCSR=0x0450 then make mrproper/ make ads826x_config/ make oldconfig/ make dep/ make pImage (bd info struct is quite same between uboot and linux) Is there anything I had ignored? (2)let's see!(I add some printf to display values, console=ttyS0,9600 is added) = bootm ffa0 ffc0 ## Booting image at ffa0 ... Image Name: Linux-2.4.20-pre7ncsd1 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size:634729 Bytes = 619 kB = 0 MB Load Address: Entry Point: Verifying Checksum ... OK Uncompressing Kernel Image ... OK ## Current stack ends at 0x03F7FC48 = set upper limit to 0x0080 ## cmdline at 0x007FFF00 ... 0x007FFF23 memstart= 0x memsize = 0x0400 flashstart = 0xFF80 flashsize = 0x0080 flashoffset = 0x sramstart = 0x sramsize= 0x immr_base = 0x0470 bootflags = 0x0001 vco = 266.666 MHz sccfreq = 66.666 MHz brgfreq = 16.666 MHz intfreq = 166.666 MHz cpmfreq = 133.333 MHz busfreq = 33.333 MHz ethaddr = 00:10:EC:00:30:8C IP addr = 8.6.0.1 baudrate= 9600 bps ## Loading RAMDisk Image at ffc0 ... Image Name: Simple Ramdisk-Image Image Type: PowerPC Linux RAMDisk Image (gzip compressed) Data Size:567988 Bytes = 554 kB = 0 MB Load Address: Entry Point: Verifying Checksum ... OK ## initrd at 0xFFC00040 ... 0xFFC8AAF3 (len=567988=0x8AAB4) Loading Ramdisk to 03ef4000, end 03f7eab4 ... OK ## Transferring control to Linux (at address ) ... then the board is dead and the LED(FCC link) coruscate . (I have modified clock calculations for this board so SCC can output message. it's the reason?) any ideas? thanks a lot! -- liu lm_mailbox at sohu.com ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Need help booting linux on my 8265 board
In message 000f01c42562$d3713150$a81e1aac at liuming you wrote: I have problem booting linux on my 8265 board. Both u-boot and ppcboot run well, but when I boot the linux kernel, the board be dead. At this time the registers look like to be some default values(use powertap pro). I try u-boot1.1, ppcboot1.1.5; linux kernel 2.4.4 2.4.18 2.4.20. I have already answered your questions on the U-Boot users mailing list. Why didn't you read my message? (1)about compile kernel vim Makefile,arch=ppc CROSS_COMPILE=ppc_82xx- vim arch/ppc/platforms/ads826x.h, IMAP_ADDR=0x0470 BCSR=0x0450 Your memory map is broken; this cannot work. Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de I will also, for an appropriate fee, certify that your keyboard is object-oriented, and that the bits on your hard disk are template- compatible.- Jeffrey S. Haemer in 411akr$3ga at cygnus.com ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Problems of kernel-2.6.4 for mpc8260
Hi,,, So so... sorry. I need to your process of module-init-tools-3.0 upgrade in detail. Unfortunately, when i upgrade module-init-tools-3.0, I have a troble with module insert continuously. Firstly, my test environment... 1) target : ppc8260 custom board. 2) kernel has compiled with module support 3) using kernel 2.6.5(also 2.6.3, 2.6.4) 4) using modutils 2.4.22 5) ELDK 3.0( cross compiler, NFS) Following test message After booting of kernel 2.6.5.. bash-2.05b# ls Makefile Makefile.l hello.c hello.ko hello.mod.c hello.mod.o hello.o == I had to compile the modules using the recommended way of 2.6.x ( $(MAKE) -C /kernel_path CROSS_COMPILE=xx_xx SUBDIRS=$(PWD) modules) bash-2.05b# insmod hello.ko insmod: QM_MODULES: Function not implemented bash-2.05b# depmod -V depmod version 2.4.22 depmod: QM_MODULES: Function not implemented I got to module-init-tools-3.0.tar.gz' After installing, boot process message is... VFS: Mounted root (nfs filesystem). Freeing unused kernel memory: 76k init request_module: runaway loop modprobe binfmt-4c46 request_module: runaway loop modprobe binfmt-4c46 request_module: runaway loop modprobe binfmt-4c46 request_module: runaway loop modprobe binfmt-4c46 request_module: runaway loop modprobe binfmt-4c46 Here stopped. As you can see above, what's the reason of above error? Any help would be appreciated. Call me Lone. Thanks, - Original Message - From: Rune Torgersen [EMAIL PROTECTED] To: linuxppc linuxppc-embedded at lists.linuxppc.org Sent: Thursday, April 08, 2004 12:40 AM Subject: RE: Problems of kernel-2.6.4 for mpc8260 You need a newer version of modutils Try module-init-tools-3.0.tar.gz from http://www.kernel.org/pub/linux/kernel/people/rusty/modules/ This fixed that problem for me on 2.6.3 and 2.6.5 on a 8266. The other version is known not to work with the new module initialization stuff in the 2.6 kernels. -Original Message- From: owner-linuxppc-embedded at lists.linuxppc.org [mailto:owner-linuxppc-embedded at lists.linuxppc.org] On Behalf Of Wolfgang Grandegger Sent: Wednesday, April 07, 2004 08:26 To: ??? Cc: linuxppc Subject: Re: Problems of kernel-2.6.4 for mpc8260 On 04/07/2004 09:51 AM ??? wrote: I got succeeded to port kernel 2.6.4 to out custom MPC8260 board with the help of DENX ELDK 3.0 tool. Thanks!! But there is some problems to be solved. After booting, when I try to install module, following error occured. bash-2.05b# insmod dsrc_drv.o insmod: QM_MODULES: Function not implemented Module support seems not to be enabled in your kernel. bash-2.05b# insmod -V insmod version 2.4.22 As you can see above, the version of modutils seems to be fine. right? If so, what's the reason of above error? And one more problem. At boot sequence(as following) lots of unexpected 'modprobe: xxx' messages are issued. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
request: PPC embedded board for DivX/MPEG-4
Hi, Does anybody here have/produce an embedded PowerPC board which is capable (enough CPU power) of decoding DivX/MPEG-4 movies and has possibility to connect display or at least graphics chip. thanks, Matevz Langus p.s. Please reply directly to me in order not to disturb the list too much. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Need help booting linux on my 8265 board
Need help booting linux on my 8265 boardHello,Mr Pereira thanks for your reply. I'm sure IMMR base is the same for both U-boot and Linux. Uboot mapped at 0xfff0, but I want to know why linux mapped at 0xC000 , the uboot say ## Transferring control to Linux (at address ) ..., so KERNELLOAD should be 0xc000 or 0x? and if I use linux kernel 2.4.20, CONFIG_CLOCKS_IN_MHZ should be 0 or 1? Best Regards Ming Liu - Original Message - From: Flavio Pereira To: liuming ; linuxppc-embedded at lists.linuxppc.org Cc: liuming Sent: Monday, April 19, 2004 3:24 PM Subject: RE: Need help booting linux on my 8265 board Hi Make sure that your IMMR base is the same for both U-boot and Linux. Ensure that they are both mapped above the virtual meomry base (0xC000) used by Linux, else you will have problems once ypou start to execute code. Regards Flavio Pereira From: [EMAIL PROTECTED] on behalf of liuming Sent: Sun 2004/04/18 06:33 PM To: linuxppc-embedded at lists.linuxppc.org Cc: liuming Subject: Need help booting linux on my 8265 board Hi, I have problem booting linux on my 8265 board. Both u-boot and ppcboot run well, but when I boot the linux kernel, the board be dead. At this time the registers look like to be some default values(use powertap pro). I try u-boot1.1, ppcboot1.1.5; linux kernel 2.4.4 2.4.18 2.4.20. (1)about compile kernel vim Makefile,arch=ppc CROSS_COMPILE=ppc_82xx- vim arch/ppc/platforms/ads826x.h, IMAP_ADDR=0x0470 BCSR=0x0450 then make mrproper/ make ads826x_config/ make oldconfig/ make dep/ make pImage (bd info struct is quite same between uboot and linux) Is there anything I had ignored? (2)let's see!(I add some printf to display values, console=ttyS0,9600 is added) = bootm ffa0 ffc0 ## Booting image at ffa0 ... Image Name: Linux-2.4.20-pre7ncsd1 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size:634729 Bytes = 619 kB = 0 MB Load Address: Entry Point: Verifying Checksum ... OK Uncompressing Kernel Image ... OK ## Current stack ends at 0x03F7FC48 = set upper limit to 0x0080 ## cmdline at 0x007FFF00 ... 0x007FFF23 memstart= 0x memsize = 0x0400 flashstart = 0xFF80 flashsize = 0x0080 flashoffset = 0x sramstart = 0x sramsize= 0x immr_base = 0x0470 bootflags = 0x0001 vco = 266.666 MHz sccfreq = 66.666 MHz brgfreq = 16.666 MHz intfreq = 166.666 MHz cpmfreq = 133.333 MHz busfreq = 33.333 MHz ethaddr = 00:10:EC:00:30:8C IP addr = 8.6.0.1 baudrate= 9600 bps ## Loading RAMDisk Image at ffc0 ... Image Name: Simple Ramdisk-Image Image Type: PowerPC Linux RAMDisk Image (gzip compressed) Data Size:567988 Bytes = 554 kB = 0 MB Load Address: Entry Point: Verifying Checksum ... OK ## initrd at 0xFFC00040 ... 0xFFC8AAF3 (len=567988=0x8AAB4) Loading Ramdisk to 03ef4000, end 03f7eab4 ... OK ## Transferring control to Linux (at address ) ... then the board is dead and the LED(FCC link) coruscate . (I have modified clock calculations for this board so SCC can output message. it's the reason?) any ideas? thanks a lot! -- liu lm_mailbox at sohu.com ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Need help booting linux on my 8265 board
In message 001401c425ee$796087b0$061410ac at liu you wrote: Need help booting linux on my 8265 boardHello,Mr Pereira Can you please STOP posting nearly the same quesrtions to the linuxppc-embedded and u-boot-users mailing lists? Please decide for one list, or, if you really, really feel the message must go to both lists, then send it as Cc:, but never two separate and slightly different messages. I'm sure IMMR base is the same for both U-boot and Linux. Uboot mapped at 0xfff0, but I want to know why linux mapped at 0xC000 , the uboot say ## Transferring control to Linux (at address ) ..., so KERNELLOAD should be 0xc00 0 or 0x? Welcome to the world of virtual addresses. See http://www.denx.de/twiki/bin/view/PPCEmbedded/Kernel#Section_10.2. and if I use linux kernel 2.4.20, CONFIG_CLOCKS_IN_MHZ should be 0 or 1? It should be not defined at all. Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de There are two ways to write error-free programs. Only the third one works. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
MPC85xx support
On Thu, 2004-04-15 at 19:21, Jason McMullan wrote: On Thu, 2004-04-15 at 11:35, Kumar Gala wrote: We have been keeping the linuxppc-2.4 bitkeeper in sync with our work for 85xx. See http://penguinppc.org/dev/kernel.shtml on how to get access. I have a raft of MPC85xx (specifically, MPC8560ADS support) for 2.6.4 if anyone wants them. While my interest is mostly academic for now, I would be happy to take a look. How are chances this becomes the mainstream port? Isn't Motorola/Metroworks working on this also? -- Stefan Nickl Project Engineering Kontron Modular Computers Sudetenstr. 7 D-87600 Kaufbeuren Phone ++49/8341/803-294 ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
MPC852 Cache initializing problem
Hello, I'm trying to put Linux on MPC852T platform (Embedded Planet). I'm using UBOOT as a Boot Loader. I'm trying to put kernel 2.4.20 On the very beginning of the Linux Initializing in initial_mmu after enabling Cache the system crashes. Any ideas? Thanks, Best Regards, Michael Meriin ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
MPC852 Cache initializing problem
It may be your debugger that is causing the problem. The next thing called is turn_on_mmu and I believe that causes an exception. -Original Message- From: Meriin Michael-BMM063 [mailto:[EMAIL PROTECTED] Sent: Monday, April 19, 2004 11:57 AM To: 'linuxppc-embedded at lists.linuxppc.org' Subject: MPC852 Cache initializing problem Hello, I'm trying to put Linux on MPC852T platform (Embedded Planet). I'm using UBOOT as a Boot Loader. I'm trying to put kernel 2.4.20 On the very beginning of the Linux Initializing in initial_mmu after enabling Cache the system crashes. Any ideas? Thanks, Best Regards, Michael Meriin ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
System ACE MPU interface to CF card
Jeff Angielski wrote: Sounds to me like you do not have your interrupts configured properly between the SystemACE and the CPU or your xsa_thread is dying prematurely. Either way, the kernel is getting no response when it actually tries to access the CF thru the SystemACE. Jeff Angielski The PTR Group I do not enable interrupts between SystemACE and the CPU. Following the debug cycle: xsysace_init() -register_disk() --grok_partitions() ---check_partition() msdos_partition() -read_dev_sector() --read_cache_page() ---lock_page() __lock_page() -schedule() And it never resumes after that. The code just goes to power_save mode. Any help would be appreciated. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
System ACE MPU interface to CF card
On Mon, 2004-04-19 at 14:06, Sharad Gupta wrote: I do not enable interrupts between SystemACE and the CPU. Doh. It is in your best interest to get the interrupts working... Following the debug cycle: xsysace_init() -register_disk() --grok_partitions() ---check_partition() msdos_partition() -read_dev_sector() --read_cache_page() ---lock_page() __lock_page() -schedule() And it never resumes after that. The code just goes to power_save mode. Any help would be appreciated. I would suggest instrumenting the code in the driver that actually handles the block request from the kernel. For instance, is the request being received by the xsa_thread? Is the driver actually making a request to the device. And most importantly and where I suspect your problem lies, is the xsa_complete_request() ever getting run? Jeff Angielski The PTR Group ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
PPC440GX GigE support
I've pushed a bunch of code for this to the linux-2.5-ocp tree. It overhauls the EMAC driver a bit and adds a number of fields to the new OCP EMAC .additions field that are set per SoC or by the board specific code. There's support for GigE on EMAC2/3, the TAH, zerocopy, and jumbo frames. There's still work to be done on jumbo frames 4062 MTU since the RX side requires a copy. If we get some assumptions about linear skbs in various protocol implementations removed, this can be fixed. TSO support is the only major thing unimplemented. Performance is right on par with an e1000 in the same platform, showing anywhere from 700-850Mbps TX throughput depending on MTU size and sendfile usage. RX range is slightly less. Pull from bk://source.mvista.com/linux-2.5-ocp Once the new OCP stuff goes into linux-2.5, I'll send some version of this (plus previous EMAC driver work for 2.6) to jgarzik. -Matt ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Linux/Fibre Channel on ML300 question.
Does anybody have a Linux on the ML300 talking to a Fibre Channel HBA? How is it done? Do you use the Rocket I/O ? -mike wellington wellington at lucent.com ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
ppc4xx_find_bridges( ) hangs kernel on Xilinx ML300 (PCI)
Hi- I am trying to port the Xilinx PCI code to an embedded linux kernel. The code calls ppc4xx_find_bridges( ) during the kernel initialization and hangs the kernel. I built the GPL 2.4 kernel from the Open Source archives and it hangs also. Then I copied ppc405_pci.c from the GPL source to my kernel tree and copied head_4xx.S from the GPL source to my kernel tree and it still hangs. I'm starting to wonder if there is something wrong with the PCI support for the Xilinx OCP PCI core. Does anybody have a working PCI device on a Xilinx Virtex-II Pro using the Xilinx-supplied PCI core? -mike wellington wellington at lucent.com anyplatform at bithead.com ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
ppc4xx_find_bridges( ) hangs kernel on Xilinx ML300 (PCI)
The PCI support that is currently included in the Linux kernel tree is for the V2PDK based OPB - PCI bridge. It will not work with the EDK based OPB - PCI bridge, i.e. you will find exactly what you see. Please download the EDK reference design for ML300 from http://www.xilinx.com/ise/embedded/edk_examples.htm (design #6). The design contains the V2PDK based bridge (including the pcore therefor) and, thus, the Linux kernel will work fine with that design. We are currently working on moving to the EDK based bridge and the Linux kernel tree will be patched once this work is completed. - Peter Mike Wellington wrote: Hi- I am trying to port the Xilinx PCI code to an embedded linux kernel. The code calls ppc4xx_find_bridges( ) during the kernel initialization and hangs the kernel. I built the GPL 2.4 kernel from the Open Source archives and it hangs also. Then I copied ppc405_pci.c from the GPL source to my kernel tree and copied head_4xx.S from the GPL source to my kernel tree and it still hangs. I'm starting to wonder if there is something wrong with the PCI support for the Xilinx OCP PCI core. Does anybody have a working PCI device on a Xilinx Virtex-II Pro using the Xilinx-supplied PCI core? -mike wellington wellington at lucent.com anyplatform at bithead.com ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
ppc4xx_find_bridges( ) hangs kernel on Xilinx ML300 (PCI)
Awesome! You Rock! -mikew Peter Ryser wrote: The PCI support that is currently included in the Linux kernel tree is for the V2PDK based OPB - PCI bridge. It will not work with the EDK based OPB - PCI bridge, i.e. you will find exactly what you see. Please download the EDK reference design for ML300 from http://www.xilinx.com/ise/embedded/edk_examples.htm (design #6). The design contains the V2PDK based bridge (including the pcore therefor) and, thus, the Linux kernel will work fine with that design. We are currently working on moving to the EDK based bridge and the Linux kernel tree will be patched once this work is completed. - Peter Mike Wellington wrote: Hi- I am trying to port the Xilinx PCI code to an embedded linux kernel. The code calls ppc4xx_find_bridges( ) during the kernel initialization and hangs the kernel. I built the GPL 2.4 kernel from the Open Source archives and it hangs also. Then I copied ppc405_pci.c from the GPL source to my kernel tree and copied head_4xx.S from the GPL source to my kernel tree and it still hangs. I'm starting to wonder if there is something wrong with the PCI support for the Xilinx OCP PCI core. Does anybody have a working PCI device on a Xilinx Virtex-II Pro using the Xilinx-supplied PCI core? -mike wellington wellington at lucent.com anyplatform at bithead.com ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
PCI - i *thought* the edk2 was what I was using!
Peter - I thought that the edk2 example from the link you gave me was the pcore I was using. I will start over from scratch and try again. My machine is busy doing some big downloads/backups so it will be tonite/tomorrow before I can verify and report back. Peter Ryser wrote: The PCI support that is currently included in the Linux kernel tree is for the V2PDK based OPB - PCI bridge. It will not work with the EDK based OPB - PCI bridge, i.e. you will find exactly what you see. Please download the EDK reference design for ML300 from http://www.xilinx.com/ise/embedded/edk_examples.htm (design #6). The design contains the V2PDK based bridge (including the pcore therefor) and, thus, the Linux kernel will work fine with that design. We are currently working on moving to the EDK based bridge and the Linux kernel tree will be patched once this work is completed. - Peter ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
PCI - i *thought* the edk2 was what I was using!
Mike, the ml300_edk2.zip design does not have PCI at all. Only the ml300_edk3.zip, i.e. the design to which the link currently points has the pcore that works with Linux. - Peter Mike Wellington wrote: Peter - I thought that the edk2 example from the link you gave me was the pcore I was using. I will start over from scratch and try again. My machine is busy doing some big downloads/backups so it will be tonite/tomorrow before I can verify and report back. Peter Ryser wrote: The PCI support that is currently included in the Linux kernel tree is for the V2PDK based OPB - PCI bridge. It will not work with the EDK based OPB - PCI bridge, i.e. you will find exactly what you see. Please download the EDK reference design for ML300 from http://www.xilinx.com/ise/embedded/edk_examples.htm (design #6). The design contains the V2PDK based bridge (including the pcore therefor) and, thus, the Linux kernel will work fine with that design. We are currently working on moving to the EDK based bridge and the Linux kernel tree will be patched once this work is completed. - Peter ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
did you give me the right ml300_edk*.zip link?
the link that you sent me was to ml300_edk2.zip , how can I download the ml300_edk3.zip ? -mikew eter Ryser wrote: Mike, the ml300_edk2.zip design does not have PCI at all. Only the ml300_edk3.zip, i.e. the design to which the link currently points has the pcore that works with Linux. - Peter Mike Wellington wrote: Peter - I thought that the edk2 example from the link you gave me was the pcore I was using. I will start over from scratch and try again. My machine is busy doing some big downloads/backups so it will be tonite/tomorrow before I can verify and report back. Peter Ryser wrote: The PCI support that is currently included in the Linux kernel tree is for the V2PDK based OPB - PCI bridge. It will not work with the EDK based OPB - PCI bridge, i.e. you will find exactly what you see. Please download the EDK reference design for ML300 from http://www.xilinx.com/ise/embedded/edk_examples.htm (design #6). The design contains the V2PDK based bridge (including the pcore therefor) and, thus, the Linux kernel will work fine with that design. We are currently working on moving to the EDK based bridge and the Linux kernel tree will be patched once this work is completed. - Peter ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
more SystemACE problems
Jeff Angielski wrote: On Mon, 2004-04-19 at 14:06, Sharad Gupta wrote: I would suggest instrumenting the code in the driver that actually handles the block request from the kernel. For instance, is the request being received by the xsa_thread? Is the driver actually making a request to the device. And most importantly and where I suspect your problem lies, is the xsa_complete_request() ever getting run? Jeff Angielski The PTR Group Hi Jeff, Thanks very much for your help. I have enabled the interrupts for SystemACE now. And in fact xsa_complete_request() was never called. I fixed that in xsa_thread. I was wondering if you could send in your modifications to the xilinx_systemace/* files so that I can know better where else the potential problems may lie. Do I need to have a device entry for xsystemacea (0/1) in my /dev directory ? If yes, then what should it be like ? Thanks Sharad. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
