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.

DRA77P: Flashing programs for DRA742 and DRA77p

Part Number: DRA77P
Other Parts Discussed in Thread: CCSTUDIO

Hi,

I wanted to know if there would be any conflicts when flashing programs for DRA74x in DRA77P.

We are using the processor-sdk-rtos-automotive-dra7xx-evm-04.03.00.05. Would there be any conflicts in memory during the flashing process of the programs included in the sdk ? What are the necessary steps to be taken if at all any conflicts are found ?

Regards,

Padmesh

  • Hi,

    What is the flashing tool you are using?

    Regards,
    Rishabh
  • Hi Rishabh,

    Code composer studio v7.4 is used

    Regards,
    Padmesh
  • Padmesh,

    Are you using qspi flash writer or nor flash writer?

    Regards,
    Rishabh
  • Hi Rishabh,

    I do not use any flash writers, what I use is the CCStudio to load the xem4 executables.
  • Will the executable that are able to be loaded in DRA74x be able to run in the DRA77p variant ?
  • Hi Padmesh,

    For CCS loading you will need a different target configuration.
    Binaries are also different for DRA74x and DRA77p.
    Hope this helps.

    Regards,
    Rishabh
  • Hi Rishabh,

    From where will I be able to get the binaries for DRA77p. Currently I am using processor-sdk-rtos-automotive-dra7xx-evm-04.03.00.05 from where I build csl projects for DRA74x.
    What do I do to configure binaries for DRA77p ?

    Regards,
    Padmesh
  • Padmesh,

    Can you check the release notes to see if DRA77p is supported and look at documentation on how to build the same.
    I have asked the processor-sdk-rtos-automotive-dra7xx expert for further help.

    Regards,
    Rishabh
  • Hi Padmesh,

    As Rishabh mentions, please look at the release notes for information on supported platforms: http://processors.wiki.ti.com/index.php/Processor_SDK_RTOS_Automotive_Release_Notes#Supported_Platforms.  Note that DRA77p is not supported in this SDK.

    Thanks,
    Stephen

  • Hi Stephen,

    What necessary steps do I need to follow to achieve the task of building binaries for DRA77P

    Regards,
    Padmesh
  • Hi Padmesh,

    Adding another platform to PDK will require a significant effort and something we won't be able to support. I can describe what is needed at a high level, but by no means will this be a comprehensive guide.

    First challenge is just to get the various libraries building for the device. This would include defining something along the lines of an SOC=dra7px and BOARD=evmDRA7Px. You could grep through the modules of interest and look for references to either TDA2Px or AM574x. These devices have most similarity to DRA77P. For any soc sub-directories in the component of interest you must also define something similarly for dra7px. If you make all of the necessary updates here, in the various makefiles definitions,and source file preprocessor (i.e. SOC_DRA7Px) then for the most part you should be good to go for the compilation.

    Then there are going to be device- and board-specific updates needed in the Board library. Pad configuration is particularly tricky and will need to be addressed in the library similar to the other DRA7xx devices. You will need to refer to the device data sheet for the IODelay configuration entries which must be included. There will be various board I/O expanders and mux selections to expose the signals to the necessary components (e.g. Ethernet PHY, Audio Codec, etc.). You will have to evaluate the UART instance for the console, I2C instance used to configure various expanders, MMCSD GPIO pin, and whatever else is needed for your application.

    If SBL is needed, you will also need to need to port TDA2Px-specific code to build for DRA7Px. Note that the SBL is designed for TDAxxx family of devices which we have enabled DRA7xx on top of, but there are differences in various CPU and PLL frequencies in a given OPP between the two families, so this must be evaluated and modified based on the data sheet for the device.

    Before going through this trouble, it would be helpful to understand your application and what it is you are trying to do. Maybe there is a workaround or shortcut we can take if you need to enable something on DRA77P.

    Thanks,
    Stephen
  • Hi Padmesh,

    What is the driver you want to use?
    Maybe you can use pdk from Processor SDK Vision which has been validated on TDA2Px which is a variant of DRA77P.

    Regards,
    Rishabh
  • Hi Rishabh,

    A custom board is being built with DRA77P Processor. As part of the board bring up process, clock and other peripherals are to be verified by using binary examples like Uart, emac,etc. to make sure if they are working. These examples which I mentioned where available for DRA 74x and I was able to visualise them. I was looking if any such things were possible in this case.
    If at all binaries are not possible to be built, can I verify the working of peripherals using xds 200 debugger and CCStudio. Sorry if I am wrong, I am new to this knowledge.

    Regards,
    Padmesh
  • Thanks Stephen for giving me an insight. Let me see if these are possible.

    Regards,
    Padmesh
  • Hi Padmesh,

    Processor SDK Vision and Processor SDK RTOS Automotive are similar but two different software offerings from TI.
    The former is mainly for TDA parts and latter is for DRA parts.
    Unfortunately DRA77P is not supported by Processor SDK RTOS Automotive.
    So either you can port those particular examples/drivers for DRA77P which is not trivial as Stephen explained.
    Or you can use Processor SDK Vision but that might not support all drivers present in DRA package.
    It is also possible that Processor SDK Vision has different software offering for a particular peripheral. E.g. For ethernet, Processor SDK Vision uses NDK/NSP instead of EMAC LLD.
    You need to decide depending upon the end use case and not just the board bring up.
    In case your objective is only board bring up then I would suggest you to port and run Proceesor SDK Vision as that will be easier.

    Also XDS200 is just a debugger used to load code and CCS is just an IDE. They are used to run the executable which has to be built from the applicable code. Hence you cannot verify any peripheral using just CCS or JTAG.

    Regards,
    Rishabh
  • Hi,

    I haven't heard back from you, I'm assuming you were able to resolve your issue.
    If not, just post a reply below (or create a new thread if the thread has locked due to time-out).

    Regards,
    Rishabh
  • Hi,

    I am still looking into it and thanks for the insight. I'll update as the custom board is bring up.

    Regards,
    Padmesh
  • Hi Padmesh,

    I am closing this thread for now.
    You can post a reply when you are done with bring up.

    Regards,
    Rishabh
  • Hi,

    I haven't heard back from you, I'm assuming you were able to resolve your issue.
    If not, just post a reply below (or create a new thread if the thread has locked due to time-out).

    Regards,
    Rishabh