• State
  • Locked Locked
  • Replies 14 replies
  • Subscribers 52 subscribers
  • Views 3162 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.

Problems Debugging Peripheral BLE Example App on DK

J W
Prodigy 130 points
Other Parts Discussed in Thread: CC2640, CCSTUDIO

Hello,

I've donwloaded the latest CC2640 SDK and installed it, along with the latest CCS. I can import the SimpleBLEPeripheral and the stack, but when I debug, I get something unexpected.

Both the Stack and Application don't stop. the CCS debugger just has the red stop button enabled. In both cases it seems to connect and download the firmware, but for application I get:

Cortex_M3_0: AutoRun: Target not run as the symbol "main" is not defined

I have also tried running with IAR. The debugger complains about the interrupt vector.

Am I missing something?

  • 0
    TI__Guru** 105180 points

    Hello J K,

    Can you confirm the version of CCS CC26xx device support that is installed on your machine?

    Best wishes

  • 0 in reply to JXS
    Prodigy 130 points

    Hi JXS,

    Going to About and looking at the version I see

    CC26xx Device Support 1.13.0.01 com.ti.ccstudio.cc26xx.devicesupport.win32.feature.group Texas Instruments

    So the version is 1.13 vs the 1.12.2 in the documentation.

  • 0 in reply to J W
    TI__Guru** 105180 points
    Hi,

    Can you try doing a Forced Mass Erase with the SmartRF Flash Programmer v2? Then, try the download with IAR or CCS.

    Best wishes
  • 0 in reply to JXS
    Prodigy 130 points

    I downloaded the SmartRF Flash Programmer and selected All Unprotected Pages then did an Erase.

    After this I tried to download the stack using CCS, it did the same thing as before. I pressed Stop and then tried to download the application, same as before.

    I also found the Forced Mass Erase option and used it. Same results

  • 0 in reply to J W
    Prodigy 130 points

    Hi JXS,

    I just took a look at the EM board and noticed it says XCC2650, not CC2640 as I thought. Would this explain the issue (CCS and IAR are compiling for CC2640). What kind of changes do I need to make?

    Why wouldn't the debugger tell me it was the wrong device for the project settings?

    I changed the configuration to CC2650F128, recompiled, but same results.

  • 0 in reply to J W
    TI__Guru** 105180 points
    Hi,

    CC2640 is fine.

    Try doing "CC26xx/CC13xx Forced Mass Erase" from the wrench icon on the SmartRF Flash Programmer v2. This is a different option that what you previously tried.

    Also, just to confirm, you are attempting to debug the Application, not Stack project workspace? The Stack is not an executable and thus can't be debugged from the project level.

    Best wishes
  • 0 in reply to JXS
    Prodigy 130 points
    Hi JXS,

    Perhaps I should have edited my original response. I found the Forced Mass Erase, but the results were the same.

    Yes, all I'm trying to do is to get a basic application running. I don't care about debugging the stack itself, but I can't even run the application and debug it to get the platform running.

    TI Should really expand their section on debugging in the manual, or provide a quick start guide. I don't even know what I should be expecting (should I be stopping at main?) There are no images and the only information are 4 bullet points about compiling and debugging on page 20 of SWRU393.
  • 0 in reply to J W
    TI__Guru** 105180 points
    Hi J W,

    I do apologize if the "Setting up the Development Environment"section of the SW Dev Guide (SWRU393) was not clear enough; the expectation is that the simpleBLEPeripheral project should build and download without errors when the procedure is followed.

    Assuming both the Stack & Application projects build without errors in IAR 7.30.4, can you advise the behavior when the following:

    Stack: Project -> Download -> Download Active Application
    App: Project -> Download & Debug

    The error you initially listed, i.e. vector table missing, typically occurs when attempting to use the Debug option for the Stack. You can ignore this for the Stack, but you should not encounter it when downloading the App. When the App is downloaded, it should run & halt at main(), assuming the project is left as default. The only requirement before running the App is the Stack must already be downloaded (flashed).

    Finally, make sure the App project config is "FlashROM" and not one of the FlashOnly configurations. The default should be FlashROM.

    Best wishes
  • 0 in reply to JXS
    Prodigy 130 points

    I tried this in IAR And still same issue. I never halt in main. You can see the screen I have.

    I tried pressing the hand to halt, it tells me it cannot find some files c:\hudson\workspace\FWGroup-DriverLib\modules\output\cc26xx_cha_2_2_ext\driverlib\chipinfo.c

    It never stopped in main. Trying to put a breakpoint in main I get an error that target is busy.

  • 0 in reply to J W
    TI__Guru** 105180 points
    Hi J W,

    This looks like you may be using pre-release silicon, e.g. earlier than PG2.2. In that case, please see the release notes (Readme.html) or the CC2640 FAQ, Troubleshooting section, in this forum. A config change is required for pre-release silicon.

    Best wishes
  • 0 in reply to JXS
    Prodigy 130 points
    Hi JXS,

    Thank you. That was the issue. The silicon was pre-release and didn't work. We put the latest silicon and now the application gets to main and runs.

    Thank you for your help.
  • 0 in reply to JXS
    Prodigy 240 points

    This fix about silicon helped in my case. But how can I confirm if I have old silicon on not looking on chip? My chip for example has G4 written on it. Does this mean PG4.0, PG2.4 or something else? There is a DK Rev 1.2.6 written on daughterboard but nothing similar to PG2.x.

  • 0 in reply to Tonu Samuel
    Prodigy 240 points
    Typo: "old silicon OR not"
  • 0 in reply to Tonu Samuel
    TI__Guru** 105180 points

    Hi Tonu,

    For production Si markings, you can refer to the CC2640 data sheet. Anything that is not consistent with the data sheet can be considered pre-production. Also, you can determine the PG rev by using SmartRF Flash Programmer 2. In the lower left corner, select the device. The PG rev is shown in the chip details box.

    Best wishes