• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 1520 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AM572x EEPROM

suhas_m
Expert 1400 points

Other Parts Discussed in Thread: AM5728

Hi,

We have a custom board based on am5728 gpevm, we also have eeprom similar to evm on board, how do we write the board name to the eeprom frm uboot, our uboot recognizes our brd as UKNOWN(beagle-x15?), So what  other parameters are  stored in e eeprom other than board name?  Is the uboot doing the pin mus and selecting the dts based on this board name? For some reason we r not getting pclk , hsync , vsync on vout1 port of our brd, does our brd pin mux is configured for bb-x15 ? Which dnt have an lcd?

Regards suhas

  • 0
    TI__Guru**** 161600 points

    Hi,

    suhas_m said:
    So what  other parameters are  stored in e eeprom other than board name? Is the uboot doing the pin mus and selecting the dts based on this board name?

    Have a look at ti_am_eeprom structutre in board/ti/common/include/board_detect.h: 
      

    /**
    * struct ti_am_eeprom - This structure holds data read in from the
    * AM335x, AM437x, AM57xx TI EVM EEPROMs.
    * @header: This holds the magic number
    * @name: The name of the board
    * @version: Board revision
    * @serial: Board serial number
    * @config: Reserved
    * @mac_addr: Any MAC addresses written in the EEPROM
    *
    * The data is this structure is read from the EEPROM on the board.
    * It is used for board detection which is based on name. It is used
    * to configure specific TI boards. This allows booting of multiple
    * TI boards with a single MLO and u-boot.
    */

    suhas_m said:
    For some reason we r not getting pclk , hsync , vsync on vout1 port of our brd, does our brd pin mux is configured for bb-x15 ? Which dnt have an lcd?

    You could check that by tracking what is happening in board/ti/am57xx/board.c. If this is the case, then you could add the settings for pclk, hsync, vsync under the bb-x15 part of the board init. 

    Best Regards, 
    Yordan

  • 0 in reply to Yordan Kovachev
    Expert 1400 points
    Thnx for the timely reply, im not able to write to the eeprom on our brd, its interfaced to processor on i2c bus 0, i have pulled down the writecprotect, our eeprom addr is 50, pulled down all addr bits of eeprom, in uboot i give the command U-Boot# i2c dev 1
    Setting bus to 1
    U-Boot# i2c dev 0
    Setting bus to 0
    U-Boot# i2c md 0x50 0 0x10
    0000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
    U-Boot# i2c mm 0x50 0
    00000000: ff ? AA
    00000001: ff ? BB
    00000002: ff ? CC
    00000003: ff ? DD
    00000004: ff ? U-Boot# <INTERRUPT>
    U-Boot# <INTERRUPT>
    U-Boot#
    U-Boot#
    U-Boot# i2c md 0x50 0 0x10
    0000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
    U-Boot#

    U-Boot# i2c mw 0x50 0 0x10 0xAA
    U-Boot# i2c md 0x50 0 0x10
    0000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
    U-Boot# i2c md 0x50 0 0x10
    0000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................


    Y this happening, is the uboot buggy? How do we write frm linux user space then?
  • 0 in reply to suhas_m
    TI__Guru**** 161600 points
    Do you have the i2c part of u-boot (board/ti/am57xx/board.c) code updated?
    What is the output of i2c probe?

    Best Regards,
    Yordan