EVMK2H: Board suddenly stopped booting

Thanks a lot Yordan,
I am not really familiarised with this, however I have set the variables just like you said but still the same, maybe I did change the wrong file.
Can you please tell me what file should I modify and whether or not I have to recompile something else.
And I still don't understand why did it happen since it was working properly and it started failing all of a sudden.
Thanks

HI,
I have tried what you suggested me but I didn't succeed. I found this other link (processors.wiki.ti.com/.../Kernel_-_Common_Problems_Booting_Linux) with the same situation I'm having but all the same :(
I will try a new installation from scratch to see how it goes.
Thanks

Hello,
I'm still having the same problem reported in the beginning of this thread, I did a new independent installation just to test but that is out of the scope. I am still concerned and trying to solved the initial problem with the initial installation. I have already tried everything I was suggested to do but still no success.
I really appreciate any help in this matter.
Thanks

Hello,
Thank you very much for your help

I have just done what you have suggested like follows:

1) Add #define DEBUG to /include/configs/k2hk_evm.h

2) Rebuild uboot
cd ti-processor-sdk-linux-k2hk-evm-03.01.00.06/
make u-boot-spl

3) copy the new generated .gph into the tftpboot
cp u-boot-spi.gph /home/user/ti/tftpboot/

4) get it and burn it (succeed)

U-Boot # env default -f -a
U-Boot # setenv serverip <ip address of tftp server>
U-Boot # setenv tftp_root <tftp root directory>
U-Boot # setenv name_uboot u-boot-spi.gph
U-Boot # run get_uboot_net
U-Boot # run burn_uboot_spi

5) Set up the variables for booting up again

env default -f -a
setenv boot net
setenv mem_reserve 1536M
setenv serverip 84.88.51.137
setenv tftp_root 84.88.51.137:/home/user/ti/tftpboot
setenv name_fdt keystone-k2hk-evm.dtb
setenv name_kern zImage-keystone-evm.bin
setenv nfs_root /home/user/ti/evmk2h_nfs
setenv nfs_serverip 84.88.51.137
saveenv
boot

6) Booting output

___________________________________________________________
netcp@2000000 Waiting for SGMII auto negotiation to complete. done
BOOTP broadcast 1
BOOTP broadcast 2
DHCP client bound to address 84.88.51.193 (258 ms)
Using netcp@2000000 device
TFTP from server 84.88.51.137; our IP address is 84.88.51.193
Filename '/home/user/ti/tftpboot/k2-fw-initrd.cpio.gz'.
Load address: 0x88080000
Loading: ##########
        1 MiB/s
done
Bytes transferred = 49676 (c20c hex)

netcp@2000000 Waiting for SGMII auto negotiation to complete. done
BOOTP broadcast 1
DHCP client bound to address 84.88.51.193 (6 ms)
Using netcp@2000000 device
TFTP from server 84.88.51.137; our IP address is 84.88.51.193
Filename '/home/user/ti/tftpboot/keystone.dtb'.
Load address: 0x88000000
Loading: ###########
        768.6 KiB/s
done
Bytes transferred = 54305 (d421 hex)

netcp@2000000 Waiting for SGMII auto negotiation to complete. done
BOOTP broadcast 1
DHCP client bound to address 84.88.51.193 (6 ms)
Using netcp@2000000 device
TFTP from server 84.88.51.137; our IP address is 84.88.51.193
Filename '/home/user/ti/tftpboot/skern-k2hk.bin'.
Load address: 0xc5f0000
Loading: #########
        1 MiB/s
done
Bytes transferred = 45056 (b000 hex)

netcp@2000000 Waiting for SGMII auto negotiation to complete. done
BOOTP broadcast 1
DHCP client bound to address 84.88.51.193 (5 ms)
Using netcp@2000000 device
TFTP from server 84.88.51.137; our IP address is 84.88.51.193
Filename '/home/user/ti/tftpboot/zImage.bin'.
Load address: 0x82000000
Loading: #################################################################
        #################################################################
        #################################################################
        #################################################################
        #################################################################
        #################################################################
        #################################################################
        #################################################################
        #################################################################
        #################################################################
        ###########################
        1.1 MiB/s
