• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 126 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.

IWRL6432BOOST: Running code

Prathik Narsetty
Prodigy 60 points
Part Number: IWRL6432BOOST
Other Parts Discussed in Thread: UNIFLASH, IWRL6432AOPEVM

Tool/software:

Hi, 

I am trying to test out the OOB demo motion and presence detection on the IWRL6432BOOST and am following these steps: 

1) Set board into flashing mode, then flash using UNIFLASH.

2) set Board into functioning mode, then send target configuration via radar visualizer. 

this is the switch settings I am using. 

But I am running into this error. 

I am also confused on how to figure out how to map the correct pins to the correct signals within the code. 

I need to configure UART, but im not sure which pins to select and where they relate to on the board itself. I want to try and use the launchpad connectivity header to also connect for some GPIO and aswell as the UART, but dont know how to map it properly.  I really appreciate your help. 

Thanks so much,

Prathik Narsetty

  • 0
    TI__Mastermind 21511 points

    Hi Prathik, 

    Can you let me know what version of the SDK you are using?

    Can you also confirm that you reset the EVM after changing to functional mode? This needs to happen after every time you change the SOP setttings.

    Prathik Narsetty said:
    I need to configure UART, but im not sure which pins to select and where they relate to on the board itself.

    I'm not sure I fully understand what you mean here. UART is already enabled by default for the motion and presence detection demo so you shouldn't need to make any changes for that.

    Best regards,

    Josh

  • 0 in reply to Josh Dye
    Prodigy 60 points

    this is the SDK I am using: (MMWAVE_L__05_05_03_00) 

     

    Yes I am pressing the rest switch after flashing the code and before changing to functional mode.

    Could you let me know where on the board the UART is brought out? Also I am confused as to how I would correlate the names of the pins in software to the board. For example here is a name in the software, but where does this map to on the board? How would I figure this out myself so I can adapt it for any use case? 

    I was wondering how the workflow is for this board. I am currently flashing the code using UNIFLASH and then sending target config using radar visualizer. Rather, is there not a way to send the flash and the target config all in ccs?

    Also, I was wondering if I wanted to develop my own code, how would I access the sensor data (to my knowledge it comes in a buffer of frames of point cloud data?) This is for if I wanted to develop my own model, and also does this mean to test I would always need to flash using UNIFLASH and then switch over to radar visualizer to send the target configs to configure the sensor frontend? 

    Also for my current application, I want to stream out point cloud data, but I want to see the exact format (I.E. how many frames are in the TLV and if it is the tracker point cloud data or the regular) and was wondering how I would see that. 

    Finally, I am also working with the IWRL6432AOPEVM, and I was told that UART is  brought out on the J8 header. I was wondering what kind of wire would I need to be able to connect this pin header to an external ESP32? Thankyou so much, I really appreciate your time! 

  • 0 in reply to Prathik Narsetty
    TI__Mastermind 21511 points

    Hi Prathik, 

    Prathik Narsetty said:
    Yes I am pressing the rest switch after flashing the code and before changing to functional mode.

    This is incorrect. the reset should be applied after changing to functional mode to latch the new SOP setting. This may be the reason you get an error in the visualizer.

    Prathik Narsetty said:
    Could you let me know where on the board the UART is brought out? Also I am confused as to how I would correlate the names of the pins in software to the board. For example here is a name in the software, but where does this map to on the board? How would I figure this out myself so I can adapt it for any use case? 

    You can refer to the EVM schematic on the IWRL6432AOPEVM tools page for understanding how the pins from the device are brought out on the EVM. The UART is routed to the XDS110 to be accessed via the USB port. It is also routed to the J8 connector.

    Prathik Narsetty said:
    I was wondering how the workflow is for this board.

    Typically, we expect users to initially evaluate the the out of box demo (motion and presence detection) using the SDK visualizer as you are doing. With this you can make adjustments to the configuration or use the predefined configurations. Once you are familiar with using the EVM you may wish to evaluate a different example that we have in the Radar Toolbox depending on your target application. From there you might customize the code or fine tune the configuration for your specific use case.

    It is not possible to write to flash or configure this EVM from CCS. You can however use CCS to execute code in 'debug mode' for faster iterative testing. Please refer to the CCS Launch, Load and Run page in the SDK documentation for more information on this. Please note also that Uniflash is an option for flashing but it is not required, the SDK visualizer also has the capability to write to flash.

    Prathik Narsetty said:
    I was wondering what kind of wire would I need to be able to connect this pin header to an external ESP32?

    You could probably acquire some sort of adapter board (like this https://www.proto-advantage.com/store/product_info.php?products_id=2700016 *note, we have not officially tested this. It's just an example.) to make the connection simpler or you could design a custom cable.

    Best regards,

    Josh