Forums

Jeff,

The environment setup script does not add the bin directory of the c6run install in the PATH environment variable, but rather defines a new variable, C6RUN_TOOLCHAIN_PATH.  The example Makefiles use that if it is defined.  Feel free to edit the environment script to actually edit the PATH as follows:

export PATH=$(C6RUN_TOOLCHAIN_PATH)/bin:$PATH

One extra word of caution is to exit whatever terminal window you are in and then start a new one to make sure you are not accidentally picking up old variables that pointed to an old install.

Regards, Daniel

I tried doing: export PATH=/usr/local/dvsdk/C6Run_0_97_03_03/bin:$PATH

But I still get the error. Also, when I open a new terminal and do echo $PATH, that directory is no longer there, is that normal?

You have source the environment variables or set the path each time you open a new terminal window.  I would try calling the c6runapp-cc tool using the absolute path and see what happens.  That will tell us if we are just seeing a problem with the PATHs or if there is some other issue with the tool (i.e. not set as executable, not finding the correct shell, etc.).

Regards, Daniel

I copied one of the examples to C6Run/lib and doing 'sudo make' still doesnt work. However it will work when I do something like ./c6runapp-cc hello_world.c, but not just 'c6runapp-cc hello_world.c'. I also added the commands in environment.sh to .bashrc, so the variables are set each time a new terminal is opened. However I still get the error when trying to execute elsewhere.

Another thought, in the setup instructions it says to 'make c6run' then 'source environment.sh'. Is there no 'make install' that needs to be done?

Jeff,

I just started from scratch and ran the following after opening a new terminal window and entering the C6Run_0_97_03_03 directory:

1. 'make get_components'

2. 'make omapl138_config'

3. 'vi platforms/omapl138/platforms.mak' (did this to make sure I was pointing to the correct paths for the Linux kernel and u-boot source in the DVSDK 4.01 I have installed)

4. 'make everything' (this passed and built the backend GPP library, the backend DSP library, and the required DSPLink and CMEM kernel modules)

5. Then I edited the environment.sh script ('vi ./environment.sh') and added the following lines to the end of that file:

PATH=${C6RUN_TOOLCHAIN_PATH}/bin:$PATH

export PATH

6. 'source ./environment.sh'

At that point I can run c6runapp and the other tools without any issues.  For example, without changing directories out of the top-level of the C6Run install, I did the following:

'c6runapp-cc -o hello examples/c6runapp/hello_world/hello_world.c'

I can also call the full path and the relative path

'./bin/c6runapp-cc -o hello1 examples/c6runapp/hello_world/hello_world.c'

'/home/daniel/C6Run_0_97_03_03/bin/c6runapp -o hello2 examples/c6runapp/hello_world/hello_world.c'

Finally I did change directory into the hello_world example:

'cd examples/c6runapp/hello_world/'

'c6runapp-cc -o hello3 hello_world.c'

That all works, so I'm don't think I'm able to reproduce the same issue you are seeing.

If you follow all of the above and still are having problems, can you provide some more info about your host system? I'm assuming you are on Ubuntu 10.04, using the bash shell as the DVSDK requires.

Regards, Daniel

Jeff Richmond

Another thought, in the setup instructions it says to 'make c6run' then 'source environment.sh'. Is there no 'make install' that needs to be done?

There is an 'install' target in the top-level makefile that will copy the required binary components out of the source/build tree to a destination that you specify.  I just never use it because I would then need to edit the environment.sh script for the new location or add the tools to the path.  I'm lazy and I just leave everything in the same source/build tree.

Regards, Daniel

This is the same process I was trying before, but I retried it and still get the error. It does work to use the absolute path and do './c6run...', so I guess I'll just use it that way for now. I am on Ubuntu 10.04 LTS 32 bit.

OK I think I have it partially working now, atleast the c6run calls work. However when I try to make the examples ie for hello_world I just do 'make' and I get the error:

"hello_world.c", line 40: fatal error #5: could not open source file "stdio.h"
1 fatal error detected in the compilation of "hello_world.c".
Compilation terminated.

Probably because I'm not root. But then when I do 'sudo make' I get the error:

jeff@jeff-ubuntu10-04:~/C6Run_0_97_03_03/examples/c6runapp/hello_world$ sudo make
c6runapp-cc -O3 -o hello_world_dsp hello_world.c
make: c6runapp-cc: Command not found
make: *** [dsp] Error 127

Yea you were right Daniel thanks. One more quick question:

If I'm configuring the DVSDK for Angstrom on Beagleboard xM rev B, which has the DM3730 processor, would I want to use the DM3730 config, or just stick the the beagleboard-xM?

The main (only?) difference between the two is the system memory map.  The DM3730 one corresponds to what you would use for the DVSDK 4.x product. The Beagleboard one is not really aligned with any particular use case.  You could modify either one to suit your own needs and use it.

Regards, Daniel

I am having the same problem. I am not really sure how to solve it. When I do "make examples" I get

make[3]: Entering directory `/home/martin/beagleboard/c6run/C6Run_0_98_03_03/examples/c6runlib/emqbit' /home/martin/beagleboard/c6run/C6Run_0_98_03_03/bin/c6runlib-cc -c -O3 -o dsp_lib/cfft.o cfft.c "/tmp/06522ACJBda", ERROR! at EOF: [E1500] file access error: failed to open "dsp_lib/cfft.o" for writing "/tmp/06522ACJBda", ERROR! : [E1000] Failed to write object file : dsp_lib/cfft.o

If I do "sudo make examples" I get errors like

make[3]: Entering directory `/home/martin/beagleboard/c6run/C6Run_0_98_03_03/examples/c6runapp/cio_example' c6runapp-cc -O3 -o cio_example_dsp cio_example.c make[3]: c6runapp-cc: Command not found make[3]: *** [dsp] Error 127

I am using this guide: http://processors.wiki.ti.com/index.php/Getting_Started_With_C6Run_On_Beagleboard

I suppose the problem lies with environment.sh. Before I edited the file, the ARM_TOOLCHAIN_PATH was the same as the C6RUN_TOOLCHAIN_PATH. I supposed this was wrong since in Rules.mak I have ARM_TOOLCHAIN_PATH pointing to the directory of the ARM cross-compiler that I'm using (CodeSourcery).