• State TI Thinks Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 2 answers
  • Subscribers 30 subscribers
  • Views 666 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-ODS: Programming failure with AWR1642

richard wilson
Intellectual 585 points
Part Number: AWR1642BOOST-ODS
Other Parts Discussed in Thread: UNIFLASH, , AWR1642BOOST, AWR1642

I cannot program the board. Out of box, the board worked fairly unreliably with the Visualiser tools with multiple power cycles required to get the software to recognize and run the demos. I attempted to change the firmware so that I could use the high precision range demo. since then , it has not functioned.  I have used the Uniflash programmer both on -line and local and it informs me that the XDS 110 firmware is out of date. I have successfully updated this firmware using Uniflash.  I am trying to reprogram the board with the following xwr16xx_radarss_rprc.bin from the mmwave_sdk_03_01_01_02 directory.  Before I return the board (I assume that it is damaged )- do I have the correct firmware / configuration ? ( BTW I have the 101 jumper configuration)  The chip has Uniflash is never able to identify the processor the 502AC marking automatically. 

the following messages are fairly typical - 

[4/3/2019, 11:01:39 AM] [ERROR] Cortex_R4_0: Trouble Writing Memory Block at 0x0 on Page 0 of Length 0x7ff0: (Error -1065 @ 0x0) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.0.903.6)
[4/3/2019, 11:01:39 AM] [ERROR] Cortex_R4_0: File Loader: Verification failed: Target failed to write 0x00000000
  • 0
    TI__Guru*** 147984 points

    Hi,

    First, please confirm that you have an AWR1642BOOST-ODS and not an AWR1642BOOST evm.

    If the antenna looks similar to the one in the picture, then you have an ODS board.

    If you have an ODS EVM, then you would need to use the SDK 2.0.

    You should be able to follow the instructions provided in the SDK UG to flash a binary.

    It is important to notice that the SDK supports only the AWR1642BOOST EVM.

    The AWR1642BOOST-ODS EVM has a different antenna and if you run the oob demo, the angle information will not be correct.

    You should run the Obstacle Detection Demo provided in the Automotive toolbox. This demo has been developed specifically for the AWR1642BOOST-ODS EVM.

    Thank you

    Cesar

  • 0 in reply to Cesar
    Intellectual 585 points
    Thank you for the quick response Cesar. I confirm that I have the AWR1642 Boost-ODS - which now explains a lot. Basically the SDK doen't work with the hardware that I have purchased. Could you please point me to the Automotive toolbox?
  • 0
    TI__Mastermind 21025 points

    > I am trying to reprogram the board with the following xwr16xx_radarss_rprc.bin from the mmwave_sdk_03_01_01_02 directory.  

    I think you are trying to flash the wrong file. This file is the BSS patch only. It contains no MSS or DSS image.

    Please go into a demo folder such as C:\ti\mmwave_sdk_03_01_00_02\packages\ti\demo\xwr18xx\mmw and look for the .bin file there, for example: xwr18xx_mmw_demo.bin.

    Each of the demos in the Automotive Toolbox (in the TI Resource Explorer) provide their own demo .bin file.  The rprc in the filename indicates it's a partial image.

      -dave

  • 0 in reply to richard wilson
    TI__Mastermind 21025 points
    Yes, you should probably be using SDK 2.1. The Resource Explorer can be found in CCS, under View -> Resource Explorer.
  • 0 in reply to db_woodall
    TI__Guru*** 147984 points
    Here is the link for the Obstacle Detection Demo in the Automotive Toolbox

    dev.ti.com/.../

    The release notes indicate which SDK version is required.

    For this demo it is SDK 2.0.0.4

    Please go to the mmWave SDK page and click "Get Software" for Version 2.01.00.04. A new page will open. At the bottom there is a link for SDK 2.00.00.04

    Thank you
    Cesar
  • 0 in reply to Cesar
    Intellectual 585 points
    Thanks for the answer - however- your answer does not match Cesars regards SDK2.1
  • 0 in reply to db_woodall
    Intellectual 585 points
    Thanks for the explanation. Now I can flash the file but the visualiser does not run doe to a GUI error (mmwDemo:/>guiMonitor -1 1 1 0 0 0 1
    Error: Invalid cfarCfg arg count). I don't understand why this software /EVM demo is so difficult to understand and test. By far it is the worst EVM that I have purchased from TI - It's like the guides, the hardware, the firmware, the applictions, the GUI were written by different companies. It is quite dissapointing. Can someone take an idiots approach ( use me if you like) and write a single cogent, coherent suite of tools and documents that works- I will gladly test it for you.
  • 0 in reply to richard wilson
    TI__Mastermind 21025 points
    Each demo runs a different set of algorithms that are focused for the application it is written for. This necessitates different CLI commands and in most cases, it's own GUI. You must run the GUI that matches the demo. For example, for the ODS demo, the GUI is found here:

    C:\ti\mmwave_automotive_toolbox_2_4_7\labs\lab0004_obstacle_detection\gui\ods_3d_visualizer.exe

    Please take a look at the demo's user guide, found here for the same demo:

    C:\ti\mmwave_automotive_toolbox_2_4_7\labs\lab0004_obstacle_detection\docs\ODSdemo_usersguide.html or .pdf

    It will take you step by step on how to install and run the demo.
  • 0 in reply to db_woodall
    Intellectual 585 points
    I will try it now - thank you very much .