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

IWRL6432AOPEVM: Making a binary file to be used by Uniflash or Visualizer to load into QSPI flash

Aleksandr Labunskiy
Intellectual 390 points
Part Number: IWRL6432AOPEVM
Other Parts Discussed in Thread: UNIFLASH, , IWRL6432

Tool/software:

I started this in unrelated topic as I was told. So, I copied my original post and reply below:

***************************************************************************

  • Hi Santosh,

    While waiting on the answers I am working on modifying the Demo SW. As I see the Demo is set up to be loaded to RAM. I connected 5V power supply and I want the board to run as a stand along. 

    1. What do I need to change in the linker.cmd file to load to flash?

    2. How do I make a binary file that I can use with Uniflash APP to load SW in the QSPI flash on the evaluation board? I found a document for using Uniflash but not how to make binary.

    Alex

  •  in reply to Aleksandr Labunskiy
    TI__Genius 17580 points

    Hello Alex.

    Aleksandr Labunskiy said:
    1. What do I need to change in the linker.cmd file to load to flash?

    You shouldn't need to change anything in the linker file in order to flash.

    Aleksandr Labunskiy said:
    2. How do I make a binary file that I can use with Uniflash APP to load SW in the QSPI flash on the evaluation board? I found a document for using Uniflash but not how to make binary.

    You can create a binary by compiling the demo software in CCS or building via the makefile.

    Also these questions have deviated from the original topic.  Please make a new thread for any new questions.

    Sincerely,

    Santosh

*********************************************************************************

I modified a project from SDK motion_and_presence_detection_demo_xwrL64xx-aop_m4fss0-0_freertos_ti-arm-clang. I want to load it into QSPI flash so the evaluation board would run my code on a power supply (not USB).

Now, I have to admit that I am a relatively new user of TI programmable product. I only have a short encounter with C2000 series chip 5 years ago. When I compile the Demo CCS does not make binary files by default. Can someone point me to a document describing how to make a binary file for the IWRL6432AOPEVM board or guide me step-by-step?

Also, I can't believe that Linker file does not need any changes. Please confirm Santosh's answer to my first question in the original post and please explain why.

Alex

  • 0
    TI__Mastermind 19810 points

    Hello Alex.

    Aleksandr Labunskiy said:

    I modified a project from SDK motion_and_presence_detection_demo_xwrL64xx-aop_m4fss0-0_freertos_ti-arm-clang. I want to load it into QSPI flash so the evaluation board would run my code on a power supply (not USB).

    Now, I have to admit that I am a relatively new user of TI programmable product. I only have a short encounter with C2000 series chip 5 years ago. When I compile the Demo CCS does not make binary files by default. Can someone point me to a document describing how to make a binary file for the IWRL6432AOPEVM board or guide me step-by-step?

    Please refer to the steps in the developer's guide section of the motion and presence demo user guide for how to import, build, and execute the project.  In the build step, you will compile and create a .appimage file that you will then flash following the UniFlash guide that you had referenced in the previous post.

    Aleksandr Labunskiy said:
    Also, I can't believe that Linker file does not need any changes. Please confirm Santosh's answer to my first question in the original post and please explain why.

    The linker file does not need to be modified in order to flash the device; if you are modifying the demo and you are running out of memory you may need to modify the linker file and change how much memory each section is getting to make sure everything can fit within the memory constraints of the device.  I was under the impression you were referring to the original demo so apologies for the confusion.

    However, depending on the modifications, the changes may not inherently warrant changing the linker file if it fits within the memory constraints of the original demo.  My point was regarding changing the linker file for flashing;  all flashing requires is that you have a .appimage file that is under 736 Kb that is properly compiled using a linker file that may or may not be modified.

    Hope this clarifies your question.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Intellectual 390 points

    Thank you, Santosh,

    When you mentioned that a binary file has .appimage extension in relation to radar boards, it cleared my mind and everything fell in place. I guess what screwed me up in the first place is the directions in the document "Using Uniflash With mmWave" which you can see below:

    I would like to mention one minor thing. Even after I re-synced database in Uniflash Settings there was no 6432AOP device or board on the list, only 6432. I used Visualizer to flash the board just to be safe. It also reminds me how to set the switches on the board. Now I am curious, if I select 6432 device or board in Uniflash will it work for 6432AOP board?

    Alex

  • 0 in reply to Aleksandr Labunskiy
    TI__Mastermind 19810 points

    Hello Alex.

    Yes that will work.   As long as you chose AWRL or IWRL6432, it should be fine.

    Sincerely,

    Santosh