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

WinEC7 Kernel Crash in Driver loading after Device manager in OMAP4430

Prashant Agrawal
Prodigy 215 points

Hi ,

 I am able to build the Debug Build Image for WinEC7(OMAP4430) and I have a crash in kernel after loading the pm.dll.

Log messages which i am getting are:

PID:00400002 TID:00920006 -OEMIoControl(rc = 1)
PID:00400002 TID:00920006 InitializePMExtension: Can't find 'PmExtPath' key.
PID:00400002 TID:00920006 OSAXST1: >>> Loading Module 'ccfgsvc.dll' (0xC040B1F8) at address 0xEEB10000-0xEEB3D000 in Process 'NK.EXE' (0x90611AD0)
PID:00400002 TID:00920006 DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\MUsbOtg\DllName) returned 2
PID:00400002 TID:00920006 DEVICE!I_ActivateDeviceEx: can't find all required activation values in 'Drivers\BuiltIn\MUsbOtg'
PID:00400002 TID:00920006 DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\FlashDisk\DllNamPID:00400002 TID:00920006
PID:00400002 TID:00920006
e) returned 2
PID:00400002 TID:00920006 DEVICE!I_ActivateDeviceEx: can't find all required activation values in 'Drivers\BuiltIn\FlashDisk'
PID:00400002 TID:00500002

After this it is going to IdleState and not launching the shell.

Any help is appreciated.

  • 0
    Genius 5120 points

    Hi,

    Since you are porting the EVM 3530 Copmact 7 BSP to OMAP4430, I don't know whether that can be done or not?

    If it can be done then don't directly jump to drivers. First make sure the OAL comes up with tiny kernel. Then you can add one driver after another and test them.

    Regards,

    GSR

  • 0 in reply to 1258021
    Prodigy 215 points

    Hi,

    OAL implementation is completed so it is going to kernel Init and in kernel init it is calling the Filesystem, Device Manager ,Power Module so till there its working fine.

    After that its started Loading the driver so then its crashing.