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

TDA2P-ABZ: VisionSDK 3.7.0 - demo apps cannot work with TDA2P EVM.

Tomotaroh Kohro
Genius 17265 points
Part Number: TDA2P-ABZ

Hello support team.

 

We are confirming Linux on TDA2Px EVM.

Then we built original software according to VisionSDK Linux User Guide.

> make linux

> make linux_install

> make -s -j depend

> make -s -j

 

We tried to run demo apps at TDA2P EVM (w/ Fusion board).

This environment, we has already confirmed by RTOS version demo apps.

However, we need to confirm it with Linux version.

Then we tested with TDA2Px EVM with Fusion board.

 

After login the linux system, we tried to run demo apps

> cd /opt/vision_sdk

> ./visionsdk_load.sh.

 

This vision_sdk_load.h called ./memcache_load.sh which executed insmod command for two module. one is ./bin/memcache.ko and and other is ./bin/cmemk.ko.

However, cmemk.ko is not under ./bin.(/opt/visionsdk/bin absolute path).

it is in /opt/visionsdk.

it is O.K. we can move it to ./bin.

 

again we tried to run ./vision_sdk_load.sh called disableDssInterruptsOnA15.sh which uses “omapconf” command.

However, several error happened.

please find the below error.

 

First line is “crossbar=`omapconf dump crossbar irq mpu | grep DISPC | awk -F" " '{ print $4}'`”.

It may happed error.

Because I tried “omapconf dump crossbar irq mpu” command manually.

However, it happened error. “mpu” parameter of omapconf generates error message. In fact, if only “omapconf dump crossbar irq” is executed , it works fine.

Anyway, I want to get your advice “how to fix this issue”.

 

======================================================================

./vision_sdk_load.sh

[   90.927658] DMA: Module install successful, device major num = 241

[   90.934143] DRV: Module install successful

[   90.956941] CMEMK module: reference Linux version 4.4.84

[   90.962968] cmemk initialized

Error: I2C Read failed

Error: I2C Read failed

Error: I2C Read failed

./disableDssInterruptsOnA15.sh: line 11: COMMANDS: command not found

./disableDssInterruptsOnA15.sh: line 12: COMMANDS: command not found

./disableDssInterruptsOnA15.sh: line 13: COMMANDS: command not found

./disableDssInterruptsOnA15.sh: line 14: COMMANDS: command not found

./disableDssInterruptsOnA15.sh: line 15: COMMANDS: command not found

./disableDssInterruptsOnA15.sh: line 16: COMMANDS: command not found

./disableDssInterruptsOnA15.sh: line 17: COMMANDS: command not found

./disableDssInterruptsOnA15.sh: line 18: COMMANDS: command not found

./disableDssInterruptsOnA15.sh: line 19: COMMANDS: command not found

updated value is

 

