EnneGi, I don't know at what step you have a problem, so let me describe how I made changes, and if you already know this part, please forgive.
I take a copy of the code from CVS and never change it. This is for reference. Then I copy the package tree to my install area after tar'ing up my old one. I make changes to files in the package tree. Now I can use diff or guiffy between the clean tree and the working tree if I get in trouble and need to know what I did. And I can use this for making patches. I then have a eCos project. That project creates two directories, one ending in _build and one ending in _install. I cd to _build and do a: make clean make I do this because the build from the eCos tool may not report errors. This prevents accidental use of old files. Then I take my application project and do a clean to make sure the compiler does not make any mistakes with old object files, and compile everything. Then I debug. If the question is about the code itself, others may know the code you are using as an example. I am only familiar with the Kinetis macros, and I am a bit of a newbie, so I have no authority when it comes to proper coding style and structure in eCos. Mike On Mar 14, 2013, at 8:40 AM, EnneGi <enricogiordano1...@gmail.com> wrote: > I try to do the porting but i failed. > Does anybody help me step by step? I really don't understand. Thanks. > > > > -- > View this message in context: > http://sourceware-org.1504.n7.nabble.com/How-to-create-a-GPIO-driver-tp224910p225400.html > Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.com. > > -- > Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos > and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss > -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
