• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 425 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.

Android and DSP/BIOS

mi1980
Prodigy 190 points
Other Parts Discussed in Thread: DM3730

Hi all,

We are currently working wirh a TIC6000 custom target and would like to migrate the processor to an Android compatible TI solution.

Is there any way to migrate our DSPBIOS developments to Android?

Thanks in advance and my apologies for the newbie question.

Best regards

Miguel

  • 0
    Prodigy 190 points

    When I read my post I realize maybe it was not clear enough.

    I meant that we have already developed an operating system based on DSP/BIOS for our custom prototype. Now we want to move to substitute the TIC6000 to an Android TI compliant device (OMAP, AM/SITARA) and It would be a pity no to take advantage of our previous developments. I am perfectly aware that both EOS (Android and DSPBIOS) are different and have different purposes but maybe there is a way to migrate from one platform to the other.

    I am starting to read about Android in these forums but for the moment I did not find information related to this issue.

    Thanks again.

     

  • 0 in reply to mi1980
    TI__Guru**** 168171 points

    Not sure if you are aware of Rowboat project - http://code.google.com/p/rowboat/, which supports DM37x on Android with DSP enabled multimedia acceleration using TI DVSDK 4.xx.

    If your DSP/BIOS implementation is similar to the DSP components in TI DVSDK, you might want to take a look at Rowboat Android.

  • 0 in reply to Bin Liu
    Prodigy 190 points

    Many thanks Bin. I didn't know about it.

  • 0 in reply to mi1980
    Expert 1345 points

    You may want to start with the AM37x version of Android (Gingerbread) and then move the dsplink drivers in from the DM3730 dvsdk or move the source under Android build.  Android is probably going to want to use the dsp for its own uses, codecs, etc.  I'm doing the same thing and figure it is easier to have Android only know of the ARM environment and I'll control the dsp myself.  In my case I'm not doing multimedia on the dsp but do want to run Android for HMI operations.

    Regards,

    Kev