done
Bytes transferred = 3462344 (34d4c8 hex)
K2_BM_15.07-39-g035329c SoC:k2hk built:18:14:12, Oct  3 2016

## installed monitor, freq [200000000], status 0
Kernel image @ 0x82000000 [ 0x000000 - 0x34d4c8 ]
## Flattened Device Tree blob at 88000000
  Booting using the fdt blob at 0x88000000
  Loading Ramdisk to 8fff3000, end 8ffff20c ... OK
  Loading Device Tree to 8ffe2000, end 8fff2420 ... OK

Starting kernel ...
______________________________________________________________________________

It seems to me that uboot is not taking the new changes I did, may be I'm missing something.

Note that I'm using the USB cable that has SoC UART and MCU UART.

After freezing at Starting Kernel I rebooted the board and keep getting "No serial driver Found". Each time I need to access the uboot console I have to unplug and plug the USB from the server, otherwise the "No serial driver Found" keeps showing.

Thank you very much,
I rally appreciate it

Hello,
Thanks for you quick reply
I'm sorry, my mistake I mistyped the wrong dtb name in item 5) of previous post.
I just checked my configuration and I'm using the right .dtb but still same problem.
Thanks

Hi,

I've consulted the design team. Feedback will be posted directly here.

Best Regards,
Yordan

Hi,

Thanks for your quick reply.

I just tried what you have suggested, It didn't work :(  still showing "No serial driver found"

In fact when it finished the command "run burn_uboot_spi" the board automatically reseted.

After this it kept showing "No serial driver found", anyway I also tested the second part you suggested me and all the same.

Thanks

Carlos,

Do you happen to have the console logs for this run still? It is a bit odd that the EVM auto reseted after burning the uboot. Could you try a few more things by following the instructions in u-boot/board/ti/ks2_evm/README to "Load and Run U-Boot on keystone EVMs using CCS" and "SPI NOR Flash programming instructions". The first one should be able to bring up the u-boot to u-boot prompt, then boot kernel using boot=net as usual. The 2nd one is to program u-boot to NOR which is equivalnt to "get_uboot_net" and "burn_uboot", but using CCS.

You may need to build u-boot.bin. The instruction of building u-boot is in u-boot User's Guide, processors.wiki.ti.com/.../Linux_Core_U-Boot_User's_Guide

The symptoms are kind of mixed. It pauses at "starting kernel" could be related to bad kernel or boot monitor images, wrong boot address, etc. but u-boot keeps resetting usually I see when u-boot had an issue, or DDR3 memory related. If issue persists after using CCS, try to see if swapping out the DDR3 DIMM helps. and you are positive nothing has been changed. It was just power off last night and power on this morning.

Rex

Hi,
Here is the console log you asked me previously.
I will try what you suggested me and I will let you know.
Thanks

____________________________________________________________________
U-Boot 2016.05-g2f757e5b2c (Oct 03 2016 - 20:12:27 -0400)

CPU: 66AK2Hx SR2.0
I2C: ready
DRAM: DDR3A Speed will be configured for 1333 Operation.
Detected SO-DIMM [SQR-SD3T-2G1333SED]
DDR3 speed 1333
DRAM: 2 GiB (includes reported below)

Clear entire DDR3 memory to enable ECC
2 GiB
NAND: 512 MiB
Net:
Warning: netcp@2000000 using MAC address from ROM
eth0: netcp@2000000
Warning: netcp@slave-1 (eth1) using random MAC address - 2a:8a:bc:a4:68:24
, eth1: netcp@slave-1
Warning: netcp@slave-2 (eth2) using random MAC address - 3a:92:73:f2:14:70
, eth2: netcp@slave-2
Warning: netcp@slave-3 (eth3) using random MAC address - 7e:4e:b2:d3:b2:19
, eth3: netcp@slave-3
Hit any key to stop autoboot: 0
=> env default -f -a
## Resetting to default environment
=> setenv serverip 84.88.51.137
=> setenv tftp_root 84.88.51.137:/home/user/ti/tftpboot/prebuilt-images
=> run get_uboot_net

