CCS/UNIFLASH: Reset sensor manually to start execution of code and CLI

Hello,

Regarding:

Slev1n said:

• Regarding CLI, I generated a zip however, I am not sure the correct settings are being applied in my script. Are all settings used which are set in uniflash under the "program" tab?
• How can I modify the script, so that the IEEE 1st MAC address is read and printed?

For the first bullet, yes any custom settings under "Program" and "Settings&Utilities" should be applied. 

For the second bullet, use the "ReadPriIeee" operation.

Example:

> dslite.bat -c .\user_files\configs\cc1310f128.ccxml -a ReadPriIeee

A device expert will reply to your other questions.

Thanks

ki

Thank you for your answer, I tried your approach for the MAC print and it works.

I have to add one thing regarding point 2 from my initial post:

When setting the switch next to button 2 on the launchpad to "XDS110 Power" I was able to choose a reset method, however I still had to set in a battery to make the code start executing.

These are my settings:

Hi Slev1n,

May you please provide more details on how exactly are you connecting your custom HW solution ("CC1310 Sensors board") to the LAUNCHXL-CC1310 debugger for flashing?

Thanks!

We do have a JTAG connection and have a similiar layout to the TIDA 00484 board.

Hey guys,

we have been working on our CLI script using UniFlash. We've been through the documentation provided here: https://processors.wiki.ti.com/index.php/UniFlash_v4_Quick_Guide
as well and do have some questions. We use a cc1310 launchpad and its JTAG connection as flashing device.

1. Although we activated "Board reset (automatic disconnect/connect)" and ReadPrimaryIeee in UniFlash, we dont see them
in the generated ufsettings. Here we can only see the "erase" option we've activated before. Is the only way to enable the
reset and read primaryIeee by employing further commands in the command line interface?

2. How can we make load programm and verify in one command line? The docu states that either -f or -v can be set in one call.

3. We noticed that if we use the command
dslite.bat -c .\user_files\configs\cc1310f128.ccxml -l .\user_files\settings\generated.ufsettings -f .\user_files\images\XXX.hex -e

and then

dslite.bat -c .\user_files\configs\cc1310f128.ccxml -v .\user_files\images\20200220_Sens_NewStorage_b9aef9b_.hex -e

to verify, the verification process works fine for the first time, if we call it again, it fails, always at address 0x00E100.
Any reason why it only works once? In UniFlash you can repeat it as often as you want, however, flashing the software using CLI
and then using verify in UniFlash does not work.

4. We made some tests and noticed, that the generated ccxml file is assigned to a certain launchpad seriel number, i.e. L2000XXX. So,
if another board is connected, the CLI script will fail. Any chance we can somehow adapt the ccxml file so that it uses any cc1310 launchpad
no matter which COM port or seriel number it is assigned to?


Btw. as regarding the "reset" issue from our first post, only if we use UniFlash, we have to manually reset the sensor before it works after flashing, using SmartFlashProgrammer 2 the board is correctly reset and works without further ado.

Just wanted to mention that we are still awaiting your answer.

Hi

Slev1n said:

How can we make load programm and verify in one command line? The docu states that either -f or -v can be set in one call.

You should be able to write your CLI call as

dslite.exe flash -c .\user_files\configs\cc1310f128.ccxml -l \user_files\settings\generated.ufsettings -e -f -v .\user_files\images\XXX.hex

And it should verify after flashing.

Slev1n said:

We made some tests and noticed, that the generated ccxml file is assigned to a certain launchpad seriel number, i.e. L2000XXX. So, if another board is connected, the CLI script will fail. Any chance we can somehow adapt the ccxml file so that it uses any cc1310 launchpad no matter which COM port or seriel number it is assigned to?

If you change the property "Debug Probe Selection" like this, it should work as you like:

From:

<property Type="choicelist" Value="1" id="Debug Probe Selection">
    <choice Name="Select by serial number" value="0">
        <property Type="stringfield" Value="LXXXXXXXX" id="-- Enter the serial number"/>
    </choice>
</property>

To:

<property Type="choicelist" Value="0" id="Debug Probe Selection"/>

I am working on getting the answer for the rest of your questions

Thank you very much, we really appreciate your efforts!