CCS/CC3220SF-LAUNCHXL: code upload error 2131 @0x0 in ubuntu

I have cofigured the device to be in development mode through uniflash in windows but it still shows the same error in ubunutu CCS after the entire process.

Hi,

Error -2131 is described in the reference below (just search for the error number).

It seems the SOP jumpers are in the correct position, therefore the suspicion falls into two possible root causes: either the firmware is somehow blocking the JTAG access or the target configuration file is incorrect.

You can try to test different projects to try and isolate the root cause for this connection error.

The target configuration file should be configured as shown below:

In the setup above, I am using CCSv8.3.0 with Ubuntu 16.04 and a CC3220SF Rev A launchpad board. 

Hope this helps,

Rafael

the target configuration file is correct because it has been tested across both ccs and energia on 2 laptops and resulted in same error. It looks like firmware is somehow blocking the JTAG access. How should i resolve it ?

Hi,

Can you post here photo with jumper configuration on LaunchPad? Do you use SWD (2-wire) or 4-wire JTAG?

Jan

above is jumper configuration and XDS110 verificarion result from ccs8

Hi,

Sorry, I don't see any image.

btw ... If I am not wrong, CC3220SF LaunchPad is not fully supported by Energia.

Jan

energia supports cc3220sf . I have previosly worked with this board on energia. But this Ihave tried on CCS8 along with energia. Uploading any sketch gives same error.

Hi,

Results of "Test connection" commands looks interesting. Jumpers configuration is OK.

If I am not wrong. Energia builds code into RAM in case of CC3220SF is selected and allows upload code into RAM only. XIP flash at CC3220SF chip is not supported by Energia.

Jan

in case of CCS8 project ..upload shows the same error.

Hi,

The jumpers match what I have here, but the test connection shows error -233, which is different than before and the screenshot shows a Windows view - wasn't the issue only happening in Ubuntu or did I miss something?

In the photograph the board seems that it has no power at all - no LEDs turned on. When you plug it to the USB to the faulty host, can you be sure that D1, D2 and D4 are on when you plug the board to the host? Especially D1, which is lit when the device is not in reset.

By the way, I can re-create the same error if I keep the top Reset switch (SW1) pressed and try to run the Test Connection, thus my suspicion the device is somehow being held in reset. I also get the same error if a jumper is missing from one fo the main JTAG signals (TDI/TDO/TCK/TMS), which would also explain this same error. I would double-check to see if you do not have an intermittent contact in one of the jumpers - it has happened to me before, where moving the board from one place to another was enough to disconnect a pin and cause it to fail.

>> the target configuration file is correct because it has been tested across both ccs and energia on 2 laptops and resulted in same error. It looks like firmware is somehow blocking the JTAG access. How should i resolve it ?

The target configuration file is not used by Energia and its programming is not done via the XDS110 but via serial, thus being a very different method. What is the CCS and OS versions of the working hosts?

Regarding the firmware, can you try to re-flash the service pack to the device and see if you regain control?

Regards,
Rafael

This is on windows, I tried with ubuntu the same error was there. Since earlier board was working on windows so i tried again on windows. But now the same error in windows too.

the power is there .I am attaching the image for the same.

I am using CCS8 and windws 10. The board was working fine earlier.

How do i re-flash service pack to the device if that helps. (Mode should  be Development?)

After re-flashing the service pack onto cc3220sf using unifash the error still persists.

Hi,

After re-flashing the service pack, did you try to flash an example application from the CC3220 SDK? This may help isolate any possible problems rooted on the application firmware.

Regards,
Rafael

Divya,

Please apologize for the delay; I was out for the holidays.

Are you still having this issue? I really couldn't reproduce this here in any of the OSes involved (Linux or Windows).

Regards,
Rafael