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.

66AK2L06: 66AK2L06 CVDD1 supply

Part Number: 66AK2L06

Hi, 

Based on the K2L EVM, its recommeded to use 1.0V for CVDD1, is it correct? But on 66AK2L06 datasheet, its stated should use 0.95V for CVDD1 (page 215), on page 212 its recommended to use 1.0V (nominal) for cvdd1, which one is correct? is the 66AK2L06 able to turn on if i using 1.0V for CVDD1?  Currently i follow the same power sequencing as stated in the EVM board but my board still not able to bootup, could you please help on this? Thanks.

  • Btw, systemclock was there, and i set the DSP to boot from flash. The reset_stat pin showing high, bootcomplete pin was low, and there is no SPI clk from DSP.
  • Hi,

    I am working on this. I will post my findings here.

    Best Regards,
    Yordan
  • Hi,

    I checked this and there is a mistake in 10.2 Recommended Operating Conditions(1)(2) (page 212 in the datasheet). The nominal voltage of CVDD1 is 0.95.
    The K2L EVM also uses 0.95V. Another confirmation is:
    e2e.ti.com/.../503206

    Currently i follow the same power sequencing as stated in the EVM board but my board still not able to bootup, could you please help on this?

    Verify that you use the following power-up sequence:
    The first sequence stipulates the core voltages starting before the IO voltages as shown below.
    1. CVDD
    2. CVDD1, VDDAHV, AVDDAx, DVDD18
    3. DVDDR
    4. VDDALV, VDDUSB, VP, VPTX
    5. DVDD33, VPH
    The second sequence provides compatibility with other TI processors with the IO voltage starting before
    the core voltages as shown below.
    1. VDDAHV, AVDDAx, DVDD18
    2. CVDD
    3. CVDD1
    4. DVDDR
    5. VDDALV, VDDUSB, VP, VPTX
    6. DVDD33, VPH

    Best Regards,
    Yordan
  • Thanks. Finally I am able to get the chip up successfully, but i still not able to boot from flash. Maybe due to my bootmode setting. Btw does it mean the power sequencing is correct if i able to connected to the DSP chip using emulator?
  • Btw does it mean the power sequencing is correct if i able to connected to the DSP chip using emulator?

    Yes, connecting to the SoC via JTAG should indicate that the SoC is powered up. Are you able to access the device registers?. You can use the GEL files & CCS to debug.

    Best Regards,
    Yordan
  • Thanks. I now able to connect to the chip using emulator and debug using CCS. I am using the same register setting as the evm board. However my chip not able to boot from the flash. I check through boundary scan, it seem like my SPI nor flash and DDR3 memory was connected correctly and i able to run some test to tested them out through the JTAG and boundary scan. Is there any step i have missed out?I loaded the .gph extension file into the boot flash, could it support? or i need to convert the .gph file to binary before loaded them to binary? Thanks

  • Hi,

    Which SDK is this, linux or rtos?

    Best Regards,
    Yordan
  • I am uisng linux.

    Second question, I try to debug through emulator, by sequence, the image stored in the internal ram first right? then the image will move to DDR3? I now not even able to write/read from DDR3. I follow the register setting as defined in the spreadsheet provided by TI for 2 x  DDR3 (MT41K256M16TW-107 IT:P). How do i ensure i set the correct register for initialization?

    Or write leveling is need to set first? i am using fly-by topology for DDR3 routing. Hope you can give me a hand on this. Thanks a lot!

  • Ok, yes it supports .gph files.

    How did you build your u-boot? You should follow this guide:
    processors.wiki.ti.com/.../Linux_Core_U-Boot_User's_Guide

    If the above seqeuence doesn't work. My first guess is that DDR settings are not correct.

    Can you try loading the .gel files through CCS & execute the ddr tests? If they work, then use the same ddr controller settings in u-boot.

    Best Regards,
    Yordan
  • Hi Yordan, Thanks for your prompt reply. May i know where to get the gel files?
  • They should come with the CCS installation.
    If you've installed CCS in your home folder, then look at the bellow location:
    ~/ti/ccsv7/ccs_base/emulation/boards/tcievmk2l/gel

    Best Regards,
    Yordan
  • Hi Yordan,

    We able to find the gal files and loaded to css to test memory read write. However we get this error listed below. Do you know what is the error Error -1205 @ 0x80000000? Do i need to change the memory block location? 

    arm_A15_0: GEL Output: PLL has been configured (CLKIN * PLLM / PLLD / PLLOD = PLLOUT):           

    arm_A15_0: GEL Output: PLL has been configured (122.879997 MHz * 16 / 1 / 2 = 983.039978 MHz)              

    arm_A15_0: GEL Output: DDR3 PLL Setup ...         

    arm_A15_0: GEL Output: DDR3 PLL Setup complete, DDR3A clock now running at 533MHz.

    arm_A15_0: GEL Output: DDR3A initialization complete    

    arm_A15_0: GEL Output: Memory Test Write Core: 0, Mem Start: 0x0x80000000, Mem Size: 0x0x00000100, value: 0x0xAAAAAAAA ...

    arm_A15_0: GEL Output: Memory Test Read Core: 0, Mem Start: 0x0x80000000, Mem Size: 0x0x00000100 ...             

    arm_A15_0: Trouble Reading Memory Block at 0x80000000 on Page 0 of Length 0x4: (Error -1205 @ 0x80000000) Device memory bus has an error and may be hung. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 6.0.222.0)     

    ddr3A_write_read_test() cannot be evaluated.     

    Target failed to read 0x80000000             

                   at read_data=*((unsigned int *) mem_location) [tcievmk2l_arm.gel:2406]

                   at ddr3A_write_read_test()arm_A15_0: Trouble Reading Register REG_SYSTEM_TARGET_CONFIG: (Error -1141 @ 0x3D58) Device is not responding to the request. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 6.0.222.0)

    arm_A15_0: Trouble Reading Register REG_SYSTEM_MMU_CONFIG: (Error -1141 @ 0x3D58) Device is not responding to the request. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 6.0.222.0)    

    arm_A15_0: Failed CPU Reset (SW): (Error -1141 @ 0x3D58) Device is not responding to the request. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 6.0.222.0)        

  • Hi,

    In general you can consult this wiki for setting DDR correctly:
    www.ti.com/.../sprabx7.pdf

    I think this is purely sw problem now. Can you close this thread & start a new one, describing your problem?

    Best Regards,
    Yordan