CCS/CC3220S-LAUNCHXL: CC3220S-LAUNCHXL

nethra v

Part Number: CC3220S-LAUNCHXL
Other Parts Discussed in Thread: CC3220S, ENERGIA, UNIFLASH

Tool/software: Code Composer Studio

subject : Issue in programming CC3220S - launch-xl.

I tried programming the launchpad initially but found that it needs to be put into the development mode before coding it.

Followed the instructions found in one of the forum discussions and fortunately was able program the board.I used the Energia IDE and was able to burn one of the example codes on to the launchpad with all success.

Later, I found that the code is just put into the SRAM and not into the flash and hence the code is erased once the board is reset. To tackle this issue, I decided to program the board using CCS7, SDK and uniflash where I was supposed to create an image with several certificates to sign it. It all worked well until the last moment where there was an error which said "operation failed: fs_programming error: ret-10289,ex_err:2633- FS_WRONG_SIGNATURE" . Now I try to debug the code using ccs7 but find this error while doing so..

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 7.0.48.0)

Unable to connect to target board.

I'm stuck up and need help for the following.

1. how do I put the code into the flash memory of the launchpad?(I have used SDK, CCS7 and uniflash and followed the instruction provided in the document www.ti.com/.../swru461a.pdf)

2. Can I download the code directly using CCS7 without uniflash? if yes, how do I do it? I'm not able to debug/download the code in CCS7. I get the error I mentioned above.

3. How do I solve the issue with errors related to certificates and wrong signatures in uniflash?

4. Also, is there any way I can put an energia code into the flash memory of the launchpad?

Any inputs regarding this is rea helpful and really appreciable.

Thanks in advance.

Regards,

Nethravathi V

over 7 years ago

0 desouza over 7 years ago

TI__Guru**** 171224 points

Nethravathi,

I suspect the problem is more fundamental: the CC3220S device does not have internal programmable Flash memory, that is probably why you are seeing your code being written to SRAM only.

Given you seem to need help with the procedure to Flash this device using Uniflash, I will notify the CC32xx group so they can help you with additional details about how to perform code development with this particular device.

In the meantime, please check the following relevant documents for help with both the Image Loader tool of Uniflash and the flash memory itself:
www.ti.com/.../swru469a.pdf
www.ti.com/.../swra515a.pdf

Regards,
Rafael

0 Michael Reymond over 7 years ago

TI__Mastermind 40965 points

Hi Hethravathi,

As Rafael mentioned, using the debugger just puts the code into SRAM, and not on the external flash. In order to make your code persistent on reset, it needs to be present on the external flash.

The most straightforward way of doing so is to use Uniflash, following the steps in the quickstart guide that you linked. To address the issues that you have encountered:

1. The "wrong signature" error means that the CC3220 cannot verify the signature of the binary. Binary signature verification errors can be due to a few things that you should check for in your project:

The trusted root certificate catalog needs to contain the top-level certificate in the chain used to sign the device binary. Check over steps 1-2 in the quick start guide (pg 24) and ensure that your Uniflash project has the same settings as Figure 2-10.
You need to have all of the certificates in the chain used to sign the image present in the device filesystem. Check over steps 3-4 in the quick start guide and ensure that you have the required dummy-* files loaded.
When adding the binary (the MCU image), you need to specify one of the dummy keys as the private key file name, and indicate which certificate on the filesystem it corresponds to. Make sure that the dialog box to add the binary looks like Figure 2-24 (pg. 28).

2. The debugger error -1170 in your case might be due to the device not being programmed successfully, or with the wrong settings. The CC3220 must be flashed using Uniflash with the development flag selected. This is a Uniflash project-level setting that must be set when first creating the project. If you look at Figure 2-8 (pg. 23) of the quick start guide, there is a "device mode" toggle switch. This must be set to "develop" in order for the JTAG interface on the CC3220 to be unlocked. Once you flash an image using a development-enabled project, the JTAG should work once again.

Try those steps and let me know if you still have any questions or problems.

Regards,

Michael

0 nethra v over 7 years ago in reply to Michael Reymond

Prodigy 80 points

Hi Michael and Rafeal,

Thanks for your reply.

I tried with the your inputs. Now, I'm able to program the board using uniflash. But the program won't execute after the programming is completed.

I did further digging and found this tool "Image programming" in CC3x20_Embedded_Programming_2_0_0 and used it too. I receive a "FINISHED OK!!!!" in the prompt. But the program won't execute (I had loaded a simple blink the on board led program).

how do I tackle this issue??

please help me in this regard.

thanks in advance.

Regards,

Nethravathi V

0 nethra v over 7 years ago in reply to nethra v

Prodigy 80 points

also, please let me know if I have to do any settings on the board like pulling up sop2 or anything else.

Code Composer Studio™︎

Code Composer Studio forum

CCS/CC3220S-LAUNCHXL: CC3220S-LAUNCHXL