About how port yocto to a customized MIPS cpu

About how port yocto to a customized MIPS cpu

[张健]

[-- Attachment #1.1: Type: text/plain, Size: 1535 bytes --]

hi,everyone:


    This is Jack from Shanghai, in my first year in graduate school. 
    I'm sending email here to asking for some help about how to port linux on a customized cpu run on FPGA board.


Before I have been working on how to use "verilog" to make a cpu (based on MIPS32 ISA) on a FPGA board, and for now  I could form a set of cpu code, and use assembly on it.
The following is my tetris demo,which is written in assembly language and run on the MPIS32 CPU (written in verilog on FPGA board). 



http://www.tudou.com/programs/view/e-E5lVrQfTw/




These days, I start to think the question about how to port linux on my tiny "cpu". So I find "yocto",which seems the thing that could help me.
I have finished the "yocto project quick start" document online yesterday. (http://www.yoctoproject.org/docs/2.0/yocto-project-qs/yocto-project-qs.html)
and was very happy to see that it could "boot" on the qemu simulator. 


and I found the following are the boot image files.



In some embedded boards, they usually write a linux image file(.img ) to a sd card. Then plug in to the board. Finally it boots.
But I have no idea what's inside the .img files, and how to let my fpga board to understand the .img files. 


So this  is reason why I'm here to ask you guys for some help.


And wish to know if it is possible to port the "yocto" to my own project.


Thank you and Best wishes !
To geeks :)




Jack


======================================
the yocto quick start training:

[-- Attachment #1.2: Type: text/html, Size: 2570 bytes --]

[-- Attachment #2: 3CAE06BA@4D0EAC29.C20AA856.png --]
[-- Type: application/octet-stream, Size: 71453 bytes --]

[-- Attachment #3: 2ED3165A@41C09A0C.C20AA856.png --]
[-- Type: application/octet-stream, Size: 62173 bytes --]

[-- Attachment #4: 0AA7762E@B8504231.C20AA856.png --]
[-- Type: application/octet-stream, Size: 100943 bytes --]

[-- Attachment #5: 69D80986@5ADC990F.C20AA856.png --]
[-- Type: application/octet-stream, Size: 95760 bytes --]

[-- Attachment #6: B5980B8A@BF9D8427.C20AA856.png --]
[-- Type: application/octet-stream, Size: 93796 bytes --]

About how port yocto to a customized MIPS cpu

[张健]

[-- Attachment #1.1: Type: text/plain, Size: 1535 bytes --]

hi,everyone:


    This is Jack from Shanghai, in my first year in graduate school. 
    I'm sending email here to asking for some help about how to port linux on a customized cpu run on FPGA board.


Before I have been working on how to use "verilog" to make a cpu (based on MIPS32 ISA) on a FPGA board, and for now  I could form a set of cpu code, and use assembly on it.
The following is my tetris demo,which is written in assembly language and run on the MPIS32 CPU (written in verilog on FPGA board). 



http://www.tudou.com/programs/view/e-E5lVrQfTw/




These days, I start to think the question about how to port linux on my tiny "cpu". So I find "yocto",which seems the thing that could help me.
I have finished the "yocto project quick start" document online yesterday. (http://www.yoctoproject.org/docs/2.0/yocto-project-qs/yocto-project-qs.html)
and was very happy to see that it could "boot" on the qemu simulator. 


and I found the following are the boot image files.



In some embedded boards, they usually write a linux image file(.img ) to a sd card. Then plug in to the board. Finally it boots.
But I have no idea what's inside the .img files, and how to let my fpga board to understand the .img files. 


So this  is reason why I'm here to ask you guys for some help.


And wish to know if it is possible to port the "yocto" to my own project.


Thank you and Best wishes !
To geeks :)




Jack


======================================
the yocto quick start training:

[-- Attachment #1.2: Type: text/html, Size: 2631 bytes --]

[-- Attachment #2: C54DC87C@B60D5E42.6E0BA856 --]
[-- Type: application/octet-stream, Size: 62173 bytes --]

[-- Attachment #3: 3171C65C@89EA4A6B.6E0BA856 --]
[-- Type: application/octet-stream, Size: 100943 bytes --]

[-- Attachment #4: 28B28809@FF92D16D.6E0BA856 --]
[-- Type: application/octet-stream, Size: 95760 bytes --]

[-- Attachment #5: FDC19658@B052544C.6E0BA856 --]
[-- Type: application/octet-stream, Size: 71453 bytes --]

[-- Attachment #6: FCE205C6@8459786E.6E0BA856 --]
[-- Type: application/octet-stream, Size: 93796 bytes --]

About how port yocto to a customized MIPS cpu

[张健]

[-- Attachment #1.1: Type: text/plain, Size: 1535 bytes --]

hi,everyone:


    This is Jack from Shanghai, in my first year in graduate school. 
    I'm sending email here to asking for some help about how to port linux on a customized cpu run on FPGA board.


Before I have been working on how to use "verilog" to make a cpu (based on MIPS32 ISA) on a FPGA board, and for now  I could form a set of cpu code, and use assembly on it.
The following is my tetris demo,which is written in assembly language and run on the MPIS32 CPU (written in verilog on FPGA board). 



http://www.tudou.com/programs/view/e-E5lVrQfTw/




These days, I start to think the question about how to port linux on my tiny "cpu". So I find "yocto",which seems the thing that could help me.
I have finished the "yocto project quick start" document online yesterday. (http://www.yoctoproject.org/docs/2.0/yocto-project-qs/yocto-project-qs.html)
and was very happy to see that it could "boot" on the qemu simulator. 


and I found the following are the boot image files.



In some embedded boards, they usually write a linux image file(.img ) to a sd card. Then plug in to the board. Finally it boots.
But I have no idea what's inside the .img files, and how to let my fpga board to understand the .img files. 


So this  is reason why I'm here to ask you guys for some help.


And wish to know if it is possible to port the "yocto" to my own project.


Thank you and Best wishes !
To geeks :)




Jack


======================================
the yocto quick start training:

[-- Attachment #1.2: Type: text/html, Size: 2698 bytes --]

[-- Attachment #2: E55F4296@FEDDAA0E.8A0CA856 --]
[-- Type: application/octet-stream, Size: 62173 bytes --]

[-- Attachment #3: B6264093@9A2EFD68.8A0CA856 --]
[-- Type: application/octet-stream, Size: 100943 bytes --]

[-- Attachment #4: DE33C508@7C4E1D2C.8A0CA856 --]
[-- Type: application/octet-stream, Size: 95760 bytes --]

[-- Attachment #5: BCFFD53E@734C4D59.8A0CA856 --]
[-- Type: application/octet-stream, Size: 71453 bytes --]

[-- Attachment #6: 6A544D81@55336A10.8A0CA856 --]
[-- Type: application/octet-stream, Size: 93796 bytes --]

Re: About how port yocto to a customized MIPS cpu

[Khem Raj]

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

On Tue, Jan 26, 2016 at 7:09 PM, 张健 <jackzhang1992@t.shu.edu.cn> wrote:

> But I have no idea what's inside the .img files, and how to let my fpga
> board to understand the .img files.
>
> So this  is reason why I'm here to ask you guys for some help.
>
> And wish to know if it is possible to port the "yocto" to my own project.
>
>
​image files are generated in several formats. There is option to generate
tarballs. You can always take the tarball and untar it and look what inside
secondly, for your FPGA to understand this, you probably will need tools to
download the binary to memory which is visitible to FPGA if I assume FPGA
is sitting along with a application processor which can then help you to
flash it to relevant memory parts.

if your application processor has a bootloader e.g. uboot which can use SD
cards as boot media then you can use wic tool to generate SD card
images directly from yocto. wic is documented in dev manual so please look
there on how to set it up. Or you can look at some other BSPs like
beaglebone ( angstrom ) or raspberrypi or freescale layer for scripts to
generate the SD card images and model your using those.​

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

Re: About how port yocto to a customized MIPS cpu

[张健]

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

About image files, i guess there are various types of it, like .img, .vdi,..etc (https://en.wikibooks.org/wiki/QEMU/Images),but I wish to find a type that is machine code of the target machine so that it could be booted directly.


About bootloader, do you you mean yocto project doesn't include bootloader tools like uboot? For now, I realize the YP is a tool chain for generating linux distributions. So it builds the source code,and  converts it to linux image files, doesn't it? So in the future, I should focus on how to use uboot to boot the linux images (generated by YP) to my my own "tiny" cpu, right?


Thank you and Best wishes.  
 
------------------ Original ------------------
From:  "Khem Raj"<raj.khem@gmail.com>;
Date:  Thu, Jan 28, 2016 03:10 AM
To:  "JackZhang"<jackzhang1992@t.shu.edu.cn>; 
Cc:  "yocto"<yocto@yoctoproject.org>; 
Subject:  Re: [yocto] About how port yocto to a customized MIPS cpu

 

On Tue, Jan 26, 2016 at 7:09 PM, 张健 <jackzhang1992@t.shu.edu.cn> wrote:
But I have no idea what's inside the .img files, and how to let my fpga board to understand the .img files. 


So this  is reason why I'm here to ask you guys for some help.


And wish to know if it is possible to port the "yocto" to my own project.





​image files are generated in several formats. There is option to generate tarballs. You can always take the tarball and untar it and look what inside
secondly, for your FPGA to understand this, you probably will need tools to download the binary to memory which is visitible to FPGA if I assume FPGA
is sitting along with a application processor which can then help you to flash it to relevant memory parts. 


if your application processor has a bootloader e.g. uboot which can use SD cards as boot media then you can use wic tool to generate SD card
images directly from yocto. wic is documented in dev manual so please look there on how to set it up. Or you can look at some other BSPs like
beaglebone ( angstrom ) or raspberrypi or freescale layer for scripts to generate the SD card images and model your using those.​

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

plan-list for porting linux Re: About how port yocto to a customized MIPS cpu

[张健]

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

Hi,everyone:
   For now, I have finished the yocto qurk_start document, and succeeded in building the yocto-raspberrypi image for my rpi2 B+ board. I beleive it's a good start!
   But after that, I still wish to figure out how to port a linux system to my fpga board with a "mips32" cpu. In the future, I will look into how to write the bsp of yocto project by refering to the poky reference distribution, the meta-raspberrypi as well as the document "yocto project BSP devellops' guide2.0" . 


This is my plan lists:
    01. to write a yocto bsp for my device
    02.learn to use qemu
    03.learn to use uboo
    04.learn to use archlinux for a general understanding of how a linux system runs and it's mechanisms. 
    ...


If anyone gets some ideas,pls feel free to contact with me
Thank you,and best regards
Jack
Shanghai
 
 
------------------ Original ------------------
From:  "Khem Raj"<raj.khem@gmail.com>;
Date:  Thu, Jan 28, 2016 03:10 AM
To:  "JackZhang"<jackzhang1992@t.shu.edu.cn>; 
Cc:  "yocto"<yocto@yoctoproject.org>; 
Subject:  Re: [yocto] About how port yocto to a customized MIPS cpu

 

On Tue, Jan 26, 2016 at 7:09 PM, 张健 <jackzhang1992@t.shu.edu.cn> wrote:
But I have no idea what's inside the .img files, and how to let my fpga board to understand the .img files. 


So this  is reason why I'm here to ask you guys for some help.


And wish to know if it is possible to port the "yocto" to my own project.





​image files are generated in several formats. There is option to generate tarballs. You can always take the tarball and untar it and look what inside
secondly, for your FPGA to understand this, you probably will need tools to download the binary to memory which is visitible to FPGA if I assume FPGA
is sitting along with a application processor which can then help you to flash it to relevant memory parts. 


if your application processor has a bootloader e.g. uboot which can use SD cards as boot media then you can use wic tool to generate SD card
images directly from yocto. wic is documented in dev manual so please look there on how to set it up. Or you can look at some other BSPs like
beaglebone ( angstrom ) or raspberrypi or freescale layer for scripts to generate the SD card images and model your using those.​




==============
On Tue, Jan 26, 2016 at 7:09 PM, 张健 <jackzhang1992@t.shu.edu.cn> wrote:


hi,everyone:
    This is Jack from Shanghai, in my first year in graduate school.
    I'm sending email here to asking for some help about "how to port linux on a customized cpu run on FPGA board".
Before I have been working on how to use "verilog" to make a cpu (based on MIPS32 ISA) on a FPGA board, and for now  I could form a set of cpu code, and use assembly on it.
The following is my tetris demo,which is written in assembly language and run on the MPIS32 CPU (written in verilog on FPGA board).
http://www.tudou.com/programs/view/e-E5lVrQfTw/
These days, I start to think the question about how to port linux on my tiny "cpu". So I find "yocto",which seems the thing that could help me.
I have finished the "yocto project quick start" document online yesterday. (http://www.yoctoproject.org/docs/2.0/yocto-project-qs/yocto-project-qs.html)
and was very happy to see that it could "boot" on the qemu simulator.
and I found the following are the boot image files:
   bzImage; bzImgage.bin; core-imgae-sato-qemux86.ext4;core-image-sato-qemux86.tar.bz2;modules-qemux86.tgz ...etc


In some embedded boards, they usually write a linux image file(.img ) to a sd card. Then plug in to the board. Finally it boots.
But I have no idea what's inside the .img files, and how to let my fpga board to understand the .img files.
So this  is reason why I'm here to ask you guys for some help.
And wish to know if it is possible to port the "yocto" to my own project.
Thank you and Best wishes !
To geeks :)


Jack

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