• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 33 subscribers
  • Views 237 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.

AWR1843BOOST: AWR1843BOOST

Hitanshu Punj
Prodigy 70 points
Part Number: AWR1843BOOST
Other Parts Discussed in Thread: AWR1843

Tool/software:

Hi,

I am working with the AWR1843 device. It was previously working fine with the same hardware setup, but now it is no longer responding. I want your assistance in diagnosing the issue.

Issue details

  • The board is connected to both the power supply and the USB port, the same as before.

  • The COM ports (as shown in Device Manager) are detected properly, so the USB interface seems fine.

  • I am sending the same configuration file/commands through my program, which used to work earlier, but now the board does not respond with any data.

  • I also tried using the TI Online Visualizer / mmWave Demo Visualizer to send the configuration, but the device does not get connected (despite the COM ports being visible).

  • Snapshots of the COM port detection and connection attempts are attached for reference.

Steps already tried

  1. Verified power supply and USB connections.

  2. Checked COM ports are correctly enumerated and assigned.

  3. Tried both my own program and TI’s online configuration page.

  4. Used the same configuration files that were previously working.

Request

Could you please help me identify the possible reasons why the AWR1843 is no longer responding?

  • Is there a way to check if the device has gone into a fault state or requires reflashing of firmware?

  • Could this be related to the SOP mode settings, firmware corruption, or hardware failure?

  • Are there diagnostic steps you recommend to confirm whether the device is still functioning properly?

Additional information

  • Device: TI AWR1843

  • Host connection: USB (CDC COM ports detected)

  • OS: [your OS, e.g., Windows 10 64-bit]

  • Previously working with the same setup, no changes made to hardware/software.

  • 0
    TI__Guru**** 151344 points

    HI,

    We recommend that you start by flashing the demo pre-built binaries on the board as described in the SDK User's Guide.

    After flashing the binaries, you should be able to to check on a Serial Emulator (such as TeraTerm) connected to the User COM Port, that you see the "mmWDemo" prompt sent by the device to the PC

    thank you
    Cesar

  • 0
    Prodigy 30 points

    Hi, you should change sdk version to 3.4 for this platform. Thanks

  • 0 in reply to Cesar
    Prodigy 30 points

    Dear Cesar,

    I've encountered a similar problem. 1843Boost board once worked fine but is not responding any more, meaning in the console of CCS I do not see any message nor a live data in the mrr visualizer. 

    Here is test condition:

    1) I resumed testing by re-using the mrr project (mss and dss) that was built in my workspace before. And this time I resumed by creating a new target configuration and loading/running the binaries, .xe674 and .xer4f.

    2) no modification has been made on any of the codes in the mss and dss directories yet. I tried to run the binary as it was.

    3) ccs and SDK version were and still are 12.7 and 3.6, respectively. The 5V power and COM port and AUX port all are connected correctly.

    4) SOP[2:0] = [0 0 1] setting is correct as to be used in "functional mode" 

    Here are my questions:

    1) in the previous inquiry to which you replied, you recommend start by flashing the demo pre-built binaries on the board as described in the SDK User's Guide. But it did not work for me. Should I flash xwr18xx_ccsdebug.bin for my case instead?

    2) should I flash this xwr18xx_ccsdebug.bin every time before I create a new target configuration or connect the target again? because I had loaded two binaries .xe674 and .xer4f. some time before?

    3) from which step should I resume in order to test successfully after the board is turned-off today and on again tomorrow? because simply connecting  target again in the Target Configuration followed by loading binaries does not simply result in live target detection.

    4) since I do not see any messages like the followings in the console, which I expected to see, what can I try next?

    • “Debug: MMWave has been configured for MRR."
    • “Debug: Sensor will start momentarily."

    Other questions not directly related to the current problems:

    1) When loading two binaries, .xe674 and .xer4f, should I connect MSS first or DSS first? The SDK users' guide and Gemini tell me the opposite. I guess when building a project, DSS must be still built first.

    I appreciate if you could help me resolve these issues.

    Thank you

    Reem

  • 0 in reply to Reem Song
    TI__Expert 4910 points

    Hello,

    To answer some questions.

    In your case you need to flash xwr18xx_ccsdebug.bin to load images in CCS. This image does some important initilizations necessary to load these core images. 

    To determine which core should be built first you can take a look at the projectspec files and see which one is a dependency for another.

    Regarding the order of loading it is specified in the "Loading the Binary" and "Running the Binary" section in the MRR user guide.

    Medium Range Radar Users Guide

    Please refer to this document, I believe it can help with many of your questions.

    Best,

    Gabriel

  • 0 in reply to Gabriel Gigliotti
    Prodigy 30 points

    Hi, Gabriel,

    Thanks to you, the flash was initialized and now targets are detected using MMR two binaries.

    But when I follow the exactly the same steps for MMR beamstreering project, NO live data is shown in visualizer, although all H/W connections and target configurations look correct. Even the following messages are shown in the console:

    • “Debug: MMWave has been configured for MRR."
    • “Debug: Sensor will start momentarily."

    1) Could you think of any reason? At least it should show something in the visualizer. (I tried both visualizers provided in mrr and mrr_beamstreering folders and none of them show anything). 

    FYI, following a comment on other forum, I had to install another SDK version (3.2) which was lower than what I had (3.6). Otherwise, there comes mss rebuild error with gmake. 

    2) When I import mrr beamstreering lab which is found in the Radar toolbox 2.0 folder, not in the SDK folder, how can I make sure this lab is based on SDK 3.2v not 3.6v? could this be the reason for not showing any live data?

    Thanks

    Reem

  • 0 in reply to Reem Song
    TI__Expert 4910 points

    Hello,

    Did you flash  xwr18xx_ccsdebug.bin from SDK 3.2 for mrr_beamsteering? That could be causing some issues.

    Also a way to confirm that a project is using the proper SDK is to right click on the project in CCS -> select properties

    From there select "General" and then there should be a "Products" tab

    The following is an example and you can see the following project is using SDK 3.5

    Best,

    Gabriel