netcp@2000000 Waiting for SGMII auto negotiation to complete. done
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
DHCP client bound to address 84.88.51.193 (1028 ms)
Using netcp@2000000 device
TFTP from server 84.88.51.137; our IP address is 84.88.51.193
Filename '/home/user/ti/tftpboot/prebuilt-images/u-boot-spi-k2hk-evm.gph'.
Load address: 0x82000000
Loading: #################################################################
########################################
1.1 MiB/s
done
Bytes transferred = 537421 (8334d hex)
=> run burn_uboot_spi
data abort
pc : [<fff56cb2>] lr : [<fff56c85>]
reloc pc : [<0c029cb2>] lr : [<0c029c85>]
sp : feee4788 ip : 00000000 fp : 00000002
r10: fff80f59 r9 : feeecee0 r8 : 00000000
r7 : 00000000 r6 : feeed308 r5 : 00000000 r4 : feef3cc8
r3 : ffffffff r2 : 00000000 r1 : 00000000 r0 : 000003e8
Flags: nZcv IRQs off FIQs off Mode SVC_32
Resetting CPU ...

resetting ...

U-Boot SPL 2016.05-g2f757e5b2c (Oct 03 2016 - 20:12:27)
Trying to boot from SPI


U-Boot 2016.05-g2f757e5b2c (Oct 03 2016 - 20:12:27 -0400)

CPU: 66AK2Hx SR2.0
I2C: ready
DRAM: DDR3A Speed will be configured for 1333 Operation.
Detected SO-DIMM [SQR-SD3T-2G1333SED]
DDR3 speed 1333
DRAM: 2 GiB (includes reported below)

Clear entire DDR3 memory to enable ECC
2 GiB
No serial driver found
resetting ...

U-Boot SPL 2016.05-g2f757e5b2c (Oct 03 2016 - 20:12:27)
Trying to boot from SPI


U-Boot 2016.05-g2f757e5b2c (Oct 03 2016 - 20:12:27 -0400)

CPU: 66AK2Hx SR2.0
I2C: ready
DRAM: DDR3A Speed will be configured for 1333 Operation.
Detected SO-DIMM [SQR-SD3T-2G1333SED]
DDR3 speed 1333
DRAM: 2 GiB (includes reported below)

Clear entire DDR3 memory to enable ECC
2 GiB
No serial driver found
resetting ...

U-Boot SPL 2016.05-g2f757e5b2c (Oct 03 2016 - 20:12:27)
Trying to boot from SPI


U-Boot 2016.05-g2f757e5b2c (Oct 03 2016 - 20:12:27 -0400)

CPU: 66AK2Hx SR2.0
I2C: ready
DRAM: DDR3A Speed will be configured for 1333 Operation.
Detected SO-DIMM [SQR-SD3T-2G1333SED]
DDR3 speed 1333
DRAM: 2 GiB (includes reported below)

Clear entire DDR3 memory to enable ECC
2 GiB
No serial driver found
resetting ...
_____________________________________________________________

Carlos,

The logs reveal more useful information.The programming was never successful. I still want you to try with CCS to see how it goes, but when you have time, you can try very quickly doing step by step of the burn_uboot_spi command. That is after getting the uboot image from net, instead of "run burn_uboot_spi", issue the sf command one by one, and see which step it fails. Before you start issuing the sf command, do a "print ${filesize}" to be sure the printed size is the same as what was downloaded.

       burn_uboot_spi=sf probe; sf erase 0 0x90000; sf write ${loadaddr} 0 ${filesize}

I still want to ask one more time which you have not confirm either way. Has anything been changed before the issue happened? I need to know to diagnose the issue and find an appropriate way to approach it.  or it just happened overnight without anyone using it? Without knowing what had happened before issue happened, I can only guess and may not have a solution.

