CCS/F28M35H52C: Adapting an Example C2000 Program for my New Hardware

I spent more time looking at this, the issue is likely in the setup of the pin permissions.  

Basically, all I am trying to do is change the standard dual core blinky program to use GPIO29 (PE5) as the output that drives LED0  from the pin example program uses which is GPIO70 (PC6).

In blinky_dc_c28.c I changed the following

Lines 46 and 48 refere to LED_0_DIR_REG and LED_0_DAT_REG so I looked up the definitions and found they were in F28M35x_set_pinout.h so I modiified the references as follows:

//#define LED_0_DIR_REG GpioG1CtrlRegs.GPCDIR.bit.GPIO70
//#define LED_0_DAT_REG GpioG1DataRegs.GPCDAT.bit.GPIO70
#define LED_0_DIR_REG GpioG1CtrlRegs.GPADIR.bit.GPIO29
#define LED_0_DAT_REG GpioG1DataRegs.GPADAT.bit.GPIO29

Note the original lines are commented out.

LED_0_DAT_REG is referenced again in the for(;;) loop so I think that's all there is for the c28 program.

------

In the blinky_dc_m3.c program I made the following changes...

Line 104 through 114 refer to LED_0_PERIPH, LED_0_BASE, and LED_0_PIN which are defined in set_pinout_f28m35x.h which I modified as follows:

//*****************************************************************************
// GPIO for the user LEDs
//*****************************************************************************
//#define LED_0_PERIPH SYSCTL_PERIPH_GPIOC
#define LED_0_PERIPH SYSCTL_PERIPH_GPIOE // TM GPIO29 is PE5
//#define LED_0_BASE GPIO_PORTC_BASE
#define LED_0_BASE GPIO_PORTE_BASE
//#define LED_0_PIN GPIO_PIN_6
#define LED_0_PIN GPIO_PIN_5

#define LED_1_PERIPH SYSCTL_PERIPH_GPIOC
#define LED_1_BASE GPIO_PORTC_BASE
#define LED_1_PIN GPIO_PIN_7

note I've lcommented out the original lines

the blinky_dc_m3.c program gives control of LED_0 to the C28 core at line 109 as follows: 

// Give C28 control of Port C pin 6
GPIOPinConfigureCoreSelect(LED_0_BASE, LED_0_PIN, GPIO_PIN_C_CORE_SELECT);

but the changes made to set_pinout_f28m35x.h should take care of the fact that my LED0 is on GPIO29 instead of GPIO70

the rest of blinky_dc_m3.c goes on to set up for LED3 and blink that LED but that should not affect my program.

I tried it, it does not work.  I'm sure my LED is good and connected the right way round - the anode is connected to GPIO29 and the cathode is connected to ground via a 150 Ohm resistor.

I reloaded everything and made the changes again from scratch to make sure I hadn't messed something up in the files. It still doesn't work.

I'm stuck ;(

Thanks, the customer has now confessed that this chip may have been subject to overvoltage - perhaps as much as 12 volts.  I'm going to replace the chip on the PCB.

New processor fitted, it's exactly the same.  I'll keep looking, thinking of writing code from scratch but this is frustrating.

