• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 953 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.

CCS/AM3359: Debug and Control the GPIO on the AM3359 with Code Composer Studio

Cheng Han Hsieh
Prodigy 100 points
Part Number: AM3359

Tool/software: Code Composer Studio

HI, I'd like to Debug and Control the GPIO on the AM3359 with CCS 9.1.0

Below is what I do:

1. Create the new Target configuration

2. Choose the connection as the picture shows

3. Test the connection, and it shows connect successfully

4. Launch the Configuration

And when I right click on the CortxA8 and choose connect target, it shows nothing.

And if I right click on the M3_wakeupSS and choose connect target, it shows the error message

I wonder which step I did is wrong, or if I want to control the GPIO by CCS, what should I do.

  • 0
    TI__Guru**** 171104 points

    Hi,

    As the message says, the Cortex M3 core is held in reset and must be released from this state before connecting. 

    Usually the process of releasing a slave core is done via a GEL script that is configured with one of the platform target configurations (BeagleBone, EVMAM3358, ICE_AM3359, etc.). However, specifically for the AM335x family of devices, this function is not implemented and I suspect this was deliberate (development on the Cortex M3 core is not supported by the SDKs). 

    The GPIO control can probably be done either via the Cortex A8 itself or via the PRU cores. For the latter, check the following series of training labs; 

    https://processors.wiki.ti.com/index.php/PRU_Training:_Hands-on_Labs 

    Hope this helps,

    Rafael