HAT EEPROM - Raspberry Pi Forums


hello guys,

i´m testing little bit hat eeprom raspberry pi. in case have ordered 24c32 eeproms , connect 1 of eedata , eeclock pins of raspberry pi v2.
after build small device tree (just testing):

code: select all

/dts-v1/; /plugin/;  / {     compatible = "brcm,bcm2708";      fragment@0     {         target = <&i2c1>;         __overlay__        {          rtc@68           {             status = "rtc";          };         };     }; };
compile it:

code: select all

dtc -@ -i dts -o dtb -o /programme/rtc_hat/rtc.dtb /programme/rtc_hat/rtc.dts
after compiling have created "rtc.txt" file:

code: select all

######################################################################## # eeprom settings text file # # edit file particular board , run through eepmake tool, # use eepflash tool write attached hat id eeprom  # # tools available: #  eepmake   parses eeprom text file , creates binary .eep file #  eepdump   dumps binary .eep file human readable text (for debug) #  eepflash  write or read .eep binary image to/from hat eeprom # ########################################################################  ######################################################################## # vendor info  # 128 bit uuid. if left @ 0 eepmake tool auto-generate # rfc 4122 compliant uuid product_uuid 00000000-0000-0000-0000-000000000000  # 16 bit product id product_id 0x0000  # 16 bit product version product_ver 0x0000  # ascii vendor string  (max 255 characters) vendor "kampis-elektroecke  # ascii product string (max 255 characters) product "rtc hat"  ######################################################################## # gpio bank settings, set nonzero change default. # note these setting can set per bank, uncommenting of # these force bank use custom setting.  # drive strength, 0=default, 1-8=2,4,6,8,10,12,14,16ma, 9-15=reserved gpio_drive 0  # 0=default, 1=slew rate limiting, 2=no slew limiting, 3=reserved gpio_slew 0  # 0=default, 1=hysteresis disabled, 2=hysteresis enabled, 3=reserved gpio_hysteresis 0  # if board back-powers pi via 5v gpio header pins: # 0 = board not back-power # 1 = board back-powers , can supply pi minimum of 1.3a # 2 = board back-powers , can supply pi minimum of 2a # 3 = reserved # if back_power=2 usb high current mode automatically  # enabled on pi back_power 0  ######################################################################## # gpio pins, uncomment gpios used on board # options function: input, output, alt0-alt5 # options pull: default, up, down, none # nb gpio0 , gpio1 reserved id eeprom cannot set  #         gpio  function  pull #         ----  --------  ---- #setgpio  2     input     default #setgpio  3     input     default #setgpio  4     input     default #setgpio  5     input     default #setgpio  6     input     default #setgpio  7     input     default #setgpio  8     input     default #setgpio  9     input     default #setgpio  10    input     default #setgpio  11    input     default #setgpio  12    input     default #setgpio  13    input     default #setgpio  14    input     default #setgpio  15    input     default #setgpio  16    input     default #setgpio  17    input     default #setgpio  18    input     default #setgpio  19    input     default #setgpio  20    input     default #setgpio  21    input     default #setgpio  22    input     default #setgpio  23    input     default #setgpio  24    input     default #setgpio  25    input     default #setgpio  26    input     default #setgpio  27    input     default
flashed both files eeprom, using official software git:

code: select all

/programme/eepmake /programme/rtc_hat/rtc.txt /programme/rtc_hat/rtc.dtb /programme/rtc_hat/rtc.eep /programme/eepflash.sh -w -f=/programme/rtc_hat/rtc.eep -t=24c32 
after activate i²c in /boot/config.txt

code: select all

dtparam=i2c_arm=on dtparam=i2c_vc=on
in last step reboot raspberry pi.
after reboot should found "rtc" device unter i2c1 think, don´t see when use "ls /proc/device-tree/soc/i2c@7e804000/"
wrong , why doesn´t load overlay eeprom?

thank help!

mmmm, playing right hats :)

dumb question: did try dtd file before?

make dtd overlay, , parse kernel, using dtoverlay=myname
@ boot, kernel dtd file, under /boot/overlays/, called myname-overlay.dtb

can check if it's faulty dt overlay or not.

hope helps


raspberrypi



Comments

Popular posts from this blog

How do I add a forum to my site? - Joomla! Forum - community, help and support

VIDIOC_S_FMT error 16, Device or resource busy - Raspberry Pi Forums

using a laptop skeleton to build a pi laptop - Raspberry Pi Forums