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

CC2530: Using the debug port for IOs causes the code is formatted for unknown reason after running the project.

Nick Sun
Intellectual 2265 points

Part Number: CC2530

Hi team,

Here's the request from the customer:

Customer configured the pins of the two IOs of the debug port as inputs. When the device is working, these two pins will have high and low level inputs.

Customer found that the code is formatted for unknown reason after running the project. Would it enter the debug mode in a certain state?

Is there any way to solve it without modifying hardware?

Could you help check this case?

Thanks. Best Regards,

Nick

  • 0
    TI__Guru**** 221687 points

    Hi Nick,

    You can refer to Chapter 3 Debug Interface of the CC253X User's Guide:

    The debug interface uses I/O pins P2.1 and P2.2 as debug data and debug clock, respectively, during debug mode. These I/O pins can be used as general-purpose I/O only while the device is not in debug mode. Thus, the debug interface does not interfere with any peripheral I/O pins.

    Debug mode is entered by forcing two falling-edge transitions on pin P2.2 (debug clock) while the RESET_N input is held low. When RESET_N is set high, the device is in debug mode. On entering debug mode, the CPU is in the halted state with the program counter reset to address 0x0000. While in debug mode, pin P2.1 is the debug-data bidirectional pin, and P2.2 is the debug-clock input pin.

    Please have the customer monitor P2.1, P2.2, and RESET_N during device start-up with a logic analyzer or oscilloscope.  They should also further explain "code is formatted for unknown reason after running the project", is this with a debug interface disconnected and does it occur every time they try to run the code?  Can they provide code excerpts of their P2.1/2 initialization and usage?

    Regards,
    Ryan