CCS/EVMK2H: Fail to burn U-boot to EVMK2H with CCS

Here is when I connect to core 0 ,GEL will output  below:

IcePick_D_0: Warning: A firmware update is recommended for the XDS200 debug probe. Click the "Update" button to update the firmware. Click the "Continue" button to continue without updating. (Emulation package 7.0.48.0)
C66xx_0: GEL Output:
Connecting Target...
C66xx_0: GEL Output: TCI6638K2K GEL file Ver is 1.60000002
C66xx_0: GEL Output: Detected PLL bypass enabled: SECCTL[BYPASS] = 0x00800000
C66xx_0: GEL Output: (2a) MAINPLLCTL1 = 0x00000040
C66xx_0: GEL Output: (2b) PLLCTL = 0x00000048
C66xx_0: GEL Output: (2c) PLLCTL = 0x00000048
C66xx_0: GEL Output: (2d) Delay...
C66xx_0: GEL Output: (2e) SECCTL = 0x00810000
C66xx_0: GEL Output: (2f) PLLCTL = 0x0000004A
C66xx_0: GEL Output: (2g) Delay...
C66xx_0: GEL Output: (2h) PLLCTL = 0x00000048
C66xx_0: GEL Output: (4)PLLM[PLLM] = 0x0000000F
C66xx_0: GEL Output: MAINPLLCTL0 = 0x05000000
C66xx_0: GEL Output: (5) MAINPLLCTL0 = 0x07000000
C66xx_0: GEL Output: (5) MAINPLLCTL1 = 0x00000040
C66xx_0: GEL Output: (6) MAINPLLCTL0 = 0x07000000
C66xx_0: GEL Output: (7) SECCTL = 0x00890000
C66xx_0: GEL Output: (8a) Delay...
C66xx_0: GEL Output: PLL1_DIV3 = 0x00008002
C66xx_0: GEL Output: PLL1_DIV4 = 0x00008004
C66xx_0: GEL Output: PLL1_DIV7 = 0x00000000
C66xx_0: GEL Output: (8d/e) Delay...
C66xx_0: GEL Output: (10) Delay...
C66xx_0: GEL Output: (12) Delay...
C66xx_0: GEL Output: (13) SECCTL = 0x00090000
C66xx_0: GEL Output: (Delay...
C66xx_0: GEL Output: (Delay...
C66xx_0: GEL Output: (14) PLLCTL = 0x00000041
C66xx_0: GEL Output: PLL has been configured (CLKIN * PLLM / PLLD / PLLOD = PLLOUT):
C66xx_0: GEL Output: PLL has been configured (122.879997 MHz * 16 / 1 / 2 = 983.039978 MHz)
C66xx_0: GEL Output: Power on all PSC modules and DSP domains...
C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=2, md=9!
C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=17, md=25!
C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=17, md=26!
C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=18, md=27!
C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=19, md=28!
C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=19, md=29!
C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=20, md=30!
C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=20, md=31!
C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=20, md=32!
C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=20, md=33!
C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=21, md=34!
C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=22, md=35!
C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=22, md=36!
C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=23, md=37!
C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=23, md=38!
C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=24, md=39!
C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=24, md=40!
C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=24, md=41!
C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=24, md=42!
C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=25, md=43!
C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=25, md=44!
C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=25, md=45!
C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=25, md=46!
C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=26, md=47!
C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=27, md=48!
C66xx_0: GEL Output: Power on all PSC modules and DSP domains... Done.
C66xx_0: GEL Output: WARNING: SYSCLK is the input to the PA PLL.
C66xx_0: GEL Output: Completed PA PLL Setup
C66xx_0: GEL Output: PAPLLCTL0 - before: 0x0x098804C0  after: 0x0x09080500
C66xx_0: GEL Output: PAPLLCTL1 - before: 0x0x00000040  after: 0x0x00002040
C66xx_0: GEL Output: DDR begin
C66xx_0: GEL Output: XMC setup complete.
C66xx_0: GEL Output: DDR3 PLL (PLL2) Setup ...
C66xx_0: GEL Output: DDR3 PLL Setup complete, DDR3A clock now running at 666 MHz.
C66xx_0: GEL Output: DDR3A initialization complete
C66xx_0: GEL Output: DDR3 PLL Setup ...
C66xx_0: GEL Output: DDR3 PLL Setup complete, DDR3B clock now running at 800MHz.
C66xx_0: GEL Output: DDR3B initialization complete
C66xx_0: GEL Output: DDR done

Hi, Rex

Thanks for your reference. I follow this section to load and run U-Boot, It did run U-boot. UART  did print the U-Boot message.

Hi, Jacky,

When you followed the steps in "SPI NOR Flash Programming", did you do step 3 to load .gph to address 0x87000000? If you did, the other thing you did differently is you issued "env default -f -a" which doesn't exist in the instruction. I suspect either you didn't do step 3 or "dev default' cleared the download area.

If you have TFTP server setup and .gph file in tftp download directory, you can use CCS to bring up to U-boot prompt, then in the UART console type the following commands:

> env default –f –a

> setenv serverip <tftp_server_ip>

> setenv tftp_root <tftp_directory>

> run get_uboot_net

> run burn_uboot_spi

The "run get_uboot_net" is equivalent to step 3 in the instruction. The above commands are documented in U-boot User's Guide (Note for KS2 platforms),

http://software-dl.ti.com/processor-sdk-linux/esd/docs/latest/linux/Foundational_Components_U-Boot.html#spi

The "Once u-boot prompt is available" is when you hit any key to stop u-boot booting and get a u-boot prompt.

Rex

Hi Rex

1,Yes, I  do step 3 to load .gph to address 0x87000000 .

2,Why has "env default -f -a" instruction?

Because if I don't enter this instruction, it will come to error message. And I don't know why. 

=> run burn_uboot_spi
## Error: "burn_uboot_spi" not defined

3,I confuse this "setenv filesize <size in hex of u-boot-spi.gph rounded to hex 0x10000>" on the document

   I guess this is not instruction,and it tell should enter size of u-boot-spi.gph,such as "setenv 0x80000". Am I right?

4.Thanks for your document for tftp u-boot. I will try it when I solve this issue

Best Regards

Jacky

Hi, Jacky,

The "env default -f -a" is to reset the u-boot env variables. It didn't find burn_uboot_spi is because the command is new in Processor SDK. In the old MCSDk, the command is burn_uboot (no _spi). It apparently that the EVM was running old MCSDK u-boot before. I didn't mention in my previous post that I don't thihk env default command would wipe out the memory at address 0x87000000, and don't thnk that is the cause of your failure. In your case, you should issue "env default" to reset the u-boot env to those of new ProcSDK settings. Once programming .gph is successful, issue "env default" aftter u-boot comes back after reboot, and saveenv afterward.

"setenv filesize <size in hex of u-boot-spi.gph rounded to hex 0x10000>"  means to set the filesize of .gph to the next 0x10000 (64KB) page. That is, if size is 0xa3604, then "setenv filesize 0xb0000" . Setting filesize is needed if you program the NOR using step 3. If you get the file using "run get_uboot_net", then you don't need to do step 3 and the filesize will be set automatically by tftp download.

Rex

Hi,Rex

I try to program .gph , but u-boot is not working successfully.

My  filesize  of .gph is 0x a360c ,so I setenv filesize 0xb0000. And the UART show written OK

But After  Power off the EVM, Set the SW1 dip switch to SPI mode,Power up the EVM .UART still don't have anything show up !!!!

May I ask how to confirm u-boot really burn to NOR flash?

Best Regards

Jacky

Hi, Rex ,

It did work ,When I switch to SPI mode . UART show up  u-boot message.

Thanks very much 

Best Regards

Jacky