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.

BT 1.2 Stack on CC2540 MiniDevKit - debug shows stuck in HAL_BOARD_INIT

Other Parts Discussed in Thread: CC2540

With the upgraded 1.2 BT stack, the program HIDEmuKBD has been changed.  After I download and debug, I see that it never gets out of the HAL_BOARD_INIT routine.  Why?  It worked before using 1.1 stack's program.  Thanks!

  • This file is common, so you can try another proj like simplebleperipheral and see is results are the same. There is some dependency on a 32khz crystal. Also try building with optimizations off and check where single stepping gets stuck in the function. - Greg
  • Hello Greg,

    Thank you for your prompt reply.  Not sure what the issue was but turning optimization off did the trick!  With this new Emulated HID KB project - when I click the button, it's suppose to be advertising - however, my iPhone 4S does not detect it.  Any reason why?  Are there any other BT4 devices out there that would detect this mini key fob running this BLE chip?

  • Do you have a CC2540 USB Dongle? If so you can use it as a packet sniffer. This is a must have for CC2540 BLE development in my opinion

  • I am having the same problems with SimpleBLEObserver getting stuck in HAL_BOARD_INIT while trying to debug it.

    Whenever I run other other projects (Broadcast & Peripheral) that have the exact same configuration with hal_board_cfg.h I do not have this problem and code and functionality is as expected.

    What could be the possible reasons for this getting stuck in the HAL_BOARD_INIT?

    Thanks in advance. 

  • I found that unlike the other projects, the Observer project has the Debugger setting configured to simulator instead of Texas Instruments like the other. Changing this resolved my problem.

    http://e2e.ti.com/support/wireless_connectivity/f/158/t/107363.aspx