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.

IWR6843: RS232 connectivity issue

Part Number: IWR6843
Other Parts Discussed in Thread: IWR1642

Hello!

I have a trouble to activate our IWR6843 test module which is composed of IWR6843 boost B'd and RF module.

Basically, the circuit was reviewed and confirmed by TI. The only different point compared with TI's reference circuit is warmRst pull-up resistor is not connected in our module. [ SOP0, 1 are closed, SOP2 is open for a DCA B'd connection]

Is this root cause? The issue is a RS232 connectivity in mmwaveStudio.

And there is no oscillation of a 40MHz crystal on module board.

Each of 1v4_synth and vout_PA is 1.37V and 1.0V. And the 1v4_APLL and VBGAP output are 0V.

This case is very similar with "IWR1642: no crystal oscillation" that I have seen on E2E forum.

However, I couldn't notice the solution to resolve this issue.

Please let me know how to resolve it.

I'm looking forward to hearing from you.


Thank you!


Regards,

  • Hi,

    • Also will it be possible to share a picture of your setup?
    • Can you connect to the UART COM port using Teraterm or similar emulation software?
    • Is there any firmware running on the device? Can you confirm you have erased the flash before trying to run with DCA?

    Regards,

    Charles O

  • Hi,


    I can't upload the setup image because of security issues.


    Basically, the connection is same as DCA B'd connection. In my case, the RF and Booster B'd are combined by single module. So, only DCA connection is needed for data acqusition.


    It contains only one 60-pin connecter for DCA connection. [RF+XDS110 Chipset] <--60pin--> [DCA]


    I have tried to connect UART COM port using Teraterm. But there is no response.

    Is there any other things what I have to check?

    Please let me know that.

    Regards,

  • Hi,

    1.  Were you able to debug the board via JTAG?
    2.  When you change the board to flashing mode, were you able to program it?
    3. lastly after programming it and changing the SOP back to functional mode, do you get any output on the UART terminal?

    Regards,

    Charles O

  • Hi,

    I have done the JTAG connection test.

    But Error is occurred as listed below.

    Please, comment to me for resolving problem.

    Regards,

    -----[An error has occurred and this utility has aborted]--------------------

    This error is generated by TI's USCIF driver or utilities.

    The value is '-233' (0xffffff17).
    The title is 'SC_ERR_PATH_BROKEN'.

    The explanation is:
    The JTAG IR and DR scan-paths cannot circulate bits, they may be broken.
    An attempt to scan the JTAG scan-path has failed.
    The target's JTAG scan-path appears to be broken
    with a stuck-at-ones or stuck-at-zero fault.

  • is this a custom board or a TI evaluation module?  The issue with the reference post was with the reset RC constant needing more time to enable the SOP latch at the right state.

    BR,

    Charles O

  • Hi,

    That  is a our board not TI's one.

    However,  the RC value of our board is the same like reference circuit.

    I really want to know what I have to check or next step to resolve problem.

    Best Regards,

     

  • Hi,

    Using an oscilloscope, can you confirm that SOP0, 1 and 2 gets to 3V3 before the reset line crosses 1.5V?

    Can you also send a snapshot of the CCS debug interface showing where the device is getting stuck?

    Regards,

    Charles O

  • Hi,

    What does that mean the reset line?

    Do you want to know settling time to get to 3.3V?

    Best Regards,

  • Hi,

    There should be an RC timer connected to the IWR6843 IC. The SOP pins should settle at 3.3V before the reset RC voltage rises to 1.5V.

    Can you confirm that this is the case?

    Regards,

    Charles O

  • Hi,


    I have tested SOP settle time between Ref. B'd of TI and our customer B'd.


    But, I can't find the difference between them. (The rising time is so fast, I can't distinguish each of them.)


    The fundamental problem is that there is no oscillation of a crystal output.

    I 'd like to know whether this has somthing to do with settling time of SOP pins.

    Please advice to me to find the reason of this problem.


    Best Regards,

  • Hi,

    1. You need to check the SOP and RESET using an osciloscope. You should be able to capture the voltage and rise time using one
    2. The resolving the JTAG connection issue, to confirm if you can debug the board so you can read certain registers on the device

    These 2 details will help determine what to do next.

    BR,

    Charles O

  • Hi,

    1. I have tested rising time of the SOP and RESET pins. The SOP rising time is 0.8ms and the RESET is 1ms at 1.5V point.

        We have found the error point which the RESET has been stuck to 0V. So, The 'No oscillation' has been resolved. 

    However, the RS232C Connectivity has not resolved yet in mmwave studio. Could you explain check point more specifically?

    Best Regards,

     

  • Hi,


    In order to confirm UART data connection by a Teraterm, a Demo binary has been downloaded and then I have confirmed that the connection is ok.

    Also, A Demo GUI is operating normally.

    However, when I try to connect DUT by mmwave Studio in DCA mode, there is a error message like below.

    " Error: Connection failed: Calling_ConnectTarget returned 3"

    Please let me know how to solve this problem.

    Best Regards,

  • Hi,

    You need set configure the SOP pins to 110 to connect to mmwave studio, can you confirm this is done?

    Can you also send a video capture mmwavestudio interface while trying to connect?

    BR,

    Charles O

  • Hi,

    As I mentioned earlier, the standalone mode operation in demo GUI is no problem. Which means the data connection of UART is working normally. Is it right?

    I have checked SOP pins to 110 to connect to DCA B'd for data acquisition.

    Actually now, I'd like to know to confirm between DCA B'd and our module which is integrated with Boost & RF components.


    Below list is error message in mmwave studio.

    Best Regards,

    GM: Constructor

    GM: Mon Oct 21 15:17:38 2019

    RSTD.Transmit("/Settings")

    [15:17:39]

    [15:17:39] ### Running Startup script: "C:\ti\mmwave_studio_02_00_00_02\mmWaveStudio\Scripts\Startup.lua" ###

    [15:17:39] RSTD.SetAndTransmit ("/Settings/Scripter/Display DateTime" , "1")

    [15:17:39] RSTD.SetAndTransmit ("/Settings/Scripter/DateTime Format" , "HH:mm:ss")

    [15:17:39] Scripter ignored: Attempt to UnBuild() again or before Build.

    [15:17:39] RSTD.SetVar ("/Settings/Clients/Client 0/Dll" , "C:\\ti\\mmwave_studio_02_00_00_02\\mmWaveStudio\\Clients\\\\LabClient.dll")

    [15:17:39] RSTD.SetVar ("/Settings/Clients/Client 0/Use" , "TRUE")

    [15:17:39] RSTD.SetVar ("/Settings/Clients/Client 1/Use" , "FALSE")

    [15:17:39] RSTD.SetVar ("/Settings/Clients/Client 2/Use" , "FALSE")

    [15:17:39] RSTD.SetVar ("/Settings/Clients/Client 3/Use" , "FALSE")

    [15:17:39] RSTD.SetVar ("/Settings/Clients/Client 4/Use" , "FALSE")

    [15:17:39] RSTD.SetVar ("/Settings/AL Client/AL Dll" , "C:\\ti\\mmwave_studio_02_00_00_02\\mmWaveStudio\\RunTime\\SAL.dll")

    [15:17:39] RSTD.SetVar ("/Settings/Clients/Client 0/GuiDll" , "")

    [15:17:39] RSTD.SetVar ("/Settings/AutoUpdate/Enabled" , "TRUE")

    [15:17:39] RSTD.SetVar ("/Settings/AutoUpdate/Interval" , "1")

    [15:17:39] RSTD.SetVar ("/Settings/Monitors/UpdateDisplay" , "TRUE")

    [15:17:39] RSTD.SetVar ("/Settings/Monitors/OneClickStart" , "TRUE")

    [15:17:39] RSTD.SetVar ("/Settings/Automation/Automation Mode" , "false")

    [15:17:39] RSTD.Transmit("/")

    [15:17:40] RSTD.SaveSettings(): Settings saved to "C:\Users\admin\AppData\Roaming\RSTD\config.xml"

    [15:17:40] RSTD.Build()

    [15:17:40] RSTD.SaveSettings(): Settings saved to "C:\Users\admin\AppData\Roaming\RSTD\config.xml"

    [15:17:40] RSTD.Transmit("/")

    [15:17:40] RSTD.AL_Build()

    [15:17:40] RSTD.AL_LoadXml()

    [15:17:40] RSTD.Transmit("/")

    [15:17:40] RSTD.AL_Init()

    [15:17:40] RSTD.Clients_Build()

    [15:17:40] GM: Init

    [15:17:40]  GM: Loaded 'C:\ti\mmwave_studio_02_00_00_02\mmWaveStudio\Clients\\LabClient.dll'

    [15:17:40] GM: 1 Guest (s) init

    [15:17:40] GM: 1 Module(s) init

    [15:17:40] GM: 2 Tab   (s) init

    [15:17:40] RSTD.Client_LoadXml()

    [15:17:40] [RadarAPI]: Starting Matlab Engine..

    [15:17:53] [RadarAPI]: Matlab Engine Started!

    [15:17:58] [RadarAPI]: ar1.LoadSettings('C:\Users\admin\AppData\Roaming\RSTD\ar1gui.ini')

    [15:17:59] TESTING = false

    [15:17:59]

    [15:17:59] ***Script completed successfully.***

    [15:18:03] [RadarAPI]: Opening Gpio Control Port()

    [15:18:03] [RadarAPI]: Status: Passed

    [15:18:04] [RadarAPI]: Opening Board Control Port()

    [15:18:04] [RadarAPI]: Status: Passed

    [15:18:05] [RadarAPI]: ar1.FullReset()

    [15:18:05] [RadarAPI]: Status: Passed

    [15:18:05] [RadarAPI]: Closing Board Control Port()

    [15:18:05] [RadarAPI]: Status: Passed

    [15:18:06] [RadarAPI]: Closing Gpio Control Port()

    [15:18:06] [RadarAPI]: Status: Passed

    [15:18:06] [RadarAPI]: ar1.SOPControl(2)

    [15:18:06] [RadarAPI]: Status: Passed

    [15:18:06] [RadarAPI]: ar1.Connect(40,115200,1000)

    [15:18:08] [RadarAPI]: Error: Connection failed: Calling_ConnectTarget returned 3

    [15:18:08] [RadarAPI]: ar1.Calling_IsConnected()

    [15:18:08] [RadarAPI]: ar1.SaveSettings('C:\Users\admin\AppData\Roaming\RSTD\ar1gui.ini')

  • Hi,

    Can you please follow debug information in the links below

    BR,

    Charles O

  • Hi,

    The rs232C connectivity issue has been resoved by rs232c pin connection eventually.

    The rs232C connection between module and DCA B'd should be disable. (TRx are connected with 60pin connector by '0 ohm' resistor)

    Anyway, Thank you so much for your help.

    Best Regards,