• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 2052 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.

EVM DM8148 & DM385 IPNC RDK

Julia K
Intellectual 280 points
Other Parts Discussed in Thread: DM385

Hi,

We have DM385 IPNC RDK 3.0 kit and EVM DM8148. IPNC application is running OK on DM385 but now I would like to run it on EVM DM8148 (Mistral board).  I have changed Rules.make file of RDK with next configuration:

SYSTEM_PLATFORM  := EVM

IPNC_DEVICE := DM812x

IPNC_FILE_SYSTEM := JFFS2

The code is compiled OK, but I got errors after application is started:

.....

notify_send_event failed! status = 0xfffffff0
VPSS_CORE : Failed to init fvid2 interface,
vpss: probe of vpss failed with error -22
VPSS_CORE : failed to register ti81xx-vpss driver
insmod: error inserting './kermod/vpss.ko': -1 No such device
ti81xxhdmi: Unknown symbol TI81xx_un_register_display_panel (err 0)
ti81xxhdmi: Unknown symbol TI81xx_register_display_panel (err 0)

 [host]

 [host]  ORG 0x46c00524: 0

 [host]  NEW 0x46c00524: 2

 [host]

 [host] Application Start Completed
CMEMK Error: ioctl: no heap available in block 0
CMEM Error: alloCMEMK Error: get_phys: Unable to find phys addr for 0x00000000
cHeap: ioctl CMECMEMK Error: get_phys: get_user_pages() failed: -14
M_IOCALLOCHEAP fCMEMK Error: GETPHYS: Failed to convert virtual 0x0 to physical.
ailed: -1
CMEM Error: getPhys: Failed to get physical address of 0

...

Is it possible to run IPNC application on DM8148 and if yes, what steps should be done?

Thank you in advance

  • 0
    TI__Guru* 80190 points
    Hello,
    For IPNC support, please contact local FAE.
    Best Regards,
    Margarita
  • 0
    TI__Expert 8780 points

    Julia,

    On the EVM, you will also need the VCAM daughter card to interface with imaging sensor. 

    Also, depending upon the VCAM daughter card that you use (rev.B, rev.C...etc); the VCAM daughter card has several muxes on board to enable and choose paths for GPIO, sensor interface etc. Thus to port the ipnc application to the EVM the mux enables and path selection needs to be done carefully.

    We have actually not validated the latest releases on VCAM + EVM setup so I will not be able to help you with specific code reference for the same. But ver.3.0 release was validated on rev.B VCAM board so I think that can be used as a reference.

    If you could review the VCAM board configuration and make the changes specific changes for onboard muxes then the porting should work.

    Please let us know incase my explanation is not clear.

    Thanks,

    Regards

    Rajat

  • 0 in reply to Rajat Sagar
    TI__Genius 11000 points

    From the log it looks like you are getting CMEM errors, can you check if your bootargs is fine?

    You need add this section in bottargs.

    As Rajat said, this was validated on EVM for v3.0

    Regards,

    Raghu