EVMK2H: Enquiry about EVMK2H Clock Frequency

Chanh Nguyen64

Expert 1190 points

Part Number: EVMK2H

Hello everyone,

I have some querries about the EVMK2H Clock Frequency:

I read the register DEVSPEED (0x02620C98), the value is 0x00020000, means the DSP is 1.2GHz and the ARM is 800MHz. Is it correct, as I thought the ARM core of EVMK2H has the speed of 1.4GHz?
Let say my DSP speed is 1.2GHz, I use function platform_init() from the PDK to set the DSP clock. My question is, can I set the value of PLLM to 20, means the DSP clock is 1228.8 MHz, or I can only set PLLM to be 18, means the maximum DSP clock I can set is 1105.92 MHz?
Is there any hardware output pin on the borad that I can use to measure the DSP clock or ARM clock?

Please advise on the above querries. Thanks a lot in advance.

over 4 years ago

0 Yordan Kovachev over 4 years ago

TI__Guru**** 161600 points

Hi,

I read the register DEVSPEED (0x02620C98), the value is 0x00020000, means the DSP is 1.2GHz and the ARM is 800MHz. Is it correct, as I thought the ARM core of EVMK2H has the speed of 1.4GHz?

Let say my DSP speed is 1.2GHz, I use function platform_init() from the PDK to set the DSP clock. My question is, can I set the value of PLLM to 20, means the DSP clock is 1228.8 MHz, or I can only set PLLM to be 18, means the maximum DSP clock I can set is 1105.92 MHz

This would depend on which processor is used in the board, see Section 12.1 Device Nomenclature in the Datasheet. If your processor supports the 1.4GHz clock speed, then it should be possible to modify the board lib and set the correct device speed. You can check Set_Pll1() function in the xtcievmk2x_arm.gel or xtcievmk2x.gel files for supported values of PLLM & PLLD.

Best Regards,
Yordan

0 Chanh Nguyen64 over 4 years ago in reply to Yordan Kovachev

Expert 1190 points

Hi Yordan,

Do you mean that the value of DEVSPEED could be changed by modifying board lib? I though it should be fixed by the processor maximum speed?

is the Device Nomenclature come along with the board in a document? Sorry I recieve the board from another person without any document, so I do not know where to find the Device Nomenclature of my processor. If the DEVSPEED is not fixed, and I does not have the document regarding my processor, any software tool I can use to retrieve the processor specification?

For the 2nd and 3rd questions, any advise?

Thanks.

0 Yordan Kovachev over 4 years ago in reply to Chanh Nguyen64

TI__Guru**** 161600 points

Hi,

Do you mean that the value of DEVSPEED could be changed by modifying board lib? I though it should be fixed by the processor maximum speed?

Perhaps I was not clear and caused a confusion. I mentioned it depends on the processor, meaning that the DEVSPEED shows the device's speed grade. So, yes your understanding is correct, you cannot exceed what is specified in the Device Speed Register, see: https://e2e.ti.com/support/processors/f/791/t/658292

Let say my DSP speed is 1.2GHz, I use function platform_init() from the PDK to set the DSP clock. My question is, can I set the value of PLLM to 20, means the DSP clock is 1228.8 MHz, or I can only set PLLM to be 18, means the maximum DSP clock I can set is 1105.92 MHz?

As I stated in my previous reply, you can refer to the GEL file:
     else if(index == 5){            // 122.88 MHz -> 1.228 GHz
        CLKIN_val   = 122.88;          // setup CLKIN to 122.88 MHz
        PLLM_val    = 20;           // setup PLLM (PLL multiplier) to x20
        PLLD_val    = 1;            // setup PLLD (reference divider) to /1
        OD_val      = 2;            // setup OD to a fixed /2
    }

Is there any hardware output pin on the borad that I can use to measure the DSP clock or ARM clock?

You could use the SYSCLKOUT pin:
https://e2e.ti.com/support/processors/f/791/t/829750

If the DSP speed is 1.2GHz you could set PLLM = 20.

Best Regards,
Yordan

0 Rahul Prabhu over 4 years ago in reply to Yordan Kovachev

TI__Guru** 114410 points

Chanh,

I would like to provide some clarification to Yordan`s responses and observations that don`t match your observations from the EVM setup. The DEVSPEED value that I am reading from the EVM is 0x00800002.

this translates to ARM And DSP speed of 1.2 Ghz which is expected value since the part used on the EVM as per the BOM is TCI6638 or 66AK2H12DAAW2 which is the 1.2 Ghz variant. For 1.4 Ghz ARM support, you need to use the 66AK2H12DAAW24 variant of the device.