Rex

Hello Rex,
I will try what you said.

Regarding the situation before and after the issue I can say: Board was working perfectly one day, I run some experiments and went home. Next day I tried to access it through ssh without success so I had to reboot it and it was then when the issue started. so it happened overnight and nobody was using it.

Thanks a lot for your help

Hello Rex,
There you have the log.
It failed at "sf probe" but before the "print ${filesize}" showed error!

netcp@2000000 Waiting for SGMII auto negotiation to complete. done
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
DHCP client bound to address 84.88.51.193 (761 ms)
Using netcp@2000000 device
TFTP from server 84.88.51.137; our IP address is 84.88.51.193
Filename '/home/user/ti/tftpboot/prebuilt-images/u-boot-spi-k2hk-evm.gph'.
Load address: 0x82000000
Loading: #################################################################
        ########################################
        1.2 MiB/s
done
Bytes transferred = 537421 (8334d hex)
=> print ${filesize}
## Error: "8334d" not defined
=> printenv burn_uboot_spi
burn_uboot_spi=sf probe; sf erase 0 0x90000; sf write ${loadaddr} 0 ${filesize}
=> sf probe
data abort
pc : [<fff56cb2>]          lr : [<fff56c85>]
reloc pc : [<0c029cb2>]    lr : [<0c029c85>]
sp : feee48a8  ip : 00000000     fp : 00000002
r10: fff80f59  r9 : feeecee0     r8 : 00000000
r7 : 00000000  r6 : feeed308     r5 : 00000000  r4 : feef3988
r3 : ffffffff  r2 : 00000000     r1 : 00000000  r0 : 000003e8
Flags: nZcv  IRQs off  FIQs off  Mode SVC_32
Resetting CPU ...

resetting ...

U-Boot SPL 2016.05-g2f757e5b2c (Oct 03 2016 - 20:12:27)
Trying to boot from SPI


U-Boot 2016.05-g2f757e5b2c (Oct 03 2016 - 20:12:27 -0400)

CPU: 66AK2Hx SR2.0
I2C:   ready
DRAM:  DDR3A Speed will be configured for 1333 Operation.
Detected SO-DIMM [SQR-SD3T-2G1333SED]
DDR3 speed 1333
DRAM: 2 GiB (includes reported below)

Clear entire DDR3 memory to enable ECC
2 GiB
No serial driver found
resetting ...

U-Boot SPL 2016.05-g2f757e5b2c (Oct 03 2016 - 20:12:27)
Trying to boot from SPI


U-Boot 2016.05-g2f757e5b2c (Oct 03 2016 - 20:12:27 -0400)

CPU: 66AK2Hx SR2.0
I2C:   ready
DRAM:  DDR3A Speed will be configured for 1333 Operation.
Detected SO-DIMM [SQR-SD3T-2G1333SED]
DDR3 speed 1333
DRAM: 2 GiB (includes reported below)

Clear entire DDR3 memory to enable ECC
2 GiB
No serial driver found
resetting ...

That's my mistake. The command should be "print filesize". The failure of "sf probe" command means the NOR can't be accessed. You can try to see if kernel boots using CCS. I am not sure what state the u-boot is without knowing the history. If it is just because a bad u-boot image, you can recover it using CCS to restore it with pre-built image. If it is hardware being bad and you can still boot kernel using CCS, then probably that's will be the way it is.

Rex

Hello Rex,

Just to give you an update:

After hard trying because the connection test was not working, I managed to try the first example of the README file. At first attempt it failed when Connecting to the target:

In the second attempt I managed to run up to the "Free run" step, but I didn't get any output in the terminal console (where uboot was supposed to show up)

I could not keep trying because the connection is not working anymore through CCS (it stopped working suddenly), I tried rebooting the board, server and the test connection is not working either.

so I will keep trying and if you have any suggestions please let me know.

Thank you

