CC2642R: LAUNCHXL-CC26X2R1 - Board issue

From the content of this post it's not possible to state what the issue could be. 

- Do they get this issue for all driver examples in the SDK? 

- How did they flash the device if it gave them warning about a locked interface? 

- Have they only tested on one board or is this issue present on more than one board? 

- Are they able to read out the flash content using flash programmer 2 and are they able to do mass erase using the same tool (if successful the flash should be filled with 0xFF)

Hi TER,

Do they get this issue for all driver examples in the SDK? 

No , I have this problem only with Project Zero  example, Simple Broadcaster seems to work

I tried to uninstal SDK and import Project Zero it again a few times.

How did they flash the device if it gave them warning about a locked interface? 

I used TI  Uniflash utility in conjunction with J-LInk Segger debuger.

Now I work with direct jtag  debug interface without J-Link Segger 

 Have they only tested on one board or is this issue present on more than one board? 

yes, I work only with one board

 Are they able to read out the flash content using flash programmer 2 and are they able to do mass erase using the same tool (if successful the flash should be filled with 0xFF)

I am not sure what is "flash programmer 2 " , I am using  Uniflash utility that I downloaded from TI

yes ,I can read and erase flash and see 0xFF.

Here are the steps I took 

I deleted all projects from workspace :

I imported new Project Zero into workspace

I tried to run it on my  board  via CCS debugger it works

I tried to run it on my  board  without debugger( after power cycle)  -  does not work  

Then I took new board with same freshly imported  project without any changes

I tried to run it on new  board  via CCS debugger - it works

I tried to run it on new   board  without debugger( after power cycle)  -  works as well

It seems like on my original board some read only flash area was cleaned out...

Is it possible?

Can I restore it?

Thanks,

Shlomi

Could you try to run the empty example from the SDK? Based on what you write it could seem that you have an issue with the 32 kHz xtal on your board. If that is the case the empty example should run with the debugger connected and not if you disconnect the debugger and power cycle the board. 

Hi TER,

What do you mean by empty example?

I am currently using  simplelink_cc13x2_26x2_sdk_3_10_00_53 on my linux host machine.

And I imported Project Zero from SDK without any changes.

Should I take another one, can you provide a path to it?

also I found this in documentation :

Halt In Boot (HIB)

There is a bug with the emulation software package that would cause the processor to enter Halt In Boot (HIB) on the next bootup when previously connected to JTAG. In the case of OAD, that is when a system reset is invoked at the end of an OAD procedure

Can it be related

Also 

Thanks,

Shlomi

This: http://dev.ti.com/tirex/explore/node?node=AOFqqK6BKDB4cRZh4.hGCQ__pTTHBmu__LATEST

Empty project working on "problematic board".

What does it mean?