• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 51 subscribers
  • Views 313 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.

CC2640R2F-Q1: Strange load/run issue

ROGERG
Mastermind 37020 points

Part Number: CC2640R2F-Q1
Other Parts Discussed in Thread: CC2640R2F

Dear Experts,

my customer is using IAR 8.11.2 with BLE stack v1.50.00.58 on custom CC2640R2F board. Their SW is based on our multi_role example with several adaptations and changes.

They are seeing a very strange issue at the moment.

If they use the "Download and Debug" option in IAR and then let the application run --> "Go", everything seems to work fine and they are able to communicate over SPI and also able to see advertising starting and so on ...

If they on the other hand either use FlashProgrammer2 or also IAR to download the application, then do a reset of the board and use it in standalone mode without debugger/emulator connection, the application is not working properly --> SPI communication is not working and thus advertising is not seen. Also if they then connect to the target using "Debug without Downloading" they see, that they are running into ICall timeout everytime.

Any ideas/hints what exactly is going wrong or might be different between "loading and running via emulator" vs. "loading, reset and running standalone or in Debug without Downloading" mode? There must be something set or configured by the emulator in case it is used directly after loading the application image ...

Many thanks and best regards,

RogerG

  • 0
    TI__Guru** 105180 points

    Hello RogerG,

    Conventional wisdom would say so, but it's not always the case that the emulator config is directly resulting in this behaviour. It could be a dependency on an external component that is initializing differently, for example.

    I recommend starting by first performing all the check items on the "CC26xx BLE HW Troubleshooting & Bring Up" article on the TI BLE wiki to confirm the board layout is functioning correctly. Sometimes the JTAG can cover up for layout issues. Then, follow the Initial Board Bringup section in the BLE SW User's Guide to load a simple_peripheral with all IOs / drivers disabled and configured for your antenna layout.  If this is successful, then add your SPI driver and confirm likewise. I further recommend taking logic analyzer captures to compare against working and non-working SPI conditions - that would help isolate where in the execution path something is going wrong.

    By following an orderly bring up plan, you should be able to identify whether this is a HW or SW configuration issue.

    Best wishes