HATs and other add-ons • Re: Why is there no M.2 HAT+ overlay?

Code:

pi@raspberrypi:~/utils/eeptools $ sudo dtoverlay i2c-gpio i2c_gpio_sda=0 i2c_gpio_scl=1 bus=9pi@raspberrypi:~/utils/eeptools $ i2cdetect -y 9     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f00:                         -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- --                         pi@raspberrypi:~/utils/eeptools $ sudo ./eepflash.sh -r  -t=24c32 -a=51 -f=eeprom.eepThis will attempt to talk to an eeprom at i2c address 0x51. Make sure there is an eeprom at this address.This script comes with ABSOLUTELY no warranty. Continue only if you know what you are doing.Do you wish to continue? (yes/no): yesReading...Closing EEPROM Device.Done.pi@raspberrypi:~/utils/eeptools $ eepdump eeprom.eep hat_eeprom_dump.txtReading atom 0 (type = 0x0001 (vendor type), length = 50 bytes)...WARNING: Dump finished before EOFWARNING: EOF does not match length specified in headerWARNING: 4096 bytes of file not processedDone.

Code:

# ---------- Dump generated by eepdump handling format version 0x02 ----------## --Header--# signature=0x69502d52# version=0x02# reserved=0# numatoms=1# eeplen=70# ----------# Start of atom #0 of type 0x0001 and length 50# Vendor infoproduct_uuid 833ad001-a8e0-4779-8e6f-3c4ee6676e9cproduct_id 0x0000product_ver 0x0003vendor "Raspberry Pi"   # length=12product "M.2 HAT+ M Key"   # length=14# End of atom. CRC16=0x1a90