Tests for the DM365 EVM & "Segmentation fault"

I want to use the GPIO of the EVMDM365 ( Read/Write), if you have another solution ( another library or driver) thank you to show me .

Thank you !

My problem with "Segmentation fault" i beleive because i have not compile my program with CCS , so there is an init of the board with

GEL file that i found it with the sample , i want to know there is a solution do this init without gel file .

Thank you !

I have not tried running the tests on DM365 EVM yet, but speaking from past experience with similar boards

1) You should not need to recompile anything; the download includes pre-compiled binaries (.out files ) for each test.

2) You do need to load the appropriate GEL file for the test as specified in the readme.txt file.  The GEL file helps initialize the EVM appropriately for the test you are trying to run.  No need to recompile it but you do need to load it via CCS before connecting to the board.

I want to compile the sample test because i want to modiy some thing to know how it works , and after i use it in my application.

To run the sample , i compile it with arm_v5t_le-gcc with eclipse IDE , i haven't CSS and i use nfs file system , so i generate the exe file and i run it .

So , what is the problem ?, i must use CCS to use the library bsl of the EVM DM365?

How i can run .out file in the board ?

Now I see where you are coming from.  These board level tests where written under CCS environment; under this enviroment, the GEL file does quite a bit of the hardware initialization for you; without this initialization, your DDR2 may not be set up correctly which can lead to all sorts of trouble, but GEL initializes much more than DDR2.  In addition, under CCS enviroment, we have linker command files (.cmd) which describe important memory ranges and assignment information. 

In conclusion, if you want to move out of CCS, then you would need to take care of doing all of the things that CCS is doing for you and which the tests expect to be done before they can run successfully.  If you do not want to use CCS, then you may be better off using the Linux OS which includes Linux driver stack.  There is basic kernel level GPIO support which you may need to extend to user level if that is where you wish to use it.  Needless to say, the bootloader and linux kernel do all the hardware initialization (and more) which was done by CCS, but then you are operating under a different enviroment where memory is protected by the Linux Virtual Memory Manager and the test will likely have to be re-written to use the Linux kernel drivers.

Thank you Juan for this informations ,

Now i see why it does'nt work , i will try to use the linux driver.