• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 50 subscribers
  • Views 426 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.

How to debug to low speed clock (cc2540)

Omri Berg1
Intellectual 1000 points

Hi TI experts.

On the embedded project I'm on, energy conservation is at top priority. so while BLE is not needed, I want to lower the cpu clock speed to 1 MHZ, I'm doing so by changing the value of CLKCONCMD.CLKSPD to 101.

Unfortunately I'm unable to debug at such clock speed as written in the user's guide p.51 (NOTE: Note that the debugger cannot be used with a divided system clock. When running the debugger, the value of CLKCONCMD.CLKSPD should be set to 000 when CLKCONCMD.OSC = 0 or to 001 when CLKCONCMD.OSC = 1 ), which means lowest debug speed is 16Mhz.

I need your thoughts / help on how can I debug my application in such clock speed?

Thanks in advance,

  • 0
    TI__Genius 12545 points

    Omri,

    You can have the CC Debugger power your board. This way you will be able to conserve the battery life. Use the Pin 9 to supply 3.3V to the board. This way you can use the full clock speed.

    Make sure that when you have the CC Debugger connected and supplying the board, the battery is not connected. You do not want to accidentally try to charge the battery. This might permanently damage the battery.

  • 0 in reply to Chatto
    Intellectual 1000 points

    Thanks Chatto,

    But I wasn't talking about battery consumption during development, but during the expected use of the device, and the need I have right now to debug my application.

    Most of the intended use for the device to be used used, the BLE won't be needed and only the 8051 mcu to communicate with a peripheral over I2C on GPIO.

    So right now I want to see how the I2C driver I wrote is working on  lower speeds (1Mhz rather then 32Mhz), I don't have access to the actual SDA and SCL  so I can't use an oscilloscope. I was hoping to use IAR to debug, but when I'm changing to 1Mhz it loses connectivity with IAR (it is mentioned in the user's guide p.51 under the note). 

    I hope my issue is now clearer.

    Thanks in advance.