CCS/UCD3138A64OEVM-662: Training projects and test firmware for UCD3138A64OEVM-662

an expert will help you soon, due to the holiday season, please allow a delayed response

Ian, thanks for the respond. Does CCS 6.2 support Win 10 64 bits? it doesn't look like it does. Will I be able to use CCS 9.0.1?

Bobby.

I just checked, and I'm using 6.2.0.48 on Windows 10, 64 bit with no problems.  I'd suggest using exactly that version.  There are some tricky things that we have to do to use all the features of the ARM core and the UCD that are somewhat dependent on the details of the compiler.  Mainly there are some spots where we stick some assembly into the middle of the C code, mostly in the software interrupt.   Those tend to break down when you move away from the version we're working with.  

Hi Ian,

I am able to download the program to the flash. But, when I went back and clicked on DEVICE ID, it said no device found. Can you what did I do wrong?

I thought the option DO NOT write program checksum (stay in ROM) is checked would prevent the locking up the device. I just compiled the training lab1 as is. The code you suggested is included in the main.c. Do I need to strap J14 pin 2 &3?

Here is the main.c code:

//###########################################################################
//
// FILE: main.c
//
// TITLE: main
//
// NOTES:
// 1)

//###########################################################################
//
// Ver | dd mmm yyyy | Who | Description of changes
// ======|=============|======|==============================================
// 1.00 | 05 May 2015 | CH |
//
// Texas Instruments, Inc
// Copyright Texas Instruments 2008. All rights reserved.
//###########################################################################
#define MAIN 1

#include "system_defines.h"
#include "Cyclone_Device.h"
#include "pmbus_commands.h"
#include "pmbus_common.h"
#include "pmbus_topology.h"
#include "variables.h"
#include "functions.h"
#include "software_interrupts.h"
#include "cyclone_defines.h"
#include "stdio.h"

void main()
{
// enable JTAG
MiscAnalogRegs.IOMUX.all = 0;

//---------------------------------------------------------------------------
// IMPORTANT: READ BELOW, OR CODE MAY NOT EXECUTE CORRECTLY
//---------------------------------------------------------------------------
// tie pin FAULT3 to ground for normal operation
// tie pin FAULT3 to 3.3V to clear checksum
if(GioRegs.FAULTIN.bit.FLT3_IN == 1)
{
clear_integrity_word();
}

#if (UCD3138|UCD3138064)
MiscAnalogRegs.CLKTRIM.bit.HFO_LN_FILTER_EN = 0;
MiscAnalogRegs.CSTRIM.bit.RESISTOR_TRIM =23; //28;
#endif

init_pmbus(0x58); // initialize PMBus handler
strcpy(A_string,"Hello World.");

for(;;)
{
pmbus_handler();
}
}

//#pragma INTERRUPT(c_int00,RESET)

void c_int00(void)
{
main();
}

You're right, you are doing the right thing with the checksum in your screen shot above.  

Yes, it looks like you could put a strap between pins 2 and 3 of J14.  I didn't even know those jumpers were there.  I have always just put a jumper between J5 pins 5 and 6.  Whichever you like apparently.  

I will try it in a little bit. Is there a training offer somewhere that I can attend? thanks