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.

getting started with concerto controlcard and dock board...

Other Parts Discussed in Thread: CONTROLSUITE

Hi folks, some newbie help needed.  I just purchased the concerto controlcard and dock (TMDXDOCKH52C1) and I'm having trouble speaking to it from CCS and running the basic (blinky_c28) project.

- I have installed CCS v4 that comes on the CD (version 4.2.4.0003 - code composer studio core edition)

- I went into controlSuite and installed the support files (ti_c2000support_setup 2.0.0.14.exe)

I can successfully build the blinky project (the one in the controlSuite\device_support\f28m35x\v110\...\blinky

Next, do I plug in the USB cable from the Docking board to my laptop, or from the controlCard?  I have tried it both ways and I get a TI XDS100v1 in the one case (when plugged to the docking board) and TI XDS100v2 in the other case.  Do I leave them both plugged in?  

When I create a new Target Configuration, and use the XDS100v2 USB emulator, there is no device/board that matches the concerto (what should I see?)?

What now?  Somewhat anxious to start playing with my new toy!

Thanks for your help

SA

 

  • Hello SA,

    Great to hear your enthusiasm!

    You will need to power the device through the docking station USB port or power jack.  A green LED, LD1, should be lit indicating the device is receiving power.  Another green LED, LD4, will be lit near the mini-USB port indicating power for the ISO JTAG logic.  These details can be found in the F28M35 controlCARD InfoSheet found under controlCARDs in the Kits section of controlSUITE.

    While creating a new XDS100v2 USB emulator Target Configuration you should see F28M35H52C1 in the list of devices.  The process for creating a new project and debugging dual core applications, as well as further discussion on firmware development with the Concerto, can be found in the Documentation section under Concerto F28M35x in the Devices section of controlSUITE. More documentation, examples, and links can all be found within the controlSUITE folder.

    Keep in mind you can always search the E2E forums to find related forum posts, and the TI Embedded Processors Wiki is always a great resource to check.

    Hope this helps,

    Mark-

  • Mark, thanks for the info.  After I re-installed ccs, I could see the c28f35xx devices.

    I had to use ccsv5 (and get a 90 day evaluation license - for my purposes that is fine).  I was not successful with ccsv4...

    Some comments - the example code in controlSuite includes both a "blinky_c28" and a "blinky_m3" example.  Both of them are supposed to toggle pin 71, which is connected to an LED on the board.

    LEDs:
    LD1 Turns on when controlCARD is powered on (Green)
    LD2 Controlled by PC6_GPIO71 (Red)
    LD3 Controlled by PC7_GPIO70 (Red)
    LD4 Power for ISO JTAG logic (Green)
    LD5 UART/SCI Rx activity indicator
    LD6 UART/SCI Tx activity indicator
    However, only blinky_m3 works.
    The version of blinky_c28 that is in controlSuite does not do anything. (it compiles and runs fine, but doesn't toggle the LED):

    //###########################################################################

    // $TI Release: F28M35x Support Library v110 $

    // $Release Date: December 12, 2011 $

    //###########################################################################

    Here is the relevant instruction that SHOULD toggle the LED:

            GpioG1DataRegs.GPCDAT.bit.GPIO71 = 0;

    Thanks for your help getting started - more questions as I run into them!
    Sridhar 

  • Sridhar,

    Both the projects that I have regarding the C28x blinking the LED, blinky_c28 and blinky_dc_c28, indicate the following code for the line you are referring to:

    GpioG1DataRegs.GPCDAT.bit.GPIO70 = 0;

    Could you try changing your blink_c28 code to toggle GPIO70 instead?  Also, the header information you posted matches my header information exactly but the GPIO pin is different from yours by default.  Not sure how this could happen, but have you updated to the latest release of controlSUITE?

    You did not have the F28M3x devices listed in your target configuration options for the XDS100v2 USB Emulator within CCSv4? Switching to CCSv5 going forward is good practice, but if for some reason you need to use CCSv4 again, these target configurations should exist.  Your install of CCSv4 may not have included the M3 devices, but CCSv4 does support the Concerto device and there should exist device configuration options for the F28M35H52C1 device.

    The fact this is GPIO70 and not GPIO71 is very important for the blinky_dc_c28 project example, which should always be run with the blinky_dc_m3 example project. However, if you are running the setup_m3 project, resetting both cores, running the blinky_c28 project first, then running the setup_m3 project either GPIO70 or GPIO71 should begin blinking their respective LEDs as can be seen in the Concerto F28M35xx DIM100 hardware schematic.

    The reason behind running the setup_m3 or blinky_dc_m3 example projects with either C28x blinky project is to allow the M3 core to transfer control of specific GPIO pins to the C28x core.  Relevant lines are pasted below from the M3 initialization code from the blinky_dc_m3 project.  Without this GPIO control transfer, the toggling done by the C28x code will not result in and LED toggle. Specifically regarding the blinky_dc_c28 example ONLY the GPIO70 pin is available to the C28x core for toggling and as a result the M3 core should toggle GPIO71 (pin 7 of Port C) and the C28x should toggle GPIO70.

    // Give C28 control of Port C pin 6

    GPIOPinConfigureCoreSelect(GPIO_PORTC_BASE, 0x40, GPIO_PIN_C_CORE_SELECT);

    Best Regards,

    Mark-

  • Mark - thanks for your quick, helpful, and detailed answers.

    Running ``setup_m3'' did it.  

    I think I'm OK for a little bit now!  Much appreciated.

    Sridhar