TDA2EG-17: TDA2EGBDQCBDQ1

Hi,

Can I know what are the steps followed after the installation of the SDK? (Please mention all the steps)

Thanks

Gaviraju

Hi, thanks for reply.

Fristly, change the Rules.make, let MAKECONFIG= tda2ex_17x17_evm_linux_all

Next execute the command

• make linux
• make linux_install
• make -s -j depend
• make -s -j

Then tar the file system and keep it in $INSTALL_DIR/vision_sdk/binaries/$(MAKEAPPNAME)/<MAKECONFIG>/hlos/linux/boot folder

and change the uenv.txt  fdtfile=dra7-evm-infoadas.dtb -> fdtfile= dra72-evm-infoada.dtb for tda2ex_17x17

Finally format sd card, then execute this command 

sudo ./hlos/scripts/linux/mksdboot.sh --device /dev/<parent_device_name> --appname <MAKEAPPNAME> --makeconfig <MAKECONFIG>

After these steps, i insert the sd card, connect the serial, power on the board, i can say nothing in the MobaXterm.

By the way, i found that, maybe i need to modify the sdram_init function,

So another question, if DDR is not properly initialized, will the serial port does not output any information?

Thanks

Hi,

fdtfile= dra72-evm-infoada.dtb for tda2ex_17x17, this is not correct & it should be fdtfile= dra71-evm-infoada.dtb

>>> By the way, i found that, maybe i need to modify the sdram_init function, So another question, if DDR is not properly initialized, will the serial port does not output any information?

Are you trying with EVM board or custom board? because we are not doing any code changes after the installation of the SDK & have done any code changes in the SDK?

Thanks

Gaviraju

Hi,

>>>fdtfile= dra72-evm-infoada.dtb for tda2ex_17x17, this is not correct & it should be fdtfile= dra71-evm-infoada.dtb

OK, i will change and try again. but in the "VisionSDK_Linux_UserGuide.pdf" it says "fdtfile= dra72-evm-infoada.dtb for tda2ex_17x17"

>>>Are you trying with EVM board or custom board? because we are not doing any code changes after the installation of the SDK & have done any code changes in the SDK?

I am trying with custom board. our board use the "M25" and "L25" as serial debugging ports and has only 1GB of DDR.

Thanks

Hi,

I'm suspecting that is an typo error in the use-guide because in the config file: vision_sdk/apps/configs/tda2ex_17x17_evm_linux_all/cfg.mk, it's set as below.

Please mention all the steps & I'm expecting all the steps like the below thread.

Thanks

Gaviraju

Hi,

I follow these steps. 

• download gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf.tar.xz under $INSTALL_DIR/ti_components/os_tools/linux/arm/
• $> cd $INSTALL_DIR/ti_components/os_tools/linux/arm
• $> tar –xvf gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf.tar.xz
• sudo apt-get install Ssh, corkscrew, gawk, uname, sed, u-boot-tools, dos2unix, dtrx, git, lib32z1 lib32ncurses5 lib32bz2-1.0 libc6:i386 libc6-i386 libstdc++6:i386 libncurses5:i386 libz1:i386 libc6-dev-i386 device-tree-compiler mono-complete lzop. 

uname, dtrx, lib32ncurses5, lib32bz2-1.0 are not in the source of the ubuntu 20.04. so it can not be installed and some related tools has beed installed. however. in the following building steps, it did not reported an error.

• $> ./PROCESSOR_SDK_VISION_XX_XX_XX_XX_setuplinux.bin
• $>vi /home/<username>/.gitconfig
• [core] gitproxy = none for ti.com gitproxy = /home/<username>/git-proxy.sh
• $>vi /home/<username>/git-proxy.sh
• exec /usr/bin/corkscrew proxyle01.ext.ti.com 80 $*
• $> git config --list
• core.gitproxy=none for ti.com
• core.gitproxy=/home/<username>/git–proxy.sh
• $> ./hlos/scripts/linux/setup_linux.sh
• Download Linux file system tisdk-rootfs-image-dra7xx-evm_vsdk_3_8.tar.xz from ti.com and keep under following directory $INSTALL_DIR/ti_components/os_tools/linux/targetfs
• cd $INSTALL_DIR/ti_components/os_tools/linux/targetfs
• $> chmod 777 ../targetfs
• $> tar xf tisdk-rootfs-image-dra7xx-evm_vsdk_3_8.tar.xz
• $> cd $INSTALL_DIR/ti_components/codecs
• $> git clone git://git.ti.com/ivimm/ipumm.git
• $> cd ipumm/
• $> git checkout -b ipumm_dev 365a9a5402c829710b7e1eefec07d26b3c94c3a9
• $> Install codec engine ver codec_engine_3_24_00_08 in the following folder <INSTALL_DIR>/ti_components/codecs/
• download FC version framework_components_3_40_02_07 and installed in the following folder <INSTALL_DIR>/ti_components/codecs/
• $> cd $INSTALL_DIR/ti_components/os_tools/linux/kernel
• $> git clone git://git.ti.com/sdo-emu/dsptop.git
• $> cd dsptop/
• $> git checkout -b dsptop_dev 0aedcab
• $> cd $INSTALL_DIR/ti_components/os_tools/linux/kernel
• $> git clone git://git.ti.com/sdo-emu/gdbc6x.git
• $> cd gdbc6x/
• $> git checkout -b gdbc6x_dev df0b8f6

