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: no data available

Part Number: AWR1843BOOST
Other Parts Discussed in Thread: UNIFLASH, AWR1843,

Hello,

I am trying to run the Demo of this evaluation module but I could not succeed. I can correctly flash the EVM using uniflash as explained in the documentation, I carefully checked that the switches are then set for functional mode and, although I can successfully transfer a configuration with the mmWave Demo Visualizer at the last step sensorStart does not return anything and no data are visible on the Plot side. I observe almost the same behaviour with version 3.3 and 3.4 (only difference is that 3.3 shows "waiting for data" instead of "connected").

Things that I have tried so far: 

  • changing several power supply (including a linear 5V 4A PSU)
  • using a different PC (only 3.3)
  • pushing reset button at different stages of power cycling
  • sending configuration commands one by one via a serial terminal: after sensorStart no answer is received and sensorStop answers that sensor never started indeed. At the same time no data is present on the data port, so it is coherent with what Demo Visualizer shows

It is like a reset occurs after sensorStart, but I have no means to positively verify it.

Do you have an explanation for this behaviour and more important a solution ?

L

  • Luigi,

    I would recommend that you take advantage of the ability to debug the demo using the CCS debug image provided in the SDK.

    You are likely encountering an error that is being raised by the demo application. You will be able to see this error message along with the error code that can be used to root cause your issue.

    In mmWave SDK v3.3, you can refer to section 3.2.2 "CCS development mode" in the User Guide. This User Guide is located in this file location:

    C:\ti\mmwave_sdk_03_03_00_03\docs\mmwave_sdk_user_guide.pdf

    Regards,

    Kyle

  • Hello Kyle,

    thank you for your answer and sorry for the delay.

    I managed to do as suggested. And I get the following information :

    When I launch the software I get the following console output

     

    [Cortex_R4_0] **********************************************
    Debug: Launching the MMW Demo on MSS
    **********************************************
    Debug: Launched the Initialization Task
    Debug: mmWave Control Initialization was successful
    Debug: mmWave Control Synchronization was successful
    [C674X_0] Debug: DPM Module Sync is done
    [Cortex_R4_0] Debug: CLI is operational

    Then, when I click on "Send Config to MMW device" on the demo interface another line appears

    Debug: Sending rlRfSetLdoBypassConfig with 3 1 0

    and then the embedded code crashes and the xml console gives the following message (in red):

    Cortex_R4_0: Error: (Error -261 @ 0x0) Invalid response was received from the XDS110. (Emulation package 9.2.0.00002) 
    Cortex_R4_0: Error: (Error -122 @ 0x0) A bad parameter value was detected within a function. It is likely a problem with `SC_ARGS' in SMG_call(). (Emulation package 9.2.0.00002) 
    Cortex_R4_0: Trouble Halting Target CPU: (Error -261 @ 0x0) Invalid response was received from the XDS110. (Emulation package 9.2.0.00002) 
    Cortex_R4_0: Unable to determine target status after 20 attempts
    Cortex_R4_0: Failed to remove the debug state from the target before disconnecting. There may still be breakpoint op-codes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging
    C674X_0: Power Failure on Target CPU 
    C674X_0: Failed to remove the debug state from the target before disconnecting. There may still be breakpoint op-codes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging

    Can you suggest where should I set a breakpoint to see things more clearly ?

    Best regards

    Luigi

  • Luigi,

    When working with the CCS debug image, it is recommended to use a terminal program like Tera Term for sending the CLI commands and not the mmWave Demo Visualizer. This will allow you to see the error messages in the CCS console output window.

    You might also need to update your XDS110 emulation software on your AWR1843. The SDK User's Guide provides instructions on how to complete these steps.

    Regards,
    Kyle

  • Kyle;

    I am sorry for the long delay.

    Unfortunately when entering commands in a serial termina I observe exactly the same behaviour : as soon as I issue the sensorStart command everything crashes and I get the console error that I have shown previously.

    I am now trying to update the XDS110 emulator. In the meantime I confirmed that the same behaviour is observed with another AWR1843BOOST card and similar error are observed on a MMWICBOOST.

    Please provide more aggressive support on this issue.

    Regards,

    Luigi

  • Hello Kyle,

    it turns out that all of this was indeed a problem of PSU. I finally tried with another 5V 4A PSU and everything worked !

    If I may, TI should definitely provide users with a list of approved power supplies, I have tested a few (and this is what sidetracked me in the first place) and the bad behaviour is quite consistent even across different technologies (battery packs, linear power supply etc.) and vendors.

    Best regards

    Luigi