Embedded Linux

[mandar.thite]

Hi Mario,

I have just begun to work on a similar porting project as yours(porting of Xilinx Linux kernel to Microblze core).

I am presently having Windows build of Xilinx EDK 12.4.

However, I suppose I don't have to procure Linux build of Xilinx EDK for generating the Microblaze hardware required for hosting the Linux kernel.

Is my thinking correct?

Thanks.

-Mandar T.

[mario.lopezmartinez87]

Sorry for the very late reply,
you're correct as far as I know, you can generate the HW design whether you are using Windows build of EDK or Linux, it's not dependant on the OS.

 However, I think the cross-compilation tools needed to build the kernel for MB are only available on Linux, unless you compile them on your own (or someone has them around there), which can be an added degree of difficulty.
Regards.

[mario.lopezmartinez87]

Someone asked me to post the device utilization summary. That info could be seen my paper, anyway, here it s for your convenience:

         Number of Slice LUT-Flip Flop pairs   17938 out of 44800  40% 

   Number of BSCANs                          1 out of 4      25%

   Number of BUFGs                           9 out of 32     28%

   Number of BUFGCTRLs                       1 out of 32      3%

   Number of BUFIOs                          8 out of 80     10%

   Number of DSP48Es                         3 out of 128     2%

   Number of IDELAYCTRLs                     5 out of 22     22%

      Number of LOCed IDELAYCTRLs            5 out of 5     100%

   Number of ILOGICs                       105 out of 800    13%

      Number of LOCed ILOGICs                8 out of 105     7%

   Number of External IOBs                 216 out of 640    33%

      Number of LOCed IOBs                 216 out of 216   100%

   Number of IODELAYs                       91 out of 800    11%

      Number of LOCed IODELAYs               8 out of 91      8%

   Number of OLOGICs                       188 out of 800    23%

   Number of PLL_ADVs                        1 out of 6      16%

   Number of RAMB18X2s                       3 out of 148     2%

   Number of RAMB18X2SDPs                    1 out of 148     1%

   Number of RAMB36_EXPs                    37 out of 148    25%

   Number of TEMACs                          1 out of 2      50%

   Number of Slice Registers             12993 out of 44800  28%

      Number used as Flip Flops          12990

      Number used as Latches                 0

      Number used as LatchThrus              3

   Number of Slice LUTS                  12124 out of 44800  27%

Feel free to ask for anything ;)

[vaibhawaxilinx]

Hi

 I was trying for the same project on ML507 with some changes like processor i was using powerpc and i was not using client / server model . Simply I comiled the microwindow source files and put in ramdisk and buit the kernal image.

I was getting bootinf msg on the monitor but when  i was running ./nano-x and so. It was saying "no such files or command" I changed the mode also but nothing happened.

Is it possible to build the kernel with already compiled ( for the same processor) microkernel files.

Can u also explain the "arch rules " of micrwindos for the ppc so that I may cross check my self

thanks & regards

[ritanagar]

Hi

 I followed same as the provided guideline for porting linux ml507 , also linux boot disply output on the monitor but when  i was running ./nano-x and so.error comes  It was saying "no such files" .

its not running GUI application , plz help me to sort out this issue.

thanks & regard

[santonop]

Hello, 

I unfortunately don't have any answer to your problem, but I would like to ask you help about the previous step of yours.

When I try to compile the microwinds I get the following:
 

Compiling engine/devopen.c ...
make[1]: mb-linux-gcc: Command not found
make[1]: *** [/home/vlsilab/microwin/src/obj/engine/devopen.o] Error 127
make: *** [subdir-/home/vlsilab/microwin/src/engine] Error 2

Have you changed anything in the .bashrc?

Looking forward to hearing from you and thank you in advance...

Greetings 

[ritanagar]

Hi,

Actually I am not using "bashrc".It is used for setting cross-compile environment.you are compiling.You are compiling your micro-windows separately.When you finished making your kernel image Copy micro-windows in edk project you are working the extract it.

[root@localhost microwindows]# cd src

[root@localhost src]# 

the config files is provided , just copy that

then compile , it will compile successfully with no errors.

Hope I make u understand

[santonop]

Well, thank you for your reply...

I solved it with a different procedure. In the config file I changed the cross-compile option from "mb-linux" to "microblaze-unknown-linux". Then I typed the bash command "make" to start the compiling process.

Through nfs you can access the compiled files from the linux host pc. In your "board-linux" terminal you have to excecute the ./ commands inside the folder where these files are. So you have to type cd <directory> and then excecute the final command.

I hope I helped you... 

[ritanagar]

thanks for your help sir, I will follow the same and later ask u if I got some doubt.Thanks a lot