• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 281 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC1350: How do you get a Launch XL CC1350 board back to its virgin state

Shawn Terry
Prodigy 250 points
Part Number: CC1350

I have two Launch XL CC1350-4 boards

The first board I have had for a while and initially ran the BLE stack and application on it and this ran fine.

Then I tried some other examples and a project of my own derived from a sample.

Recently I went back to wanting to use this board for BLE and flashed the stack and simple peripheral in that order.

It partially works in that it advertises but when I attempt to connect I get an immediate disconnect.

Fortunately I had another identical Launch XL CC150-4 board that I had never used.    I did the same flashing as above to it and it works fine.

As it does not appear that there is any hardware differences (all jumpers same, and no component changes) I am assuming that there is something different in the flash between the two that is causing this issue.

What I guess I am looking for is a complete (all flash memory) flash image that gets the LaunchXL CC1350-4 back to how it came from the factory?

Thanks,

                           Shawn

  • 0
    TI__Mastermind 23356 points
    Hello Shawn,

    The SW that comes pre flashed is the same as in the SDK. Make sure you have the latest SDK which is v2.30

    Regards,
    AB
  • 0 in reply to AB
    Prodigy 250 points

    What project comes pre-flashed?

    This may not matter as here is what I did I erased the flash from within the debugger and verified it was erased via "save memory" it was all 0xFF. Then I tried flashing the BLE stack and App and on the older board the Simple BLE peripheral app advertised but would not allow me to Connect as described initially.

    I then did the same thing (erased fall flash, verified, and then flashed the stack and app) with the newer but identical board and the same app worked fine on this board. This would seem to indicate it is not anything to do with what is in flash.

    However the issue is Indeed strange.

    Any ideas on possible cause?

    My initial thought here is that there is an uninitialized variable in the stack or app and depending on the state of RAM at powerup I may be hitting this. In my experience a specific device will start RAM cells out in about the same state each powerup (not really random) so an uninitialized variable would affect a specific board rather consistently.

    Does TI clear RAM to zero in the startup ROM before passing control to the SW in flash?? Most do not.

    It is also possible this is just a random instability but that is rare on a micro-controller.

    I will purchase one more of these boards (they are pretty cheap) and see how the third one behaves.

    Does the 128KB of flash memory represent all the persistent storage on the CC1350?

  • 0 in reply to Shawn Terry
    Guru 735685 points

    If you install BLE Device Monitor, you can find prebuilt CC1350 FW under C:\Program Files (x86)\Texas Instruments\SmartRF Tools\BLE Device Monitor\firmware\cc1350\launchpad and I believe CC1350LaunchPad_BLE_All_v1_20.hex is the one shipped with CC1350 LanuchPad. I attach it for your test.

    8875.CC1350LaunchPad_BLE_All_v1_20.zip

  • 0 in reply to YiKai Chen
    Prodigy 250 points
    YK,

    Thanks the Zip helped my figure out what was going on still not sure why.

    It turns out I had paired with the older board in the past and so in the BLE scanner it said it was BONDED apparently when this is the case the scanner fails to connect. By telling the phone to Forget the device it was no longer bonded and I could then connect. So now the old board is again working fine both with the FW you sent me and with the simple peripheral stack+app.

    I do have a related question though. The CC1350 User Guide seems to say that the factory Config that I assume contains the BLE address is in flash? I erased all of flash and then read back 0-1FFFFh and got all FFh and as a result assumed that I cleared the factory Config also (and was a bit worried about this) but it seems that it retained the old BLE address, I assume in the factory Config? Can you explain how the factory Config information works??
  • 0 in reply to Shawn Terry
    Guru 735685 points
    BLE address is configured in CCFG which you can refer to chapter 9 in www.ti.com/.../swcu117h.pdf