I think there's a problem with my understanding of the setup of the CCS environment.  I can get my board to run but only under a specific  sequence of actions.  If you can look at my screen capture below what I have is the dual example of blinky which has actually been set back to the standard settings and I've connected an LED to GPIO71 (plus I'm able to probe GPIO70 with a scope) anyway I can see that both are 'flashing' when I get it to run but I can only make it run by doing the following steps:

1. Click on either the debug button on the toolbar or item 1: blinky_dc_m3 - it then tells me it's loading_program blinky_dc_m3.out

2. I then see the 2 cores in the debug window, the m3 is connected but suspended and the C28 is disconnected

3. I then run the m3 section and it says "running" (the C28 shows "disconnected")

4. I then right click on the C28 line and select connect target, I then see the C28 core shows as "suspended"

5. With the C28 section selected, I click on the run button and both cores then show running and the GPIO ports start flashing - neither flashes before this step

6. I can then hit the stop button and I drop out of debugging in the CCS session but the hardware keeps running with the LED flashing

7. If I power cycle the PCB, it doesn't start (flash) (it doesn't matter whether the XDS100V2 is connected or not

I thought that once code was running, that it would start whenever the hardware was power cycled.  I also thought that I should be running by selecting one of the .ccxml files - I tried to create my own but it doesn't work, nor does the once that was there when I loaded the project, the ConcertoCard.ccxml - these files seem to load and control the cores but when I pause them while they show "running", the procesor cores seem to be in idle.

Can you shed any light on what I'm doing wrong from this description? Let me know if you want me to do further tests.

This is likely the issue, the hardware designer has not provided pull ups or pull downs on the Boot pins - is there any other way to set these or can I reallocate the boot pins to other GPIOs?

Update.  The client realized they'd given me an old prototype chip so they sent me one that's Revision 1 silicon and I've swapped that one onto the PCB.  Now I should be able to solder resistors to unused pins to implement the missing Boot Mode pins and, given that's a one-time (OTP) operation, I'd like some guidance on how to do that please.

The Reference Manual (spruh22h.pdf) says on page 539... "To change the default boot mode pin to GPIOx, program GPIOx+1 in the corresponding bit field."

I understand that I need to program (GPIOx+1) numbers into the Bmode1,2,3,4 registers but how do I actually do that?  Is it done from within CCS?

Thanks in advance.

So now I have fitted a replacement Rev 1 chip which means that I should be able to assign the boot mode pins to spare GPIO pins; I realize that, to change the default boot mode pin to GPIOx, I need to program GPIOx+1 in the corresponding bit field of the Bmode_pinx pins but how do I actually do that? Is it done somehow through Code Composer Studio?

Thanks in advance.

Thanks, I don't understand the suggestion to "use the linker".  Do you mean that I just add the pragma statements to my code and then flash the device?

So I added the #pragma statement to my C file and it builds, my extra lines look like this

#pragma DATA_SECTION(TedsVariable,".TedsNewSection")
unsigned long TedsVariable = 0x48474645;

I am pretty sure that what I need to do is to store 0x48474645 into location 0x680824 to make GPIO71,70,69,68 be Boot pins 4,3,2,1 respectively - anyone who can confirm that, please do.

I realize that I need to open and edit the linker file to add the instruction to tell it where to store my new variable and that you're advising me to test it in RAM or a Flash Location first.

My question is, from within CCS, where do I go to find, open, and edit the Linker file?

Thanks.

Chris,

I'm running CCS 7.2 and I'm using the Dual Blinky M3 example (default install location on my PC), the attached picture shows a page from the options dialog box, please confirm that I'm right in thinking that the file at C:\ti\controlSUITE\device_support\f28m35x\v210\MWare\cmd\F28M35x_generic_M3_FLASH.cmd is the linker file I need to edit.

It's been suggested that I use a different location other than 0x680824 to first test that I can write the data and see it's written before I actually make the attempt a OTP,  I went into the data sheet for the processor f28m35h52c.pdf and, on page 156 in the memory map section, there's a block from 0068 0818 - 0070 00FF that's 'reserved' so that makes me worry that the write is not going to work without other changes.  Also, can you suggest an area from which to pick an address for the test write?

Chris,

I looked in the actual link file today and this is the memory section...

MEMORY
{

    INTVECS (RWX)    : origin = 0x20000000, length = 0x01B0
    C0 (RWX)         : origin = 0x200001B0, length = 0x1E50
    C1 (RWX)         : origin = 0x20002000, length = 0x2000
    BOOT_RSVD (RX)   : origin = 0x20004000, length = 0x0900
    C2_1 (RWX)       : origin = 0x20004900, length = 0x0700
    RESETISR (RWX)   : origin = 0x20005000, length = 0x0008
    C2_2 (RWX)       : origin = 0x20005008, length = 0x0FF8
    C3 (RWX)         : origin = 0x20006000, length = 0x2000
    CTOMRAM (RX)     : origin = 0x2007F000, length = 0x0800
    MTOCRAM (RWX)    : origin = 0x2007F800, length = 0x0800
	
	OTPSECLOCK       : origin = 0x00680800, length = 0x0004
    OTP_Reserved1    : origin = 0x00680804, length = 0x0004
    OTP_Reserved2    : origin = 0x00680808, length = 0x0004
    OTP_Z2_FLASH_START_ADDR             : origin = 0x0068080C, length = 0x0004
    OTP_EMACID       : origin = 0x00680810, length = 0x0008
    OTP_Reserved3    : origin = 0x00680818, length = 0x0004
    CUSTOMER_OTP_MAIN_OSC_CLK_FREQ      : origin = 0x0068081C, length = 0x0004
    OTP_Reserved4    : origin = 0x00680820, length = 0x0004
    OTP_BOOT_MODE_GPIO_CONFIGURE        : origin = 0x00680824, length = 0x0004
    OTP_Reserved5    : origin = 0x00680828, length = 0x0004
    OTP_ENTRY_POINT  : origin = 0x0068082C, length = 0x0004
    OTP_Reserved6    : origin = 0x00680830, length = 0x0010
}

Note that, in there, there's a "OTP_BOOT_MODE_GPIO_CONFIGURE : origin = 0x00680824, length = 0x0004" so can't I just write in the main code, something like this..

OTP_BOOT_MODE_GPIO_CONFIGURE = 0x48474645;

Please advise.

Well it's not working.

I added my variable, called TedsVariable, assigned it the required value, and edited the .cmd file so that it's stored in TedsNewSection.  I tried to run the program and got no error. so I rebooted without CCS connected and found that the code was not running.  When I reconnected, I tried to look at the contents of 0x680824 or the contents of TedsVariable but I seem unable to see any variables in the Debug watch window... sigh

Right now I just want to look at the content of the OTP Boot Mode register at 0x680824

Somewhere I saw that there was a Flash Config GUI tool, might that help?

Ted,

In CCS, when connected and debugging the device, did you try the memory browser (View->Memory Browser)?

Edit : You might not be able to see it in the memory window without editing the GEL file that gets loaded through your target configuration file. It is likely you are using the gel "f28m35h52c_m3.gel". If you go into your CCS install -> ccs_base -> emulation -> gel and find this file. Open with text editor, and change line 113 to the following:

    GEL_MapAddStr(0x68080C,      0, 0x00100,    "R",   0);        /* OTP BANK 1 Application 2            */

Save and restart CCS, it should now be visible in the memory window.

Also, be aware this location has ECC, read more in  "6.5.6 M-Boot ROM User OTP" in the TRM.

Best regards
Chris

I edited the .gel file and now I can see the contents of the memory, 0x680824 contains 0xFFFFFFFF so clearly my code has not been allowed to write the values to the OTP.  I'll keep trying.

Ted,

thanks for confirming. Please use the forums if you have any further questions or feedback as your project progresses.

Best Regards
Santosh Athuru