Hi,
I managed to get the connection working again and tried but no success, I run up to "Free run" step and terminal console did not show anything. just like the last picture of previous post.
Thanks

Hi, Carlos,

The terminal console you meant is either the minicom or teraTerm, not the console window in CCS, correct?

Rex

Carlos,

In this case, I am not sure what the problem could be. I am out of idea.

Rex

Thank you very much for your help Rex,

I gave it a last try following your video to restore factory default images on keystone II platforms. (training.ti.com/restoring-factory-defaults-keystoneii-evm) This is the output when executing the last command:

Should I try performing the suggested firmware update? I have seen this warning message for this update:

IMPORTANT! Very old firmware releases such as the ones present in Keystone II EVMs (1.0.0.2) are known to have problems updating. In general they work well in Windows, therefore proceed with the update at your own risk as the JTAG debugger may be bricked and only recoverable by returning the board for repair.
##############################################################################################

__________________________________________________________________________________________________-
user@denso:~/ti/ti-processor-sdk-linux-k2hk-evm-03.01.00.06/bin/program_evm$ $DSS_SCRIPT_DIR/dss.sh program_evm.js evmk2h-le nor
board: evmk2h
endian: Little
emulation: XDS2xx emulator
binaries: /home/user/ti/ti-processor-sdk-linux-k2hk-evm-03.01.00.06/bin/program_evm/binaries/evmk2h/
ccxml: /home/user/ti/ti-processor-sdk-linux-k2hk-evm-03.01.00.06/bin/program_evm/configs/evmk2h/evmk2h-linuxhost.ccxml
SEVERE: IcePick_D_0: Error initializing emulator: (Error -1056 @ 0x0)
A firmware update is recommended for the XDS2xx debug probe.
For XDS200 probes, update the firmware using the xds2xx_conf utility found in the .../ccs_base/common/uscif/xds2xx directory of the CCS installation. View the ReadMe.txt file there for instructions.
For other XDS2xx variants, follow the manufacturer's instructions for updating the firmware.
(Emulation package 6.0.222.0)


SEVERE: Could not start server: DebugServer.1: IcePick_D_0: Error initializing emulator: (Error -1056 @ 0x0)
A firmware update is recommended for the XDS2xx debug probe.
For XDS200 probes, update the firmware using the xds2xx_conf utility found in the .../ccs_base/common/uscif/xds2xx directory of the CCS installation. View the ReadMe.txt file there for instructions.
For other XDS2xx variants, follow the manufacturer's instructions for updating the firmware.
(Emulation package 6.0.222.0)


org.mozilla.javascript.WrappedException: Wrapped com.ti.ccstudio.scripting.environment.ScriptingException: Could not start server: DebugServer.1: IcePick_D_0: Error initializing emulator: (Error -1056 @ 0x0)
A firmware update is recommended for the XDS2xx debug probe.
For XDS200 probes, update the firmware using the xds2xx_conf utility found in the .../ccs_base/common/uscif/xds2xx directory of the CCS installation. View the ReadMe.txt file there for instructions.
For other XDS2xx variants, follow the manufacturer's instructions for updating the firmware.
(Emulation package 6.0.222.0)

