• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 101 subscribers
  • Views 618 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.

Can't open engine

Ofer Zimmerman
Intellectual 995 points
Other Parts Discussed in Thread: OMAP3530

I am running universal_copy example application from Codec Engine. I just compiled the codec, server and application (this order) load .ko files (cmemk, dsplinkk and lpm_omap3530) and execute the application (remote for OMAP3530) it fails with the above error

Ofer

  • 0
    TI__Genius 17205 points

    Does setting CE_DEBUG=3 reveal any more details?

    http://processors.wiki.ti.com/index.php/CE_DEBUG

    Chris

  • 0 in reply to Ofer Zimmerman
    TI__Genius 12025 points
    Ofer, It looks like there was an error from the lpm driver. I see the following in your attached log file. @2,148,688us: [+0 T:0x4096d490 S:0x4096cd2c] ti.sdo.ce.ipc.Power - Power_on> Enter(handle=0x628a4) @2,148,718us: [+2 T:0x4096d490 S:0x4096cd2c] ti.sdo.ce.ipc.Power - Power_on> Opening Local Power Manager for the DSP on /dev/lpm0... @2,482,184us: [+2 T:0x4096d490 S:0x4096cd2c] ti.sdo.ce.ipc.Power - Power_on> Turning on DSP power... @2,482,245us: [+7 T:0x4096d490 S:0x4096cd2c] ti.sdo.ce.ipc.Power - Power_on> Turning on DSP power FAILED @2,482,306us: [+2 T:0x4096d490 S:0x4096cd2c] ti.sdo.ce.ipc.Power - Power_on> return (1) @2,482,367us: [+6 T:0x4096d490 S:0x4096cd4c] OP - Processor_create_d> Power_on failed. Sometimes this happens if a previous program has left the DSP in an unstable state. Power cycle the board to get a clean start. See if this happens on the first run of your program. You can also enable some trace in the lpm driver. Build the driver in debug mode. Then install it with the following option. insmod lpm_omap3530.ko trace=1 The trace statements from the driver will be mixed in with the Codec Engine trace and might be hard to find. Try running it without any Codec Engine trace to find the lpm driver trace more easily. You can also test the lpm driver using the lpmON and lpmOFF utilities. When you run these programs, you should see some trace from the driver. These programs are located in the Codec Engine product at cetools/packages/ti/bios/power/utils/bin/ti_platforms_evm3530/linux/debug lpmON.xv5T lpmOFF.xv5T Just run each one without any arguments. They turn the DSP subsystem on and off. ~ Ramsey
  • 0 in reply to Ramsey
    Intellectual 995 points
    Ramsey, OK I will try, but is this (power) can explain the failare of can not open engine ? (perhaps it is an issue of locatin the engine/name etc?) Ofer
  • 0 in reply to Ofer Zimmerman
    TI__Genius 12025 points
    This may not be the only problem in opening the codec, but it certainly is a problem. From your attached log, I see that once the power function failed, the execution flow starts to unwind. Ultimately, the engine open call fails with a generic "cannot open" error message.
  • 0 in reply to Ofer Zimmerman
    Intellectual 995 points
    Ramsey, You are right lpm fails. I did exactly as you told me and indeed the ON/OFF fails and also during running the application the debug info produced by the lpm_3530.ko says so. Now I read some docs and as I understand I need to wrire a driver that controls the power in addition to the lpm_3530.ko? is that right? Ofer
  • 0 in reply to Ofer Zimmerman
    Intellectual 995 points
    Ramsey, I managed - I put a patch in the one of the sources of the LPM driver to enable a PLL (per another thread suggestion) and it works. Thanks Ofer
  • 0 in reply to Ofer Zimmerman
    TI__Genius 12025 points

    Ofer,

    Well done. Good luck with your project.

    ~ Ramsey

  • 0 in reply to Ofer Zimmerman
    Prodigy 60 points

    Ofer,

    Can you please share your fix? I'm running into same problem. Thanks!

  • 0 in reply to Xin Sun
    Prodigy 190 points

    Ofer, I'm running into the same problem as well.  Would you mind posting the patch you applied or providing a link to the thread that had the solution that worked for you?  It would be greatly appreciated!  Thanks!

    -Donald