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.

Using IAR EW 8.10 with Old SimpleBLEPeripheral

Other Parts Discussed in Thread: CC2540, Z-STACK

Hi,

Just started trying to use the CC2540, and hit this problem. I just can not debug anythign right now.

I get the following message after clicking the option to Download&Debug.

 

 

Then after click OK, to a few error windows, the final window shows this status about not having a 'Target device'. Any ideas?

 

  • Hi,

     

    Scott Walsh said:
    I get the following message after clicking the option to Download&Debug

    No message in here, can you repost it please.

     

    How exactly you've connected the cc2540 device, through a smartRF05EB or CC debugger?

    I the connection is through CC debugger, did you apply an external voltage to your cc2540 device?

  • Igor Sherer said:

    How exactly you've connected the cc2540 device, through a smartRF05EB or CC debugger?

    I the connection is through CC debugger, did you apply an external voltage to your cc2540 device?

    I am using a CC deubugger, the LED on the debugger is Green too. Yes power is on the CC2540 device, which is actually a CC2540MiniDK Keyfob.

     

     

  • Hi,

     

    Can you check whether the keyfob detected by the smartRF flash programmer.

  • Will check ...

     

    it also seems the IAR site has changed the link in the developers guide for the CC2540 sends you to http://www.iar.com/website1/1.0.1.0/667/1/ I dont think that points where it should do any longer.

     

    What versions of the IAR tools are other people using for use on the CC2540?

  • I dont have the SmartRF programmer, I find references to it, but no link for downloading that tool. :(

  • Hi,

     

    My bad, here's a link to the smartRF flash programmer download.

    As for the IAR versions, if I'm not mistaken latest BLE stack was compiled with v7.60.

    I myself using the 8.10 for Z-stack (ZigBee) and all is working as should be

  • The compiler, the 7.6 version of the EW8051 tool this time, is giving me the following error trying to load the TI examples applications:

     

    Tue Dec 06 14:36:51 2011: Warning: The device description file: C:\Program Files\IAR Systems\Embedded Workbench 5.4\8051\config\devices\Texas Instruments\ioCC2540F256.ddf  defined on the Project->Options->Debugger page does not exist.

  • Hi Scott,

    Have you checked if the file is found at that directory? If not, you may have to change the searchpath in IAR or add the file to that specific path. I myself has the file at C:\Program Files (x86)\IAR Systems\Embedded Workbench 5.4\8051\inc\ioCC2540.h.

    BR

  • Hi,

     

    As Nick said, you can do some manual adjustments, however if you 

    opened this project in the newer version of IAR and then with v7.60 several

    project files will be overwritten and\or replaced.

    Anyhow, I suggest you to do a clean install of the BLE stack and then open it with IAR v7.60

  •  

    It is a .ddf file which EW8051 is looking for, not a .h file.

    This is a standard project TI ship to evaluate the CC2540 but it does not build.

  • Hi again,

     

    Also should be added, the path to device description files (AKA .ddf) is different in in v8.10 and in v7.60.

  • Igor Sherer said:

     however if you opened this project in the newer version of IAR and then with v7.60 several

    project files will be overwritten and\or replaced.

    Anyhow, I suggest you to do a clean install of the BLE stack and then open it with IAR v7.60

    Yes, Thanks, I did see that 8.10 did open/modify some files.

    I have done as you suggest, and trashed the C:\Texas Instruments\BLE-CC2540-1.1a directory and started again.

    I still get the error I started with.

    And that is 'no target selected'.

     

    This is the worse start to using any Bluetooth tools I have experienced. What started as, lets use this week to evaluate the TI BLE tools, has turned into a waste of time so far. I dont have these basic cockpit errors with other BLE single chip development tools.

  • Let's start all over again...

     

    1. Is the cc2540 device recognized by smartRF flash programmer (while the LED on cc debugger is green)?
    2. Are there any other errors/warnings in IAR, or it is just the no target issue?
  • Igor,

    Yes, it did need to be a case of starting over ... ;)

    The LED on the CCDebugger has been Green the whole time.

    Yes the whole problem has been the no target issue.

    I dont know what it did, but for some reason using SmartRF to load  the file cc2540_ble1.1_SmartRF_SimpleBLEPeripheral.hex from C:\Texas Instruments\BLE-CC2540-1.1a\Accessories\Hex_Files onto the CC2540 MiniDK card, and then running the SimpleBLEPeripheral.eww project file again under EW8051 v7.6 built without an error.

     

    To be clear though, I did have to copy .ddf, .xcl and .h files from EW8051 v8.10 related to the CC2540 chip over to the correct places which the v7.6 tools are looking for.

     

    I do have things running in the debugger though now, even I dont know why what I have done has helped! Always an uneasy feeling.

     

    Thanks for your help.

  • Well, I'm glad it works, after all this time wasted on practically nothing useful.

     

    Scott Walsh said:
    I do have things running in the debugger though now, even I dont know why what I have done has helped! Always an uneasy feeling.

    This is the almighty electronics (and programming), sometimes things just don't work, for no special reason...

    and then, all of a sudden, everything works.

    For example today I did a power consumption measurements to one of the PCBs I've designed,

    when I was jumping** (please don't ask me why I was jumping while measuring power consumption) the power 

    consumption was much larger then it should be, but, placing the same PCB on another table and running the same

    sort of experiment produced no errors as in previous experiment, no matter how high I jumped... The almighty electronics,

    sometimes it works and sometimes it's not. :)

     

    **To be mentioned, there was no physical connection between me and the PCB whatsoever