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.

  • TI Thinks Resolved

DRA72XEVM: Disabling DSS during kernel load leads to an error when apps.out is executed and usecase do not execute

Intellectual 480 points

Replies: 4

Views: 146

Part Number: DRA72XEVM

Hi TI Forum,

We are trying to enable Reverse View Camera usecase on our custom board having TDA2xx SoC. We are using Vision SDK 3.0.7

According to the Steps as specified in VisionSDK_Linux_UserGuide.pdf - > 3.5 - Early M4 based chains for VSDK-Linux builds

enabled the EARLY_USECASE_ENABLE to "yes" in the below cfg.mk file

vision_sdk/apps/configs/tda2xx_evm_linux_all/cfg.mk

#Enable/Disable early use-cases (yes/no)
EARLY_USECASE_ENABLE=yes

And also enabled early_capture_late_weston usecase in uc_cfg.mk file

To ensure the Reverse camera gets started early within 5-6 seconds, we are loading IPU2 core during uboot.We disabled the pheripherals used by ipu core in dts as per the document :

DISABLE_COMPLETE(vip1);
DISABLE_COMPLETE(dss);

                                 But with dss disabled, it leads to an error when apps.out is executed.In we enable dss in kernel the displays goes off and shows "out of range" signal.

Below is the Error message that appears after running apps.out: The usecase will not run as the execution is stuck in System_init(chains_main.)

### 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>.

Calling System_init
[HOST] OSA: MEM: 0: Mapped 0xa0100000 to 0xb6000000 of size 0x00100000
[HOST] OSA: MEM: 1: Mapped 0x84203000 to 0xa3400000 of size 0x12c00NET: Registered protocol family 41
000
[HOST] OSA: MEM: 2: Mapped 0xa0200000 to 0xb620f000 of size 0x00040000
[HOST] OSA: MEM: 3: Mapped 0xa02c0000 to 0xb624f000 of size 0x00080000
[HOST] OSA: MEM: 4: Mapped 0x00000000 to 0x00000000 of size 0x00000000

This is the dts file with late attach configurations:

4212.dra7-evm-infoadas.txt

  • I dont think this is caused by enabling / disabling DSS, and it looks more like a early boot issue. Let us look at the logs and get back to you

  • In reply to Subhajit Paul:

    Hi Sudhi,

    Can you share your dtb used for this usecase?

    Thanks

    RamPrasad

  • In reply to Ramprasad:

    Hi RamPrasad,

    PFA the dtb file we are using for this scenario....!! As .dtb file attachment was not happening, I have changes the extension of dtb to .txt. So could you please change the extension to .dtb when you try opening it..

    Thanks & Regards,

    Sudhi

    7762.dra7-evm-infoadas.txt

  • In reply to Sudhi Sudhi:

    Hi Sudhi,

    I regenerated dts file from dts and compared with TI's default dra-evm-infoadas.dtb(with late-attach patches applied).

    I am not seeing late-attach attributes for timers, mailbox, IPU1, IPu2, and DSP2 etc. 

    TI has added only one usecase with EARLY_USECASE_ENABLE=yes(early_capture_lateweston) and these nodes need to be late-attached for the usecase.

    Can you check once?

    Thanks

    RamPrasad

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.