• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 55 subscribers
  • Views 463 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.

Original question:

CC2538: What debugger\programmer can I use for this controller

CC2538: Programming CC2538 with CC2650 Launchpad

Ali Hassan
Prodigy 80 points
Part Number: CC2538


Hi,

I am trying to program CC2538 with the above mentioned launchpad but I am not able to program the microcontroller,

Do I need external crystal osccilator with CC2538? Or 32KHz internal clock is okay for programming?

Schematic:

              

I made direct pin to pin connection between my J4 and lauchpad

  • 0
    TI__Guru**** 171299 points

    Hi,

    Yes, you need an external 32MHz crystal for programming. Only the 32kHz will not work.

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Prodigy 80 points

    Hi, I am able to program the controller without an external crystal. I am able to change LED status, Also the datasheet states that there is an internal RC oscilator, But I am not able to use srial comunication.

    I have a EvalBoard, Serial communication works fine on the evaluation board, which has 32MHZ crystal but serial comunication does not work on my board without the crystal.

    On my board I have connected a clock generator that is not configured and it is producing 4KHz clock. So in the FW i tried to configure the clock using internal RC oscilator, I set system clock to 16MHz.

  • 0 in reply to Ali Hassan
    TI__Guru**** 171299 points

    Ali,

    Please apologize for my mistake; I completely forgot about the 16MHz RC oscillator.

    To verify the serial port, can you try to use the serial bootloader? Since the bootloader uses the internal RC oscillator and communicates via serial, this could help isolate the issue to the device serial configuration in SW or something with the HW connections.

    If that is not the case, did you try to run an example code such as the Driverlib UART example? This uses the external crystal by default for both system and I/O but you can change it to the internal RC (the values are shown in the file sys_ctrl.c, part of the driverlib package).

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Prodigy 80 points

    Problem was with my configuration of system clock, Howver the problem is resolved, thank you,