• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 191 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

AWR2544LOPEVM: Metaimage

AWR2544LOPEVM: FTDI SPI access using mmwave OOB MSS and BSS image

Ross Bajocich
Prodigy 70 points
Part Number: AWR2544LOPEVM
Other Parts Discussed in Thread: AWR2544

Tool/software:

I've successfully used + flashed the mmwave out of box demo given provided meta image files. These work and are compatible with the 2544 visualization and CLI API. This metaImage includes valid recent MSS and BSS firmware which are shown with the version CLI command.

Separately, I've also successfully connected the DCA1000 and controlled and received data using the FTDI SPI control using mmwaveStudio 3. In this use case it appears I am forced to download the MSS and BSS firmware files at startup. If I attempt to control the board (in QSPI boot mode with above valid MSS+BSS) without loading this firmware, I receive a timeout/failed message response in the first command sent.

My question is this: Can I use the FTDI based SPI communication with a metaImage loaded MSS + BSS firmware ? So far I have only been able to use them independently. The MSS + BSS are loaded in flash, but it appears that FTDI SPI control no longer is able to communicate.

For example, if I wanted to control the awr2544EVM using only FTDI control, what metaImage needs to be flashed to the board to support this permanently? MMwaveStudio downloads it at each startup.

Thank you,

-Ross B

  • 0
    TI__Mastermind 27585 points

    Hello Ross,

    So, the FTDI control path can only be done using studio.
    In case of studio there are 2 .bin file it loads, which is masterss and radarss files.

    For creating an app image and flashing you will need the .out file, which is what the demo generates. These files are then fed into the image generator to provide you the final app image. You cannot do the same with .bin files.

    So, what you are looking for is not possible without the source code of the masterss and radarss codebase, which is not available.

    Regards,
    Saswat Kumar

  • 0 in reply to Saswat Kumar
    Prodigy 70 points

    Hi Saswat,

    Thank you for your prompt response. I now understand that FTDI SPI control requires the two .bin (MSS + BSS) files provided with in mmwaveStudio rf_eval folder only.

    Is there another way to flash these files so that they are persistent on the awr2544? Just confirming I'm understanding that the FTDI SPI control method is only accessible from the host computer after downloading firmware to the awr2544 after every power cycle.

    My goal is to flash a set of firmware that allows full host computer control over the features in mmwave_dfp_02_04_13_00, rather than relying only on demo app or MCU development.

    It seemed probable that the MultiCoreAppImageCreator could be used for making the (persistent flashed) .appimage MSS and BSS rf_eval firmware, though your comment indicates it's not possible with the provided .bin files from mmWaveStudio 3 and dfp_02_04_13.

    Thanks,

    -Ross B

  • 0 in reply to Ross Bajocich
    TI__Mastermind 27585 points

    Hello Ross,

    For your application you should be looking at an application like studio cli: mmWaveStudio CLI Getting Started Guide
    Please refer this for AWR2544. Use this as reference and you can develop your application.

    It is not possible to achieve the below at all. The whole point of studio is that it flashes the firmware.

    Ross Bajocich said:
    My goal is to flash a set of firmware that allows full host computer control over the features in mmwave_dfp_02_04_13_00, rather than relying only on demo app or MCU development

    Regards,
    Saswat Kumar