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

DM6446 DSP JPEG encode library sprc343 block in function IIMGENC1fxns->process()

Richard12023
Intellectual 300 points

Hi

     We do jpeg encoding in dsp, we feed YUV from arm through dsplink and got the jpeg picture back as same as dsplink demo scale does. But we found IIMGENC1fxns->process() will block forever after encoding for a while. If we start dm6446 from dsp-boot mode, our jpeg encode demo works well. We think we doesn't do the right thing in arm-boot mode.

    After that, we do two simple dsp demo:

  • dsp-boot mode, it read one frame of YUV from file via CCS and encode it to jpeg in a while() loop       // OK
  • arm-boot mode, it stops in while(1) at the beginning of main(), read one yuv from file via CCS and encode it in loop   // Block in IIMGENC1fxns->process() after some while

    I have following questions:

  • Our demo code is ported from the demo in sprc343, deos there any different usage of sprc343 between dsp-boot mode and arm-boot mode?
  • Does dsplink effect jpeg encoding? because if we choose dsp-boot mode, our jpeg encode demo doesn't  config/init/use any dsplink features
  • does there any "simplest config/usage" of jpeg encoding? ex. no-cache, less dependence, less system resource requirement.......

Thanks!

 

  • 0 in reply to Richard12023
    Intellectual 300 points

    Does there any version match problem between sprc343 and dsplink in dm6446?

    we use dsplink_1_30_08_02 and dm6446_jpegenc_2_00_002_production

  • 0 in reply to Richard12023
    TI__Expert 4930 points

    Hello,

    I am not aware of the sprc343 package and I will  not be able to answer the questions related to JPEG demo. But I can answer the questions related to DSPLink.

    DSPLink does the following in host boot mode:

    1) In PROC_attach function, DSPLink powers up the DSP and puts it in reset state

    2) IN PROC_start, release DSP from reset and start execution of the DSP code

    Your observation is that the demo hangs after a while in host boot mode. DSPLink has no effect on the logic/code running on DSP. The only effect that it can potentially have is if PROC_attach leaves the DSP in an incorrect state (from power transition point of view) which could cause affect the codec run.

    DSPLink 1.30.08.02 is a very old version of DSPLink. There have been many fixes in the power related code since then.  Is there any reason you are on that version? You could try using the newer version of DSPLink available at http://software-dl.ti.com/dsps/dsps_public_sw/DSPLink/index.html

    After the hang, have you tried debugging it further using CCS?

    Deepali

  • 0 in reply to Deepali Uppal
    Prodigy 80 points

    Deepali Uppal said:

    DSPLink 1.30.08.02 is a very old version of DSPLink. There have been many fixes in the power related code since then.  Is there any reason you are on that version? You could try using the newer version of DSPLink available at http://software-dl.ti.com/dsps/dsps_public_sw/DSPLink/index.html

    hi, I am a new learner on Dm6446, and I also have the same problem as Richard.

    I want to know something about Dsklink update:

    Whether it will take a lot of work to update the DSPLINK ?  Do I need to update/modify the DVSDK as well if I update the DSPlink from one version to anther in an existed project? E.g., if I update the DSPLINK from Ver. 1.3 to Ver1.6, whether it will cost me considerable workload or maybe bring me some unpredictable trouble.

     

    Deepali Uppal said:

    After the hang, have you tried debugging it further using CCS?

    The program crashed in "IIMGENC1fxns->process" by invoking the “abort()” function on DSP side. I have also posted a similar question on this topic. You can find it at: http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/99/t/42894.aspx

    Thanks,

    Meisi

     

  • 0 in reply to xiaoming lv
    TI__Expert 4930 points

    Meisi,

    There is a lot of change between Ver 1.3 and Ver 1.6. Plugging 1.6 in a a DVSDK which supports 1.3 will not work. Please update to the DVSDK release which supports DSPLink 1.6

    As I suggested earlier, can you update to the newer version and check if you continue to see the problem?

    Deepali