• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 99 subscribers
  • Views 438 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.

dm816x firmware loading issue.

Nithin kumar24
Intellectual 905 points

Hi All,

I'm using DM816X custom board in my project.

Using ADV7182 decoder for CVBS IN.

When I use dm816x_hdvpss.xem3 firmware which is used in DM816X EVM board to load VPSS, I'm getting log like below, and fails to load firmware.

FIRMWARE: Ipc_CONTROLCMD_STARTCALLBACK Error: ProcMgr status 0xffffffff
FIRMWARE: Could not start: -1
notify_send_event failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0

But when I use ti816x_hdvpss.xem3 firmware file in custom board, firmware loads successfully.

When I try to load ti816x_hdvpss.xem3 firmware in DM816X EVM board, I'm getting same above prints in console.

What is the difference between these two firmwares.
Whether from board to board firmware will differ?
In VPSS firmware code any ADV7182 decoder specific configurations to be taken care.

Is there any firmware binary which can be used in EVM board as well as in custom board.

Can any one please help me to solve this issue.

Thanks and Regards,
NIthin








  • 0
    TI__Guru* 80190 points

    Hello,

    Nithin kumar2 said:


    notify_send_event failed! status = 0xfffffff0

    notify_send_event failed! status = 0xfffffff0

    notify_send_event failed! status = 0xfffffff0

    notify_send_event failed! status = 0xfffffff0



    In most of the cases this error means wrong bootargs. Could you post the boot args.

    You are using the same dm816x_hdvpss.xem3 firmware on the EVM and custom board right?

    The same firmware doesn't not work on the EVM but is working on the custom board correct?

    Is this the default firmware?

    Best Regards,

    Margarita

  • 0 in reply to Margarita Gashova
    Intellectual 905 points

    Hi Margarita,

    DM816X EVM bootargs:

    'console=ttyO2,115200n8 rootwait root=/dev/mmcblk0p2 rw mem=364M@0x80000000 324M@0x9F900000 notifyk.vpssm3_sva=0xBF900000 ip=off noinitrd'

    Custom Board bootargs:

    'console=ttyO0,115200n8 rootwait root=/dev/mmcblk0p2 rw mem=256M earlyprink vram=50M ti816xfb.vram=0:16M,1:16M,2:6M ip=off noinitrd notifyk.vpssm3_sva=0xA0000000'

    dm816x_hdvpss.xem3 I'm using in EVM board as well as in Custom board.

    dm816x_hdvpss.xem3 firmware is working in EVM board but not in Custom board.

    Default firmware I'm using.

    When I use ti816x_hdvpss.xem3 firmware which is mentioned in below link,

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

    This firmware worked in Custom board but not in EVM board.

    Thanks and Regards,

    Nithin

  • 0 in reply to Nithin kumar24
    TI__Guru* 80190 points

    Hello,

    Could you change notifyk.vpssm3_sva=0xBF900000.

    Let me know the result.

    Best Regards,

    Margarita

  • 0 in reply to Margarita Gashova
    Intellectual 905 points

    Hi Margarita,

    I changed the  same in boot.scr file and I got below prints in console it stopped in uboot itself.

    300 bytes read
    Running bootscript from MMC/SD to set the ENV...
    ## Executing script at 80900000
    Bad data crc

    but with notifyk.vpssm3_sva=0xA0000000 able to boot.

    Thanks and Regards,

    Nithin

  • 0 in reply to Nithin kumar24
    Genius 3700 points

    Hi Nithin,

          I suppose that you are using the same software release in both boards (same EZSDK version), EVM and Custom board.

    Before loading the firmware you need to be sure that you have run prcm_config_app, that you have loaded the syslink module:

    prcm_config_app s > /dev/null
    rmmod syslink 2>/dev/null || true
    modprobe syslink

    also you have set the correct address for notifyk.vpssm3_sva in your bootargs since this address is used for IPC between Host and MC-HDVPSS (MC_HDVPSS_NOTIFY_MEM in http://processors.wiki.ti.com/index.php/EZSDK_Memory_Map). On EZSDK 5.05.02.01 this address is:

    notifyk.vpssm3_sva=0xBF900000

    If you are booting from SD card, you need to edit the boot.scr however it is not just a text file, it contains a header (CRC) that is added by a tool called mkimage (http://processors.wiki.ti.com/index.php/DM816x_AM389x_PSP_U-Boot#ENV_on_SD_card_using_a_script) so if you want to edit it you need to edit the .txt file and then create the boot.scr to put it on your SD card. 

    -David

  • 0 in reply to David Soto - RidgeRun
    Intellectual 905 points

    Hi All,

    I'm able to use ti816x_hdvpss.xem3 firmware itself to get correct output.

    For using ti816x_hdvpss.xem3 have to use notifyk.vpssm3_sva=0xA0000000 address as mentioned in the user manual, otherwise will not be able to load this firmware.

    Thanks and Regards,

    Nithin