C5000 Ultra Low Power DSP Forum - Recent Threads

USB problems when booting from flash

DanB — Thu, 23 May 2013 01:50:13 GMT

After successfully running the USB_CDC CSL example through the XDS debugger, I'm now having problems running the same code from flash (I am booting from an SD card). Basically, I no longer receive USB interrupts.

Reading through http://e2e.ti.com/support/dsp/c5000/f/109/p/95041/332809.aspx#332809, I made sure to incorporate all GEL-contained initialization into my main() loop. However, this does not seem to help.

I tried running via the debugger, and eliminated all init code from the GEL file. This ran fine.

What else might be different between running via debugger and running via flash?

Any help would be very appreciated.

Thanks,

Dan

Error connecting to the target

Albert Torn�� — Fri, 24 May 2013 12:26:20 GMT

Hello,

recently i've got this error:

C55xx: Error connecting to the target: Error 0x80000244/-1143 Fatal Error during: Register, Initialization, OCS, The memory at 0x00000000 continually indicated it was 'not ready' All memory operations currently in progress were aborted in order to regain control of the processor. This is considered a catastrophic event, but the debugger should still be able to access memory and CPU registers. System state has been altered. It is strongly advised that the processor should be reset before resuming execution,

I am workinng with EVM5515 and it was working fine but now i got this and I didn't do anything strange.

Please I would need some urgent help.

Best regards!

C5505 ADC error count

Stuart Baker — Fri, 17 May 2013 18:31:22 GMT

I have a C5505 design that is seeing a large offset error in the conversion close to Vref High.

When the ADC input is connected to ground, the ADC conversion value is always 1 or 2 counts, well within the datasheet specification.

With a Vref High of 1 Volt and an ADC input value of 1Volt, the conversion value is 989 counts when the expected value should be closer to 1023 counts.

We also see errors at two other voltages

0.937 volts, conversion value is 933 counts, expected 959 counts

0.914 volts, conversion value is 907 counts, expected 936 counts

The questions are to start are:

What is the expected error? From the datasheet, I would expect a maximum error of about ~4-5 counts at full scale voltage.

If the error that we are seeing is expected, is there a calibration procedure to follow?

Thanks,

Stuart

Is there a way to trace *.bin file boot problem on C5535 based application?

Jun Cao — Sun, 14 Apr 2013 22:04:02 GMT

I use CCSV5.3 (with latest update) to debug C5535 DSP based application through Blackhark USB560M JTAG Emulator.

I first tried a short application project, V2EP0Test. I was able to build V2EP0Test.out file; load V2EP0Test.out to the target board (my application board); run the code and get the correct results. Then I generate the V2EP0Test.bin file from V2EP0Test.out as below run record.

C:\G2V2_workspace\V2EP0Test\Debug>"C:/TI_CCSV5/ccsv5/tools/compiler/c5500_4.4.1/bin/hex55.exe" V2EP0Test_Debug_bin.cmd

Translating to Binary format...

".\V2EP0Test.out" ==> .const (BOOT LOAD)

".\V2EP0Test.out" ==> .cinit (BOOT LOAD)

".\V2EP0Test.out" ==> .switch (BOOT LOAD)

".\V2EP0Test.out" ==> .text (BOOT LOAD)

".\V2EP0Test.out" ==> vectors (BOOT LOAD)

C:\G2V2_workspace\V2EP0Test\Debug>type V2EP0Test_Debug_bin.cmd

/* Convert a .out file to a binary *.bin file */

-boot /* Make a boot table */

-v5505 /* Boot format */

-serial8 /* A byte-wide serial flash will be used */

-b /* for binary */

-map .\V2EP0Test.mxp /* Map file generated by hex55 */

-o .\V2EP0Test.bin /* Output file name for the resulting boot table */

.\V2EP0Test.out /* Input file */

However after loaded the V2EP0Test.bin to the flash memory, boot C5535 (load V2EP0Test.bin and run) could not give me the correct results.

I verified that

* The V2EP0Test.bin was correctly write to the flash memory

* Observe the LED display (on my application board), the code was loaded and run

* It seems the C5535 DMA does not response / active.

I am looking for experts’ help:

1. Is there a way to trace this bin file boot problem?

2. Just give me your guess – what can cause this problem

Thanks!

Jun Cao

Converting C5515 Assembly code to equivalent C

Honey Sukesan — Fri, 24 May 2013 10:41:43 GMT

Hi,

