• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 29 subscribers
  • Views 488 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.

AWR1642BOOST: AWR1642 BOOST Uniflash OOB demo flash not working

Cagri Tanriover
Intellectual 905 points
Part Number: AWR1642BOOST
Other Parts Discussed in Thread: UNIFLASH, DCA1000EVM

Hi,

I have a Rev B AWR1642BOOST board.

When I tried to run the mmWave out of the box demo, the SDK version on the hardware was reported as [2,0]. The demo does not support that version anymore.

So I downloaded the latest mmWave SDK (version: 3.04.00.03) and located the *.bin file of the demo for my board. (I also installed mmWave SDK version 2.01.00.04 but observed exactly the same problem reported below)

I went to Uniflash and specified that *.bin file to be flashed to my device. My device was successfully autodetected, which tells me Uniflash can link to the AWR1642BOOST at least.

I also made sure SOP (101) jumpers were configured as required to make sure the board was in the flash state. (I power cycled the board BEFORE attempting to load the *.bin file as well)

When I hit the "Load Image" button, the program gets stuck as follows. I see no progress once that display is shown. (I terminated the program a few times and restarted my PC but the result did not change)

I gave up on loading the *.bin file and tried to erase the flash ONLY but observed the same behavior.

(I also have a DCA1000EVM that AWR1642BOOST was connected. I tried the above when DCA was connected and disconnected but the result did not change)

Any thoughts on what may be going wrong here?

Regards,
Cagri

  • 0
    Intellectual 905 points

    I made some progress in terms of getting the OOB demo working. The correct link to the demo for SDK version 2.x and 1.x seems to be this one.

    (The demo tutorial video mislead me to this link which is for SDK versions 3.x and did not work for me. I tried to flash the *.bin file for the demo to get around that problem as described in my earlier message.)

    Even though I managed to get the demo running on my AWR1652BOOST, the problem of flashing still persists and I don't know why I could not get the flashing to work with my hardware. I still need help with that.

    Regards

  • 0 in reply to Cesar
    Intellectual 905 points

    Hi Cesar,

    I had a look at the link you shared. Besides the bullet on trying a new machine, all other steps in that link were already tested.

    So I installed all of the tools on a Linux Ubuntu 18.04 machine and tested the flashing there. This time it worked on first trial. I was successfully able to upgrade the SDK on the EVM to version 3.4.

    It looks like the problem may be related to the Windows 10 USB drivers. I tried the cloud as well as the desktop version of the Uniflash on Win 10 and power cycled my PC a few times on multiple retries but nothing worked.

    One interesting observation is the demo (after being flashed to the EVM on Ubuntu machine) works reliably on the Win 10 machine. So the problem comes down to the difference between the flashing and the normal operation of the board using Windows 10.

    Having to use two different machines for development is a big problem as you can imagine and resolving the Win 10 flashing problem will really help. I will try to manage with the two machines I have in the meantime.

    Regards,
    Cagri

  • 0 in reply to Cagri Tanriover
    TI__Guru*** 149084 points

    Hi,

    Our team uses Win10 machines with no problem. So I think that the issue is related to your setup.

    I will leave this question open to the forum community to see if there is any additional feedback.

    For future issues please check our updated mmWave FAQ

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

    Thank you

    Cesar