If you have a Pi M.2 HAT+ and if you really want to see for yourself what the EEPROM contains and whether it specifies a DT overlay, you can just dump and decode the contents yourself:
1. Make sure i2c0 is enabled in config.txt.
2. Build the HAT EEPROM tools.
3. eepflash.sh --read --device=0 --address=0x50 -t=24c32 -f hat_eeprom_dump.eep (note address might instead be 0x51; not sure if they're specifying it as a stackable HAT)
4. eepdump hat_eeprom_dump.eep hat_eeprom_dump.txt
5. Look at the .txt file contents and see if it contains a "dt_blob" entry.
I would be willing to bet good money it does not.![:P]( "Razz")
You can decide for yourself whether it meets HAT+ specification.
1. Make sure i2c0 is enabled in config.txt.
2. Build the HAT EEPROM tools.
3. eepflash.sh --read --device=0 --address=0x50 -t=24c32 -f hat_eeprom_dump.eep (note address might instead be 0x51; not sure if they're specifying it as a stackable HAT)
4. eepdump hat_eeprom_dump.eep hat_eeprom_dump.txt
5. Look at the .txt file contents and see if it contains a "dt_blob" entry.
I would be willing to bet good money it does not.
You can decide for yourself whether it meets HAT+ specification.
Statistics: Posted by HwAoRrDk — Sun May 26, 2024 2:30 am