Is there any update on the above ported C code?

I am also stuck with a similar problem.

I am trying to run equivalent C function in C5515 DSP itself.

But my equivalent C function is producing results not comparable with the assembly function.

My ultimate aim is to port it to C64x DSP. But before that, i am trying to analyse if my equivalent function

in C is producing the same result with C5515 itself. Please share your thoughts.

Thanks,

Honey S

Doubt regarding C5515 MACM instruction

Honey Sukesan — Thu, 23 May 2013 16:58:42 GMT

Hi all,

I am a newbie in DSP. We have grabbed the ADS1298-C5515 EVM kit and successfully built the ECG MDK source code.

Now we are trying to port the ECG algorithm to C64x DSP. For that, I am trying to convert the two assembly functions in

ECG MDK to C source code. At first, I am trying to test the equivalent C code in C5515 EVM itself. But when I convert the assembly functions

to C code, it is not working properly in C5515 EVM. Below are the functions for your reference:

ECG_FilterProcess:

AC0 = 0;

repeat (#351)

AC0 = AC0 + ((*AR0-)* (*AR1+));

(*AR2+) = HI(AC0);

(*AR2) = AC0;

return

_ECG_AntiAlising_FilterProcess:

AC0 = 0;

repeat (#51)

AC0 = AC0 + ((*AR0-)* (*AR1+));

(*AR2+) = HI(AC0);

(*AR2) = AC0;

return

The Test routine takes three int16 pointers. The first two are inputs and the third one is output.

One of the operands for multiplication is Q15 format filter coefficients.

I understood that there is some problem when I port the multiplication instruction to C source code.

On viewing the disassembly view, I understood that equivalent instruction for multiplication is MACM.

I have also verified the status register settings of SATD, M40, SMUL, FRCT bits in my source code. All these

are found to be in their default values in the lpva2000.inc file.

I have debugged the C code and understood that the problem is with the multiplication instruction in my C code.

I have also referred the following posts in TI forums and made several trials.

http://e2e.ti.com/support/dsp/c5000/f/109/t/103964.aspx

I have tried with the SMULT macro mentioned in the above forum. But still I didn't get the expected results.

http://e2e.ti.com/support/dsp/tms320c6000_high_performance_dsps/f/115/t/187702.aspx?pi64368=1

http://e2e.ti.com/support/dsp/c5000/f/109/t/101101.aspx

Still my multiplication output fails.

Could you please share your thoughts on this issue?

Also please tell if it is okay for these asm porting to C while porting to C64x DSP.

Thanks,

Honey S

Connecting ADS1298RECG-FE to C5515-EMV

Udi Dagan — Fri, 24 May 2013 07:00:35 GMT

Hello,

I have an ADS1298RECG-FE and would like to connect it to a DSP board for development purposes. hence, I need a board with an emulator and that is compatible with ADS1298.

I have seen the C5515-EVM and I have 2 questions:

1. Is it compatible with ADS1298RECG-FE REV.B? if it does, Which revision of the evm would be the most suitable?

2. Do you have a source code to start with in order to program the dsp? (For starter - I would like to create a small PC application).

Thank you very much,

Udi

Creating a Second-Level Bootloader for FLASH Bootloading on TMS320C5000

Howard Marshall — Tue, 12 Oct 2010 15:48:59 GMT

Greetings, We are developing a product around the TI C5515 Fixed Point DSP. In this product we utilize our own Bootloader program which provides firmware image management and execution capabilities. Our bootloader resiseds in the base of flash memory and is invoked by the on-chip primary DSP bootloader. Our Bootloader receives firmware images via a UART in binary data format and stores them in upper flash along with related data structures. We need our Bootloader to be able to load a firmware image from flash to the corresponding areas of RAM according to its linking and then be able to execute that firmware program. We have done this successfully on our existing product based on the TI C6727 Floating Point PRocessor based upon assembly language code we obtained that I translated to "C". I have a document that explains how to create a second-level bootloader (SPRA999A1) but I cannot seem to find this same document for the TMS320C5515 DSP. It is all well and good to understand that the linker creates .out files in Common Object File Format (COFF) and that the Hex Conversion Utility (hex55v4.exe) converts the COFF file to various formats. The problem is that I cannot find documentation as to the exact format produced by the hex55v4 -b (binary) switch and what the on-chip bootloader does when it loads and executes a program residing in flash memory created in binary format by hex55v4. I need to be able to reproduce the functionality of the on-chip primary bootloader and encapsulate that function, preferably in "C" code, and integrate it into our Bootloader program. Would it be possible to obtain the source code for the DSP on-chip bootloader? This would obviously be the most pragmatic way to proceed. If not, if I could get a detailed description of what the on-chip bootloader does, and a through defintion of the format of the binary file produced by hex55v4, then I could write my own second-level bootloader function. Any help in this matter would be greatly appreciated. Thanks very much.

Howard Marshall, Senior Software Engineer, Aegis Lightwave, 78A Olympia Ave, Woburn, MA 01801 USA

DSPLIB logarithm error?

Alberto Lessio — Thu, 23 May 2013 15:52:11 GMT

Hello,

I'm working on a TMS320C5515 DSP. My application computes a logarithm using the log_10 function of DSPLIB for C55x.

The function is described as:

ushort oflag = log_10 (DATA *x, LDATA *r, ushort nx)

I would like to know what is the maximum error introduced by this function. Given that my input (x) has a +/- 1 lsb error, what is the maximum resulting error for the output (r)?

Apparently this information is missing from the documentation. I'm going to perform some tests, but I would like to know if some knowledge already exists on this argument.

Thanks for the attention,

Alberto

C5515 customized device gives issues when flashed

AV54983 — Tue, 21 May 2013 14:05:09 GMT

Hi C55x users,

I am working on code which does the writing and reading of codec data using Direct Memory Access (DMA).

The application code uses DMA controller 1. Serial flash is being used.

CCS 4.0 is being used.

-> A C5515 customized device (not ezdspC5515) is used to flash/burn the code image and test it in the field.

-> So when my code is run via CCS 4.0 on this device there is no issue. Output is clear.

-> The image or .out of the code is converted to .bin and is flashed onto the device and restarted.

The output heard from the speakers has some disturbance along with the other environment sounds coming in from the mics.

-> After some arbitrary resets or OFF/ONs of the device the output is clear and fine.

-> Then again after some random off/on or resets the output is noisy/has disturbance.

Do you have any suggestions as to why this could happen ?

I have been scratching my head on this for a few weeks now.

Thanks,

Error when Writing to or Reading from UART registers.

nathan zorndorf1 — Tue, 21 May 2013 06:51:59 GMT

Hi,

I am using the C5535 ezdsp, and CCS v4 with Texas Instruments XDS100v2 USB Emulator.
I am writing code that uses some CSL and some register programming to input an analog audio signal, use the DMA to do processing, and then output UART signals that contain information about the input samples. It seems that when I am debugging and I try to read or write UART registers, or use UART CSL functions that require a handle, I get an error where the device memory bus hangs.

When i run my code using the debugger, I get an error at the line of code commented below.

Uint16 register_value;

register_value = UART_PWREMU_MGMT; // ERROR happens when trying to execute this code
UART_PWREMU_MGMT = register_value | 0x0000;

my definition for UART_PWREMU_MGMT is below:

#define UART_PWREMU_MGMT *(volatile ioport Uint16*)(0x1B18)

THis is the error I get:

Trouble Reading Memory Block at 0x1b18 on Page 2 of Length 0x1: (Error -1143 @ 0x1B18) Device memory bus has an error and may be hung. Verify that the memory address is in valid memory.

I always get this error when I write to or read from any UART register. If I replace the UART code with code that does anything else, the program runs correctly. I can write to and read from other peripheral registers, but I cannot write to and read from UART registers without receiving this error. I tried using the CSL to configure UART registers, and I get the same error when I use any function that requires a handle, which includes UART_setup, and the UART_reset function. UART_init (which does not require a handle) can be called successfully.

If, after receiving this error message, I "Disconnect from the Target", and then try to reconnect, I will get an error that says the "Device memory bus has an error and may be hung.".

1) I have already made sure that the UART is out of reset by reading from the PRCR register.
2) I have also made sure the UART CLK is enabled by writing a 0 to the UARTCG bit in the PCGCR1 register (although the tech ref. says to write a 1 when initializing UART, which I believe is a typo, because a 1 disables the UART CLK).
3) I have slowed the emulator clock (TCLK) to 100 kHz, which did not fix the problem.
4) I have tried using a different C5535, and the problem persists.

