• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 50 subscribers
  • Views 1234 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.

Problem when trying to debug SimpleBLEPeripheral in IAR

Jun Li
Prodigy 225 points
Other Parts Discussed in Thread: CC2540

I am learning to compile and program on CC2540 Mini Development Kit. According to "TI CC2540 Bluetooth Low Energy Developer's Guide (SWRU271 Version 1.0) page 26," it says that after make the project as long as I connect the keyfob using a CC debugger, I can just press "Debug" button in IAR to download and program the keyfob. However, I connected the keyfob using the CC debugger in the kit, and the LED on the debugger is green. When I press the "Debug" button in IAR, it shows the following window ("Target selection"):

Because it's empty, so I can do nothing but press "Cancel," then a dialog box shows:

And back to the main window with some error message at the bottom:

Could somebody help me on this? I would like to know that if I missed anything that I should do so that I cannot program the keyfob as in the Developer's Guide.

Furthermore, I have another question. In IAR, after I make the project, it seems that the output file is a .d51 file. However, I don't understand what is the difference between .hex files and .d51 file. How can I convert a .d51 file to a .hex file? If I can do so, then I will be able to use SmartRF Flash Programmer to program the keyfob, which only accepts .hex file.

Thank you very much in advance.

  • 0
    TI__Genius 17975 points

    A few points:

    1. Have you downloaded all of the latest patches from IAR? If not, they might be the reason you don't see the debugger / device on there.

    2. For the keyfob, you want to use the "CC2540DK-MINI Keyfob Slave" configuration, rather than the "CC2540 Slave" configuration.

    3.In the IAR options, under "linker" in the "output" and "extra output" tabs, you can set the extra output type to Intel extended hex format.

  • 0 in reply to Willis1
    Prodigy 225 points

     

    Hi Willis,

     

    Thank you very much for your prompt reply.

    I found that I missed the latest patch, which is "IAR Systems Embedded Workbench for 8051 patch 7.51M". After applying the patch, I can program and debug through IAR now. Many thanks.

    Regarding the other question, I looked into the extra output tab but I am not sure which options in "Output" and "Extra Output" I should set in order to get the correct .hex file for CC2540 Mini Development Kit. For example, like "Format variant" and "Module-local symbols" in Output tab and "Output format" and "Format variant" in Extra Output tab. Could you kindly let me know which options I should set? Thanks.

    Best wishes,

    Jun