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.

IWR6843ISK: Cannot connect to COM Port

Part Number: IWR6843ISK
Other Parts Discussed in Thread: MMWAVEICBOOST, , UNIFLASH, IWR6843

I have been struggling over a week now since I cannot connect the IWR6843ISK + MMWAVEICBOOST to my windows 10 PC.
It went well by the cloud version Visualizer on the first day but from the 2nd day on I cannot connect at all. It falls into an infinite loop trying to connect to the CFG port. The com port is successfully identified by Windows in the Device manager and I have tried to update all the com port drivers via the SDK 3.3 and the latest XDS110 drivers but no luck. There is no LED error on the board as far as I can tell. There are no other apps using the COM Ports and I have also updated the COM Port assignment. I downloaded TI Uniflash Version: 5.1.0.2397 to flash the latest demo by flash mode but it cannot connect to the COM port neither. I tried with a different Windows PC, stopped Windows Defender, tried new USB Cable, rebooted board (NRST and Power), Application, and Windows with no luck.I am clueless now. Can I get any support for this?  

  • Former Member
    0 Former Member

    Hello,

    Can you try another PC and see if you have the same issue?

    Otherwise - can you use the Device Manager to manually assign the COM ports numbers (try something like 3 and 4) and then try connecting to it again. There have been cases where Windows has a hard time when COM ports go in the hundreds.

    Amanda

  • Hi Amanda,

    I tried on a different Windows 10 PC and it is the same.

    I also tried to assign the com port number from app:4 data:3 to 5/6 respectively and it was the same.

    Regards,

    Cole 

  • Former Member
    0 Former Member in reply to user6187385

    Hello Cole,

    You are still having issue having issue even flashing the EVM? Can you please provide pictures of the EVM to check your switch settings? And a screenshot of the error you see using UniFlash. 

    Thanks,

    Amanda

  • Hi Amanda,

    These are the screenshots.

    Regards, Cole

  • Former Member
    0 Former Member in reply to user6187385

    Hello Cole,

    Thanks for providing the images, the DS2 yellow LED (above the FTDI USB on the carrier board) should be ON when you are in the SOP mode for flashing. After setting up the EVM can you ensure that you press the NRST button (hold for 1-3sec) and then release? Does the LED come on? If yes you should be able to flash. If that LED isn't coming on then the SOP mode isn't setting correctly.

    Amanda

  • Hi Amanda,

    I have pressed the NRST button several times as you have instructed but that does not turn on the DS2 LED.

    Actually I don't ever recall I have seen it on.

    I have also confirmed that the LEDs for D5 and D7 are correctly on.

    Can we conclude that there is a hardware error unique to my board? Or is there anything else I can try?

    Regards, Cole

  • Former Member
    0 Former Member in reply to user6187385

    Hello Cole,

    Thanks for continuing to work through this.

    From the pictures you provided - you have a Rev A carrier board (I assume this was ordered awhile ago since we've been shipping Rev B carrier boards since ~March). In Rev A carrier boards some EVMs experience an issue with latching to the correct SOP mode. The SOP 5 setting will not latch if the power cycle is only via power supply. NRST must be pressed at least once after changing the jumpers in order for the flash mode to work. This is why I asked you to follow this procedure:

     EVM unpowered, no USB plugged in, SOP0 and SOP2 ON (for flashing mode). Then plug in USB then power. You should see that the Yellow GPIO2 LED on the top right of the carrier is off. (This indicates that it is not in flashing mode). Hit the NRST switch once. Does the Yellow LED come on – it should ? 

    Previously, in boards where this has been an issue ensuring NRST is held for 1-3sec has resolved the latching issue. In your case it does not appear to be for some reason. Can you confirm that it's indeed the wrong mode by following the procedure below and then we can provide resolutions if it's the case:

    0. Install CCS: http://processors.wiki.ti.com/index.php/Download_CCS#Code_Composer_Studio_Version_8_Downloads

    1. Launch CCS
    2. In menu bar go to View > Target Configurations; Then in the Target configurations window go to User Defined and  select IWR6843.ccmxl; Right click and select Launch Configuration (See mmWave SDK user's guide if you haven't created the CCMXL file previously)
    3. Right click on the debug probe for CORTEX_R4_0 >  Select Connect Target
    4. In the menu bar go to View > Memory Browser; In the memory browser field box type 0xFFFFE268
    5. The value should be 5 (since carrier board has jumpers for SOP 0 and 2 in ON position)
    6. Instead, if you have the value 1 press reset many times repeatedly until see the correct value latch (5).
    7. Then open Uniflash and should be able to follow the normal flashing procedures.

    Amanda

  • Hi Amanda

    I will be out for a few days but I will work on your advices hopefully by the end of next week.

    Regards,

    Cole

  • Hi Amanda,

    I tried to go through your advised steps here is the outcome.

    Trial 1: flash mode->USB->power-> NRST

    Result: No luck, GPIO2 LED does NOT turn on

    Trial 2: Install CCS->define configuration-> save-> launch configuration -> connect target (debug probe for CORTEX_R4_0)

    Result: Error message as shown

    Pressing the NRST button and Retry button shows the same message.

    (Windows Defender asks for permission to install/execute CCS and I granted access but) I also tried turning Windows Defender off and it was the same.

    I also tried "show all cores" in debug view and tried to start CS_DAP_0 by itself but I got the same error as well.

    Any suggestions?

    Regards, Cole

  • Hi Amanda,

    About 20 days have passed and we need to get to the bottom of this problem.

    I think the DAP problem is the same as the COM Port problem. So in all, I assume there are 2 problems with my hardware.

    1) Flash mode problem (NRST does not solve)

    2) COM/DAP Port connection problem.

    Best Regards, Cole

  • Former Member
    0 Former Member in reply to user6187385

    Hello Cole,

    Please refer to your message inbox to resolve this.

    Amanda

  • Thank you Amanda,

    Is it possible to receive 6843 ISK ES2.0 rather than ES1.0 so that the latest SDK can be applied?

    Also, if you could give us an outlook on how many days it will take, it would help.  

    Regards, Cole