• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 39 subscribers
  • Views 152 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CC3235MODS: Error -1170 @ 0x0

Maxime Lorimier
Prodigy 195 points
Part Number: CC3235MODS
Other Parts Discussed in Thread: LAUNCHCC3235MOD, CC3235S, SYSCONFIG

Bonjour, 

After testing the LaunchCC3235MOD dev boards thoroughly, we made a custom board. We are currently trying to program the module without success, we have the error : 

CS_DAP: Error connecting to the target: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.4.0.00129) 

Please note:

-We tried to lower the speed of TCLK to the maximum without success

-The JTAG pass test has been successfully completed in code composer studio

 

Schematic: 

With: 

R27 / R40 / R44 / R26 / R35 / R23 : Not connected 

R31 = 100K

Debug probe : 

We use JTAG Out from the "LAUCHCC3235MOD" dev board to program our module. 

Soft: 

Before we try our program we try the CC3235S LauchPad "empty" project  in Resource Explorer

  • 0
    TI__Mastermind 38980 points

    Hi Maxime,

    All devices ship in production mode (versus LaunchPads that ship in development mode). Before you can connect the JTAG, there must be a development image flashed to the module. See SysConfig ImageCreator Basics for more details.

    Best regards,

    Sarah

  • 0 in reply to Sarah P
    Prodigy 195 points

    Hi Sarah, 

    I can't program an "empty" image, I get the following message: 

    INFO:root:FTDI not detected, trying XDS
    INFO:slbootloader.slbootloader:Connecting to device
    INFO:slbootloader.slbootloader:Power off
    INFO:slbootloader.slbootloader:Set break signal
    INFO:slbootloader.slbootloader:Power on
    Traceback (most recent call last):
    File "<string>", line 5262, in <module>
    File "<string>", line 5258, in main
    File "<string>", line 5228, in cmdline
    File "<string>", line 4653, in command_sysconfig_create_image
    File "<string>", line 2498, in create_image_from_sysconfig
    File "<string>", line 1567, in connect_device
    File "W:\slbootloader\slbootloader.py", line 409, in connect_with_reset
    File "W:\slbootloader\slbootloader.py", line 271, in _expect_ack
    File "W:\slbootloader\slbootloader.py", line 302, in _read_data
    slbootloader.slbootloader.BootLoaderError:
    Error: SLImageCreator.exe: BootLoaderError, Timeout reading data
    SLImageCreator returned -1
    Appuyez sur une touche pour continuer...

    Do you know where this can come from?

    Do you know what "capacity" refers to? Why can we choose?

  • 0 in reply to Maxime Lorimier
    TI__Mastermind 38980 points

    Hi Maxime,

    How are your SOP pins configured? Do you have UART and reset pins connected?

    The ImageCreator tool is the same for module and IC. Since the IC requires the external serial flash to be provided, the customer can choose the capacity. This is irrelevant for the module.

    Best regards,

    Sarah