COMMANDS

              ### WARNING ###: use the following [read | write | set bit | clear bit | dump] commands at your own risk!

              No address check done, may generate:

              - bus error (invalid or not accessible <physical address>,

              - platform crash/hang (bad <value>).

                 Read any OMAP memory address (register), given its <physical address> or <name> as listed in TRM.

                 Write <value> at any OMAP memory address (register), given its <physical address> or <name> as listed in TRM.

                 Set bit at <position> into any OMAP memory address (register), given its <physical address> or <name> as listed in TRM.

                 Clear bit at <position> into any OMAP memory address (register), given its <physical address> or <name> as listed in TRM.

                 Dump a range of OMAP memory addresses, from <start address> to <end address>.

                 Note all addresses within given range must be valid and accessible.

 

              ### WARNING ###: use the following I2C [read | write] commands at your own risk!

              No address check done, may generate:

              - I2C bus error (invalid or not accessible <physical address>,

              - platform crash/hang (bad <value>).

                 Read I2C register at address <addr> from I2C chip at <chip-addr> on I2C <bus>.

                 Write <value> in I2C register at address <addr> from I2C chip at <chip-addr> on I2C <bus>.

======================================================================

 

Best Regards

KORO

 

  • 0
    TI__Mastermind 42515 points

    Hi Koro-san,

    Do you have any problems running the usecases under Linux?

    The errors you get when run vision_sdk_load.sh can be ignored. In chapter "4.3 Run demos" in VisionSDK_Linux_UserGuide.pdf there is following note:

    IMPORTANT NOTE: Some kernel logs and errors failure message will appear while running “source ./vision_sdk_load.sh”, this is caused when DSS interrupts are disabled on A15 using omapconf write, and these errors need be ignored as it would not harm the execution

    Regards,

    Yordan

  • 0 in reply to Yordan Kamenov
    TI__Genius 17265 points

    Hello Yordan-san.

    Thanks a lot for your quick reply.

    I see. I understood.

    Currently, we could not execute demo apps at Linux on TDA2P EVM.

    Therefore, I thought this issue may be one of the causes.

     

    Our demo environment, TDA2P EVM has fusion board which is connected with OV10640-IMI camera sensors. (4 sensors).

    Then the below we conducted.

    - setting -> Display : HDMI(FHD)

    - setting -> Sensor : OV10640-IMI

    - RUN -> 5. ISS Usecase, (TDA2Px ONLY) -> 1. 1CH ISS Capture + ISP + DISPLAY.

     

    However, it could not work with the below log.

    Even though “Sensor OV10640-IMI is not support for this usecase” is displayed, but I am not sure the reason why DSS side happened error.

    Also I would like to know which demo we can executed at TDA2P EVM with Linux.

     

    [HOST] [HOST ]   137.519856 s: Entered Chains_issIspSimcop_Display

    [HOST] [HOST ]   137.519886 s: Sensor OV10640-IMI is not support for this usecase

    [HOST] [IPU2 ]   137.520069 s: ISSCAPTURE: Create in progress !!!

    [HOST] [IPU2 ]   137.595284 s: ISSCAPTURE: Create Done !!!

    [HOST] [IPU2 ]   137.595711 s: ISSM2MISP: Create in progress !!!

    [HOST] [IPU2 ]   137.655645 s: ISSM2MISP: Create Done !!!

    [HOST] [IPU2 ]   137.656103 s: ALGORITHM: Create in progress (algId = 3) !!!

    [HOST] [IPU2 ]   137.685841 s: ALGORITHM: Create Done (algId = 3) !!!

    [HOST] [IPU2 ]   137.686329 s: ISSM2MSIMCOP: Create in progress !!!

    [HOST] [IPU2 ]   137.761636 s: UTILS: DMA: Allocated CH (TCC) = 32 (32)

    [HOST] [IPU2 ]   137.761758 s: UTILS: DMA: 0 of 1: Allocated PaRAM = 32 (0x63304800)

    [HOST] [IPU2 ]   137.763252 s: ISSM2MSIMCOP: Create Done !!!

    [HOST] [IPU2 ]   137.763649 s: DISPLAY: Create in progress !!!

    [HOST] [IPU2 ]   137.763923 s: dispcore/src/vpscore_dss.c @ Line 476:

    [HOST] [IPU2 ]   137.764076 s: Display Controller registration failed for dss core instance 0

    [HOST] [IPU2 ]   137.764198 s: dispdrv/src/vpsdrv_displayCore.c @ Line 411:

    [HOST] [IPU2 ]   137.764289 s: Dss core open failed!!

    [HOST] [IPU2 ]   137.764350 s: dispdrv/src/vpsdrv_displayApi.c @ Line 348:

    [HOST] [IPU2 ]   137.764442 s: Core open failed!!

    [HOST] [IPU2 ]   137.764533 s: Assertion @ Line: 386 in displayLink_drv.c: pObj->displayHndl != NULL : failed !!!

     

    Best Regards

    KORO

     

  • 0 in reply to Tomotaroh Kohro
    TI__Genius 17265 points

    Hello Support team.


    I would like to know this reply

    Because our customer cannot start the evaluation.

    Br

    KORO

  • 0 in reply to Tomotaroh Kohro
    TI__Genius 15985 points

    Hi,

    Can you share the steps you have performed while building and preparing the sd card.

    Common mistake which max customer does is they do not change the name on dts file in uenv.txt file available boot partition of sd card.

    Can you confirm that its been changes to proper dts file name as per linux userguide section 3.1.2.

    Can you also try to run any other usecase like single camera display usecase or null Source display usecase.

    And check whether that works or not.

    Regards,

    Anuj

  • 0 in reply to Anuj Gupta
    TI__Genius 17265 points

    Hello Anuj-san

    Thanks a lot for your reply.

    My build actions are the below:

    After full clean installation according to VisionSDK_Linux_UserGuide.pdf.

    (1) Change Rules.make

    MAKECONFIG?=tda2px_evm_linux_all

    MAKEAPPNAME?=apps

    (1) build

    make linux

    make linuc_install

    make -s -j depend

    make -s -j

    (2) Make root filesystem

    cd $INSTALL_DIR/ti_components/os_tools/linux/targetfs

    tar cvf tisdk-rootfs-image-dra7xx-evm.tar.xz ./*

    mv ./tisdk-rootfs-image-dra7xx-evm.tar.xz $INSTALL_DIR/vision_sdk/binaries/$(MAKEAPPNAME)/<MAKECONFIG>/hlos/linux/boot 

    (3) Modify uenv.txt

    cd $INSTALL_DIR/vision_sdk/binaries/$(MAKEAPPNAME)/<MAKECONFIG>/hlos/linux/boot

    vi uenv.txt

    fdtfile=dra76-evm-infoadas.dtb

    (4) SD card

    cd $INSTALL_DIR/vision_sdk/build

    sudo ./hlos/scripts/linux/mksdboot.sh --device /dev/sdb --appname apps --makeconfig tda2px_evm_linux_all

    (5) Booting TDA2P EVM with this SD card

    (6) DEMO execute

    login at "root"

    cd /opt/vision_sdk

    source ./vision_sdk_load.sh.

    ./apps.out

    (7) Menu of demo

    s (System Setting) -> 1 (Display Setting) -> 2 (HDMI 1080P60)

    s (System Setting) -> 2 (Capture Setting) -> 4 (OV10640 IMI Sensor 1280x720 ....

    5 (ISS Usecases. (TDA2Px ONLY)) -> 1 (1CH ISS Capture + ISP + DISPLAY)

    then I mentioned error happens.

    I could not find "null Source display usecase."

    Best Regards

    KORO

  • 0 in reply to Tomotaroh Kohro
    TI__Genius 17265 points

    Hello Anuj-san

    Thanks a lot for your sending e-mail.

    I have confirmed it works fine.

    This ticket can be closed.

    Again thanks a lot.

    Br

    KORO