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.

LAUNCHCC3235MOD: Facing issue while flashing code to the launchpad

Part Number: LAUNCHCC3235MOD
Other Parts Discussed in Thread: CC3235MODSF, UNIFLASH

PART NO - LAUNCHCC3235MOD

CCS software version -  10.3.1.00003 

XDS110-Based Onboard Debug Probe

Jumper are placed in default settings as per the CC3235MODSF SimpleLinkTm Wi-Fi® and IoTSolution With MCU LaunchPadTm Hardware user's guide.

We are facing an issue , while flashing the code to LAUNCHCC3235MOD board

Error: SLImageCreator.exe: BootLoaderError, Timeout reading data. As shown in the attached image.

Please help us to resolve the issue.

Thank you.

  • What is the SOP settings? (make sure it is 100 or 010)

    Maybe the COM Port is used by another application (terminal app?).

    Are you able to flash using Uniflash? (see https://www.ti.com/lit/swru469)

    br,

    Kobi

  • The SOP settings is 010 , we also tried with 100 settings.
    No, the COM port is not used in any other terminal application.
    No, we are not able flash code to launchpad using Uniflash software.
    We are getting a same error ,when we give connect in the Uniflash software. As shown in attached image.
    We also checked with debug session in CCS software, we are getting error.
    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.3.0.00058).

  • This is very strange. Have you tried a power cycle for the device (plug the USB out and then back in)?

    What version of uniflash and CCS are you using?

    Can you test using different PC? different board?

  • Yes, we have tried to unplug the device and plugged it again.
    CCS Version      -  10.3.1.00003 
    Uniflash Version:-   6.3.0.3193
    We checked with different PC with uniflash software , we are facing same issue,  No we don't have another board.

    The device is showing in the device manager as well device is able to detect in the uniflash software.

  • don't use the auto detection in uniflash home screen (change this to manual mode and select the "new configuration" yourself, then start ImageCreator).

    Have you gone through the getting starting guide?

    Please send a photo of the launchpad.

  • hello kobi,
    we have selected manual and selected new configuration , we have followed getting started guide . we have selected development mode. As shown in attached image below.

     

    When we give connect ,it will throw the error. Operation failed:Error: SLImageCreator.exe: BootLoaderError, Timeout reading data. 

    Board jumper settings are same as per the default settings given in the user guide, we have not changed any jumper settings.

  • ok. I'm not familiar with a similar issue.

    I assume you have never worked with board before?

    It seems like an issue with the board but this is very uncommon. 

  • hello kobi.
    We were working on this board from past 20 days , We have checked with example code earlier. All of sudden this error started to come 3 days ago, when we try to flash the code. I have seen similar issue faced by so many people in the forum. Some got resolved by a factory reset or other methods. How can i perform factory reset of the device using SOP combination. So that ,factory image starts running on the board.

  • if you enabled the factory reset in your previous Uniflash programming (General Settings -> Restore To Factory Image SOP == Enable), then the device will revert to the factory default upon setting SOP to 011 during reset .

  • It was programmed last using CCS software. General settings is as shown in the attached image.

    We turned off the device made SOP to 011 plugged it again and pressed the reset button.


    I checked in terminal (application ) no factory image is running on the device.

  • what was the MCU image that was used in the last programming?

    was it a working (functional) code?

    Are you able to use the debugger to download and execute code?

  • The last MCU image was loaded SPI master example code. It was working (functional). In the terminal it was able to display the data using the same debug probe.

  • Are you able to use the CCS debugger? 

    When you say the SPI Master was loaded, i assume you mean it was programmed to the external flash (and not loaded with the debugger - to the internal XIP flash).

    It seems like the board got damaged somehow.

    I will need to consult regarding the next steps.

  • Hello kobi,

    This is the error we get in CCS debugger.

    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.3.0.00058).

    SPI master example code which is imported from SDK . It was programmed to communicate with external SPI peripheral, nothing to do with flash.

  • i'm not asking about the functionality of the app, but about the way you downloaded it to the device (did you use the uniflash / CCS "Flash" option which write the app to the external flash or you used the CCS "debug" option which only write to the internal flash).

  • We always used "Flash " option in CCS  Software, we never downloaded using uniflash software. So we were always programming to the external flash.

  • ok (just to clarify, using CCS "Flash" is the same as using Uniflash - both program the external flash. CCS "Debug" (the green "bug" icon) is writing the MCU image directly to the internal XiP flash). 

  • Hi Matt,

    Just a quick comment...

    • From my point of view it looks like damaged hardware. How looks power consumption of your board?
    • Once you flashed own image into sFlash, factory default feature to OOB will not help you any-more
    • As to be honest I read at this forum many-times that LaunchPad was damaged by connecting wrong external hardware. And because you are using SPI peripheral, I am assuming that you are connecting external SPI device. Be aware that CC32xx pins are not 5V tolerant.
    • Proper function of XDS110 UART you can check by loopback pins RX, TX with terminal software

    Jan

  • Thanks Kobi and Jan for the support.

    Power led D4 which Indicates when the 3.3-V power is supplied to the board is always turned ON.

    SPI peripheral which we connected operates at 3.3V and we had already downloaded the code and checked with the same peripheral many times. We were also able to receive data from the SPI peripheral.

    I checked  XDS110 UART  by loopback pins RX, TX with terminal software, it is working.

    looking forward for your help.

  • Hi,

    How looks power consumption of your board (at SOP mode 1-0-0)? Maybe you can check state of CC_nRESET pin a oscilloscope (you shod see toggling reset during Uniflash connection attempt).

    • In case of jumpers are properly configured (especially J10, J11, J12, J13, J16) ... can you provide real photo of you LP?
    • And set SOP mode (2-1-0) 1-0-0
    • And your XDS110 UART is functional (as you already check)
    • And LED D4 is on
    • And your are not able connect by Uniflash with timeout error
    • I think only explanation is that your hardware is damaged somehow (likely module itself)

    Jan

  • hi Jan,

    After setting SOP position to 100 .

    We checked the nReset during uniflash connection attempt it is toggling.

    I have attached the launcpad image.

  • Hi,

    How much current consume your board at SOP mode 1-0-0?

    I don't see anything noticeable wrong with your LP or jumper configuration. Only idea is that module is damaged somehow.

    Jan

  • Hi, Jan 

    With SOP mode 1-0-0 current consumption is 0.79 mA.

    With SOP mode 0-1-0 current consumption is 0.78 mA.

  • Hi,

    This consumption looks normal. I don't have any idea what you should check next. Maybe you can visually inspect solder joints for a cracks at jumpers row, but I don't see big chance to success.

    I think that your LP is damaged, but please wait for confirmation from Kobi.

    Jan

  • I agree with Jan.

    I'm still checking if there are other things we can do here. 

  • Ok kobi, looking forward for your reply.

  • you can check the customer returns policy in https://www.ti.com/support-quality/additional-information/customer-returns.html

    I don't think there is anything else to try on this board.

    Br,

    Kobi