LAUNCHXL-CC1350: CC1350 Flashing using CSS

Meaning that you want to flash one board as concentrator and one board as node? Did you have both lauchpads connected when you did this, could it be that you have flashed a different Launchpad than you think you flashed? The LEDs on the XDS110 part of the LP typically blink when you flash the board.

Test with only one LP connected to the PC.

The debug button (looking like a small bug) will compile and flash the code.

Hi, TER! I tried with only one board connected to PC at a time. I cheked their respective IDs each attempt. The issue is I managed to flash them as a node and concentartor, and even connect the node to the concentrator. Nonetheless, after power-reset the "node" board became concentartor again. And it doesn't matter which one of two boards I flashed with "concentrator" and which as "node". I tired several times: reflashing them with diffrent firmware, making "Node" and "Concentrator" each one. But after power reset they both becoming "Concentartors".  

I have tested this on my side and the "node" doesn't do anything after a reset. I don't have a LCD display here at the moment, it could be that it writes something to the LCD display and not the UART. It could look like it starts on something OAD related after a reset and overwrite the flash with something else.

If  you are not going to use the OAD part I would suggest that you use the rfWsnNode example available under the CC1310 LP and use this (you probably have to set the RF switch on the CC1350 LP to manage to run the example, check one of the basic RF examples for the CC1350 LP on how this is done.) 

If you plan to use OAD later on, follow the description in the examples readme files on how you set on the examples to get a valid OAD file.  

Unfortunatelly, I din't manage to use CC1310 app. I have also tried to use Flash Programmer 2, and the result is the same. The IC don't vene started after flashing. While the verification shows that the binary is there.

And I also tried to disbale OnBoard Debugger using Jumpers. Will be taking further experiments... By the way, if I am trying to flash the board as Coordinator, It works well.

TER said:

What did you try

I tried to debug the rfNode code, to understand why it has been resetted to some undefined state just after reset. 

TER said:

Have you tried this

Yes, I did. Followed this thread https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/534247/bin-file-for-oad-not-getting-generated-cc1350 and afterwards "ProjectZero"http://software-dl.ti.com/lprf/simplelink_academy/modules/prop_05_cc1350lpdm_project_zero/prop_05_cc1350lpdm_project_zero.html. 

Aftewads, I followed your recommendation to use another example, but not for CC1310, and find the next one fro CC1350 (rfWsnNodeBleAdv). 

It preserves the firmware after reset, so it solves my issue.

TER said:

- Why was CC1350 selected (and not the CC1310)

I only have two these boards (LAUNCHXL-CC1350) at a current time in office. And I have to do very trivial prototype, forming "one-to-many" network, to explore how "sensor" will work in our expected environment. The key idea is to extend our HomeGateway, which forms ZigBee Network, with Sub-1GHz devices. I completely understand that we do not need CC1350 device, since it is dual-band. I suppose, we should focus on CC1310 device.   

TER said:

- Why did you select these two examples? Could you use some other examples as a start? 

I followed your advice and managed to connect them together. And the "Node" still works after reset. So I will mark you previous post as resolving my issue. Thank you for your help!

P.S. Unfortunatelly, I didn't solve the issue with the "Node" restarting after power-reset in rfWsnNodeIntFlashOadClient, but that was not my main target.