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.

[FAQ] mmWave Sensor- Uniflash related queries

Mastermind 28905 points

Replies: 1

Views: 140

Here are frequently asked questions related to the Uniflash tool with mmWave Sensor.

 

Q1. I’m having trouble flashing my EVM using the Uniflash tool.

Answer:

  • Please make sure that you have set the right SOP jumper (SOP0 and SOP2) on EVM in order to put device in flashing mode. Do the power cycle after putting the jumpers then start using Uniflash.
  • Make sure the COM port number is correct in the Uniflash ‘Settings & utilities’ TAB. This COM port should be the number which is populated as a “XDS110 Class Application/User UART”.
  • Disconnect and connect the USB cable if Uniflash is not able to access the COM port.
  • Check the power supply if it is according to the spec. (5V ~3A)
  • If Uniflash was crashed or closed forcefully in last session then try to kill these processes from TaskManager – “DSLite.exe” and “Python**” and restart the Uniflash GUI. [TODO] find the 2nd process name.
  • Try different PC to use the Uniflash. (if above doesn’t resolve the issue)
  • Update to latest Uniflash version if using old version of it.

Related thread- https://e2e.ti.com/support/microcontrollers/c2000/f/171/t/740576

https://e2e.ti.com/support/sensors/f/1023/t/824004

 

Q2. How can I flash image without installing UniFlash?

TI provides browser-based UniFlash tool which user can use to flash image to mmwave sensor. Chrome is the recommended browser and on top of that, you need to install a browser extension (TI Cloud Agent).

https://dev.ti.com/uniflash

Q3. How to flash multiple images to device using Uniflash?

Answer: Uniflash provides four MetaImage field to select files from PC and then it flashes to sFlash chip connected with mmWave Sensor at every 512KB offset (starting from zero offsets). So first file (MetaImage1) goes to top location of sFlash chip and next at 512KB location of sFlash.

In the functional mode device’s bootloader always starts from zero offset of sFlash for any valid MetaImage and jump to 512KB offset if not found valid image in last offset location. The bootloader reads and verify MetaImage header content to get to know the image’s validity and does the CRC check at last chunk of image loading.

If a user needs to use SBL (secondary bootloader) then this must be flashed at zero offset of the sFlash (metaImage1 from Uniflash) where SBL can look for application image at programmed offset location.

 

Q4. Supported flash device for mmWave Sensor

Answer: Refer this app-note- http://www.ti.com/lit/an/sprach9a/sprach9a.pdf

 

Q6.5. How not to erase, format entire flash when flashing new binaries?

Answer: Refer this thread https://e2e.ti.com/support/sensors/f/1023/t/795052?tisearch=e2e-sitesearch&keymatch=FAQ%2520uniflash

1 Reply

  • Thanks for the info

    ----------------------------------------------------------------------------------------------------------

    Please click the Verify Answer button on this post if it answers your question.
    ----------------------------------------------------------------------------------------------------------

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.