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.

CC3200 "Error Connecting to the target"

Other Parts Discussed in Thread: CC3200, UNIFLASH, CC3100, CC3200-LAUNCHXL, ENERGIA

I have a CC3200 launchpad and have been using this successfully for weeks, but now I have a problem connecting.


I have all of the jumpers in their default positions...

It seems that I cannot connect to the target for executing/debugging or even flashing using uniflash, unless the "Access Point Mode" jumper is in place (i.e P1-P58).

If I try to run one of the example projects without the P1-P58 jumper in place I get the following error message "Error connecting to the target".

If I try to run the sample example project with the P1-P58 jumper, if downloads and begins to execute then I get the following errors: "Cortex_M4_0: Error " and "Cortex_M4_0: Unable to determine target status after 20 attempts"

I have tried going back and re-running the example projects, but I cant connect any more.

Thanks for your help.


Paul

  • Hi,

        Using Uniflash format your CC3200 Launchpad with settings, 1 MB and secure and alert option left unchecked.

        Remove the jumper at P1-P58 and place it at SOP2 before formatting. Then try a example program and see if it works.

    - kel

  • Hi Paul,

    you are describing a case where you cannot debug or flash (which connects to the target on two different interfaces). It might be that your device got broken somehow but before we jump into conclusions, please share more details:

    • can you try to remember the procedure you took before it happened? any information is valuable
    • have you ever flashed the device before? more specifically, have you flashed the latest service pack 1.0.0.1.2?
    • what Launchpad version are you using?
    • also, please make sure you do not have another FTDI based board connected to the PC while Launchpad is connected. It has been observed that CCS cannot connect in this constellation
    • With Uniflash, also verify no other utility grabs the same COM port and that SOP2 jumper is connected

    Shlomi

  • Hi Markel,

    Thank you for your reply.

    I have the jumper SOP2 (FLASH) installed.

    I tried formatting with Uniflash but when I remove the jumper P1-P58 I cannot connect to the CC3200.

    Regards,

    Paul

  • Hi Shlomi,

    Thank you for your reply.

    - In regards to the procedure I took before this happened. I didn't really do anything... I was using the board happily for a couple of weeks, then I didn't use it at all for 2 weeks. Now when I come to use it again I cannot connect to it (unless the P1-P58 jumper is in place).

    Previously I had followed the procedures in: Project0 (http://processors.wiki.ti.com/index.php/CC32xx_Getting_Started) and some demo applications (specifically: WLAN, TCP/IP Socket, FileDownload, TFPT Client, SmartConfig and SSL example projects). I don't believe I did anything other than instructed to in these example projects.

    - I have flashed the device before and specifically - service pack 1.0.0.1.0

    - The launchpad board is Rev3.2

    - I have CCS version 6.0.1.00040

    - I don't have any other FDTI devices connected.

    - Nothing else is on port 28 (CC3200LP Dual Port)

    When I try to connect to the device (without the P1-P58 jumper is in place) - I get the error "Cortex_M4_0: Error connecting to the target ".

    Regards,

    Paul

  • Hi,

    I do not see the relation to P1-P58 jumper as it is just a GPIO for AP role.

    Are you saying that with this jumper connected you are able to connect to the target? is it valid also for Uniflash connection?

    Shlomi

  • Hi Shlomi,

    Yes that is correct.

    I can only connect to the CC3200 target (using Uniflash or CCS) with the AP jumper (P1-P58) connected.

    Without this jumper connected, I cannot connect to the target.

    Please advise.

    Paul

  • Very strange,

    I'll forward your query to an HW engineer for further debugging.

    Shlomi

  • Shlomi,

    Yes it is very strange. Doesn't this corroborate your original comment on Nov 18th: "It might be that your device got broken somehow" ??

    Regards,

    Paul

  • Well, this would be my guess as you are not able to debug or connect via Uniflash (where each uses a different interface). However, the last finding on P58 cannot explain why you suddenly can interact with the device.

    I'm trying to find out whether there is a rational behind it.

    Shlomi

  • Can you check if the jumper J12 used to power the CC3100 is correctly installed. Check for any loose connection there, may be a dry solder on the jumpers.

    Can you also check the voltage on J12 . It should be close to 3.3V.

    Also make sure that no other boosterpacks are attached to your board.

    Can you also connect using the SWD mode. SOP[2:0] = [001]. You will have to select appropriate target configuration in CCS to do this.

  • I had the exact same problem while I was trying to unravel the GPIO mess.  I had PinMux generate the code to set all GPIO points to output.  The goal was to turn them off one at a time to re-create the GPIO chart.  I am simply trying to find two pins next to each other where I can place a jumper.  Seems simple enough.

    I finally found that 15 and 17 would work.  I could toggle them.

    However, the following setup, generated by PinMux causes the problem:

    PinTypeGPIO(PIN_17, PIN_MODE_0, false);
    GPIODirModeSet(GPIOA3_BASE, 0x1, GPIO_DIR_MODE_OUT);

    Pin 16 should give the same result.  Although the documentation shows 16 and 17 as a general purpose io points (A3 0x01 GPIO_23 & A2 0x80 GPIO_24) and the schematic shows them going to GPIO_23 & 24 they also run through headers J10 & 11 to JTAG_TD0 and 1 so there is no joy in removing the jumpers. 

    So I am still looking for two points to jumper.  Any ideas?

    Bob Roth

  • Hi Prajay,

    Thanks for your reply.

    Just to be sure we are talking about the same board. I am using the CC3200-LAUNCHXL not a CC3100.

    Jumper J12 is installed and I measured the voltage at 3.3V.

    There are no boosterpacks attached to the board.

    I have tried connecting to the board with the following SOP[2:0] settings:

     - 000:JTAG

     - 001: SWD

     - 100: FLASH

    For all of the above configurations I get the error message: "Cortex_M4_0: Error connecting to the target ".

    Thanks,

    Paul

  • Hi Bob,

    Good to know that other people have the same problem.

    Have you tried the Jumper settings described above?

    Regards,

    Paul

  • Hi Paul,

    Once I removed the setup for PIN 17 the problem went away.  Check your pinmux.c.

    Tried the SOP settings:

    000 Program Fails

    001 Cortex_M4_0: Err...

    100 Sunshine, blue skies and clear sailing!!

    Have you noticed that pin 55 is not connected to reality?  Also, still looking for two adjacent GIO pins that work!!!

    Bob

  • Robert Roth said:

    Once I removed the setup for PIN 17 the problem went away.  .

    I had the same result.

    It doesn't make much sense. But it worked.

    Thanks!

  • Hi Paul, Robert,

    Just to recap, originally you were describing a case where you cannot debug or flash (which connects to the target on two different interfaces). Are you saying that cofiguration of PIN_17 solved both? are you able to use Uniflash and flash the device?

    PIN_17 configuration (if you added it to the binary mcu image) is executed prior to connecting the target via UART. This is why it sound strange that this was the problem.

    Shlomi

  • I experienced the same issue. But I can solve it by just re-plug the USB cord several times without changing any code.

    Long
  • Hi Bob,

    I am a newby programming with CCS, could you please be more specific about how to remove the setup for PIN17?

    I am trying to debug the wlan_station example, but I can't find any pinmux.c file in this folder.

    Thank you

    Manuel

  • Hi Robert,

    I just saw pinmux.c at my wlan_station folder. So, it is unusual not to see it there.

    - kel
  • Hi,

    This solution didnt work for me. I'm using a rev 4.1 board. Connected the SOP2 and J8 jumpers. But when I press reset I get the

    Cortex_M4_0: Error
    Cortex_M4_0: Unable to determine target status after 20 attempts

    error. This problem has been there since the first time. I could however, load an example program from energia.

    I'm wondering if this solution different for v4.1?

    Thanks.

    EDIT: I cant get it working with energia anymore. All I've done so far is flash it with uniflash to install servicepack. Since then it the board isnt working anymore.

    Could that be the problem in my case? no matter what jumpers are connected, uniflash doesnt throw error.

  • Hi I am a noob when it comes to hardware since am a software engineer and I came across the same problem .... Similar to yours my program builds correctly when the pin on P1 is there ..... Here is what worked for me...... When you click the debug option in CCS , have the pin P1 connected .... Then opne the TeraTerm and connect it with the right settings of port and buad rate ... Then before you hit the run on CCS , remove the pin P1 now .... It runs successfully .... So in short while debugging P1 needs to be there and when you continue to run , P1 should be removed.
  • I was able to replicate this problem. After checking the jumper at J12, I noted that it was not installed. 

    The HTTPServer tutorial has a jumper installation picture that does not include the jumper at J12. 

    The example works as expected when that jumper is installed 

    I was following the tutorial instrucitons listed here: 

    The 

  • I also experienced this problem, which appeared out of nowhere. CCS was giving me this issue while everything else worked perfectly INCLUDING Uniflash. As it turns out, i had accidentally created new target configurations on various projects, i.e. @ project level target configurations. I don't know what this caused, maybe it corrupted the workspace target configuration. Anyway, i deleted every target configuration, rebooted PC (don't know whether this was necessary) and imported new CC3200 target configuration as per the getting started guide and i was able to debug the program with CCS. Also make sure that for a project the option "Manage the project's target-configuration automatically" (Project properties->General) is not selected, as this creates a project-level target configuration, which can mess things up. Hopefully this may be of use to someone.