• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 1603 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.

Linux/PROCESSOR-SDK-DRA7X: Folder structure mismatch in v3.00.00

abhijeet dixit
Prodigy 100 points
Part Number: PROCESSOR-SDK-DRA7X


Tool/software: Linux

Hi all,

I have installed the Vision SDK v3.00.00, released recently, on a 64 bit Ubuntu 14.04 LTS. For building the linux, I am following the instructions given in VisionSDK_Linux_UserGuide.pdf. 

Herein, the instruction to clone ipumm mentions the destination folder as $INSTALL_DIR/ti_components/algorithms_codecs but, in the folder structure, there is no folder by this name.However, there are two separate folders as $INSTALL_DIR/ti_components/algorithms and $INSTALL_DIR/ti_components/codecs. 

In the previous Vision SDK releases, the mentioned folder was present.

Any help regarding how to proceed with the ipumm cloning in Vision SDK 3.00.00 will be appreciated

  • 0
    TI__Mastermind 42515 points
    Hi,

    It should be under "$INSTALL_DIR/ti_components/codecs".

    I am just not sure if the correct version is checked out, because the "git checkout" command is the same as in VisionSDK_Linux_UserGuide.pdf in older VisionSDK version. I will ping VisionSDK experts to comment that.

    Regards,
    Yordan
  • 0 in reply to Yordan Kamenov
    Prodigy 100 points
    Hi yordan,

    I have cloned the ipumm in "$INSTALL_DIR/ti_components/codecs" as you mentioned. The build seems to be going through. Will be able to get back on working once the system is up and IPUMM is fine.
    However, while preparing the SD card with the image. There seems to be a mismatch in the path of $BOOT_DIR mentioned in UserGuide (section 4.2) and the path taken by mksdboot.sh
    The UserGuide mentions the path of $BOOT_DIR as <$INSTALL_DIR/vision_sdk/binaries/apps/<MAKECONFIG>/hlos/linux> and the mksdboot.sh script is appending </hlos/linux/boot> to $BOOT_DIR and then searching for MLO, uenv, fs and u-boot. However, the appending of </hlos/linux/boot> to $BOOT_DIR by mksdboot.sh is making the final path as <$INSTALL_DIR/vision_sdk/binaries/apps/<MAKECONFIG>/hlos/linux/hlos/linux/boot> which, it seems, has a redundant <hlos/linux> section.
    Currently, I have edited the $BOOT_DIR accordingly and managed to get the SD card.
    It will be helpful if you are able to check and let me know if this $BOOT_DIR change is correct or I have missed something in the build procedure.

    Regards,
    Abhijeet
  • 0 in reply to abhijeet dixit
    Prodigy 100 points
    Further, when I tried to boot with the SD card, which I created using the above mentioned changes, the dtb file, which was mentioned in uenv.txt was not present in the /boot of targetfs.
    1. Is this expected behaviour?
    2. In the previous vision SDKs, the dts file was a link to a deviceTree file present in the same folder (/boot). Are we supposed to create that link manually? If yes, to which deviceTree file should the dtb point?
    3. If no manual link needs to be created, does uenv.txt needs to be modified to take some other dtb? If so, which one?
    4. Does both of the above errors point to something missing in the build/card preparation procedure?

    Regards,
    Abhijeet
  • 0 in reply to abhijeet dixit
    TI__Genius 13395 points

    Hi

    Sorry, for these documentaion errors

    IPUMM should be installed im $INSTALL_DIR/ti_components/codecs folder

    Pls edit the $BOOT_DIR accordingly and managed to get the SD card

    WRT the dts file, did you apply the kernel paches as described in the Userguide?

    regrads, Shiju

  • 0 in reply to Shiju Sivasankaran
    TI__Expert 3970 points

    Abhijeet 

    The boot folder changes are correct.

    Can you please tell me the contents of boot folder and its size. 

    I assume you have tar the filesystem after building .

    Regards

    Chetan.M