Why is the debugger having trouble only when reading the memory blocks related to UART? How do I clear this error?

I would greatly appreciate help in resolving this issue. I am attaching my project for reference.

Thanks,

Nate
(Please visit the site to view this file)

P.S. Does this have anything to do with my problem? I do not know whether I am using port B or A.

Q: Can I use port B as a UART?

A: Yes. The TI XDS100v2 reference design uses the port A of the FTDI2232H to be for JTAG. This leaves the port B available for use either to program the CPLD and/or for use as a UART. The XDS100v2 design puts the CPLD JTAG programming on a selected number of pins (see XDS100v2 readme for details). This allows the CPLD to be programmed via the FTDI device, greatly simplifying manufacturing.

Please note that there is a known issue with the current XDS100v2 reference design with the placement of the BCBUS. If you plan to use the port B, please check the readme of the XDS100v2 reference design for details. Generally, a serial port on BCBUS should connect the CPLD as follows: BCBUS1 -> CPLD TCK, BCBUS2 -> CPLD TDI, BCBUS5 -> CPLD TDO, BCBUS6 -> CPLD TMS.

Please note that using UART mode simultaneously with Code Composer Studio v4 has NOT been tested on the XDS100v2 design and is not officially supported

image boot on VC5505 EVM

Yake Li — Fri, 17 May 2013 15:11:46 GMT

