Where to store the Linux kernel.
I used the VP20 before. You can use the Xilinx's tool to generate the .ace file from the .elf, bit stream, etc and put it in the CF. It is very simple ponce you do it once and Xilinx has very good app note to tell you exactly what need to do. -Tony On 7/27/06, Frank D Lombardo wrote: > > Ming, > > I am using an ML403 in a similar way. I have the download.bit file > stored in platform flash. U-Boot, the Linux Kernel and initrd are stored > in the linear flash. > > Frank > > > Ming Liu wrote: > > Hello everyone, > > Now I am doing a embedded linux project on the board of ML403(virtex4, > > ppc405). In my product, I cannot use CF card. So I have to use flash > memory > > to store the Linux kernel. Except for the Linux kernel, also I have to > > store the hardware information of the system.bit file. I know in ml403 > > board, there are two types of flash. One is Platform Flash and the other > is > > Linear Flash. Can anyone tell me how can I arrange my hardware .bit file > > and Linux kernel zImage.elf file and store them in the flash provided in > > the board? Can I put both of them in the Platform Flash chip? Thanks for > > the telling. > > > > Regards > > Ming > > > > _ > > ?? MSN Messenger: http://messenger.msn.com/cn > > > > ___ > > Linuxppc-embedded mailing list > > Linuxppc-embedded at ozlabs.org > > https://ozlabs.org/mailman/listinfo/linuxppc-embedded > > ___ > Linuxppc-embedded mailing list > Linuxppc-embedded at ozlabs.org > https://ozlabs.org/mailman/listinfo/linuxppc-embedded -- -Tony Having fun with FPGA, gige, mpeg, snmp, ppc, Linux -- next part -- An HTML attachment was scrubbed... URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060727/46395e2b/attachment.htm
linuxppc-2.4.30-pre1 crashes with root fs on Xilinx SystemACE
Keith, Some suggestions, before you verify your hw board/FPGA works fine with SYSACE, * don't use sysace as root fs. * use a ram fs as root fs. * Next, load sysace driver a loadable driver module. It works, I tried it. * check mount read only and see if it works. * Next, mount it writable. We have some issues with sysace driver initially, everything works out fine later. There were small errors in our HW layout. I had to hack the sysace driver left and right to id the problem. But at the end, after I fixed the layout problem from the fpga's ucf file, the original driver run perfectly without any modification. In my experiences, the ppc linux distribution and its linux sysace driver are good if everything is setup correctly. One minor issues: The sysace driver's write performance sucks. I have to explain to others why the upgrade 10 MBytes files with usb flash writer takes tens of seconds. When we do it from linux (nfs or ftp), it tooks minutes to sync. Peter, maybe you can push the xilinx a bit on sysace write performance? :-) -Tony On 8/29/05, Peter Ryser wrote: > > Hi Keith, > > I sent you a private email but for other interested people: > Downloading the latest linuxppc-2.4 kernel I could boot from and access > System ACE CF without problems on a ML403 (Virtex-4, 4VFX12) and a ML310 > (Virtex-II Pro, 2VP30) using EDK 7.1.2. In both cases I started with > config_xilinx_ml300. > > - Peter > > > > Keith J Outwater wrote: > > >Hello - > >Per a previous suggestion from this list, I rsynced the linuxppc-2.4 > >kernel sources from MontaVista and modified the kernel to run on my > custom > >ppc405/VirtexII Pro based system with U-Boot as the bootloader. > >When I try to use the SystemACE device as the root filesystem, the kernel > >crashes with a sig 11. Looking at the 'oops' output it appears the > >SystemACE driver may be to blame. The crash is random - sometimes I get > >all the way to login as root and then things crash on a file copy or a > >file read. > >Before I start digging deeper, is anyone running a VirtexIIPro based > >system with the root filesystem in the CF card attached to a SystemACE? > >I'm wondering if I really have the best kernel and SystemACE driver. > >BTW, I'm developing the hardware design using Xilinx EDK 7.02i. > >Thanks, > >Keith > >___ > >Linuxppc-embedded mailing list > >Linuxppc-embedded at ozlabs.org > >https://ozlabs.org/mailman/listinfo/linuxppc-embedded > > > > > > > > > > > > ___ > Linuxppc-embedded mailing list > Linuxppc-embedded at ozlabs.org > https://ozlabs.org/mailman/listinfo/linuxppc-embedded > -- -Tony Having fun with FPGA HW + ppc + Linux -- next part -- An HTML attachment was scrubbed... URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20050831/d460bb12/attachment.htm
Problems with MontaVista Linux on a Memec Virtex-II pro ff672 board
Peter, Maybe xilinx can come up with app note on how to debug the kernel bring up / hanging issue with chipscope on PLB bus. That would be the most powerful way to demo how to use the Xilinx VP HW platform to debug some tricky kernel issues. You have a extreme flexible platform for this. We just need a xilinx's guiding hand from time to time. I can use the same help too for following issues with linux on VP 20. :-) * I have trouble finding where 700+ msec cpu time went in my currect system - kernel, ISR, other user tasks. * Sometime on power on, the linux would lockup before everything is ready. -Tony On 3/17/05, Peter Ryser wrote: > Also try to boot the first Linux kernel (the one without the Flash > support) on the EDK design with Flash support. It will help narrow down > the problem to the HW or the SW. > > - Peter > > S. van Beek wrote: > > >>How did you add the Flash (EMC) peripheral? Did you use the Base System > >>Builder to generate your hardware? > >> > >> > > > >Yes, we started a new project using the base system builder with the same > >options as the previous (working) project and flash, so the address range > >should be ok. I'll check tomorrow, right now its time to go home ;) > > > >Regards, > >Sander > > > >- Original Message - > >From: "Peter Ryser" > >To: "S. van Beek" > >Cc: > >Sent: Thursday 17 March 2005 16:37 > >Subject: Re: Problems with MontaVista Linux on a Memec Virtex-II pro ff672 > >board > > > > > > > > > >>How did you add the Flash (EMC) peripheral? Did you use the Base System > >>Builder to generate your hardware? > >> > >>If you configure the hardware manually and use the OPB EMC make sure > >>that you add the address range to the PLB2OPB bridge. > >> > >>- Peter > >> > >> > >>S. van Beek wrote: > >> > >> > >> > >>>Hello there, > >>> > >>>This is our first post on this list, hi all! > >>>We're two Dutch students working with a Virtex-II pro ff672 board from > >>>Memec with the Communications 2 module. We've compiled a simple kernel > >>>wich comes with MontaVista Linux 3.1 (2.4.20) with ethernet and a > >>>serial port. It mounts its root filesystem over NFS and everything > >>>seems to work nicely. The next step we wanted to make was > >>>adding support for the Flash on the com board. We added the IP to the > >>>hardware and loaded the new bitstream in the FPGA. Next thing, we > >>>enabled support for MTD devices in the kernel. After that, the kernel > >>>did not seem to boot anymore. It stopped at the message 'Now booting > >>>the kernel'. So we read some documentation about debugging. We > >>>recompiled this kernel with the -g -ggdb options and removed the -O > >>>(optimalization) flag. Then we did not even see the ppc boot loader > >>>messages anymore when trying to boot. So we tried to compile the first > >>>kernel (with only serial and ethernet support) -wich worked fine > >>>before- with debugging and it gave us the same result.. no output at > >>> > >>> > >all. > > > > > >>>Can anyone give us some hints on what we can try more to find out what > >>>is going wrong? > >>> > >>>Regards, > >>>Sander van Beek > >>>Daniel van Os > >>> > >>> > >>> > >>>___ > >>>Linuxppc-embedded mailing list > >>>Linuxppc-embedded at ozlabs.org > >>>https://ozlabs.org/mailman/listinfo/linuxppc-embedded > >>> > >>> > >>> > >> > >> > >> > > > > > > > > > > > > > > ___ > Linuxppc-embedded mailing list > Linuxppc-embedded at ozlabs.org > https://ozlabs.org/mailman/listinfo/linuxppc-embedded > -- -Tony Having fun with FPGA HW + ppc + Linux
TZ variable setting for denx 2.4.20
What's denx? Anyway, in my embeded ppc-linux, I set it with /etc/TZ echo "PST8PDT" > /etc/TZ to set it to pacific time. Have fun. -Tony On Fri, 07 Jan 2005 12:58:42 +0530, Robin wrote: > Hi > Thanx for your response. I am setting TZ variable as > given in the documentation. >export TZ="xxx5:30yyy4:30,M10.1.1,M2.1.1" > Its working fine till Dec 31 23:59:59GMT. On Jan 01 00:00:00, > its not taking DST into account at all. > > Please tell me some way of setting it across an year boundary. > Thanks, > Robin > > Marius Groeger wrote: > > > Robin, > > > > On Thu, 6 Jan 2005, Robin wrote: > > > >> I have tried with the standard linux date too. That too doesnt seem > >> to consider timezone variable that has been set. Can you give me a > >> way for setting timezone for southern hemisphere countries?? The > >> busybox code uses strftime function. But that does not seem to > >> consider TZ variable... > > > > > > You should read up on how glibc handles all that timezone stuff: > > > > sh# info libc "TZ Variable" > > > > Most notably, make sure you /etc/localtime is set up correctly. There > > is also a tool (script) called tzselect which may be helpful for you. > > > > Note I'm not exactly an expert on this, I'm just giving pointers... > > > > Regards, > > Marius > > > > ___ > Linuxppc-embedded mailing list > Linuxppc-embedded at ozlabs.org > https://ozlabs.org/mailman/listinfo/linuxppc-embedded > -- -Tony Having fun with FPGA HW + ppc + Linux
Linux on Memec Virtex II Pro V4P7 Rev. 3
On Sat, 9 Oct 2004 20:27:15 +0100, Jon Masters wrote: > On Thu, 7 Oct 2004 19:53:52 -0700, Tony Lee wrote: > > > The problem I saw was that I can't turn off the interrupt at all. > > On the Memec board? really? > No, not on Memec, just on our own HW.I have the memec board, but I don't have time to play on that one. I got to debug the HW one week after I was hired.As far as I can tell, our linux for memec board doesn't load the sysace driver. > > Once I start one write command, the ISR keep coming in. > > Ouch. Tell me about it. It tooks me 3+ days to id this. > Perhaps. But that's down to your hardware guys to check the error > output from your synthesis tool to see if this weirdly has happened. > Our board doesn't have lines hard tied together, if that was the > notion you were offering. I tried to synthesize chipscope into into our VP20. But don't have much time for it now. It is less of a priority since the sysace is working now for 1.5 months (without ISR). Also, we use linux as Xilinux dev environment but the chipscope only work in Windows platform. Our HW folks don't have time to touch Windows side of Xilinx tools. It make it more difficult to debug SW/HW integration issue. > > > I try turn off the ISR on write with SYSACE register and > > the ppc interrupt control register. None of them worked. > > Did you do it as per my patch, or what? No, where can I find your patch? > > Yes. We come up in 8 seconds to my firmware, and total boot time is > around 20 seconds, without any effort to make it less. That includes > cunning DHCP+ZeroConf scripts I wrote. > That's about right, We don't do DHCP, it comes up a bit faster. -- -Tony Having a lot of fun with Xilinx Virtex Pro II reconfigurable HW + ppc + Linux
Linux on Memec Virtex II Pro V4P7 Rev. 3
On Fri, 08 Oct 2004 01:12:51 +0100, Jon Masters wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > The polled approach is worse IMO although I agree that there is very > little overhead in the actual ISR. Where the author went wrong (well > perhaps not wrong per se but didn't provide enough protection) was in > the unlikely case that the hardware is braindead and generates > interrupts that you didn't ask it to - the xsysace driver should also > catch interrupts when we're QUEUE_EMPTY and should not try to manipulate > an empty request queue. > > Jon. The problem I saw was that I can't turn off the interrupt at all. Once I start one write command, the ISR keep coming in. I review the verilog code and schematic multiple times with the HW group but can't figure out what went wrong. My best guess was the BUFRDY line is mix up with the ISR line some how when write cmd and when IDEN drive command is issued. I try turn off the ISR on write with SYSACE register and the ppc interrupt control register. None of them worked. Jon, Do you think if we add a small DMA engine would help the performance or the performance problem is caused by the sysace firmware + the CF disk? The sysace controller IS VERY fast on loading the bitstream and linux boot image. -- -Tony Having a lot of fun with Xilinx Virtex Pro II reconfigurable HW + ppc + Linux
Linux on Memec Virtex II Pro V4P7 Rev. 3
On Wed, 06 Oct 2004 19:41:22 +0400, Andrei Konovalov wrote: > Jon Masters wrote: > > On Tue, 05 Oct 2004 20:05:29 +0400, Andrei Konovalov > > wrote: > > > > > > While we're on this subject I will ask - do you also need something > > like the nointr mods I pointed out in order to use sysace for writing > > on that board? The hardware generates more interrupts than anything > > documented suggests that it should and your driver dies horribly (or > > is completely unreliable) unless I modify it as I mentioned. It's > > probably a sysaceism. > > Not too much to say about sysace at the moment. > We do not use xsysace in our Memec 2VP7 design (this is a chip select > issue with P160 flash and xsysace sitting on the same bus - we do > not have HW engineer to do an IP to control the chip select inputs; > by default both are tied to ground - always selected). > With ML300 we've never seen this problem. I was just asked to try > to enhance the xsysace driver performance - will use this opportunity > to have a deeper look at the driver's internals. > I have to use the non-interrupt mode in sysace. I thought there were some HW issue in our HW board (no ML 300). Good to know other have the same problem. We don't have ML300, otherwise, I will run the kernel with printk in the sysace driver to see that system ISR behavior on write. The problem I had was: I can not turn off the ISR when write to the system (nor when send ID drive command). Jon, what kind of performance you got from the sysace? When I copy 18 MB of ace file into sysace with Linux, the sync command took minutes to complete for me. Sysace ISR should not be the issue, since there is no seeks and all the IO is dirven from the kernel. -- -Tony