the DEVSPEED register latches values that TI programs in the device during manufacturing so it can`t be written to and modified in runtime to run the device at higher speed. The DEVSPEED indicates the highest speed grade that the silicon is qualified to run. Please provide a screen capture of the memory browser similar to what I have provided so we can confirm the device programming.

There is a SYSCLKOUT pin on the SOC that outputs the programmed SYSCLK value/6 so for 1.2 Ghz PLL settings you should read 200 Mhz on that pin. This pin is meant only for debug purposes.

Regards,

Rahul

0 Chanh Nguyen64 over 4 years ago in reply to Rahul Prabhu

Expert 1190 points

Hi Yordan and Rahul,

My device memory browser is as below:

According to the datasheet it should be 1.2GHz DSP + 800 MHz ARM. Please correct me if I was wrong.

Another question, for DSP speed, your reading is 0x0080, mine is 0x0002, from datasheet both of them point to 1.2 GHz. Any different between the processor that has value 0x0080 and 0x0002?

Thanks.

0 Rahul Prabhu over 4 years ago in reply to Chanh Nguyen64

TI__Guru** 114410 points

Can you please provide the revision of the EVM that you are using ? If possible, you may also want to run the GEL file below to provide us the DIEID and JTAGID to understand the revision of the silicon in use. You can see from samples listed below that we only have orderable variants with ARM and DSP at 1.2 GHz or ARM at 1.4Ghz and DSP at 1.2 Ghz.

http://www.ti.com/product/66AK2H12/samplebuy

We have not shipped any EVMs with the configuration that you are reading from the efuse.

0 Rahul Prabhu over 4 years ago in reply to Rahul Prabhu

TI__Guru** 114410 points

I have attached a GEL file here that you can run on your platform which will allow us to read back DEVSPEED, JTAGID, DEVSTAT, DIEID from your device.

6266.K2H_register_dump.gel

Can you please use the GEL in CCS (In CCS Debug View Tools->GEL files; Right click and import the GEL attached ). You can then go into Scripts-> K2H Device Efuse settings and provide the log here.

Regards

Rahul

0 Chanh Nguyen64 over 4 years ago in reply to Rahul Prabhu

Expert 1190 points

Hi Rahul,

The EVM board revison is Rev. A102-1

Sorry I did not found where is the attachment. Could you please check? Thanks.

0 Rahul Prabhu over 4 years ago in reply to Chanh Nguyen64

TI__Guru** 114410 points

I have updated my earlier post with the GEL file attached and checked that I can download it. Please run this on the EVM and provide us the log to analyze.

I have also attached the log that I observed from the EVM at my desk for your reference:

K2H_EVM_log.txt

arm_A15_0: GEL Output:  *******************************************************************************************************
arm_A15_0: GEL Output:  ********************************** K2H EFUSE STATUS and SNAPSHOT ******************************
arm_A15_0: GEL Output:  *******************************************************************************************************

arm_A15_0: GEL Output:  ********************************** K2H DEVSTAT Register (DEVSTAT) ************************************

arm_A15_0: GEL Output:  DEVSTAT ---> 0x02012005
arm_A15_0: GEL Output:  ********************************** K2H JTAGID Register (JTAGID) ************************************

arm_A15_0: GEL Output:  BOOTCFG_JTAGID ---> 0x1B98102F
arm_A15_0: GEL Output:  ********************************** K2H MACID Register (MACID) ************************************

arm_A15_0: GEL Output:  MACID[31:0] ---> 0xBAAB26FF
arm_A15_0: GEL Output:  MACID[32:47] ---> 0xC4ED
arm_A15_0: GEL Output:  BCAST[16](Broadcast Reception) ---> Broadcast
arm_A15_0: GEL Output:  BCAST[17](MAC Flow Control) ---> Off
arm_A15_0: GEL Output:  CHECKSUM[24:31] ---> 0x10

arm_A15_0: GEL Output:  *******************************************************************************************************
arm_A15_0: GEL Output:  ********************************** K2H DEVICE SPEED CONFIGURATION ******************************************************
arm_A15_0: GEL Output:  *******************************************************************************************************

arm_A15_0: GEL Output:  BOOTCFG_EFUSE_RSVD2 ---> 0x00800002
arm_A15_0: GEL Output:  DEVICE SPEED[27:16] ---> 1.2288 GHz
arm_A15_0: GEL Output:  ARM SPEED[27:16] ---> 1.2288 GHz
arm_A15_0: GEL Output:  ********************************** KS-II DIEID Register (DIEID) ************************************

arm_A15_0: GEL Output:  DIEID0 ---> 0x1000C00E
arm_A15_0: GEL Output:  DIEID1 ---> 0x0401024F
arm_A15_0: GEL Output:  DIEID2 ---> 0x20000000
arm_A15_0: GEL Output:  DIEID3 ---> 0x681A0001
IcePick_D_0: Power Failure on Target CPU 
arm_A15_0: Failed to remove the debug state from the target before disconnecting.  There may still be breakpoint op-codes embedded in program memory.  It is recommended that you reset the emulator before you connect and reload your program before you continue debugging

0 Chanh Nguyen64 over 4 years ago in reply to Rahul Prabhu

Expert 1190 points

Hi Rahul,

I have run the proviede GEL file. Please find the log as below.

8473.Log.txt

arm_A15_0: GEL Output:  *******************************************************************************************************
arm_A15_0: GEL Output:  ********************************** K2H EFUSE STATUS and SNAPSHOT ******************************
arm_A15_0: GEL Output:  *******************************************************************************************************

arm_A15_0: GEL Output:  ********************************** K2H DEVSTAT Register (DEVSTAT) ************************************

arm_A15_0: GEL Output:  DEVSTAT ---> 0x02000001
arm_A15_0: GEL Output:  ********************************** K2H JTAGID Register (JTAGID) ************************************

arm_A15_0: GEL Output:  BOOTCFG_JTAGID ---> 0x0B98102F
arm_A15_0: GEL Output:  ********************************** K2H MACID Register (MACID) ************************************

arm_A15_0: GEL Output:  MACID[31:0] ---> 0xEAF6F762
arm_A15_0: GEL Output:  MACID[32:47] ---> 0x0017
arm_A15_0: GEL Output:  BCAST[16](Broadcast Reception) ---> Broadcast
arm_A15_0: GEL Output:  BCAST[17](MAC Flow Control) ---> Off
arm_A15_0: GEL Output:  CHECKSUM[24:31] ---> 0xA0

arm_A15_0: GEL Output:  *******************************************************************************************************
arm_A15_0: GEL Output:  ********************************** K2H DEVICE SPEED CONFIGURATION ******************************************************
arm_A15_0: GEL Output:  *******************************************************************************************************

arm_A15_0: GEL Output:  BOOTCFG_EFUSE_RSVD2 ---> 0x00020000
arm_A15_0: GEL Output:  DEVICE SPEED[27:16] ---> 1.2288 GHz
arm_A15_0: GEL Output:  ARM SPEED[27:16] ---> 800 MHz
arm_A15_0: GEL Output:  ********************************** KS-II DIEID Register (DIEID) ************************************

arm_A15_0: GEL Output:  DIEID0 ---> 0x0100A008
arm_A15_0: GEL Output:  DIEID1 ---> 0x0401022E
arm_A15_0: GEL Output:  DIEID2 ---> 0x00000000
arm_A15_0: GEL Output:  DIEID3 ---> 0x38CA0020

Thanks.

0 Rahul Prabhu over 4 years ago in reply to Chanh Nguyen64

TI__Guru** 114410 points

I have analyzed the log and it seems from the JTAGID that you are using PG 1.0 silicon which is fairly old revision of the silicon. Are you using K2H EVM Rev 4.0 or older? The production EVM should have PG 1.1 and later as far as I can tell.

I suspect that the DEVSPEED encoding changed or was not applicable for older versions of the silicon as the higher speeds were not available with earlier versions of the silicon. I am checking on this detail with our product engineering teams to find out the history on this issue. Also note that the location of DEVSPEED change after PG 1.1 silicon as you can see from the data sheet:

0 Chanh Nguyen64 over 4 years ago in reply to Rahul Prabhu

Expert 1190 points

Hi Rahul,

From the tag on the board, the it is EVM Rev 1.1

I also notice that there are 2 diffrent address of DEVSPEED. I am not sure what is my processor silicon revision. However from the memory map, seems the address 0x02620C98 is the correct address which give the value 0x00020000. The address 0x02620C90 give the value 0x00000000

Thanks.

0 Rahul Prabhu over 4 years ago in reply to Chanh Nguyen64

TI__Guru** 114410 points

Chanh,

I recommend that you run the DSP and ARM at speeds that are specified in our GEL files as they are meant for the Nominal use case. It appears that PG 1.1 on the EVM that you are using doesn`t have the EFUSE programming that reflects the DEVSPEED and ARMSPEED spec that is available in the latest data sheet as they may be pre-production parts used on the EVM version that you have.

When you order production K2H parts, they will have the right set of DEVSPEED and ARMSPEED programmed in the efuse that can be used for your usecase. If you have the production EVM (rev 4.0) with PG2.0 silicon, that should have the correct settings.

Let us know if you have any further questions.

Regards,

Rahul

0 Chanh Nguyen64 over 4 years ago in reply to Rahul Prabhu

Expert 1190 points

Hi Rahul,

Noted. Thanks a lot.

Processors

Processors forum

EVMK2H: Enquiry about EVMK2H Clock Frequency