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.

[Concerto] ControlCard cpu_timers c28 example problem (LED not blink)

Other Parts Discussed in Thread: CONTROLSUITE

Hello, Engineers.

I buy ControlCard package. I spend 3 days to run board and enter to debug mode. :)

It seemed that CCS can not work with correct emulator if connect both at same time (ISO JTAG (XDS 100 V2) and base USB-B cable (XDS100V1)). Then i use 5V wall adapter. Today I found this forum and migrate to microUSB+miniUSB without XDS100 V1 board (J8 plug - I also found today :)).

I think that should note on TI Concerto Experimenter kit website, that XDS100 V1 board is not usefull for program Concerto ControlCard.

I have one (yet) problem:

"F28M35x-FRM-EX-UG.pdf" page 28 see the "cpu_timers" example. I Import project, build, run, and.... LED is not blink. Interrupt appears, but GpioG1DataRegs.GPCSET.bit.GPIO70 = 1 code no effect.

 

interrupt void cpu_timer0_isr(void)
{
    CpuTimer0.InterruptCount++;
    //Toggle pin 70 for visual confirmation of timer operation
    if(GpioG1DataRegs.GPCDAT.bit.GPIO70 == 0) {
        GpioG1DataRegs.GPCSET.bit.GPIO70 = 1;
        Test = GpioG1DataRegs.GPCDAT.bit.GPIO70;     <------------- THIS "Test" variable equal zero all time. LED NOT BLINK!!!
    }else{
        GpioG1DataRegs.GPCCLEAR.bit.GPIO70 = 1;
    }

    // Acknowledge this interrupt to receive more interrupts from group 1
    PieCtrlRegs.PIEACK.all = PIEACK_GROUP1;
}

 

Sorry if it nooby question, but I have no any experience in TI dsp or ARM early.

First experiense = so big rake :)  What I do wrong?

Best regards, Nastovjak Artem.

  • Hello,

    You have to "give" all the GPIO pins to the C2000 core. Therefore there is a Stellaris project included in the examples in the controlSuite... Maybe this can solve your problem...?

     

    Grtz 3s

  • Hello, 3sRol.

    M3 example for LED also not blink. I think that I not understand something.

     

    Best regards, Artem.

  • Artem Nastovyak said:

    Hello, 3sRol.

    M3 example for LED also not blink. I think that I not understand something.

     

    Best regards, Artem.

     

    At start up (as soon as you power up the controlCard), the M3 owns all the GPIOS. In Order to run any of the C28 example codes, you first need to import the setup_m3 project , build and load it to the M3. Once you do that import the blinky project build it and load it to the C28. Once the executable files are loaded, run the M3 first and then run the C28.

    Thanks

    Noah

  • Thank Noah and 3sRoll.

    I think that this setup_m3 by default inclede in all examples and all allright (newbe...).

    I understand that I must open two projects - example and setup_m3 project, then manually startup on m3 core, then c28 can control GPIO.

    I check this later.

  • Yes. setup_m3 help me!

    But it is not easy to run setup_m3 in parallel with c28 at the first time.

    LED blink! blink! blink!

  • What I would suggest you is to run the setup_m3 code from flash and boot from flash so the assignment is always done at startup so you can run any c28 example without problem.  What you will need to change is the .cmd file to use the file specific file for your board instead of F28M35x_generic_M3_RAM so it can run from flash.  Also do not forget to but the SW1 dip switch to boot from Flash (ON OFF OFF OFF).

  • wow thanks it helped me too.

    but i dont understand the dip switch configuration,

    in the infosheet "on off off off" means M3 boot from parallel IOs, but we set it to boot from

    flash, so is this wrong in the infosheet?

    Thanks.

  • for FLASH boot mode, GPIO settings need to be "X HIGH HIGH HIGH"

    on Concerto F28M35x controlCARD, by setting SW1 to "on off off off" you create "X HIGH HIGH HIGH" situation

    It is a little backwards, but you can verify by looking at the schematic.  "on" position connects a pull down resistor, resulting in LOW on the GPIO.