• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 343 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Notes on building the MVL kernel on a debian host.

Check12
Prodigy 240 points


I thought it would be a good idea to share my notes on building the kernel from a debian host.

The menuconfig option does not run unless you install the ncurses library. I tried compiling this from source and the make failed with a directory not found error. I then found that if you download the ncurses library using apt-get then all is OK

sudo apt-get install libncurses5-dev libncursesw5-dev

A good reference page for this can be found here:

http://www.cyberciti.biz/faq/linux-error-cursesh-no-such-file-directory/ 

I have a question about the kernel config and the McASP.  Is access to the McASP mutually exclusive to GPP or DSP? or can they be used by both GPP and DSP provided one does not open the device on both GPP and DSP at the same time?

Now, I am able to run the make menuconfig for the kernel, and I would like to know if there are any templates or include files for accessing the McASP from the GPP side.

Thanks

  • 0
    TI__Mastermind 41665 points

    Thank you for pointing this out, I just recently figured this out as well when I needed ncurses on my Ubuntu box for make menuconfig, I usually only use the default configuration so I had not run into the issue. I was able to run it with only the libncurses5-dev package, I don't have libncursesw5-dev installed.

    Check12 said:
    I have a question about the kernel config and the McASP.  Is access to the McASP mutually exclusive to GPP or DSP? or can they be used by both GPP and DSP provided one does not open the device on both GPP and DSP at the same time?

    Generally for for a safe and stable system I would keep the McASP exclusive to one core or the other, theoretically however you could have both using it as long as they both do not try using it at the same time, though I foresee a bit of a software mess to ensure they do not step on each other doing this.

    Check12 said:
    I would like to know if there are any templates or include files for accessing the McASP from the GPP side.

    The GPP will be treating the McASP as a standard audio device, so there is code in there for the McASP but it is not being used at a very low level, to a user it is exposed as an ALSA driver.