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.

Latest ipc 3.21.00.07 lad_dra7xx server and messageQApp failing

Latest IPC 3.21.00.07 Android applications are not working. Where as old ipc 3.20 Android applications are able to communicate with ipc 3.21 xem4 loaded with late attach feature.

While running lad_dra7xx from Android shell it is throwing an error:

ERROR: Failed to create LAD's working directory! 

It is found that changes are made in to 

-#define LAD_COMMANDFIFO         "/data/local/tmp/LAD/LADCMDS"

-#define LAD_WORKINGDIR          "/data/local/tmp/LAD/"

+#define LAD_COMMANDFIFO         "/data/lad/LAD/LADCMDS"

+#define LAD_WORKINGDIR          "/data/lad/LAD/"

After changing these two lines to old one. lad_dra7xx started running but still messageQApp not able connect to lad server. It throws below error.

Ipc_start: LAD_connect() failed: 4

ProcId (2) must be nonzero and less than 0

Ipc_stop: MessageQ_destroy() failed: -9


Any idea what could be the reason here.

Thanks,

Rabi

  • Rabi,

    Can you show the LAD log?

    To do so, start lad_dra7xx with the logging option:
        % ./lad_dra7xx -l log.txt
    and that should produce a file named log.txt in /data/lad/LAD.

    Rabindra Paikaray said:

    -#define LAD_COMMANDFIFO         "/data/local/tmp/LAD/LADCMDS"

    -#define LAD_WORKINGDIR          "/data/local/tmp/LAD/"

    +#define LAD_COMMANDFIFO         "/data/lad/LAD/LADCMDS"

    +#define LAD_WORKINGDIR          "/data/lad/LAD/"

    Did you rebuild lad_dra7xx after making this change?

    Did you rebuild the Linux apps as well?

    Regards,

    - Rob

  • Hi Rob,

    Could able to make latest lad_dra7xx running and communicating with SLAVE IPU1.

    There are mainly two reasons it was failing .

    1. ERROR: Failed to create LAD's working directory . It is expecting /data/lad/ should exist before lad starts . In our case it was not there. I created manually lad dir under /data  before lad server starts. It started running smoothly.
    2. Again  hit the issue of NAMESERVER_GET_TIMEOUT. Changed from 40000 micro sec to 1000000 microsec (1 sec) . It started communicating with the IPU1 SLAVE and could see messageQApp message sent and received successfully.

    Thanks,

    Rabi