Linux on PPC
Hiya, I'm no expert in this, but here's the basics; > We have a customized board running on IBM PPC 750. The customer boot > loader is provided by the vendor. Also, the vendor has provided > the BSP on vxworks. The PPC 750 is a fairly old processor, so there will be Linux support for it. For example, I picked up a couple of Artesyn PrPMC boards that contain a PPC 750, and this board can run Linux, though I have not had time to try booting it yet. If the vendor provided the VxWorks BSP, then hopefully they also provided you with the physical memory map of the board. This is what you really need to get another bootloader (eg. U-Boot) and Linux up-and-running. If the vendor will provide schematics for the board, that would also help (hey, it never hurts to ask for them). > We are planning to use linux on this processor. What are the steps > involved in booting the board with linux. > Which linux to be used and what are the procedures involved. I dint come > across a documents which had these details. > > I am new to the linux front. So any help is highly appreciated. > Step 1. Get the memory map of the board. Step 2. Find a PPC 750 port in the Linux source. For example, in the 2.6 series kernel, the place to start looking is under arch/ppc/platforms. grep -Ie 750 shows up some of the PPC 750 based systems. chestnut.c 750FX/GX evaluation board katana.c Looks like one too prpmc750.c Looks like a Motorola board Look at the comments in the code, look at the memory map of the reference board versus your custom board. There is a very good chance that the custom board is based on a reference design - thats the whole point of them. Step 3. Build a minimal kernel Step 4. Boot Step 5. Purchase a BDI2000 JTAG debugger and use it to figure out why Step 4 didn't work. Repeat at Step 3. When I get time to play with my Artesyn board, I'll go back to the katana.c file, the grep above had some comments about Artesyn boards. If it fails to boot, I'll use the BDI2000 to see where it dies and go from there. Once you can boot Linux, you might decide that the custom bootloader on the board is inflexible. The U-Boot bootloader is very nice and will have support for other 750-based boards, it shouldn't take too much to port that too. But first, try to get a Linux kernel booted, even if it has a hard-wired command line. Also take a look over on the Freescale web site, search for 'porting linux', it'll show up AN2145, AN, AN2579, and a bunch of other application notes. They'll give you an idea of what it takes to port to a new processor. > I am new to the linux front. So any help is highly appreciated. So it depends how much time you have versus how much you want to spend. There are also commercial companies that will do the job for you. If you can come up with the memory map and hardware details of the board, you could always post a request on this list, and I am sure there are people reading this list that would respond. (I'm not one of them though, so I'm not trying to drum up business ok) Regards, Dave
Linux on PPC
You can easily migrate to linux environment. 1. You can use u-boot as a boot loader. 2. You can choose any standard linux kernel but you may have to do some R&D on it to port to your board. Insted you can buy Montavista Linux, so that you can get support also. And also there are many mailing lists where yo ucan get tremendous help on linux. Thanks, Nagi > Hi, > > We have a customized board running on IBM PPC 750. The customer boot > loader > is provided by the vendor. > Also, the vendor has provided the BSP on vxworks. > > We are planning to use linux on this processor. What are the steps > involved > in booting the board with linux. > Which linux to be used and what are the procedures involved. I dint come > across a documents which had these details. > > I am new to the linux front. So any help is highly appreciated. > > thanks > ___ > Linuxppc-embedded mailing list > Linuxppc-embedded at ozlabs.org > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Linux on PPC
Hi, We have a customized board running on IBM PPC 750. The customer boot loader is provided by the vendor. Also, the vendor has provided the BSP on vxworks. We are planning to use linux on this processor. What are the steps involved in booting the board with linux. Which linux to be used and what are the procedures involved. I dint come across a documents which had these details. I am new to the linux front. So any help is highly appreciated. thanks -- next part -- An HTML attachment was scrubbed... URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060302/5afc30e3/attachment.htm
Linux on PPC
--- rtosrtososrtosgmaigmail> wrote: > Hi, > > We have a customized board running on IBM PPC PPC. The > customer boot loader > is provided by the vendor. > Also, the vendor has provided the BSP BSPvxwovxworks > We are planning to use linulinuxthis processor. What are the > steps involved > in booting the board with linulinux Which linulinuxbe used and what are the procedures involved. I > dint come > across a documents which had these details. > > I am new to the linulinuxnt. So any help is highly > appreciated. > > thanks I recommend using u-boot and the ELDK from denx.de __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
How to quickly write cleanmarkers to jffs2 partitions?
Hi David, I indeed did write a small program that only writes the cleanmarkers in all flash blocks used for jffs2. We assume (and check) all flash sectors are erased already. Jaap-Jan On 2-mrt-2006, at 17:06, David Jander wrote: > > Hi, > > I was wondering if there is a trick or common technique I am > ignoring to make > this more efficient: > > This is for a 2.4 kernel based system. > In production we use either u-boot or a NFS mounted linux system to > erase > flash and write jffs2 partitions to it. The jffs2 images are small > (not > padded to full partition size to save programming time), but the > partitions > are rather big (12 Mbyte in one case). Problem is that when booting > for the > first time, one has to wait several minutes (during which the > system is more > or less useless and busy) to get all cleanmarkers written to flash > by the > jffs2 gc thread. This huge delay is rather unacceptable for > production, so we > are looking for a work-around. > > One option would be to make jffs2 images that are padded to full > partition > size, but that also isn't very efficient, considering the image is > only about > 100k in beginning and the partition is 12 Mbyte in size. That would > take a > lot of time programming flash (less time than having the jffs2 > driver fix > this nevertheless). > > Another option is making a little program that writes cleanmarkers > in every > eraseblock starting from the first completely empty one in a > partition before > mounting that partition for the very first time after flashing. > > Since this seems to me like a common situation, I'd like to know if > anybody > knows about a better solution, or if anybody has already dealt with > this > before. > > Greetings, > > -- > David Jander > Protonic Holland. > tel.: +31 (0) 229 212928 > fax.: +31 (0) 229 210930 > Factorij 36 / 1689 AL Zwaag > ___ > Linuxppc-embedded mailing list > Linuxppc-embedded at ozlabs.org > https://ozlabs.org/mailman/listinfo/linuxppc-embedded > > -- > This message has been scanned for viruses and is believed to be clean > J.G.J. Boor Anton Philipsweg 1 Software Engineer 1223 KZ Hilversum AimSys bv tel. +31 35 689 1941 Postbus 2194, 1200 CD Hilversum jjboor at aimsys dot nl
How to quickly write cleanmarkers to jffs2 partitions?
Hi, I was wondering if there is a trick or common technique I am ignoring to make this more efficient: This is for a 2.4 kernel based system. In production we use either u-boot or a NFS mounted linux system to erase flash and write jffs2 partitions to it. The jffs2 images are small (not padded to full partition size to save programming time), but the partitions are rather big (12 Mbyte in one case). Problem is that when booting for the first time, one has to wait several minutes (during which the system is more or less useless and busy) to get all cleanmarkers written to flash by the jffs2 gc thread. This huge delay is rather unacceptable for production, so we are looking for a work-around. One option would be to make jffs2 images that are padded to full partition size, but that also isn't very efficient, considering the image is only about 100k in beginning and the partition is 12 Mbyte in size. That would take a lot of time programming flash (less time than having the jffs2 driver fix this nevertheless). Another option is making a little program that writes cleanmarkers in every eraseblock starting from the first completely empty one in a partition before mounting that partition for the very first time after flashing. Since this seems to me like a common situation, I'd like to know if anybody knows about a better solution, or if anybody has already dealt with this before. Greetings, -- David Jander Protonic Holland. tel.: +31 (0) 229 212928 fax.: +31 (0) 229 210930 Factorij 36 / 1689 AL Zwaag
802.3ah OAM
HI; who has 802.3ah OAM code (C language in the linux) Thanks feng chinafeng2008 at 163.com ??2006-03-02
boot failure on lite5200b board
(Feb 6 2006 - 09:56:46) > > > > CPU: MPC5200 v2.2 at 462 MHz > > Bus 132 MHz, IPB 132 MHz, PCI 33 MHz > > Board: Freescale MPC5200 (Lite5200B) > > I2C: 85 kHz, ready > > DRAM: 256 MB > > FLASH: 32 MB > > PCI: Bus Dev VenId DevId Class Int > > 00 1a 1057 5809 0680 00 > > In:serial > > Out: serial > > Err: serial > > Net: FEC ETHERNET > > IDE: Bus 0: OK > >Device 0: not available > >Device 1: not available > > > > Autostarting. Press any key to abort.. > > > > Hit any key to stop autoboot: 0 > > Using FEC ETHERNET device > > TFTP from server 10.190.3.103; our IP address is 10.190.3.144 > > Filename 'MPC5200/uImage'. > > Load address: 0x10 > > Loading: > > # > > > > > > done > > Bytes transferred = 658114 (a0ac2 hex) > > ## Booting image at 0010 ... > > Image Name: Linux-2.6.16-rc1 > > Image Type: PowerPC Linux Kernel Image (gzip compressed) > > Data Size:658050 Bytes = 642.6 kB > > Load Address: > > Entry Point: > > Verifying Checksum ... OK > > Uncompressing Kernel Image ... OK > > id mach(): done > > MMU:enter > > MMU:hw init > > MMU:mapin > > MMU:setio > > MMU:exit > > setup_arch: enter > > setup_arch: bootmem > > arch: exit > > > > > > I am wondering whether it's a kernel problem or more likely to be a > problem > > lying with the U-boot. It seems to hang when executing setup_arch() > > function, or maybe there is sth else behind the wall? > > > > Regards, > > Jianggan LI > > > > > > > > > > -Original Message- > > From: Sylvain Munaut [mailto:tnt at 246tNt.com] > > Sent: Thu 2/23/2006 15:38 > > To: #LI JIANGGAN# > > Cc: linuxppc-embedded at ozlabs.org > > Subject: Re: boot failure on lite5200b board > > > > #LI JIANGGAN# wrote: > > > Hello all, > > > > > > For my end-of-study project, I am working on an embedded system with > > > reference of freescale's lite5200b reference board. I was trying to > boot > > > Linux 2.6.15 on the board (with the fec and bestcomm corrected). > however > > > the booting was stuck at the following stage: > > > > In addition to what has already been said (use a higher address for the > > image and don't forget console=ttyPSC0 in kernel command line), make > > sure you use the kernel from my git tree, it contains a few patches from > > John Rigby to add support for the lite5200b. > > > > Please report if it works, I've not been able to test those myself since > > i'm still on lite5200. > > > > > > Sylvain > > > > > > > > > > > > > > ___ > > Linuxppc-embedded mailing list > > Linuxppc-embedded at ozlabs.org > > https://ozlabs.org/mailman/listinfo/linuxppc-embedded > > > > > > > > > -- next part -- An HTML attachment was scrubbed... URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060302/6158c754/attachment.htm
