• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 221 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.

AWR2944EVM: Viewing used binaries by meta images (.appimage)

Mark Passia
Intellectual 300 points
Part Number: AWR2944EVM
Other Parts Discussed in Thread: UNIFLASH,

Tool/software:

I am using the uart_uniflash.py script to flash created binaries onto an AWR2944EVM created as instructed on P.41 of  "MMWAVE MCUPLUS SDK User Guide" though the flushing was successful, the documentation does not answer some of my questions. Therefore I hope that you can help with that:

  • The documentation states: "This will create <mmwave_sdk_device>_mmw_demo_mss.xer5f, <mmwave_sdk_device>_mmw_demo_dss.xe66 & <mmwave_sdk_device>_mmw_demo.appimage binaries", however gmake all created a multitude of files (see Image). I am curious why so many files were created? Is this typical only for the demo code to create TDM, DDM and other version of the 'same' demo code?

  • As I understand the AWR2944EVM needs to get both the C66x and R5F flashed, these are the binaries that are created upon compilation of the demo code files. However the default.cfg file does not contain any paths to the binaries for the C66x and the R5F. To my understanding the meta image (, i.e. the .appimage) contains these paths, is this correct? If so which of the multitude of the created files are these? Is there a possibility to view the internals of the .appimage and explicitly check the used/referenced binary files? 

  • 0
    TI__Expert 3490 points

    Hello,

    1) To answer your first question, these are all files made for different purposes. There is DDM & TDM which are different demos. Enet is for ethernet demos. .map files are to observe the memory allocation used for that specific demo. If you are wondering about specific ones, ask and I will answer. Yes, it is very typical to build all these files.

    2) I believe you have a slight misunderstanding here. The .appimage is what is flashed on using default.cfg. Those core files (.xerf5, etc.) are loaded using CCS. This is done usually when more debugging is desired.

    Let me know if you have any further questions.

    Best,

    Gabriel

  • 0 in reply to Gabriel Gigliotti
    Intellectual 300 points

    Hi thank you for your answer, it helped a lot! 

    Concerning the first part all is clear - for now!

    Concerning the second part I am completely new to TI's SDK, but I do have quite a bit of experience in post processing so what I would like to do now is to start working with real time systems. Thus it would be super helpful if you could answer some additional questions: 

    1. I have inspected the main makefile under C:\ti\mmwave_mcuplus_sdk_04_07_00_01\mmwave_mcuplus_sdk_04_07_00_01\ti\demo\awr294x\mmw it references other makefiles in the mss, dss and common directories. I wonder if there is a quick way of getting a list of all used source code files within a build/compilation?
    2. In one of the makefiles I have found this directory being referenced C:\ti\mmwave_mcuplus_sdk_04_07_00_01\mmwave_mcuplus_sdk_04_07_00_01\ti\datapath\dpu\dopplerproc/lib this contains HWA binaries as I understand, these are compiled and non editable? There is a related directory ...\src  containing dopplerprochwa.c my question is what's the idea behind this structure? Does dopplerprochwa.c set the parameters of the HWA files and thus it gets included into the compilation or do only the directly referenced HWA files get compiled?
    3. I have some issues with loading the binaries via CCS in the volatile development mode, could you give me some steps to follow? I have found the documentation a bit vague in this respect, or perhaps I didn't find the proper documentation. 

    Thank you very much for your help!

    Best regards 

    Mark 

  • 0 in reply to Mark Passia
    TI__Expert 3490 points

    Hello,

    1) No there is not a quick list to see all the source code files used. One must navigate through these makefiles and see what each respective demo uses.

    2) To my understanding, these libraries are just precompiled versions of the source code present. They are used in packages when it is not necessary for the user to see the source code. You can even rebuild these libraries if you edit the source code to make it more customized for your specific application.

    3) The following are the steps to take to load on CCS.

    - flash an empty app image on your board. They can be found at this location. Flash the respective device app image on your board. Make sure your board is in flashing mode.

    C:\ti\mmwave_mcuplus_sdk_04_07_00_01\mmwave_mcuplus_sdk_04_07_00_01\ti\utils\ccsdebug

    - switch your board to functional mode and then connect to the board on CCS. To do so you might have to add a new target configuration for your device. Once you have you can launch the selected configuration.

    - then connect to the respective cores (rease/reset the cpu's once connected to ensure clear cores) and you can load the core files.

    - run the mss core and then dss core and the demo should run.

    Let me know if any questions. There should be a section on the user guide talking about this as well if I missed any details.

    Best,

    Gabriel

  • +1 in reply to Gabriel Gigliotti
    Intellectual 300 points

    Ho thank you for your help!

    So now I do understand the layout of the SDk but I have an issue, it seems that the new version of the CCS has a very different layout than the one that you have refferenced and that the documentation https://dr-download.ti.com/software-development/software-development-kit-sdk/MD-U4MY7aGNn5/04.02.00.02/mmwave_mcuplus_sdk_user_guide.pdf .

    More precisely I have created a new target configuration, here I am unsure what about the additional settings which seem to be absent in the previous version mentioned in the SDK documentation:

    Critically I cannot manage to launch this target configuration, the CCS documentation https://downloads.ti.com/ccs/esd/documents/users_guide_ccs_20.1.1/ccs_debug-main.html?highlight=target%20configurations#target-configuration-files doesn't really describe how to do that besides the structure of the file itself.

    Could you give me guidance how to get these 2 steps done with the new CCS 20.1.1?

  • +1 in reply to Mark Passia
    TI__Expert 3490 points

    Hello,

    Please use version 12.8.1 for now.

    Best,

    Gabriel