• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 104 subscribers
  • Views 1136 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

"POST I2C eeprom read ... FAILED" while testing H265 Encoder Video Demo

Prathamesh Ghodke
Prodigy 120 points
Other Parts Discussed in Thread: 66AK2H12

Hi,

For H265 Encoder Demonstration testing when I wanted to use a K2h EVM, I am getting below error:

root@nikhil-OptiPlex-3010:/dev# picocom -b 115200 ttyUSB0
picocom v1.4

port is : ttyUSB0
flowcontrol : none
baudrate is : 115200
parity is : none
databits are : 8
escape is : C-a
noinit is : no
noreset is : no
nolock is : no
send_cmd is : ascii_xfr -s -v -l10
receive_cmd is : rz -vv

Terminal ready

U-Boot SPL 2013.01 (Feb 03 2015 - 00:25:05)
SF: Detected N25Q128A with page size 64 KiB, total 16 MiB


U-Boot 2013.01 (Feb 03 2015 - 00:25:05)

I2C: ready
Detected SO-DIMM [SQR-SD3T-2G1333SED]
DRAM: 2 GiB

Reseting entire DDR3 memory to 0 ...
DRAM: 1 GiB
NAND: 512 MiB
Net: K2HK_EMAC, K2HK_EMAC1, K2HK_EMAC2, K2HK_EMAC3


KS2_EVM POST Version 01.00.02.01
------------------------------------------
SOC Information
EFUSE MAC ID is: 00 17 ea f7 5c 1d
------------------------------------------

Power On Self Test
POST I2C eeprom read ... FAILED

Relative information in forum required format below:

MCSDK (Multicore Software Development Kit): mcsdk_3_00_04_18: for DSP build tools
Desktop Linux SDK: desktop-linux-sdk_01_00_00_07
MCSDK Video: mcsdk_video_2_1_0_8
U-Boot 2013.01 (Feb 03 2015 - 00:25:05)
EVM: 66AK2H12/06 Multicore DSP+ARM KeyStone II System-on-Chip (SoC)
Bootmode: ARM SPI Little Endian mode
Filesystem: Network File System
Linux Images Prebuilt: loading from TFTP
(TFTP Server, NFS Server, Computer System Ubuntu, K2H EVM all are on the same network, connected to the same switch, firewalls are off, even tried testing this issue with other test Computer).

After almost 1 year we are trying this board, because of testing need.
Kindly share your expert opinion, on how to solve this issue.

Regards,
Prathamesh Ghodke

  • 0
    TI__Guru* 81335 points
    Hi Prathamesh,

    What is the procedure followed to test the H265 Encoder Demonstration testing on K2H?

    My understanding is that MCSDK Video and Desktop Linux SDK has been validated on C6678 (Keystone I) platform not on Keystone II.

    Thank you.
  • 0 in reply to Raja
    Prodigy 120 points
    Hi Raja,

    With reference above error log, initially only in bootloader stage while POST we are getting this error.
    So we haven't yet reached to the stage of following H265 encoder testing steps like:
    - mpmcl load dsp
    - mpmcl run dsp
    - Exports path for MCSDK Video dir, desktop_linux_sdk, DSP image dir, Host image dir
    - Insert cmem modules
    - Then test video encoding H265 by running a shell script, with the input of raw yuv video and dumping output .h265

    So we are getting this error at very bringup stage only without entering anything, so please share your opinions.

    Regards,
    Prathamesh Ghodke
  • 0 in reply to Prathamesh Ghodke
    TI__Guru* 81335 points

    Hi Prathamesh,

    Thank you for the procedure.

    I think you are not running pre-built u-boot of MCSDK on EVM. The normal booting of K2H EVM will be like below,

    Thank you.

  • 0 in reply to Raja
    Prodigy 120 points
    Hi Raja,

    We are having the pre-built U-boot images of "mcsdk 3_1_3_6". But we don't know how to flash U-boot on k2H EVM. So we request you to kindly share us the procedure to flash U-boot on k2H EVM or direct us to any TI MCSDK User Guide for flashing U-boot.

    Thanks and Regards,
    Prathamesh
  • 0 in reply to Prathamesh Ghodke
    TI__Guru* 81335 points

    Hi,

    Please refer below wiki for flashing the images or MCSDK user guide,

    Program EVM:

    UG:

    Thank you.

  • 0 in reply to Raja
    Prodigy 100 points
    Hi Raja,

    - Tried to reflash the latest "u-boot-k2hk-evm.bin" of mcsdk_3_1_3_6, on K2H EVM by running below commands on U-boot prompt.

    1.setenv get_uboot_net tftp 0x87000000 /<path of latest uboot in tftpboot folder on filesystem>
    2.run uboot_get_net
    3.run burn_uboot
    4.reset

    - Latest Uboot got updated and was able to boot, but hangs at root prompt. Restarted the EVM and later was not even able to connect to EVM using serial port (attached log below). Ensured that the EVM is set in proper boot mode(ARM SPI mode 0010).



    root@nikhil-OptiPlex-3010:/dev#
    root@nikhil-OptiPlex-3010:/dev# picocom -b 115200 ttyUSB0
    picocom v1.4

    port is : ttyUSB0
    flowcontrol : none
    baudrate is : 115200
    parity is : none
    databits are : 8
    escape is : C-a
    noinit is : no
    noreset is : no
    nolock is : no
    send_cmd is : ascii_xfr -s -v -l10
    receive_cmd is : rz -vv

    Terminal ready


    Thanks and Regards,
    Prathamesh
  • 0 in reply to Nikhil Mantripragada
    TI__Guru 50170 points

    I posted the steps to flash u-boot in the other thread: https://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/p/433149/1572319#1572319.

    Please give it a try.

    Rex

  • 0 in reply to Rex Chang
    Prodigy 100 points
    Hi Rex,

    - Followed the steps suggested by you to flash the Latest U-boot and was able to remove earlier error "POST I2C eeprom read ... FAILED" . But as it continues it gives "Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid" error.

    - As suggested by Stalin checked bootargs variable is set for NFS or not. So ensured bootargs are proper(setenv bootargs 'earlyprintk debug console=ttyS0,115200n8 ip=dhcp rootwait=1 root=/dev/nfs nfsroot=10.100.1.94:/usr/local/ks2_fs,v3,tcp rw').

    - After Rebooting the EVM again it hangs while connecting to terminal itself(It dosen't show the U-boot prompt).

    - Kindly share your expert opinion, on how to solve this issue.

    Thanks and Regards,
    Nikhil
  • 0 in reply to Nikhil Mantripragada
    TI__Guru** 116100 points

    Hi Nikhil,

    We were glad that you able to solve the problem.
    You can followup the u-boot update problem in the following thread.

    e2e.ti.com/.../433149

    I'm closing this thread since you solved the "POST I2C eeprom read ... FAILED" problem.

    Thanks for your understanding.