Hi, i am burning a program that operates SD card into SPI EEprom of VC5505 on the evm board. But the ccs always gives me the message that "WRITE ERROR! at 0x0000
Wrote 0x0000 Read 0xffff". it seems that when i comment out all the sd operation functions (like MMCSD_multipleBlkWrite or csl mmc/sd function), the image can be burned successfully. does anybody know where is the problem.

However, i can burn the image into I2C EEprom, but the the programm won't run when the evm board stands alone. can i make some settings to make the program executed from I2C EEprom?

TMS320VC33 DSP boot up question

Charlie Zhang2 — Mon, 29 Apr 2013 18:36:36 GMT

Dera TI engineers,

We have been using TMS320VC33 DSP in our products over ten years. Recently we are redesigning the circuit board to upgrade the FPGA and Flash memory chips. We kept using the VC33 DSP for FW code compatibility to meet our customers’ requirements, while changed the bootup sequence from DSP->FPGA to FPGA->DSP. The new board has been fabricated and FPGA is programmed and working as to the design. However, we are stuck when FPGA sends RESET signal to boot up the DSP. It seems the DSP somehow stopped loading the DSP code from Flash memory after successfully reading the first few words (see the signal snapshots attached). We could not understand the DSP behaviors and desperately need helps to resolve the issue. Does anyone know what happened and if there is any solution for it?

Thanks.

Charlie

(Please visit the site to view this file)

C5515 FDK

Chris Stanton — Mon, 20 May 2013 19:55:18 GMT

I am posting about my FDK C5515. I am looking to connect this to a microprocessor. I am unable to figure out which pin is the output pin. I have read the manuals and I'm still unclear as to which one it is or whether I am able to use it as a hyper terminal? I need to get an output so I can open an actuator for a locking mechanism. I would greatly appreciate a reply. Thank you very much.

C5535 bootloader SPI pin assignments?

gmarsh — Tue, 21 May 2013 14:33:09 GMT

The SPI interface on the C553x can be on two different sets of pins, depending on the PPMODE setting in EBSR.

Which configuration is used by the C553x bootloader? only the "PPMODE = 1 or 6" that is used on the EZ5535 card, or does the bootloader also try the other "PPMODE = 3 or 5" pin configuration?

Thanks!

C5535 USB DMA Example

DanB — Tue, 21 May 2013 01:08:49 GMT

Hi,

I'm trying to run the USB DMA example found in the latest CSL (version 3.03) on the TMS320C5535. The documentation mentions that TI provides a PC application that can be used to test the USB functionality. Can someone please provide a link to download this software?

Thanks,

Dan

EVM5515 Audio Pass Through

w longenecker — Fri, 11 Feb 2011 17:17:54 GMT

Basically we're just trying to pass an audio signal from a stereo input to the headphone output. To be honest, we've recycled a lot of the sample code from the sine wave demo. We did the majority of the modifications in the dma.c file (included). We believe it should just play an audio signal, in this case provided by a headphone output on a pc to a stereo input, at the headphone output.

Here are two of the recieving and transmitting DMA functions:

Uint16 set_dma0_ch0_i2s0_Lout(void)

