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.

AM5728 SDK RTOS command line arguments

Other Parts Discussed in Thread: AM5728

Hi,

   I'm working on AM5728 SDK RTOS for custom diagnostic applications for my project, one my application having command line arguments how i suppose port code in the format of diag apps provided by the SDK. I have gone through the following links there its explained for CCS but i want it in Linux. Please explain for AM5728 processor.

https://e2e.ti.com/support/development_tools/compiler/f/343/t/86832

https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/3263

https://e2e.ti.com/support/embedded/tirtos/f/355/t/36444

  • The RTOS team have been notified. They will respond here.
  • Chethan,

    Could you please explain how your own diag application runs?

    Is it runs under linux command line like: \diag_app argument1 argument2 .....
    or
    It runs like our diagnostic framework: there is a framework loads each individual diag_app into memory then jumps into each diag_app then jump back to run the next diag_app, you want to pass some atguments in this usage case? And how many arguments you want to pass? Also note the framework we have is bare metal, it is not a Linux application.

    Regards, Eric
  • Eric,

      Yes its runs under linux command line ./diag_app arg1 arg2 arg3

    One of our application has SPI protocol and it takes 6 agrs. Yes i understand that MLO is responsible to load all applications into the memory we have no OS.

    Also in order to our SPI application has multiple chip selects are there but in diag apps example none of the apps written with CHIP SELECT applications and library also not providing anything related chip select(API's are not discussed about CS). Please consider this question high priority!!!

    Note: If you have any SPI diag application please share with me it will be usefull!!!!

    BR

    Chethan

  • Chethan,

    If you use application 1 to loads application 2, also passing several arguments to application 2. I think a simple way is to save the arguments in a fixed location in memory by application 1, then application 2 just read that location to get arguments to run. Another way is to save arguments as a structure, let a register (e.g. R0) to point to the start address of the struture, then passing R0 when jump into application 2. 

    The SPI diag is under \board\diag\mcspi, it has calls into spi_open_v1 for AM57x device, in SPI_v1_HWAttrs there is pinMode, either can be 3-pin or 4-pin, where the latter enabled chip select.

    Regards, Eric

  • Eric,

      Sorry first answer didn't clear to me.

    Since AM572x soc doesn't have much SPI diag applications, but closer and simple to understand diag app is mcspi, but mcspi is mainly for K2G soc. Is it possible to adding K2G SoC header file in our custom diag app??? and make utilize the APIs of the K2G, is it legal??? 

    Other than MCSPI which code i can refer?? If you SPI diag code please share me.

    Chethan

  • Chethan,

    AM572x has (see datasheet):
    - Four Multichannel Serial Peripheral Interfaces (MCSPI)
    - Quad SPI Interface (QSPI)

    SPI is a bus interface, both MCSPI and QSPI are SPI on AM572x. Why can't you use the MCSPI diag on AM572x? If you look at K2G pdk_k2g_1_0_2\packages\ti\drv\spi\example, they are also MCSPI and QSPI, the API level for K2G and AM572x should be the same from application point of view, but they will calls into individual SPI driver libraries. I don't see the value of using the API and header file of K2G on AM572x, you still need to use the library of AM572x.

    Regards, Eric
  • Eric,

    1.  No MCSPI is not for AM572x its clearly shown in makefile. Yes i'm referring MCSPI and QSPI diag but it supports only K2G SoC.

    2.  Yes i want to use K2G API because "SPI_v1_HWAttrs" has only definitions but no function call, that's why i want call K2G function.

    3.  ../../ti/drv/spi/example/qspi_flash really helped a lot as a reference, but why none of the diag application doesn't have multi-slave mode, if it is available please let me know. Because multi-slave mode design is implemented in our project ---- please consider this as very important.

    Thanks & regards,

    Chethan

  • Eric,

    Why none of the diag application doesn't have multi-slave mode, if it is available please let me know. Because multi-slave mode design is implemented in our project ---- please consider this as very important.

    Please guide me for multi-slave mode.


    Chethan