[yocto] About how port yocto to a customized MIPS cpu

张健 jackzhang1992 at t.shu.edu.cn
Tue Jan 26 16:17:14 PST 2016


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:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20160127/04830b75/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: E55F4296 at FEDDAA0E.8A0CA856
Type: application/octet-stream
Size: 62173 bytes
Desc: not available
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20160127/04830b75/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: B6264093 at 9A2EFD68.8A0CA856
Type: application/octet-stream
Size: 100943 bytes
Desc: not available
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20160127/04830b75/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: DE33C508 at 7C4E1D2C.8A0CA856
Type: application/octet-stream
Size: 95760 bytes
Desc: not available
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20160127/04830b75/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: BCFFD53E at 734C4D59.8A0CA856
Type: application/octet-stream
Size: 71453 bytes
Desc: not available
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20160127/04830b75/attachment-0003.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 6A544D81 at 55336A10.8A0CA856
Type: application/octet-stream
Size: 93796 bytes
Desc: not available
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20160127/04830b75/attachment-0004.obj>


More information about the yocto mailing list