{

Uint16 temp;

DMA0_CH0_TC_LSW = XMIT_BUFF_SIZE*2;

DMA0_CH0_TC_MSW = 0x3204; //src incre, destination fix, sync, auto, int

#endif

temp = DMA0_CH10_EVENT_SRC;

DMA0_CH10_EVENT_SRC = temp | 0x0001; // I2S2 transmit event

DMA0_CH0_SRC_LSW = (Uint16)TxL1_DMA_address;

DMA0_CH0_SRC_MSW = 0xFFFF & (TxL1_DMA_address >> 16);

DMA0_CH0_DST_LSW = 0x2808; // is20 transmit left data register lsw

DMA0_CH0_DST_MSW = 0;

// CurrentTxL_DMAChannel =1;

// DMA starts

temp = DMA0_CH0_TC_MSW;

temp |= 0x8000;

DMA0_CH0_TC_MSW = temp;

return SUCCESS;

}

-----------------------------------------------------------------------------------------------------------------------------------------------------

And the input function

Uint16 set_dma0_ch2_i2s0_Lin(void)

{

Uint16 temp;

DMA0_CH2_TC_LSW = XMIT_BUFF_SIZE*2;

DMA0_CH2_TC_MSW = 0x3084; //src fix, destination increase, sync, auto, int

temp = DMA0_CH32_EVENT_SRC;

DMA0_CH32_EVENT_SRC = temp | 0x0002; // I2S2 receive event

DMA0_CH2_DST_LSW = (Uint16)RxL1_DMA_address;

DMA0_CH2_DST_MSW = 0xFFFF & (RxL1_DMA_address >> 16);

DMA0_CH2_SRC_LSW = 0x2828; // is22 receive left data register lsw

DMA0_CH2_SRC_MSW = 0;

// CurrentRxL_DMAChannel =1;

// DMA starts

temp = DMA0_CH2_TC_MSW;

temp |= 0x8000;

DMA0_CH2_TC_MSW = temp;

return SUCCESS;

}

--------------------------------------------------------------------------------------------------------------------------------------------------------------------

We don't have a ton of experience with the DSP's and we're hoping a pair of experienced eyes could spot a simple fix. The remainder of the project is included as well.

Thanks very much in advance!

William Longenecker & Doug Lambert(Please visit the site to view this file)

g726DecoderMain.c of TI sample G.726 Decoder / Encoder

Yu — Mon, 20 May 2013 13:01:46 GMT

Hi all,

I downloaded from the page of the TI G726 Encoder and Decoder c55xx, but there are questions.

http://software-dl.ti.com/dsps/dsps_public_sw/codecs/C55X_Speech/index_FDS.html
G726 Encoder and Decoder, Version 2.00.00.012

・g726DecoderMain.c ([install folder]\G726_3X_REL200_ROOTDIR\g726\tstsrc\c55x)

line 121 to 123
        tablesPtr [0] = (void *) G726_TII_g726itbl40;
        tablesPtr [1] = (void *) G726_TII_adpcmalaw;
        tablesPtr [2] = (void *) G726_TII_adpcmmulaw;
It has been an assignment, but can I do? Describe this three lines without thinking?

I think to try to linear PCM format of the PCM, but it is sufficient to describe the three rows in that case?

G726_TII_g726itbl40 is like the encoder table but can not find it.
Please tell me the meaning for the above process.

Regards.

EZDSP5515 runs OK in Debug but when I convert to .bin gets stuck in a loop.

Roman bere — Sun, 19 May 2013 22:55:34 GMT

Really need your help.

my project is to make a 4 channel colour organ using the build in FFT basically it's a spectrum analyzer,

the 4 leds on the board respond to the different frequencies

In Debug the application runs fine.
But when I try to convert to a bin file and run it gets stuck (stand alone project)
in the while loop "while((I2S0_IR & RcvR)== 0 )"
don't know why, run out of Ideas.
I have commented all the lines in the .gel file and I configured the clocks
don't know what to look for next.

Been working on this for 6 weeks, and 2 weeks pulling my hair out.

Been searching the forum found a lot of information and incorporated it within my app. now I'm really stuck.

To make it easier for me, I combined all the function within the main application. to make it easier to debug, instead of bouncing around

Regards

Roman

Below is the snippet, I have also included the complete directory
================================================================