(program_evm.js#324)
at org.mozilla.javascript.Context.throwAsScriptRuntimeEx(Context.java:1693)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:160)
at org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:204)
at org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:76)
at org.mozilla.javascript.gen.c1._c0(program_evm.js:324)
at org.mozilla.javascript.gen.c1.call(program_evm.js)
at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:340)
at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:2758)
at org.mozilla.javascript.gen.c1.call(program_evm.js)
at org.mozilla.javascript.gen.c1.exec(program_evm.js)
at org.mozilla.javascript.tools.shell.Main.evaluateScript(Main.java:503)
at org.mozilla.javascript.tools.shell.Main.processFileSecure(Main.java:425)
at org.mozilla.javascript.tools.shell.Main.processFile(Main.java:391)
at org.mozilla.javascript.tools.shell.Main.processSource(Main.java:382)
at org.mozilla.javascript.tools.shell.Main.processFiles(Main.java:179)
at org.mozilla.javascript.tools.shell.Main$IProxy.run(Main.java:100)
at org.mozilla.javascript.Context.call(Context.java:528)
at org.mozilla.javascript.ContextFactory.call(ContextFactory.java:450)
at org.mozilla.javascript.tools.shell.Main.exec(Main.java:162)
at com.ti.ccstudio.apps.internal.scripting.RunScript$1.run(RunScript.java:88)
Caused by: com.ti.ccstudio.scripting.environment.ScriptingException: Could not start server: DebugServer.1: IcePick_D_0: Error initializing emulator: (Error -1056 @ 0x0)
A firmware update is recommended for the XDS2xx debug probe.
For XDS200 probes, update the firmware using the xds2xx_conf utility found in the .../ccs_base/common/uscif/xds2xx directory of the CCS installation. View the ReadMe.txt file there for instructions.
For other XDS2xx variants, follow the manufacturer's instructions for updating the firmware.
(Emulation package 6.0.222.0)


at com.ti.debug.engine.scripting.DebugServer$SessionFactory.<init>(DebugServer.java:164)
at com.ti.debug.engine.scripting.DebugServer.openSession(DebugServer.java:1327)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:145)
... 18 more
______________________________________________________________________________________________________________

Please let m know if you see anything else.
Thanks

Hi, Carlos,

That firmware update warning message shows up if using a newer version of CCS with an old rev EVM. It does no harm and the CCS should still be able to connect to the target. If it is annoying, you can follow the instruction as indicated in the ReadMe.txt to update the firmware.

Did you do a connection test before trying to connect to the target? If connection failed, a power cycle or restarting the CCS may help.

If connection test fails, make sure you follow the instruction to set them up.

Rex

Hi Rex,
I performed the firmware update and it allowed me to continue the steps to restore "nor" successfully but when it comes to "nand" it stops at (Start loading nand.bin) forever. I also tried formatting with "format-nand" command before executing "nand".

Here is the log.


~/ti/ti-processor-sdk-linux-k2hk-evm-03.01.00.06/bin/program_evm$ $DSS_SCRIPT_DIR/dss.sh program_evm.js evmk2h-le nand
board: evmk2h
endian: Little
emulation: XDS2xx emulator
binaries: /home/user/ti/ti-processor-sdk-linux-k2hk-evm-03.01.00.06/bin/program_evm/binaries/evmk2h/
ccxml: /home/user/ti/ti-processor-sdk-linux-k2hk-evm-03.01.00.06/bin/program_evm/configs/evmk2h/evmk2h-linuxhost.ccxml
C66xx_0: GEL Output:
Connecting Target...

C66xx_0: GEL Output: TCI6638K2K GEL file Ver is 1.29999995

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: 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: 0x0x07080400

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

Writer:/home/user/ti/ti-processor-sdk-linux-k2hk-evm-03.01.00.06/bin/program_evm/binaries/evmk2h/nandwriter_evmk2h.out

NAND:/home/user/ti/ti-processor-sdk-linux-k2hk-evm-03.01.00.06/bin/program_evm/binaries/evmk2h/nand.bin

Start loading nand.bin

Thanks

I just realized that it fails when formatting nand. It says at the end of the output log:

Formatting NAND device ... Initiated
NAND Writer Utility Version 01.00.00.05

.....................................................................................................Formatting all nand blocks - failed
Formatting NAND device ...Completed

Carlos,

You don't really need NAND and from your first post, you were not using NAND. With NOR programmed, you should be able to bring up U-boot. Please try using TI pre-built images in the PDK and see if you can boot up the EVM.

Rex

Thanks Rex,
I just tried again with the pre-built images but still the same error "No serial driver Found". Should we send the board to repair or check. Or any other suggestions?.
Thanks a lot

Carlos,

I am not sure about the process. You may want to contact TI local sales office. At the mean time, I'll check internally how that work.

Rex