The next steps are all the ones I mentioned before

Fristly, change the Rules.make, let MAKECONFIG= tda2ex_17x17_evm_linux_all

Next execute the command

• make linux
• make linux_install
• make -s -j depend
• make -s -j

Then tar the file system and keep it in $INSTALL_DIR/vision_sdk/binaries/$(MAKEAPPNAME)/<MAKECONFIG>/hlos/linux/boot folder

and change the uenv.txt  fdtfile=dra7-evm-infoadas.dtb -> fdtfile= dra71-evm-infoada.dtb for tda2ex_17x17

Finally format sd card, then execute this command 

sudo ./hlos/scripts/linux/mksdboot.sh --device /dev/<parent_device_name> --appname <MAKEAPPNAME> --makeconfig <MAKECONFIG>

that's all,  thanks

in addtion, i can not found "opencl_fs_patches.tar.gz" in the $INSTALL_DIR/ti_components/os_tools/linux/kernel/linux-kernel-addon/fs-patches. Could you find the problem in this information?

Hi,

The OpenCL & OpenCV is deprecated from the vision SDK so we are not supporting any query related to OpenCV & OpenCL.

Why are you following the above steps? because these steps are not mentioned in the Linux user-guide.

Where is the U-boot source code? have you cloned the U-boot code?

The below steps are mentioned in the Linux user-guide to clone the Kernel & U-boot, SGX, CMEM

OR

Run the script from <INSTALL_DIR>/vision_sdk/build Direcrory to clone Kernel, U-boot, SGX, Cmem
$> ./hlos/scripts/linux/setup_linux.sh

Thanks

Gaviraju

Hi，

Actually in the  Linux user-guide. PROCESSOR_SDK_VISION_03_08_00_00\vision_sdk\docs\Linux\VisionSDK_Linux_UserGuide.pdf on page 8.

picture.xlsx

Yes, i have cloned the uboot code by the method  $> ./hlos/scripts/linux/setup_linux.sh which had mentiioned above. You can see in the next picture.

thanks

Hi,

Yes, you followed all the steps but unfortunately not able to see any logs on the console, so I will check with the team & let you know asap.

Thanks

Gaviraju

Hi,

OK, Thanks for your reply and waiting for your message！

Hi Ye Yao,

You have to make changes to u-boot and kernel for the custom board. Default u-boot and Kernel won't work on custom board.
You are using a different serial port compared to TI EVM? if so that should be changed first to get some prints on console.

Regards,
Vishal

Hi,

Sorry for reply late. due to a holiday and happy new year!

yeah, i think so, i ready to modify the uboot first.  OK, i will check uart again. currently, our custom board have same serial port with TI EVM.

So I wonder why the serial port doesn't have any information.

Thanks

Also you mentioned in your initial post that some SD card worked

i think the board, the configutation, the hardware device and uart connection is right. because i use another sd card it can boot correctly.

What image was there in this SD card? did the same board work with this SD card?

Hi,

By modifying the uboot code, I can see some information in the serial port. It says "SDRAM: identified size not same as expected size identified: 0 expected: 40000000".

So, next step, i will modify DDR3 initialization code. By the way, where to download the EMIF configuration tools? 

I found that through my TI account, I cannot log in to this website "cdds.ext.ti.com/.../emxTree.jsp to download the tools.

Could you help me this?

Thanks

Hi,

Please see these links for the TDA2x EMIF Register Configuration Tool:

• PDF: www.ti.com/.../sprac36
• XLS: www.ti.com/.../sprac36

Thanks,
Kevin

Hi,

Sorry for replying late, i have tested some times, all are failed.

It always shows "SDRAM: identified size not same as expected size identified: 0 expected: 40000000".

Our costom board use two “MT41K256M16TW-107AATP” DDR. I follow the document "sprac36e.pdf", fill in some parameters in the "EMIF_RegisterConfig.xlsm" and update the value of register. However, it still ailed.

Can these situation cause the problem?

• I found that the CAS Latency for the parameter "EMIF_REGISTERCONFIG. CONF" is a maximum of 11. But our DDR CAS Latency has a value of 13.
• I fill nothing is the sheet "Step2-BoardDetails", because i think this is the hardware-related parameter.

The following "6740.EMIF_RegisterConfig.zip" shows the configuration.

Thinks

The DDR questions above are being addressed on this thread: e2e.ti.com/.../3602353

Will close this thread and keep the new thread open.

Best regards,
Kevin

HI，

Ok，Thanks