void aic3204_read(Int16* left_input, Int16* right_input)
{
    volatile Int16 dummy;
    counter_1 = 0;

    /* Read Digital audio inputs */

/*   gets stuck here -- need help don't know the cause
      gets stuck here -- need help don't know the cause
      gets stuck here -- need help don't know the cause
      gets stuck here -- need help don't know the cause

      I2S0_IR bit 3 in Debug it's OK all works great
      but when I try to convert to .BIN gets stuck here */
//    led(1);         // test to determine where it gets stuck

    while((I2S0_IR & RcvR)== 0 ) //& (I2S0_IR & RcvL)== 0 )// (0x2810) & 0x08
    {
//    led(2);         // test to determine where it gets stuck LED stay on
        counter_1++; // Wait for receive interrupt

    }

Header file ig726enc.h of TI sample G.726 Decoder / Encoder

Yu — Mon, 20 May 2013 12:29:57 GMT

Hi all,

I downloaded from the page of the TI G726 Encoder and Decoder c55xx, but there are questions.

http://software-dl.ti.com/dsps/dsps_public_sw/codecs/C55X_Speech/index_FDS.html
G726 Encoder and Decoder, Version 2.00.00.012

Appendix B Table B-1 and Appendix A Table A-1 of g726_api_ref_xdais.doc
How to specify is unknown about CompandingLaw of No. 3 in.

the comments of ig726dec.h and ig726enc.h
   CONST_COMP_ALAW_8
   CONST_COMP_MULAW_8
   CONST_COMP_LINEAR_8 (no companding)

It is written above and can be used, but I do not know the value because there is no # define.

Regards.

Interfacing the TI ADS1294R (Analog Front End for ECG) with the C5535

Aritra Paul — Tue, 14 May 2013 04:29:21 GMT

Hi there!

Developing an ECG module with the C5535, and I was trying to obtain data from the ADS1294R through SPI.

Could you point me to some sample reference programs for similar applications? My goal is to get familiarized with the SPI interface of the C5535.

Thank you!

Problems using dlms() function of dsplib

Nacuri — Mon, 20 May 2013 05:12:09 GMT

Hello all

We are developing our application using the TMS320C5515 DSP Evaluation Module and the TLV320AIC34 (Codec) Evaluation Module. We created a breadboard for interconnecting the boards.

We have problems using dlms( ) function of Dsplib 2.4 library. When the code runs from ram using Code Composer 5.3.0 there is a noise of about 100 hz no matter there are not voices (or any sound) at the microphones.

When the dlms () function is not called in the application, there is not that 100 Hz noise and the voices are heard normally at the output of the codec.

On the other hand, when running the code from flash there is only noise at the output of the codec.

Does anyone have idea what is happening? What could be missing when calling the dlms () function?

Best Regards

Nacuri

ezdsp5505 i2c

seeni vasan — Sun, 19 May 2013 13:51:26 GMT

hai

once i assigned the audio codec aic3204 to detect the headset and i tried to read the the page 1 regester 68 before the headset connected it gives the value that it is not detected and value is 136 once when connected it gives decimal value 168 that headset is detected again when it is removed it gives the headset is detected .is it necessary to give some delay and read the register or every time i has to reset the audio codec and reinitialise the register for our application and read the headset detect register.At one time the page read gives the correct value and the next read it gives zeros to all the register in the page1.

with regards

seeni

C55xx AEC Software Link Broken

JasonHaedt — Thu, 16 May 2013 16:36:01 GMT

Dear TI,

The link seems dead, can you let me know if you have this code or can update the link: https://focus-webapps.ti.com/licreg/docs/swlicexportcontrol.tsp?form_type=2&prod_no=aer_c55l_obj_16_1_0_3_Win32.exe&ref_url=http://software-dl.ti.com/libs/aer/latest/&form_id=154910

Thanks,

Jason Haedt

Confirm CLKOUT pin behavior of C553x

Kato Motoki — Thu, 28 Mar 2013 02:15:28 GMT

Hi community member,

Please let me confirm the following question.

[Question.1]

Regarding to the TRM of C553x, CLKOUT pin can generate the signal of PLLOUT by changing the register of CCSSR.

However, I could not see the PLLOUT even though I changed the register from mode11 to mode 2.

Can this pin generate the PLLOUT signal?

[Question.2]

Regarding to the register map of CCSSR, there are the same descriptions (i.e. CLKOUT pin outputs System PLL output clock, PLLOUT.) on this table.

Is there any differences for those descriptions? (i.e. is there any difference between mode2 and mode 4 and so on?)

Note: Mode2 means that the value of SRC is "2h". Mode4 also means that the value of SRC is "4h".

If you have any questions, please let me know.

Best regards,

Kaka