LOGIN   :::   RECOVER PASS   :::   GET ACCOUNT    
Browse
  • Projects
  • Code (CVS)
  • Forums
  • News
  • Articles
  • Polls
  •  
    OpenCores
  • FAQ
  • CVS HowTo
  • Mission
  • Media
  • Tools
  • Advertise
  • Mirrors
  • Logos
  • Contact us
  • Find Resources
  • Job Opportunity
  •  
    Tools
  • Search
      
  • Download Cores (CVSGet)
  •  
    More
  • Wishbone
  • Perlilog
  • EDA tools
  • OpenTech CD
  •  
    Navigation: All forums > Openrisc > Message List > Message Post

    Message

    Reply | Reply all
    Date Prev | Date Next | Thread Prev | Thread Next Date Index | Thread Index

    From: Simon Srot <simons@o...>
    Date: Tue, 06 May 2003 10:18:57 +0200
    Subject: Re: [openrisc] problems on porting uClinux to my own cpu!
    Top

    ee9721@e... wrote:
    > 
    > as I know some  experts has ported uclinux to OpernRISC,
    > could anyone give me some advice on porting uClinux to my
    > own cpu and hardware.
    > 
    > My troubles are:
    > 
    > 1. If a new type of CPU(such as OpenRISC 1000) is used to run ucLinux,
    > what kinds of  files in the source code of ucLinux need to be revised,
    > and what kind of new source files should be written into ucLinux by
    > myself.  What directories are these files locating besides the ARCH
    > directory?
    
    Actually these and header files in include/asm-xx/ folder are the only
    files that you need to add/change for a new port.
    
    > 
    > 2. How to debug the kernel image after it is downloaded into the flash
    > memory? Could you let me know how to get debug information before
    > the UART normally works?. Could you pls tell me how you handle with
    > debugging and porting uclinux on you FPGA board?
    
    In our case, we used simulator to develop or1k port. This was quite
    easy, because we had complete view on program flow and processor state
    at all times. If you are using real HW, you will need some sort of
    debugger, that will enable you setting breakpoints, stepping through the
    instructions and also get you the state of internal CPU registers and
    contents of the memory. I think this is a must.
    
    > 
    > 3.I am required to complete the porting in May and June. Could you pls
    > advise me how to arrange my porting schedule in such time slot? In
    > another words, could you pls suggest me a feasible step and procedure
    > to port uclinux. Do you think this step will work if I run the cpu-
    > depended initial code first, and then run the process management, and
    > later run memory management, and finally run the file system and I/O
    > drivers?
    
    I'm not sure. I think that you complete the whole port with ram file
    system and put for example sash into FS image as your first application.
    Then start testing the code and solving the problems step by step. This
    was my approach.
    
    Simon
    
    > 
    > Best Regards
    > 
    > William Neal
    > 
    
    
    

    ReferenceAuthor
    [openrisc] problems on porting uClinux to my own cpu!Ee9721

     
    Copyright (c) 1999 OPENCORES.ORG. All rights reserved.